From dc968941bfc9be464e1df15afa05693dec3ec192 Mon Sep 17 00:00:00 2001
From: Jan Engelhardt <jengelh@inai.de>
Date: Mon, 17 Feb 2014 02:49:45 +0100
Subject: [PATCH] doc: choose different words to improve clarity

I suggest the following changes to improve the way the text reads
("flows").
---
 man/crypttab.xml                          | 6 +++---
 man/sd_bus_creds_get_pid.xml              | 2 +-
 man/sd_bus_message_get_monotonic_usec.xml | 2 +-
 3 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/man/crypttab.xml b/man/crypttab.xml
index 2d4150013..668e51dc0 100644
--- a/man/crypttab.xml
+++ b/man/crypttab.xml
@@ -171,7 +171,7 @@
                                 If the key slot does not match the given
                                 passphrase or key, but another would, the
                                 setup of the device will fail regardless.
-                                This implies <varname>luks</varname>. See
+                                This option implies <varname>luks</varname>. See
                                 <citerefentry><refentrytitle>cryptsetup</refentrytitle><manvolnum>8</manvolnum></citerefentry>
                                 for possible values. The default is to try
                                 all key slots in sequential order.</para></listitem>
@@ -275,7 +275,7 @@
                                 <term><varname>tcrypt-hidden</varname></term>
 
                                 <listitem><para>Use the hidden TrueCrypt volume.
-                                This implies <varname>tcrypt</varname>.</para>
+                                This option implies <varname>tcrypt</varname>.</para>
 
                                 <para>This will map the hidden volume that is
                                 inside of the volume provided in the second
@@ -304,7 +304,7 @@
                                 <term><varname>tcrypt-system</varname></term>
 
                                 <listitem><para>Use TrueCrypt in system
-                                encryption mode. This implies
+                                encryption mode. This option implies
                                 <varname>tcrypt</varname>.</para></listitem>
                         </varlistentry>
 
diff --git a/man/sd_bus_creds_get_pid.xml b/man/sd_bus_creds_get_pid.xml
index 25978a289..a35efef0c 100644
--- a/man/sd_bus_creds_get_pid.xml
+++ b/man/sd_bus_creds_get_pid.xml
@@ -252,7 +252,7 @@ along with systemd; If not, see <http://www.gnu.org/licenses/>.
     numeric GID (group identifier).</para>
 
     <para><function>sd_bus_creds_get_comm</function> will retrieve the
-    comm field (name of the executable, as stored in
+    comm field (truncated name of the executable, as stored in
     <filename>/proc/<replaceable>pid</replaceable>/comm</filename>).
     </para>
 
diff --git a/man/sd_bus_message_get_monotonic_usec.xml b/man/sd_bus_message_get_monotonic_usec.xml
index 57b115c63..b9437ff62 100644
--- a/man/sd_bus_message_get_monotonic_usec.xml
+++ b/man/sd_bus_message_get_monotonic_usec.xml
@@ -104,7 +104,7 @@
 
                 <para>These timestamps and the sequence number are
                 attached to each message by the kernel and cannot be
-                manipulated by the sending userspace.</para>
+                manipulated by the sender.</para>
 
                 <para>Note that these timestamps are only available on
                 some bus transports, and only after support for them
-- 
2.30.2