man: fix typos (#7029)

diff --git a/man/journald.conf.xml b/man/journald.conf.xml
index 8974f8f8d5306fe0d53ac5fe8d1b0ac9990e7c3f..fa3694d3b433e06c762846c9144fba91986454d5 100644 (file)
--- a/man/journald.conf.xml
+++ b/man/journald.conf.xml
@@ -379,7 +379,7 @@
         <listitem><para>The maximum line length to permit when converting stream logs into record logs. When a systemd
         unit's standard output/error are connected to the journal via a stream socket, the data read is split into
         individual log records at newline (<literal>\n</literal>, ASCII 10) and NUL characters. If no such delimiter is
-        read for the specified number of bytes a hard log record boundary is artifically inserted, breaking up overly
+        read for the specified number of bytes a hard log record boundary is artificially inserted, breaking up overly
         long lines into multiple log records. Selecting overly large values increases the possible memory usage of the
         Journal daemon for each stream client, as in the worst case the journal daemon needs to buffer the specified
         number of bytes in memory before it can flush a new log record to disk. Also note that permitting overly large

diff --git a/man/systemctl.xml b/man/systemctl.xml
index 4abee60790b1dbc61e72221d53528881601c8a8b..bb3fc1763c6c74de8689a7c1dcef7512bd214456 100644 (file)
--- a/man/systemctl.xml
+++ b/man/systemctl.xml
@@ -1795,7 +1795,7 @@ Jan 12 10:46:45 example.com bluetoothd[8900]: gatt-time-server: Input/output err
             <command>poweroff</command> otherwise. This command is asynchronous; it will return after the exit
             operation is enqueued, without waiting for it to complete.</para>
 
-            <para>The service manager will exit with the the specified exit code, if
+            <para>The service manager will exit with the specified exit code, if
             <replaceable>EXIT_CODE</replaceable> is passed.</para>
           </listitem>
         </varlistentry>

diff --git a/man/systemd-journald.service.xml b/man/systemd-journald.service.xml
index fec0e1fe88d5ee41abb4987784be749c309b09b9..b099d74afd9074e1ad57feeebb333f769b31cbcd 100644 (file)
--- a/man/systemd-journald.service.xml
+++ b/man/systemd-journald.service.xml
@@ -123,7 +123,7 @@ systemd-tmpfiles --create --prefix /var/log/journal</programlisting>
     <para>If <filename>systemd-journald.service</filename> is stopped, the stream connections associated with all
     services are terminated. Further writes to those streams by the service will result in <constant>EPIPE</constant>
     errors. In order to react gracefully in this case it is recommended that programs logging to standard output/error
-    ignore such errors. If the the <constant>SIGPIPE</constant> UNIX signal handler is not blocked or turned off, such
+    ignore such errors. If the <constant>SIGPIPE</constant> UNIX signal handler is not blocked or turned off, such
     write attempts will also result in such process signals being generated, see
     <citerefentry><refentrytitle>signal</refentrytitle><manvolnum>7</manvolnum></citerefentry>. To mitigate this issue,
     systemd service manager explicitly turns off the <constant>SIGPIPE</constant> signal for all invoked processes by
@@ -145,12 +145,12 @@ systemd-tmpfiles --create --prefix /var/log/journal</programlisting>
     transports listed above, which are inherently record based and where the metadata is always associated with the
     individual record.</para>
 
-    <para>In addition to the the implicit standard output/error logging of services, stream logging is also available
+    <para>In addition to the implicit standard output/error logging of services, stream logging is also available
     via the <citerefentry><refentrytitle>systemd-cat</refentrytitle><manvolnum>1</manvolnum></citerefentry> command
     line tool.</para>
 
     <para>Currently, the number of parallel log streams <filename>systemd-journald</filename> will accept is limited to
-    4096. When this limit is reached further log streams may be established but will receieve
+    4096. When this limit is reached further log streams may be established but will receive
     <constant>EPIPE</constant> right from the beginning.</para>
   </refsect1>
 

diff --git a/man/systemd.exec.xml b/man/systemd.exec.xml
index dfae0572d889f1ef06aaacf7f9ec1e8a16757f10..802eb41c47332c11a53374095d0ed1de223a7eaa 100644 (file)
--- a/man/systemd.exec.xml
+++ b/man/systemd.exec.xml
@@ -2392,7 +2392,7 @@ CapabilityBoundingSet=~CAP_B CAP_C</programlisting>
           <row>
             <entry>205</entry>
             <entry><constant>EXIT_LIMITS</constant></entry>
-            <entry>Failed to adjust resoure limits. See <varname>LimitCPU=</varname> and related settings above.</entry>
+            <entry>Failed to adjust resource limits. See <varname>LimitCPU=</varname> and related settings above.</entry>
           </row>
           <row>
             <entry>206</entry>
@@ -2497,7 +2497,7 @@ CapabilityBoundingSet=~CAP_B CAP_C</programlisting>
           <row>
             <entry>227</entry>
             <entry><constant>EXIT_NO_NEW_PRIVILEGES</constant></entry>
-            <entry>Failed to disable new priviliges. See <varname>NoNewPrivileges=yes</varname> above.</entry>
+            <entry>Failed to disable new privileges. See <varname>NoNewPrivileges=yes</varname> above.</entry>
           </row>
           <row>
             <entry>228</entry>
@@ -2512,7 +2512,7 @@ CapabilityBoundingSet=~CAP_B CAP_C</programlisting>
           <row>
             <entry>230</entry>
             <entry><constant>EXIT_PERSONALITY</constant></entry>
-            <entry>Failed to set up a execution domain (personality). See <varname>Personality=</varname> above.</entry>
+            <entry>Failed to set up an execution domain (personality). See <varname>Personality=</varname> above.</entry>
           </row>
           <row>
             <entry>231</entry>
@@ -2547,22 +2547,22 @@ CapabilityBoundingSet=~CAP_B CAP_C</programlisting>
           <row>
             <entry>238</entry>
             <entry><constant>EXIT_STATE_DIRECTORY</constant></entry>
-            <entry>Failed to set up a the unit's state directory. See <varname>StateDirectory=</varname> above.</entry>
+            <entry>Failed to set up unit's state directory. See <varname>StateDirectory=</varname> above.</entry>
           </row>
           <row>
             <entry>239</entry>
             <entry><constant>EXIT_CACHE_DIRECTORY</constant></entry>
-            <entry>Failed to set up a the unit's cache directory. See <varname>CacheDirectory=</varname> above.</entry>
+            <entry>Failed to set up unit's cache directory. See <varname>CacheDirectory=</varname> above.</entry>
           </row>
           <row>
             <entry>240</entry>
             <entry><constant>EXIT_LOGS_DIRECTORY</constant></entry>
-            <entry>Failed to set up a the unit's logging directory. See <varname>LogsDirectory=</varname> above.</entry>
+            <entry>Failed to set up unit's logging directory. See <varname>LogsDirectory=</varname> above.</entry>
           </row>
           <row>
             <entry>241</entry>
             <entry><constant>EXIT_CONFIGURATION_DIRECTORY</constant></entry>
-            <entry>Failed to set up a the unit's configuration directory. See <varname>ConfigurationDirectory=</varname> above.</entry>
+            <entry>Failed to set up unit's configuration directory. See <varname>ConfigurationDirectory=</varname> above.</entry>
           </row>
         </tbody>
       </tgroup>

diff --git a/man/systemd.nspawn.xml b/man/systemd.nspawn.xml
index 58024a071d545f579083ad9cc8594997e1ff8f40..8a59fc78ff8c6adff7501ec994d1238203a59c0e 100644 (file)
--- a/man/systemd.nspawn.xml
+++ b/man/systemd.nspawn.xml
@@ -275,7 +275,7 @@
         <term><varname>NotifyReady=</varname></term>
 
         <listitem><para>Configures support for notifications from the container's init process.  This is equivalent to
-        the <option>--notify-ready=</option> command line switch, and takes the same paramaters. See
+        the <option>--notify-ready=</option> command line switch, and takes the same parameters. See
         <citerefentry><refentrytitle>systemd-nspawn</refentrytitle><manvolnum>1</manvolnum></citerefentry> for details
         about the specific options supported.</para></listitem>
       </varlistentry>

diff --git a/man/systemd.resource-control.xml b/man/systemd.resource-control.xml
index 0c0c91608ac82d8063752f1414a07c6c8a73b4d1..62dad5774823d8fe170e2e347fd51a1a99aba935 100644 (file)
--- a/man/systemd.resource-control.xml
+++ b/man/systemd.resource-control.xml
@@ -500,7 +500,7 @@
       </varlistentry>
 
       <varlistentry>
-        <term><varname>IPAddressAllow=<replaceable>ADDDRESS[/PREFIXLENGTH]…</replaceable></varname></term>
+        <term><varname>IPAddressAllow=<replaceable>ADDRESS[/PREFIXLENGTH]…</replaceable></varname></term>
         <term><varname>IPAddressDeny=<replaceable>ADDRESS[/PREFIXLENGTH]…</replaceable></varname></term>
 
         <listitem>

diff --git a/man/systemd.unit.xml b/man/systemd.unit.xml
index bec63562704c4b0b107627dbdb3000b8a876809c..b66225fc6e0448098222ee4b166226fb6bb2f08b 100644 (file)
--- a/man/systemd.unit.xml
+++ b/man/systemd.unit.xml
@@ -295,7 +295,7 @@
     <varname>DefaultDependencies=</varname> in each unit types.</para>
 
     <para>For example, target units will complement all configured
-    dependencies of type type <varname>Wants=</varname> or
+    dependencies of type <varname>Wants=</varname> or
     <varname>Requires=</varname> with dependencies of type
     <varname>After=</varname>. See
     <citerefentry><refentrytitle>systemd.target</refentrytitle><manvolnum>5</manvolnum></citerefentry>