Some typos are corrected. Signed-off-by: Tsutomu Itoh <t-itoh@xxxxxxxxxxxxxx> --- Documentation/btrfs-check.asciidoc | 4 ++-- Documentation/mkfs.btrfs.asciidoc | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/Documentation/btrfs-check.asciidoc b/Documentation/btrfs-check.asciidoc index a929862..327a45d 100644 --- a/Documentation/btrfs-check.asciidoc +++ b/Documentation/btrfs-check.asciidoc @@ -24,7 +24,7 @@ OPTIONS ------- -s|--super <superblock>:: use <superblock>th superblock copy, valid values are 0 up to 2 if the -respective superblock offset is within the fileystem +respective superblock offset is within the filesystem --repair:: try to repair the filesystem --init-csum-tree:: @@ -32,7 +32,7 @@ create a new CRC tree and recalculate all checksums --init-extent-tree:: create a new extent tree --check-data-csum:: -verify checkums of data blocks +verify checksums of data blocks -p|--progress:: indicate progress at various checking phases --qgroup-report:: diff --git a/Documentation/mkfs.btrfs.asciidoc b/Documentation/mkfs.btrfs.asciidoc index 0b145c7..82bb756 100644 --- a/Documentation/mkfs.btrfs.asciidoc +++ b/Documentation/mkfs.btrfs.asciidoc @@ -78,7 +78,7 @@ where the space is reserved for the other block group type, is not available for allocation and can lead to ENOSPC state. + The recommended size for the mixed mode is for filesystems less than 1GiB. The -soft recommendation is to use it for filesystems smaller than 5GiB. Thie mixed +soft recommendation is to use it for filesystems smaller than 5GiB. The mixed mode may lead to degraded performance on larger filesystems, but is otherwise usable, even on multiple devices. + -- 2.6.4 -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
