summaryrefslogtreecommitdiff
path: root/e2fsck
diff options
context:
space:
mode:
authorEric Sandeen <sandeen@redhat.com>2011-03-10 10:09:35 -0600
committerTheodore Ts'o <tytso@mit.edu>2011-03-18 15:03:15 -0400
commitd4a9330212280e0ff1204a4052f09f18691ed1cf (patch)
tree82290997501b1c29016c86cde8e0f0eca2637c5c /e2fsck
parent4df1618250349dbe71f9474c42d52d7d03cc68a0 (diff)
downloade2fsprogs-d4a9330212280e0ff1204a4052f09f18691ed1cf.tar.gz
e2fsprogs: man page typo fixes
Fix a few typos in manpages. Reported-by: Branislav NĂ¡ter <bnater@redhat.com> Signed-off-by: Eric Sandeen <sandeen@redhat.com> Signed-off-by: Theodore Ts'o <tytso@mit.edu>
Diffstat (limited to 'e2fsck')
-rw-r--r--e2fsck/e2fsck.conf.5.in6
1 files changed, 3 insertions, 3 deletions
diff --git a/e2fsck/e2fsck.conf.5.in b/e2fsck/e2fsck.conf.5.in
index e09cd6d7..2a600d0e 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