btrfs-progs: docs: fix more typos and spelling errors

With help of ispell.

Signed-off-by: David Sterba <dsterba@suse.com>

Documentation/btrfs-balance.asciidoc

@@ -11,7 +11,7 @@ SYNOPSIS
 
 DESCRIPTION
 -----------
-The primary purpose of the balance feature is to spread block groups accross
+The primary purpose of the balance feature is to spread block groups across
 all devices so they match constraints defined by the respective profiles. See
 `mkfs.btrfs`(8) section 'PROFILES' for more details.
 The scope of the balancing process can be further tuned by use of filters that
@@ -147,7 +147,7 @@ only the single value format.  The range minimum and maximum are inclusive.
 
 *stripes=<range>*::
 Balance only block groups which have the given number of stripes. The parameter
-is a range specified as 'start..end'. Makes sense fo block group profiles that
+is a range specified as 'start..end'. Makes sense for block group profiles that
 utilize striping, ie. RAID0/10/5/6.  The range minimum and maximum are
 inclusive.
 
@@ -192,7 +192,7 @@ command:
 
 An example of a filter that does not require workspace is 'usage=0'. This will
 scan through all unused block groups of a given type and will reclaim the
-space. Ater that it might be possible to run other filters.
+space. After that it might be possible to run other filters.
 
 **CONVERSIONS ON MULTIPLE DEVICES**
 

Documentation/btrfs-convert.asciidoc

@@ -75,7 +75,7 @@ consumption and may help to convert a filesystem with low free space
 -N|--nodesize <SIZE>::
 set filesystem nodesize, the tree block size in which btrfs stores its metadata.
 The default value is 16KB (16384) or the page size, whichever is bigger.
-Must be a multiple of the sectorsize, but not larger than 65536. Se
+Must be a multiple of the sectorsize, but not larger than 65536. See
 `mkfs.btrfs`(8) for more details.
 -r|--rollback::
 rollback to the original ext2/3/4 filesystem if possible

Documentation/btrfs-filesystem.asciidoc

@@ -79,11 +79,11 @@ show sizes in TiB, or TB with --si
 If conflicting options are passed, the last one takes precedence.
 
 *defragment* [options] <file>|<dir> [<file>|<dir>...]::
-Defragment file data on a mounted filesytem.
+Defragment file data on a mounted filesystem.
 +
 If '-r' is passed, files in dir will be defragmented recursively.
 The start position and the number of bytes to defragment can be specified by
-start and len using '-s' and '-l' options below.
+start and length using '-s' and '-l' options below.
 Extents bigger than value given by '-t' will be skipped, otherwise this value
 is used as a target extent size, but is only advisory and may not be reached
 if the free space is too fragmented.

Documentation/btrfs-man5.asciidoc

@@ -293,7 +293,7 @@ cache consumes some resources.
 +
 Options to control SSD allocation schemes.  By default, BTRFS will
 enable or disable SSD allocation heuristics depending on whether a
-rotational or nonrotational disk is in use.  The 'ssd' and 'nossd' options
+rotational or non-rotational disk is in use.  The 'ssd' and 'nossd' options
 can override this autodetection.
 +
 The 'ssd_spread' mount option attempts to allocate into bigger and aligned
@@ -337,7 +337,7 @@ such syncs, the pending tree log operations are replayed during mount.
 WARNING: currently, the tree log is replayed even with a read-only mount!
 +
 The tree log could contain new files/directories, these would not exist on
-a mounted filesystm if the log is not replayed.
+a mounted filesystem if the log is not replayed.
 
 *user_subvol_rm_allowed*::
 (default: off)

Documentation/btrfs-qgroup.asciidoc

@@ -25,7 +25,7 @@ Quota groups or qgroup in btrfs make a tree hierarchy, the leaf qgroups are
 attached to subvolumes. The size limits are set per qgroup and apply when any
 limit is reached in tree that contains a given subvolume.
 
-The limit sare separated between shared and exclusive and reflect the extent
+The limits are separated between shared and exclusive and reflect the extent
 ownership. For example a fresh snapshot shares almost all the blocks with the
 original subvolume, new writes to either subvolume will raise towards the
 exclusive limit.

Documentation/btrfs-replace.asciidoc

@@ -61,7 +61,7 @@ Print status and progress information of a running device replace operation.
 +
 -1::::
 print once instead of print continuously until the replace
-operation finishes (or is canceled)
+operation finishes (or is cancelled)
 
 EXIT STATUS
 -----------

Documentation/btrfs-scrub.asciidoc

@@ -25,7 +25,7 @@ If a <device> is given, the corresponding filesystem is found and
 scrub cancel behaves as if it was called on that filesystem.
 
 *resume* [-BdqrR] [-c <ioprio_class> -n <ioprio_classdata>] <path>|<device>::
-Resume a canceled or interrupted scrub cycle on the filesystem identified by
+Resume a cancelled or interrupted scrub cycle on the filesystem identified by
 <path> or on a given <device>.
 +
 Does not start a new scrub if the last scrub finished successfully.
@@ -64,13 +64,13 @@ Set IO priority class (see `ionice`(1) manpage).
 Set IO priority classdata (see `ionice`(1) manpage).
 -f::::
 Force starting new scrub even if a scrub is already running.
-This is useful when scrub stat record file is damaged.
+This is useful when scrub status record file is damaged.
 
 *status* [-d] <path>|<device>::
 Show status of a running scrub for the filesystem identified by <path> or
 for the specified <device>.
 +
-If no scrub is running, show statistics of the last finished or canceled scrub
+If no scrub is running, show statistics of the last finished or cancelled scrub
 for that filesystem or device.
 +
 `Options`

Documentation/btrfs-subvolume.asciidoc

@@ -73,7 +73,7 @@ stored on the media.
 wait for transaction commit at the end of the operation
 +
 -C|--commit-each::::
-wait for transaction commit after delet each subvolume
+wait for transaction commit after deleting each subvolume
 
 *find-new* <subvolume> <last_gen>::
 List the recently modified files in a subvolume, after <last_gen> ID.

Documentation/btrfstune.asciidoc

@@ -57,7 +57,7 @@ If a previously-seeding device is changed, all filesystems that used that
 device will become unmountable. Setting the seeding flag back will not fix
 that. +
 A valid usecase is 'seeding device as a base image'. Clear the seeding
-flag, update the filesystem and make it seeding again, provided that it's ok
+flag, update the filesystem and make it seeding again, provided that it's OK
 to throw away all filesystems built on top of the previous base.
 
 EXIT STATUS