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

Lintian is opinionated about this and we get nagged

3 files changed, 6 insertions, 6 deletions

diff --git a/man/org.freedesktop.resolve1.xml b/man/org.freedesktop.resolve1.xml
index b8fff5a502..72beffc288 100644
--- a/man/org.freedesktop.resolve1.xml
+++ b/man/org.freedesktop.resolve1.xml
@@ -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>
 
diff --git a/man/systemd.netdev.xml b/man/systemd.netdev.xml
index ee5b61a068..eeca0a4eb5 100644
--- a/man/systemd.netdev.xml
+++ b/man/systemd.netdev.xml
@@ -2073,7 +2073,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
diff --git a/man/systemd.network.xml b/man/systemd.network.xml
index 93c10b7755..574cf599ec 100644
--- a/man/systemd.network.xml
+++ b/man/systemd.network.xml
@@ -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>,