shaba/systemd-stable
1
1
Fork 0
mirror of https://github.com/systemd/systemd-stable.git synced 2024-12-21 09:33:57 +03:00
Code

man: change 'allow[s] to' -> 'allow[s] one to'

Browse Source 
Lintian is opinionated about this and we get nagged

(cherry picked from commit 6eed65d455)
This commit is contained in:
Luca Boccassi 2022-01-16 12:44:52 +00:00 committed by Zbigniew Jędrzejewski-Szmek
parent 44198d7ddb
commit 5cc70d1759
3 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
man/org.freedesktop.resolve1.xml
View File

@ -506,7 +506,7 @@ node /org/freedesktop/resolve1 {
<filename>/etc/hosts</filename>. Moreover, it is set for all LLMNR or mDNS RRs which originate from
the local host. Applications that require authenticated RR data for operation should check this flag
before trusting the data. Note that <filename>systemd-resolved</filename> will never return
invalidated data, hence this flag simply allows to discern the cases where data is known to be
invalidated data, hence this flag simply allows one to discern the cases where data is known to be
trusted, or where there is proof that the data is "rightfully" unauthenticated (which includes cases
where the underlying protocol or server does not support authenticating data).</para>

2
man/systemd.netdev.xml
View File

@ -2064,7 +2064,7 @@
<varlistentry>
<term><varname>HopPenalty=</varname></term>
<listitem>
<para>The hop penalty setting allows to modify
<para>The hop penalty setting allows one to modify
<citerefentry project='mankier'><refentrytitle>batctl</refentrytitle><manvolnum>8</manvolnum></citerefentry>
preference for multihop routes vs. short routes. This integer value is applied to the
TQ (Transmit Quality) of each forwarded OGM (Originator Message), thereby propagating the

8
man/systemd.network.xml
View File

@ -362,7 +362,7 @@
<varlistentry>
<term><varname>Trust=</varname></term>
<listitem>
<para>Takes a boolean. Allows to set trust mode of the virtual function (VF). When set, VF
<para>Takes a boolean. Allows one to set trust mode of the virtual function (VF). When set, VF
users can set a specific feature which may impact security and/or performance. When unset,
the kernel's default will be used.</para>
</listitem>
@ -371,7 +371,7 @@
<varlistentry>
<term><varname>LinkState=</varname></term>
<listitem>
<para>Allows to set the link state of the virtual function (VF). Takes a boolean or a
<para>Allows one to set the link state of the virtual function (VF). Takes a boolean or a
special value <literal>auto</literal>. Setting to <literal>auto</literal> means a
reflection of the physical function (PF) link state, <literal>yes</literal> lets the VF to
communicate with other VFs on this host even if the PF link state is down,
@ -2038,7 +2038,7 @@ Table=1234</programlisting></para>
<varlistentry>
<term><varname>FallbackLeaseLifetimeSec=</varname></term>
<listitem>
<para>Allows to set DHCPv4 lease lifetime when DHCPv4 server does not send the lease
<para>Allows one to set DHCPv4 lease lifetime when DHCPv4 server does not send the lease
lifetime. Takes one of <literal>forever</literal> or <literal>infinity</literal>. If
specified, the acquired address never expires. Defaults to unset.</para>
</listitem>
@ -3234,7 +3234,7 @@ Token=prefixstable:2002:da8:1::</programlisting></para>
<term><varname>SyncJumpWidth=</varname></term>
<listitem>
<para>Specifies the time quanta, propagation segment, phase buffer segment 1 and 2, and the
synchronization jump width, which allow to define the CAN bit-timing in a hardware
synchronization jump width, which allow one to define the CAN bit-timing in a hardware
independent format as proposed by the Bosch CAN 2.0 Specification.
<varname>TimeQuantaNSec=</varname> takes a timespan in nanoseconds.
<varname>PropagationSegment=</varname>, <varname>PhaseBufferSegment1=</varname>,