From: Sami Kerola <kerolasa@iki.fi>
To: util-linux@vger.kernel.org
Cc: kerolasa@iki.fi
Subject: [PATCH 11/14] docs: remove repeated words [checkmans.sh]
Date: Mon, 8 Apr 2013 20:32:56 +0100 [thread overview]
Message-ID: <1365449579-13238-12-git-send-email-kerolasa@iki.fi> (raw)
In-Reply-To: <1365449579-13238-1-git-send-email-kerolasa@iki.fi>
Signed-off-by: Sami Kerola <kerolasa@iki.fi>
---
disk-utils/elvtune.8 | 2 +-
libuuid/man/uuid_generate.3 | 2 +-
sys-utils/cytune.8 | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/disk-utils/elvtune.8 b/disk-utils/elvtune.8
index f71b1d4..0554269 100644
--- a/disk-utils/elvtune.8
+++ b/disk-utils/elvtune.8
@@ -45,7 +45,7 @@ pending in the queue.
Display help text and exit.
.TP
.BI -v
-Display version version information and exit.
+Display version information and exit.
.SH NOTE
Actually, the only fields tunable are those relative
to the IO scheduler. It's not possible to select
diff --git a/libuuid/man/uuid_generate.3 b/libuuid/man/uuid_generate.3
index 07ad94c..3bb789c 100644
--- a/libuuid/man/uuid_generate.3
+++ b/libuuid/man/uuid_generate.3
@@ -79,7 +79,7 @@ by concurrently running processes, the uuid library uses global
clock state counter (if the process has permissions to gain exclusive access
to this file) and/or the
.B uuidd
-daemon, if it is running already or can be be spawned by the process (if
+daemon, if it is running already or can be spawned by the process (if
installed and the process has enough permissions to run it). If neither of
these two synchronization mechanisms can be used, it is theoretically possible
that two concurrently running processes obtain the same UUID(s). To tell
diff --git a/sys-utils/cytune.8 b/sys-utils/cytune.8
index fd82391..940fa28 100644
--- a/sys-utils/cytune.8
+++ b/sys-utils/cytune.8
@@ -154,7 +154,7 @@ units. When the
.I tty
is next opened, this value will be used instead of the default. If
.I value
-is zero, then the the value will default to 0x20 (160ms), soon to be 0x02
+is zero, then the value will default to 0x20 (160ms), soon to be 0x02
(10ms).
.TP
\fB\-G\fR, \fB\-\-get\-glush\fR
--
1.8.2.1
next prev parent reply other threads:[~2013-04-08 19:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-08 19:32 [PATCH 00/14] [pull] smatch scan, and manual tooling Sami Kerola
2013-04-08 19:32 ` [PATCH 01/14] setarch: clean up usage() Sami Kerola
2013-04-08 19:32 ` [PATCH 02/14] bash-completion: setarch: use correct list for architectures Sami Kerola
2013-04-08 19:32 ` [PATCH 03/14] bash-completion: swapon: add options and fix argument Sami Kerola
2013-04-08 19:32 ` [PATCH 04/14] various: fix variable and function declarations [smatch scan] Sami Kerola
2013-04-08 19:32 ` [PATCH 05/14] various: fix shadow " Sami Kerola
2013-04-08 19:32 ` [PATCH 06/14] libmount, col: remove redundant null checks " Sami Kerola
2013-04-08 19:32 ` [PATCH 07/14] libblkid: number of functions should not be declared extern " Sami Kerola
2013-04-08 19:32 ` [PATCH 08/14] tools: add checks to manual page test script Sami Kerola
2013-04-08 19:32 ` [PATCH 09/14] docs: mount.8: make propagation flags adjustable [checkmans.sh] Sami Kerola
2013-04-08 19:32 ` [PATCH 10/14] docs: col.1: fix manual page name section [checkmans.sh] Sami Kerola
2013-04-08 19:32 ` Sami Kerola [this message]
2013-04-08 19:32 ` [PATCH 12/14] tools: make checkmans.sh to find missing manuals Sami Kerola
2013-04-08 19:32 ` [PATCH 13/14] docs: add mkfs.cramfs manual page Sami Kerola
2013-04-08 19:32 ` [PATCH 14/14] docs: add fsck.cramfs " Sami Kerola
2013-04-09 10:30 ` [PATCH 00/14] [pull] smatch scan, and manual tooling Karel Zak
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1365449579-13238-12-git-send-email-kerolasa@iki.fi \
--to=kerolasa@iki.fi \
--cc=util-linux@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox