shaba/systemd
1
0
Fork 0
mirror of https://github.com/systemd/systemd.git synced 2025-03-25 18:50:18 +03:00
Code

doc: choose different words to improve clarity

Browse Source 
I suggest the following changes to improve the way the text reads
("flows").
This commit is contained in:
Jan Engelhardt 2014-02-17 02:49:45 +01:00 committed by Zbigniew Jędrzejewski-Szmek
parent 66f756d437
commit dc968941bf
3 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
man/crypttab.xml
View File

@ -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>

2
man/sd_bus_creds_get_pid.xml
View File

@ -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>

2
man/sd_bus_message_get_monotonic_usec.xml
View File

@ -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