codespell: fix spelling errors

21 files changed, 28 insertions, 28 deletions

diff --git a/man/resolvectl.xml b/man/resolvectl.xml
index f986e98ba3..d4c04a1e32 100644
--- a/man/resolvectl.xml
+++ b/man/resolvectl.xml
@@ -255,7 +255,7 @@
           through external means. The <option>dns</option> command expects IPv4 or IPv6 address specifications of DNS
           servers to use. The <option>domain</option> command expects valid DNS domains, possibly prefixed with
           <literal>~</literal>, and configures a per-interface search or route-only domain. The
-          <option>default-route</option> command expects a boolean paremeter, and configures whether the link may be
+          <option>default-route</option> command expects a boolean parameter, and configures whether the link may be
           used as default route for DNS lookups, i.e. if it is suitable for lookups on domains no other link explicitly
           is configured for. The <option>llmnr</option>, <option>mdns</option>, <option>dnssec</option> and
           <option>dnsovertls</option> commands may be used to configure the per-interface LLMNR, MulticastDNS, DNSSEC
diff --git a/man/sd_bus_add_object_vtable.xml b/man/sd_bus_add_object_vtable.xml
index 92be236afd..6cbb84e7ff 100644
--- a/man/sd_bus_add_object_vtable.xml
+++ b/man/sd_bus_add_object_vtable.xml
@@ -277,7 +277,7 @@
           </para>
 
           <para>Equivalent to <constant>SD_BUS_SIGNAL_WITH_NAMES()</constant> with the
-          <replaceable>names</replaceable> paramater unset (i.e. no parameter names).</para>
+          <replaceable>names</replaceable> parameter unset (i.e. no parameter names).</para>
           </listitem>
         </varlistentry>
 
diff --git a/man/sd_bus_close.xml b/man/sd_bus_close.xml
index b09f488874..d81c593878 100644
--- a/man/sd_bus_close.xml
+++ b/man/sd_bus_close.xml
@@ -44,7 +44,7 @@
 
     <para><function>sd_bus_close()</function> disconnects the specified bus connection. When this call is invoked and
     the specified bus object refers to an active connection it is immediately terminated. No further messages may be
-    sent or receieved on it. Any messages queued in the bus object (both incoming and outgoing) are released. If
+    sent or received on it. Any messages queued in the bus object (both incoming and outgoing) are released. If
     invoked on <constant>NULL</constant> bus object or when the bus connection is already closed this function executes
     no operation. This call does not free or unreference the bus object itself. Use
     <citerefentry><refentrytitle>sd_bus_unref</refentrytitle><manvolnum>3</manvolnum></citerefentry> for that.</para>
diff --git a/man/sd_bus_message_new_method_error.xml b/man/sd_bus_message_new_method_error.xml
index 27cec8ed01..0c471c534f 100644
--- a/man/sd_bus_message_new_method_error.xml
+++ b/man/sd_bus_message_new_method_error.xml
@@ -116,7 +116,7 @@
     project='man-pages'><refentrytitle>printf</refentrytitle><manvolnum>3</manvolnum></citerefentry>
     format string <parameter>format</parameter> and corresponding arguments.
     <literal>%m</literal> may be used in the format string to refer to the error
-    string corresponding to the specified errno code. The error message is initalized
+    string corresponding to the specified errno code. The error message is initialized
     using the error identifier generated from <constant>error</constant> and the
     formatted string. (If <parameter>error</parameter> is zero, no error is actually
     set, and an error reply with no information is created.)</para>
diff --git a/man/sd_bus_message_rewind.xml b/man/sd_bus_message_rewind.xml
index aa8aea987b..cbfa2511d2 100644
--- a/man/sd_bus_message_rewind.xml
+++ b/man/sd_bus_message_rewind.xml
@@ -19,7 +19,7 @@
   <refnamediv>
     <refname>sd_bus_message_rewind</refname>
 
