man: fix typos

man/busctl.xml

@@ -448,7 +448,7 @@ ARRAY "s" {
     <example>
       <title>Invoking a Method</title>
 
-      <para>The following command invokes a the
+      <para>The following command invokes the
       <literal>StartUnit</literal> method on the
       <literal>org.freedesktop.systemd1.Manager</literal>
       interface of the

man/machinectl.xml

@@ -247,7 +247,7 @@
         <literal>checksum</literal> is specified, the download is
         checked for integrity after the transfer is complete, but no
         signatures are verified. If <literal>signature</literal> is
-        specified, the checksum is verified and the images's signature
+        specified, the checksum is verified and the image's signature
         is checked against a local keyring of trustable vendors. It is
         strongly recommended to set this option to
         <literal>signature</literal> if the server and protocol

man/sd-event.xml

@@ -136,7 +136,7 @@
 
       <listitem><para>Event sources may be assigned a 64bit priority
       value, that controls the order in which event sources are
-      dispatched if multiple are pending simultanously. See
+      dispatched if multiple are pending simultaneously. See
       <citerefentry><refentrytitle>sd_event_source_set_priority</refentrytitle><manvolnum>3</manvolnum></citerefentry>.</para></listitem>
 
       <listitem><para>The event loop may automatically send watchdog

man/sd_bus_creds_get_pid.xml

@@ -470,7 +470,7 @@
     modified by the caller.</para>
 
     <para>All functions that take a <parameter>char***</parameter>
-    parameter will store the answer there as an address of a an array
+    parameter will store the answer there as an address of an array
     of strings. Each individual string is NUL-terminated, and the
     array is NULL-terminated as a whole. It will be valid as long as
     <parameter>c</parameter> remains valid, and should not be freed or

man/sd_event_add_child.xml

@@ -127,7 +127,7 @@
     <constant>SD_EVENT_OFF</constant> with
     <citerefentry><refentrytitle>sd_event_source_set_enabled</refentrytitle><manvolnum>3</manvolnum></citerefentry>.</para>
 
-    <para>If the the second parameter of
+    <para>If the second parameter of
     <function>sd_event_add_child()</function> is passed as NULL no
     reference to the event source object is returned. In this case the
     event source is considered "floating", and will be destroyed

man/sd_event_add_defer.xml

@@ -108,7 +108,7 @@
     handler will be called once
     (<constant>SD_EVENT_ONESHOT</constant>). Note that if the event
     source is set to <constant>SD_EVENT_ON</constant> the event loop
-    will never go to sleep again, but continously call the handler,
+    will never go to sleep again, but continuously call the handler,
     possibly interleaved with other event sources.</para>
 
     <para><function>sd_event_add_post()</function> adds a new event

man/sd_event_add_io.xml

@@ -141,14 +141,14 @@
     <constant>EPOLLHUP</constant> set.</para>
 
     <para>By default, the I/O event source will stay enabled
-    continously (<constant>SD_EVENT_ON</constant>), but this may be
+    continuously (<constant>SD_EVENT_ON</constant>), but this may be
     changed with
     <citerefentry><refentrytitle>sd_event_source_set_enabled</refentrytitle><manvolnum>3</manvolnum></citerefentry>.
     If the handler function returns a negative error code, it will be
     disabled after the invocation, even if the
     <constant>SD_EVENT_ON</constant> mode was requested before. Note
     that an I/O event source set to <constant>SD_EVENT_ON</constant> will
-    fire continously unless data is read or written to the file
+    fire continuously unless data is read or written to the file
     descriptor in order to reset the mask of events seen.
     </para>
 
@@ -169,7 +169,7 @@
     <constant>SD_EVENT_OFF</constant> with
     <citerefentry><refentrytitle>sd_event_source_set_enabled</refentrytitle><manvolnum>3</manvolnum></citerefentry>.</para>
 
-    <para>If the the second parameter of
+    <para>If the second parameter of
     <function>sd_event_add_io()</function> is passed as NULL no
     reference to the event source object is returned. In this case the
     event source is considered "floating", and will be destroyed

man/sd_event_add_signal.xml

@@ -128,7 +128,7 @@
     <constant>SD_EVENT_OFF</constant> with
     <citerefentry><refentrytitle>sd_event_source_set_enabled</refentrytitle><manvolnum>3</manvolnum></citerefentry>.</para>
 
-    <para>If the the second parameter of
+    <para>If the second parameter of
     <function>sd_event_add_signal()</function> is passed as NULL no
     reference to the event source object is returned. In this case the
     event source is considered "floating", and will be destroyed

man/sd_event_add_time.xml

@@ -159,7 +159,7 @@
     disabled after the invocation, even if the
     <constant>SD_EVENT_ON</constant> mode was requested before. Note
     that a timer event set to <constant>SD_EVENT_ON</constant> will
-    fire continously unless its configured time is updated using
+    fire continuously unless its configured time is updated using
     <function>sd_event_source_set_time()</function>.
     </para>
 
@@ -172,7 +172,7 @@
     <constant>SD_EVENT_OFF</constant> with
     <citerefentry><refentrytitle>sd_event_source_set_enabled</refentrytitle><manvolnum>3</manvolnum></citerefentry>.</para>
 
-    <para>If the the second parameter of
+    <para>If the second parameter of
     <function>sd_event_add_time()</function> is passed as NULL no
     reference to the event source object is returned. In this case the
     event source is considered "floating", and will be destroyed

man/sd_event_exit.xml

@@ -76,7 +76,7 @@
     exit. The <parameter>code</parameter> parameter may be any integer
     value and is returned as-is by
     <citerefentry><refentrytitle>sd_event_loop</refentrytitle><manvolnum>3</manvolnum></citerefentry>
-    after the last event loop iteration. It may also be be queried
+    after the last event loop iteration. It may also be queried
     using <function>sd_event_get_exit_code()</function>, see
     below. </para>
 

man/sd_event_now.xml

@@ -67,7 +67,7 @@
 
     <para><function>sd_event_now()</function> returns the timestamp
     the most recent event loop iteration began. This timestamp is
-    taken right after after returning from the event sleep, and before
+    taken right after returning from the event sleep, and before
     dispatching any event sources. The <parameter>event</parameter>
     parameter takes the even loop object to retrieve the timestamp
     from. The <parameter>clock</parameter> parameter specifies the clock to

man/sd_event_source_set_enabled.xml

@@ -105,7 +105,7 @@
     with calls such as
     <citerefentry><refentrytitle>sd_event_add_io</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
     <citerefentry><refentrytitle>sd_event_add_time</refentrytitle><manvolnum>3</manvolnum></citerefentry>. However,
-    depending on the event source type they are enabled continously
+    depending on the event source type they are enabled continuously
     (<constant>SD_EVENT_ON</constant>) or only for a single invocation
     of the event source handler
     (<constant>SD_EVENT_ONESHOT</constant>). For details see the

man/sd_event_source_set_prepare.xml

@@ -71,7 +71,7 @@
     <title>Description</title>
 
     <para><function>sd_event_source_set_prepare()</function> may be
-    used to set a prepartion callback for the event source object
+    used to set a preparation callback for the event source object
     specified as <parameter>source</parameter>. The callback function
     specified as <parameter>callback</parameter> will be invoked
     immediately before the event loop goes to sleep to wait for

man/sd_event_source_set_priority.xml

@@ -111,7 +111,7 @@
     dispatched is undefined, but the event loop generally tries to
     dispatch them in the order it learnt about events on them. As the
     backing kernel primitives do not provide accurate information
-    about the order in which events occured this is not necessarily
+    about the order in which events occurred this is not necessarily
     reliable. However, it is guaranteed that if events are seen on
     multiple same-priority event sources at the same time, each one is
     not dispatched again until all others have been dispatched

man/sd_event_wait.xml

@@ -107,7 +107,7 @@
     and
     <citerefentry><refentrytitle>sd_event_loop</refentrytitle><manvolnum>3</manvolnum></citerefentry>
     for higher-level functions that execute individual but complete
-    iterations of an event loop or run it continously.</para>
+    iterations of an event loop or run it continuously.</para>
 
     <para><function>sd_event_prepare()</function> checks for pending
     events and arms necessary timers. If any events are ready to be
@@ -169,7 +169,7 @@
         <term><constant>SD_EVENT_PREPARING</constant></term>
 
         <listitem><para>An event source is currently being prepared,
-        i.e. the preparation handler is currently being excuted, as
+        i.e. the preparation handler is currently being executed, as
         set with
         <citerefentry><refentrytitle>sd_event_set_prepare</refentrytitle><manvolnum>3</manvolnum></citerefentry>. This
         state is only seen in the event source preparation handler

man/sd_notify.xml

@@ -242,7 +242,7 @@
         multiple file descriptors are submitted at once, the specified
         name will be assigned to all of them. In order to assign
         different names to submitted file descriptors, submit them in
-        seperate invocations of
+        separate invocations of
         <function>sd_pid_notify_with_fds()</function>. The name may
         consist of any ASCII character, but must not contain control
         characters or <literal>:</literal>. It may not be longer than

man/sd_seat_get_active.xml

@@ -192,7 +192,7 @@
     <function>sd_seat_get_sessions()</function>,
     <function>sd_seat_can_multi_session()</function>,
     <function>sd_seat_can_tty()</function> and
-    <function>sd_seat_can_grapical()</function> interfaces are
+    <function>sd_seat_can_graphical()</function> interfaces are
     available as a shared library, which can be compiled and linked to
     with the
     <constant>libsystemd</constant> <citerefentry project='die-net'><refentrytitle>pkg-config</refentrytitle><manvolnum>1</manvolnum></citerefentry>

man/systemctl.xml

@@ -1176,7 +1176,7 @@ kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
                   </row>
                   <row>
                     <entry><literal>bad</literal></entry>
-                    <entry>Unit file is invalid or another error occured. Note that <command>is-enabled</command> will not actually return this state, but print an error message instead. However the unit file listing printed by <command>list-unit-files</command> might show it.</entry>
+                    <entry>Unit file is invalid or another error occurred. Note that <command>is-enabled</command> will not actually return this state, but print an error message instead. However the unit file listing printed by <command>list-unit-files</command> might show it.</entry>
                     <entry>&gt; 0</entry>
                   </row>
                 </tbody>

man/systemd-resolved.service.xml

@@ -117,7 +117,7 @@
       <listitem><para>Multi-label names are routed to all local
       interfaces that have a DNS sever configured, plus the globally
       configured DNS server if there is one. Address lookups from the
-      link-local addres range are never routed to
+      link-local address range are never routed to
       DNS.</para></listitem>
     </itemizedlist>
 

man/systemd.network.xml

@@ -228,7 +228,7 @@
             <literal>ipv4</literal>, or <literal>ipv6</literal>.</para>
 
             <para>Note that DHCPv6 will by default be triggered by Router
-            Advertisment, if that is enabled, regardless of this parameter.
+            Advertisement, if that is enabled, regardless of this parameter.
             By enabling DHCPv6 support explicitly, the DHCPv6 client will
             be started regardless of the presence of routers on the link,
             or what flags the routers pass. See
@@ -673,7 +673,7 @@
           <term><varname>UseTimezone=</varname></term>
 
           <listitem><para>When true, the timezone received from the
-          DHCP server will be set as as timezone of the local
+          DHCP server will be set as timezone of the local
           system. Defaults to <literal>no</literal>.</para></listitem>
         </varlistentry>
 

man/systemd.special.xml

@@ -587,7 +587,7 @@
       <varlistentry>
         <term><filename>umount.target</filename></term>
         <listitem>
-          <para>A special target unit that umounts all mount and
+          <para>A special target unit that unmounts all mount and
           automount points on system shutdown.</para>
 
           <para>Mounts that shall be unmounted on system shutdown

man/systemd.timer.xml

@@ -284,7 +284,7 @@
         unloaded. Turning this off is particularly useful for
         transient timer units that shall disappear after they first
         elapse. Note that this setting has an effect on repeatedly
-        starting the a timer unit that only elapses once: if
+        starting a timer unit that only elapses once: if
         <varname>RemainAfterElapse=</varname> is on, it will not be
         started again, and is guaranteed to elapse only once. However,
         if <varname>RemainAfterLeapse=</varname> is off, it might be

man/systemd.unit.xml

@@ -918,7 +918,7 @@
         <filename>/var</filename> on the next following boot. Units
         making use of this condition should order themselves before
         <citerefentry><refentrytitle>systemd-update-done.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
-        to make sure they run before the stamp files's modification
+        to make sure they run before the stamp file's modification
         time gets reset indicating a completed update.</para>
 
         <para><varname>ConditionFirstBoot=</varname> takes a boolean

man/tmpfiles.d.xml

@@ -421,7 +421,7 @@
           <command>systemd-tmpfiles</command> will automatically add
           the required base entries for user and group based on the
           access mode of the file, unless base entries already exist
-          or are explictly specified. The mask will be added if not
+          or are explicitly specified. The mask will be added if not
           specified explicitly or already present. Lines of this type
           accept shell-style globs in place of normal path names. This
           can be useful for allowing additional access to certain