summaryrefslogtreecommitdiffstats
path: root/sys-utils
diff options
context:
space:
mode:
authorJakub Wilk2018-08-16 11:08:42 +0200
committerJakub Wilk2018-08-16 11:09:15 +0200
commitb9c3b903fe4a704974755b4b3ac3ac75dc8bf0e7 (patch)
treeab5169829477481c4eff474ca99d5c649ed2e98f /sys-utils
parentsu: add --whitelist-environment (diff)
downloadkernel-qcow2-util-linux-b9c3b903fe4a704974755b4b3ac3ac75dc8bf0e7.tar.gz
kernel-qcow2-util-linux-b9c3b903fe4a704974755b4b3ac3ac75dc8bf0e7.tar.xz
kernel-qcow2-util-linux-b9c3b903fe4a704974755b4b3ac3ac75dc8bf0e7.zip
Fix man page typos
Signed-off-by: Jakub Wilk <jwilk@jwilk.net>
Diffstat (limited to 'sys-utils')
-rw-r--r--sys-utils/choom.12
-rw-r--r--sys-utils/mount.86
-rw-r--r--sys-utils/readprofile.84
-rw-r--r--sys-utils/setarch.82
-rw-r--r--sys-utils/swapon.82
-rw-r--r--sys-utils/umount.82
6 files changed, 9 insertions, 9 deletions
diff --git a/sys-utils/choom.1 b/sys-utils/choom.1
index 13e4fc247..2b844cbe2 100644
--- a/sys-utils/choom.1
+++ b/sys-utils/choom.1
@@ -63,7 +63,7 @@ always preferring a certain task or completely disabling it. The lowest
possible value, -1000, is equivalent to disabling oom killing entirely for that
task since it will always report a badness score of 0.
-Setting a adjust score value of +500, for example, is roughly equivalent to
+Setting an adjust score value of +500, for example, is roughly equivalent to
allowing the remainder of tasks sharing the same system, cpuset, mempolicy, or
memory controller resources to use at least 50% more memory. A value of -500,
on the other hand, would be roughly equivalent to discounting 50% of the task's
diff --git a/sys-utils/mount.8 b/sys-utils/mount.8
index 1a42a36e3..8ee0a03c5 100644
--- a/sys-utils/mount.8
+++ b/sys-utils/mount.8
@@ -1400,7 +1400,7 @@ independent of indices created in other instances of devpts.
All mounts of devpts without this
.B newinstance
-option share the same set of pty indices (i.e legacy mode).
+option share the same set of pty indices (i.e. legacy mode).
Each mount of devpts with the
.B newinstance
option has a private set of pty indices.
@@ -1503,7 +1503,7 @@ normal check is too inflexible. With this option you can relax it.
.RE
.TP
.BI check= value
-Three different levels of pickyness can be chosen:
+Three different levels of pickiness can be chosen:
.RS
.TP
.BR r [ elaxed ]
@@ -1714,7 +1714,7 @@ filesystem.)
Normal
.I iso9660
-filenames appear in a 8.3 format (i.e., DOS-like restrictions on filename
+filenames appear in an 8.3 format (i.e., DOS-like restrictions on filename
length), and in addition all characters are in upper case. Also there is
no field for file ownership, protection, number of links, provision for
block/character devices, etc.
diff --git a/sys-utils/readprofile.8 b/sys-utils/readprofile.8
index 9686380e0..a37aa0a91 100644
--- a/sys-utils/readprofile.8
+++ b/sys-utils/readprofile.8
@@ -111,7 +111,7 @@ Look at all the kernel information, with ram addresses:
readprofile -av | less
.fi
-Browse a `freezed' profile buffer for a non current kernel:
+Browse a `frozen' profile buffer for a non current kernel:
.nf
readprofile -p ~/profile.freeze -m /zImage.map.gz
@@ -123,7 +123,7 @@ Request profiling at 2kHz per CPU, and reset the profiling buffer:
.SH BUGS
.LP
.B readprofile
-only works with an 1.3.x or newer kernel, because
+only works with a 1.3.x or newer kernel, because
.I /proc/profile
changed in the step from 1.2 to 1.3
.LP
diff --git a/sys-utils/setarch.8 b/sys-utils/setarch.8
index d0fd5b945..efa3d5088 100644
--- a/sys-utils/setarch.8
+++ b/sys-utils/setarch.8
@@ -27,7 +27,7 @@ The default \fIprogram\fR is \fB/bin/sh\fR.
.PP
Since version 2.33 the
.I arch
-comnand line argument is optional and
+command line argument is optional and
.B setarch
may be used to change personality flags (ADDR_LIMIT_*, SHORT_INODE, etc) without
modification of the execution domain.
diff --git a/sys-utils/swapon.8 b/sys-utils/swapon.8
index 8398f1b35..510a15fd0 100644
--- a/sys-utils/swapon.8
+++ b/sys-utils/swapon.8
@@ -222,7 +222,7 @@ Swap over \fBNFS\fR may not work.
.PP
.B swapon
automatically detects and rewrites a swap space signature with old software
-suspend data (e.g S1SUSPEND, S2SUSPEND, ...). The problem is that if we don't
+suspend data (e.g. S1SUSPEND, S2SUSPEND, ...). The problem is that if we don't
do it, then we get data corruption the next time an attempt at unsuspending is
made.
diff --git a/sys-utils/umount.8 b/sys-utils/umount.8
index eb2e65dd7..f94d2f41f 100644
--- a/sys-utils/umount.8
+++ b/sys-utils/umount.8
@@ -56,7 +56,7 @@ offending process could even be
.B umount
itself - it opens libc, and libc in its turn may open for example locale
files. A lazy unmount avoids this problem, but it may introduce another
-issues. See \fB\-\-lazy\fR description bellow.
+issues. See \fB\-\-lazy\fR description below.
.SH OPTIONS
.TP
.BR \-a , " \-\-all"