man: fix typos

Author: eriksjolund

man/systemctl.xml

@@ -101,7 +101,7 @@ To show all installed unit files use 'systemctl list-unit-files'.</programlistin
             <constant>failed</constant>, <constant>activating</constant>, <constant>deactivating</constant>. The SUB
             column shows the unit-type-specific detailed state of the unit, possible values vary by unit type. The list
             of possible LOAD, ACTIVE, and SUB states is not constant and new systemd releases may both add and remove
-            values. <programlisting>systemctl --state=help</programlisting> command maybe be used to display the
+            values. <programlisting>systemctl --state=help</programlisting> command may be used to display the
             current set of possible values.</para>
 
             <para>This is the default command.</para>

man/systemd.exec.xml

@@ -1112,7 +1112,7 @@ CapabilityBoundingSet=~CAP_B CAP_C</programlisting>
         the root user) do not share their key material among each other. If <option>shared</option> is used a new
         session keyring is allocated as for <option>private</option>, but the user keyring of the user configured with
         <varname>User=</varname> is linked into it, so that keys assigned to the user may be requested by the unit's
-        processes. In this modes multiple units running processes under the same user ID may share key material. Unless
+        processes. In this mode multiple units running processes under the same user ID may share key material. Unless
         <option>inherit</option> is selected the unique invocation ID for the unit (see below) is added as a protected
         key by the name <literal>invocation_id</literal> to the newly created session keyring. Defaults to
         <option>private</option> for services of the system service manager and to <option>inherit</option> for
@@ -1738,7 +1738,7 @@ BindReadOnlyPaths=/var/lib/systemd</programlisting>
       <varlistentry>
         <term><varname>NetworkNamespacePath=</varname></term>
 
-        <listitem><para>Takes an absolute file system path refererring to a Linux network namespace
+        <listitem><para>Takes an absolute file system path referring to a Linux network namespace
         pseudo-file (i.e. a file like <filename>/proc/$PID/ns/net</filename> or a bind mount or symlink to
         one). When set the invoked processes are added to the network namespace referenced by that path. The
         path has to point to a valid namespace file at the moment the processes are forked off. If this
@@ -1792,7 +1792,7 @@ BindReadOnlyPaths=/var/lib/systemd</programlisting>
       <varlistentry>
         <term><varname>IPCNamespacePath=</varname></term>
 
-        <listitem><para>Takes an absolute file system path refererring to a Linux IPC namespace
+        <listitem><para>Takes an absolute file system path referring to a Linux IPC namespace
         pseudo-file (i.e. a file like <filename>/proc/$PID/ns/ipc</filename> or a bind mount or symlink to
         one). When set the invoked processes are added to the network namespace referenced by that path. The
         path has to point to a valid namespace file at the moment the processes are forked off. If this

man/systemd.nspawn.xml

@@ -521,7 +521,7 @@
         name is the interface name on the host, the second the interface name in the container. The latter
         may be omitted in which case it is set to the same name as the host side interface. This setting
         implies <varname>Private=yes</varname>. This setting corresponds to the
-        <option>--network-veth-extra=</option> command line switch, and maybe be used multiple times. It is
+        <option>--network-veth-extra=</option> command line switch, and may be used multiple times. It is
         independent of <varname>VirtualEthernet=</varname>. Note that this option is unrelated to the
         <varname>Bridge=</varname> setting below, and thus any connections created this way are not
         automatically added to any bridge device on the host side. This option is privileged (see

man/systemd.service.xml

@@ -1129,7 +1129,7 @@
         nor failed, or a job is queued for the service, or the service is expected to be restarted. If
         <constant>yes</constant> the file descriptor store is kept around until the unit is removed from
         memory (i.e. is not referenced anymore and inactive). The latter is useful to keep entries in the
-        file descriptor store pinned until the service manage exits.</para>
+        file descriptor store pinned until the service manager exits.</para>
 
         <para>Use <command>systemctl clean --what=fdstore …</command> to release the file descriptor store
         explicitly.</para></listitem>

man/systemd.socket.xml

@@ -486,7 +486,7 @@
         and the <ulink
         url="http://www.tldp.org/HOWTO/html_single/TCP-Keepalive-HOWTO/">TCP
         Keepalive HOWTO</ulink> for details.)
-        Defaults value is 7200 seconds (2 hours).</para></listitem>
+        Default value is 7200 seconds (2 hours).</para></listitem>
       </varlistentry>
 
       <varlistentry>
@@ -496,7 +496,7 @@
         <constant>TCP_KEEPINTVL</constant> socket option (see <citerefentry
         project='man-pages'><refentrytitle>socket</refentrytitle><manvolnum>7</manvolnum></citerefentry> and
         the <ulink url="http://www.tldp.org/HOWTO/html_single/TCP-Keepalive-HOWTO/">TCP Keepalive
-        HOWTO</ulink> for details.) Defaults value is 75 seconds.</para></listitem>
+        HOWTO</ulink> for details.) Default value is 75 seconds.</para></listitem>
       </varlistentry>
 
       <varlistentry>
@@ -508,7 +508,7 @@
         <citerefentry project='man-pages'><refentrytitle>socket</refentrytitle><manvolnum>7</manvolnum></citerefentry>
         and the <ulink
         url="http://www.tldp.org/HOWTO/html_single/TCP-Keepalive-HOWTO/">TCP
-        Keepalive HOWTO</ulink> for details.) Defaults value is
+        Keepalive HOWTO</ulink> for details.) Default value is
         9.</para></listitem>
       </varlistentry>
 

man/systemd.special.xml

@@ -1105,7 +1105,7 @@
             <citerefentry><refentrytitle>systemd-timesyncd.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>
             service is a simple daemon that pulls in this target and orders itself before it. Besides
             implementing the SNTP network protocol it maintains a timestamp file on disk whose modification
-            time is regularlary updated. At service start-up the local system clock is set from that modification time,
+            time is regularly updated. At service start-up the local system clock is set from that modification time,
             ensuring it increases roughly monotonically.</para>
 
             <para>Note that ordering a unit after <filename>time-set.target</filename> only has effect if