diff options
| author | Joey Sabey <GameFreak7744@gmail.com> | 2017-02-22 09:04:19 +0000 |
|---|---|---|
| committer | David Sterba <dsterba@suse.com> | 2017-03-08 13:00:48 +0100 |
| commit | 9a4b0e512ecaf61cde280278e948d24ddeb4ae37 (patch) | |
| tree | da238ad5490295d9de79d87a71e918a9915c338b /Documentation | |
| parent | 2b92a224c7713465150d3e3f57246dc054108284 (diff) | |
btrfs-progs: docs: fix typo in btrfs-quota
reinstall ation -> reinstallation
Signed-off-by: David Sterba <dsterba@suse.com>
Diffstat (limited to 'Documentation')
| -rw-r--r-- | Documentation/btrfs-quota.asciidoc | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/btrfs-quota.asciidoc b/Documentation/btrfs-quota.asciidoc index 77d4c685..06d49b1a 100644 --- a/Documentation/btrfs-quota.asciidoc +++ b/Documentation/btrfs-quota.asciidoc @@ -52,7 +52,7 @@ On the other hand, the traditional approach has only a poor solution to restrict directories. At installation time, the harddisk can be partitioned so that every directory (eg. /usr, /var/, ...) that needs a limit gets its own partition. The obvious -problem is, that those limits cannot be changed without a reinstall ation. The +problem is, that those limits cannot be changed without a reinstallation. The btrfs subvolume feature builds a bridge. Subvolumes correspond in many ways to partitions, as every subvolume looks like its own filesystem. With subvolume quota, it is now possible to restrict each subvolume like a partition, but keep |