diff mbox

btrfs-progs: doc: fix typo of some documents

Message ID 201601280800.AA00001@WIN-5MHF4RKU941.jp.fujitsu.com (mailing list archive)
State Accepted
Headers show

Commit Message

Tsutomu Itoh Jan. 28, 2016, 8 a.m. UTC 
Some typos are corrected.

Signed-off-by: Tsutomu Itoh <t-itoh@jp.fujitsu.com>
---
 Documentation/btrfs-check.asciidoc | 4 ++--
 Documentation/mkfs.btrfs.asciidoc  | 2 +-
 2 files changed, 3 insertions(+), 3 deletions(-)

Comments

David Sterba Jan. 28, 2016, 11:42 a.m. UTC | #1 
On Thu, Jan 28, 2016 at 05:00:24PM +0900, Tsutomu Itoh wrote:
> Some typos are corrected.
> 
> Signed-off-by: Tsutomu Itoh <t-itoh@jp.fujitsu.com>

Applied, thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
diff mbox

Patch

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.
 +