-    <refpurpose>Return to begining of message or current container</refpurpose>
+    <refpurpose>Return to beginning of message or current container</refpurpose>
   </refnamediv>
 
   <refsynopsisdiv>
@@ -38,7 +38,7 @@
     <title>Description</title>
 
     <para><function>sd_bus_message_rewind()</function> moves the "read pointer" in the message
-    <parameter>m</parameter> to either the begining of the message (if
+    <parameter>m</parameter> to either the beginning of the message (if
     <parameter>complete</parameter> is true) or to the beginning of the currently open container. If
     no container is open, <parameter>complete</parameter> has no effect.</para>
   </refsect1>
diff --git a/man/sd_bus_message_verify_type.xml b/man/sd_bus_message_verify_type.xml
index c3230e5833..e03a253885 100644
--- a/man/sd_bus_message_verify_type.xml
+++ b/man/sd_bus_message_verify_type.xml
@@ -70,7 +70,7 @@
           <listitem><para><parameter>m</parameter> or both <parameter>type</parameter> and
           <parameter>contents</parameter> are <constant>NULL</constant>.</para>
 
-          <para>Arguments do not satisfy other contraints listed above.</para>
+          <para>Arguments do not satisfy other constraints listed above.</para>
           </listitem>
         </varlistentry>
 
diff --git a/man/systemd-analyze.xml b/man/systemd-analyze.xml
index f559b858f9..abc05e9303 100644
--- a/man/systemd-analyze.xml
+++ b/man/systemd-analyze.xml
@@ -337,7 +337,7 @@ $ eog targets.svg</programlisting>
       </example>
 
       <para>Note that this verb prints the list that is compiled into <command>systemd-analyze</command>
-      itself, and does not comunicate with the running manager. Use
+      itself, and does not communicate with the running manager. Use
       <programlisting>systemctl [--user] [--global] show -p UnitPath --value</programlisting>
       to retrieve the actual list that the manager uses, with any empty directories omitted.</para>
     </refsect2>
diff --git a/man/systemd-boot.xml b/man/systemd-boot.xml
index 3b1319687f..2575ab3fe5 100644
--- a/man/systemd-boot.xml
+++ b/man/systemd-boot.xml
@@ -357,7 +357,7 @@
 
     <para><command>systemd-boot</command> implements a simple boot counting mechanism on top of the <ulink
     url="https://systemd.io/BOOT_LOADER_SPECIFICATION">Boot Loader Specification</ulink>, for automatic and unattended
-    fallback to older kernel versions/boot loader entries when a specific entry continously fails. Any boot loader
+    fallback to older kernel versions/boot loader entries when a specific entry continuously fails. Any boot loader
     entry file and unified kernel image file that contains a <literal>+</literal> followed by one or two numbers (if
     two they need to be separated by a <literal>-</literal>), before the <filename>.conf</filename> or
     <filename>.efi</filename> suffix is subject to boot counting: the first of the two numbers ('tries left') is
diff --git a/man/systemd-gpt-auto-generator.xml b/man/systemd-gpt-auto-generator.xml
index 0d6d4e307e..d94d6ac715 100644
--- a/man/systemd-gpt-auto-generator.xml
+++ b/man/systemd-gpt-auto-generator.xml
@@ -234,7 +234,7 @@
         <term><varname>root=</varname></term>
 
         <listitem><para>When used with the special value <literal>gpt-auto</literal>, automatic discovery of
-        the root parition based on the GPT partition type is enabled.  Any other value disables this
+        the root partition based on the GPT partition type is enabled.  Any other value disables this
         generator.</para></listitem>
       </varlistentry>
 
diff --git a/man/systemd-networkd-wait-online.service.xml b/man/systemd-networkd-wait-online.service.xml
index 7c82f68fb3..51b865dc0b 100644
--- a/man/systemd-networkd-wait-online.service.xml
+++ b/man/systemd-networkd-wait-online.service.xml
@@ -55,7 +55,7 @@
         one is necessary to access some network resources. When used, all other interfaces are ignored.
         This option may be used more than once to wait for multiple network interfaces. When this
         option is specified multiple times, then <command>systemd-networkd-wait-online</command> waits
-        for all specified interfaces to be online. Optinally, required minimum operational state can be
+        for all specified interfaces to be online. Optionally, required minimum operational state can be
         specified after a colon <literal>:</literal>. Please see
         <citerefentry><refentrytitle>networkctl</refentrytitle><manvolnum>1</manvolnum></citerefentry>
         for possible operational states. If the operational state is not specified here, then
diff --git a/man/systemd-resolved.service.xml b/man/systemd-resolved.service.xml
index 807c3238b8..53c46a1018 100644
--- a/man/systemd-resolved.service.xml
+++ b/man/systemd-resolved.service.xml
@@ -163,7 +163,7 @@
       <listitem><para>Otherwise the query is failed as no suitable DNS servers could be determined.</para></listitem>
     </itemizedlist>
 
-    <para>The "DNS default route" option is a boolean setting configureable with <command>resolvectl</command> or in
+    <para>The "DNS default route" option is a boolean setting configurable with <command>resolvectl</command> or in
     <filename>.network</filename> files. If not set, it is implicitly determined based on the configured DNS domains
     for a link: if there's any route-only domain (not matching <literal>~.</literal>) it defaults to false, otherwise
     to true.</para>
diff --git a/man/systemd-udev-settle.service.xml b/man/systemd-udev-settle.service.xml
index 6fbd99111f..3698bfaf19 100644
--- a/man/systemd-udev-settle.service.xml
+++ b/man/systemd-udev-settle.service.xml
@@ -33,7 +33,7 @@
 
   <para><emphasis>Using this service is not recommended.</emphasis> There can be no guarantee that hardware
   is fully discovered at any specific time, because the kernel does hardware detection asynchronously, and
-  certain busses and devices take a very long time to become ready, and also additional hardware may be
+  certain buses and devices take a very long time to become ready, and also additional hardware may be
   plugged in at any time. Instead, services should subscribe to udev events and react to any new hardware as
   it is discovered. Services that, based on configuration, expect certain devices to appear, may warn or
   report failure after a timeout. This timeout should be tailored to the hardware type. Waiting for
diff --git a/man/systemd.exec.xml b/man/systemd.exec.xml
index b69691b3c4..719c2c5ff3 100644
--- a/man/systemd.exec.xml
+++ b/man/systemd.exec.xml
@@ -1304,7 +1304,7 @@ BindReadOnlyPaths=/var/lib/systemd</programlisting>
         running in user mode, or in system mode, but without the <constant>CAP_SYS_ADMIN</constant> capability
         (e.g. setting <varname>User=nobody</varname>), <varname>NoNewPrivileges=yes</varname> is implied. By default,
         no restrictions apply, all address families are accessible to processes. If assigned the empty string, any
-        previous address familiy restriction changes are undone. This setting does not affect commands prefixed with
+        previous address family restriction changes are undone. This setting does not affect commands prefixed with
         <literal>+</literal>.</para>
 
         <para>Use this option to limit exposure of processes to remote access, in particular via exotic and sensitive
@@ -1928,7 +1928,7 @@ SystemCallErrorNumber=EPERM</programlisting>
         <para>Note that services which specify <option>DefaultDependencies=no</option> and use
         <varname>StandardInput=</varname> or <varname>StandardOutput=</varname> with
         <option>tty</option>/<option>tty-force</option>/<option>tty-fail</option>, should specify
-        <option>After=systemd-vconsole-setup.service</option>, to make sure that the tty intialization is
+        <option>After=systemd-vconsole-setup.service</option>, to make sure that the tty initialization is
         finished before they start.</para></listitem>
       </varlistentry>
 
diff --git a/man/systemd.mount.xml b/man/systemd.mount.xml
index d0ccd39e38..022e227e83 100644
--- a/man/systemd.mount.xml
+++ b/man/systemd.mount.xml
@@ -312,7 +312,7 @@
         <listitem><para>The file system will be initialized
         on the device. If the device is not "empty", i.e. it contains any signature,
         the operation will be skipped. It is hence expected that this option
-        remains set even after the device has been initalized.</para>
+        remains set even after the device has been initialized.</para>
 
         <para>Note that this option can only be used in
         <filename>/etc/fstab</filename>, and will be ignored when part of the
diff --git a/man/systemd.netdev.xml b/man/systemd.netdev.xml
index a58de37b3c..b71320e20d 100644
--- a/man/systemd.netdev.xml
+++ b/man/systemd.netdev.xml
@@ -829,13 +829,13 @@
       <varlistentry>
         <term><varname>Name=</varname></term>
         <listitem>
-          <para>Specifies the name of the sesssion. This option is compulsory.</para>
+          <para>Specifies the name of the session. This option is compulsory.</para>
         </listitem>
       </varlistentry>
       <varlistentry>
         <term><varname>SessionId=</varname></term>
         <listitem>
-          <para>Specifies the sesssion id. The value used must match the <literal>SessionId=</literal> value being used at the peer.
+          <para>Specifies the session id. The value used must match the <literal>SessionId=</literal> value being used at the peer.
           Ranges a number between 1 and 4294967295). This option is compulsory.</para>
         </listitem>
       </varlistentry>
diff --git a/man/systemd.network.xml b/man/systemd.network.xml
index be982cbb1a..4381090d34 100644
--- a/man/systemd.network.xml
+++ b/man/systemd.network.xml
@@ -637,7 +637,7 @@
           <para>Note that if this option is enabled a userspace implementation of the IPv6 RA protocol is
           used, and the kernel's own implementation remains disabled, since `networkd` needs to know all
           details supplied in the advertisements, and these are not available from the kernel if the kernel's
-          own implemenation is used.</para>
+          own implementation is used.</para>
         </listitem>
         </varlistentry>
         <varlistentry>
@@ -1077,7 +1077,7 @@
         <varlistentry>
           <term><varname>InvertRule=</varname></term>
           <listitem>
-            <para>A boolean. Specifies wheather the rule to be inverted. Defaults to false.</para>
+            <para>A boolean. Specifies whether the rule to be inverted. Defaults to false.</para>
           </listitem>
         </varlistentry>
       </variablelist>
@@ -1197,7 +1197,7 @@
         <varlistentry>
           <term><varname>InitialAdvertisedReceiveWindow=</varname></term>
           <listitem>
-            <para>The TCP initial advertised receive window is the amount of receive data (in bytes) that can initally be buffered at one time
+            <para>The TCP initial advertised receive window is the amount of receive data (in bytes) that can initially be buffered at one time
             on a connection. The sending host can send only that amount of data before waiting for an acknowledgment and window update
             from the receiving host. Takes a size in bytes between 1 and 4294967295 (2^32 - 1). The usual suffixes K, M, G are supported
             and are understood to the base of 1024. When unset, the kernel's default will be used.
diff --git a/man/systemd.nspawn.xml b/man/systemd.nspawn.xml
index 1485a26f02..70c6ff33a6 100644
--- a/man/systemd.nspawn.xml
+++ b/man/systemd.nspawn.xml
@@ -429,7 +429,7 @@
         <term><varname>Inaccessible=</varname></term>
 
         <listitem><para>Masks the specified file or directly in the container, by over-mounting it with an empty file
-        node of the same type with the most restrictive access mode. Takes a file system path as arugment. This option
+        node of the same type with the most restrictive access mode. Takes a file system path as argument. This option
         may be used multiple times to mask multiple files or directories. This option is equivalent to the command line
         switch <option>--inaccessible=</option>, see
         <citerefentry><refentrytitle>systemd-nspawn</refentrytitle><manvolnum>1</manvolnum></citerefentry> for details
diff --git a/man/systemd.swap.xml b/man/systemd.swap.xml
index 66d63503db..d2a9123b0b 100644
--- a/man/systemd.swap.xml
+++ b/man/systemd.swap.xml
@@ -148,7 +148,7 @@
 
         <listitem><para>The swap structure will be initialized on the device. If the device is not
         "empty", i.e. it contains any signature, the operation will be skipped. It is hence expected
-        that this option remains set even after the device has been initalized.</para>
+        that this option remains set even after the device has been initialized.</para>
 
         <para>Note that this option can only be used in <filename>/etc/fstab</filename>, and will be
         ignored when part of the <varname>Options=</varname> setting in a unit file.</para>
