Fix a few typos in manpages. Reported-by: Branislav Náter <bnater@xxxxxxxxxx> Signed-off-by: Eric Sandeen <sandeen@xxxxxxxxxx> --- diff --git a/debugfs/debugfs.8.in b/debugfs/debugfs.8.in index 44d4640..41c73fd 100644 --- a/debugfs/debugfs.8.in +++ b/debugfs/debugfs.8.in @@ -214,7 +214,7 @@ to only display the leaf nodes in the extent tree. .IP (Please note that the length and range of blocks for the last extent in an interior node is an estimate by the extents library functions, and is -not stored in file esystem data structures. Hence, the values displayed +not stored in filesystem data structures. Hence, the values displayed may not necessarily by accurate and does not indicate a problem or corruption in the file system.) .TP diff --git a/e2fsck/e2fsck.conf.5.in b/e2fsck/e2fsck.conf.5.in index e09cd6d..2a600d0 100644 --- a/e2fsck/e2fsck.conf.5.in +++ b/e2fsck/e2fsck.conf.5.in @@ -112,14 +112,14 @@ boolean value of false. This setting defaults to true. .I broken_system_clock The .BR e2fsck (8) -program has some hueristics that assume that the system clock is +program has some heuristics that assume that the system clock is correct. In addition, many system programs make similar assumptions. For example, the UUID library depends on time not going backwards in order for it to be able to make its guarantees about issuing universally unique ID's. Systems with broken system clocks, are well, broken. However, broken system clocks, particularly in embedded systems, do -exist. E2fsck will attempt to use hueristics to determine if the time -can no tbe trusted; and to skip time-based checks if this is true. If +exist. E2fsck will attempt to use heuristics to determine if the time +can not be trusted; and to skip time-based checks if this is true. If this boolean is set to true, then e2fsck will always assume that the system clock can not be trusted. .TP diff --git a/misc/mke2fs.conf.5.in b/misc/mke2fs.conf.5.in index 2e8b585..1834654 100644 --- a/misc/mke2fs.conf.5.in +++ b/misc/mke2fs.conf.5.in @@ -363,10 +363,10 @@ and .IR tea . .TP .I flex_bg_size -This relation specifies the number of block goups that will be packed +This relation specifies the number of block groups that will be packed together to create one large virtual block group on an ext4 filesystem. This improves meta-data locality and performance on meta-data heavy -workloads. The number of goups must be a power of 2 and may only be +workloads. The number of groups must be a power of 2 and may only be specified if the flex_bg filesystem feature is enabled. .I options This relation specifies additional extended options which should be -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