diff --git a/man/systemd.timer.xml b/man/systemd.timer.xml
index 6a13e52ccf..13b9ed35d2 100644
--- a/man/systemd.timer.xml
+++ b/man/systemd.timer.xml
@@ -314,7 +314,7 @@
         <term><varname>RemainAfterElapse=</varname></term>
 
         <listitem><para>Takes a boolean argument. If true, an elapsed
-        timer will stay loaded, and its state remains queriable. If
+        timer will stay loaded, and its state remains queryable. If
         false, an elapsed timer unit that cannot elapse anymore is
         unloaded. Turning this off is particularly useful for
         transient timer units that shall disappear after they first
diff --git a/man/systemd.unit.xml b/man/systemd.unit.xml
index 81a02253ed..fdeaef3db4 100644
--- a/man/systemd.unit.xml
+++ b/man/systemd.unit.xml
@@ -512,7 +512,7 @@
         <replaceable>description</replaceable>.</literal>, <literal>Reached target
         <replaceable>description</replaceable>.</literal>, <literal>Failed to start
         <replaceable>description</replaceable>.</literal>), so it should be capitalized, and should
-        not be a full sentence or a phrase with a continous verb. Bad examples include
+        not be a full sentence or a phrase with a continuous verb. Bad examples include
         <literal>exiting the container</literal> or <literal>updating the database once per
         day.</literal>.</para>
         </listitem>
@@ -886,7 +886,7 @@
         of powering down the system with similar semantics. <option>exit</option> causes the manager to exit following
         the normal shutdown procedure, and <option>exit-force</option> causes it terminate without shutting down
         services. When <option>exit</option> or <option>exit-force</option> is used by default the exit status of the
-        main process of the unit (if this applies) is returned from the service manager. However, this may be overriden
+        main process of the unit (if this applies) is returned from the service manager. However, this may be overridden
         with <varname>FailureActionExitStatus=</varname>/<varname>SuccessActionExitStatus=</varname>, see
         below.</para></listitem>
       </varlistentry>
@@ -1273,7 +1273,7 @@
         <literal>&lt;</literal>, <literal>&lt;=</literal>, <literal>=</literal>, <literal>!=</literal>,
         <literal>&gt;=</literal>, <literal>&gt;</literal>. Compares the number of CPUs in the CPU affinity mask
         configured of the service manager itself with the specified number, adhering to the specified
-        comparision operator. On physical systems the number of CPUs in the affinity mask of the service
+        comparison operator. On physical systems the number of CPUs in the affinity mask of the service
         manager usually matches the number of physical CPUs, but in special and virtual environments might
         differ. In particular, in containers the affinity mask usually matches the number of CPUs assigned to
         the container and not the physically available ones.</para>
diff --git a/man/user-system-options.xml b/man/user-system-options.xml
index 195c2e4163..8034735658 100644
--- a/man/user-system-options.xml
+++ b/man/user-system-options.xml
@@ -30,7 +30,7 @@
       <para>Execute the operation remotely. Specify a hostname, or a
       username and hostname separated by <literal>@</literal>, to
       connect to. The hostname may optionally be suffixed by a
-      port ssh is listening on, seperated by <literal>:</literal>, and then a
+      port ssh is listening on, separated by <literal>:</literal>, and then a
       container name, separated by <literal>/</literal>, which
       connects directly to a specific container on the specified
       host. This will use SSH to talk to the remote machine manager