tree-wide: fix typos found by Fossies codespell report

6 files changed, 7 insertions, 7 deletions

diff --git a/man/less-variables.xml b/man/less-variables.xml
index 049e9f75d7..702ca06c76 100644
--- a/man/less-variables.xml
+++ b/man/less-variables.xml
@@ -87,7 +87,7 @@
       pager may be enabled automatically as describe above. Setting <varname>SYSTEMD_PAGERSECURE=0</varname>
       or not removing it from the inherited environment allows the user to invoke arbitrary commands. Note
       that if the <varname>$SYSTEMD_PAGER</varname> or <varname>$PAGER</varname> variables are to be
-      honoured, <varname>$SYSTEMD_PAGERSECURE</varname> must be set too. It might be reasonable to completly
+      honoured, <varname>$SYSTEMD_PAGERSECURE</varname> must be set too. It might be reasonable to completely
       disable the pager using <option>--no-pager</option> instead.</para></listitem>
     </varlistentry>
 
diff --git a/man/machine-id.xml b/man/machine-id.xml
index 7e889ca47a..45607d5264 100644
--- a/man/machine-id.xml
+++ b/man/machine-id.xml
@@ -124,7 +124,7 @@
 
     <orderedlist>
       <listitem><para>If <filename>/etc/machine-id</filename> does not exist, this is a first boot.  During
-      early boot, <command>systemd</command> will write <literal>unitialized\n</literal> to this file and overmount
+      early boot, <command>systemd</command> will write <literal>uninitialized\n</literal> to this file and overmount
       a temporary file which contains the actual machine ID.  Later (after <filename>first-boot-complete.target</filename>
       has been reached), the real machine ID will be written to disk.</para></listitem>
 
diff --git a/man/systemd-cryptsetup-generator.xml b/man/systemd-cryptsetup-generator.xml
index cb18db246b..a479b23406 100644
--- a/man/systemd-cryptsetup-generator.xml
+++ b/man/systemd-cryptsetup-generator.xml
@@ -125,7 +125,7 @@
         <varname>luks.uuid=</varname>, the data device will be set to the one specified by
         <varname>rd.luks.data=</varname> or <varname>luks.data=</varname> of the corresponding UUID.</para>
 
-        <para>LUKS data device parameter is usefull for specifying encrypted data devices with detached headers specified in
+        <para>LUKS data device parameter is useful for specifying encrypted data devices with detached headers specified in
         <varname>luks.options</varname> entry containing <literal>header=</literal> argument. For example,
         <varname>rd.luks.uuid=</varname>b40f1abf-2a53-400a-889a-2eccc27eaa40
         <varname>rd.luks.options=</varname>b40f1abf-2a53-400a-889a-2eccc27eaa40=header=/path/to/luks.hdr
diff --git a/man/systemd-resolved.service.xml b/man/systemd-resolved.service.xml
index 8f3494e36b..8bd3ade9e2 100644
--- a/man/systemd-resolved.service.xml
+++ b/man/systemd-resolved.service.xml
@@ -184,7 +184,7 @@
 
       <para>In case of single-label names, when search domains are defined, the same logic applies, except
       that the name is first suffixed by each of the search domains in turn. Note that this search logic
-      doesn't apply to any names with at least one dot. Also see the discussion about compatiblity with
+      doesn't apply to any names with at least one dot. Also see the discussion about compatibility with
       the traditional glibc resolver below.</para></listitem>
 
       <listitem><para>If a query does not match any configured routing domain (either per-link or global), it
@@ -232,7 +232,7 @@
       <filename>/etc/hosts</filename>.</para></listitem>
 
       <listitem><para>Single-label names are not resolved for A and AAAA records using unicast DNS (unless
-      overriden with <varname>ResolveUnicastSingleLabel=</varname>, see
+      overridden with <varname>ResolveUnicastSingleLabel=</varname>, see
       <citerefentry><refentrytitle>resolved.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry>).
       This is similar to the <option>no-tld-query</option> option being set in
       <citerefentry><refentrytitle>resolv.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry>.
diff --git a/man/systemd.exec.xml b/man/systemd.exec.xml
index 454dd66199..5c18fffbc8 100644
--- a/man/systemd.exec.xml
+++ b/man/systemd.exec.xml
@@ -885,7 +885,7 @@ CapabilityBoundingSet=~CAP_B CAP_C</programlisting>
         <citerefentry><refentrytitle>umask</refentrytitle><manvolnum>2</manvolnum></citerefentry> for
         details. Defaults to 0022 for system units. For user units the default value is inherited from the
         per-user service manager (whose default is in turn inherited from the system service manager, and
-        thus typically also is 0022 — unless overriden by a PAM module). In order to change the per-user mask
+        thus typically also is 0022 — unless overridden by a PAM module). In order to change the per-user mask
         for all user services, consider setting the <varname>UMask=</varname> setting of the user's
         <filename>user@.service</filename> system service instance. The per-user umask may also be set via
         the <varname>umask</varname> field of a user's <ulink url="https://systemd.io/USER_RECORD">JSON User
diff --git a/man/systemd.net-naming-scheme.xml b/man/systemd.net-naming-scheme.xml
index e894db7cd6..6efb5be2fb 100644
--- a/man/systemd.net-naming-scheme.xml
+++ b/man/systemd.net-naming-scheme.xml
@@ -362,7 +362,7 @@
         <varlistentry>
           <term><constant>v247</constant></term>
 
-          <listitem><para>If the PCI slot is assocated with PCI bridge and that has multiple child network
+          <listitem><para>If the PCI slot is associated with PCI bridge and that has multiple child network
           controllers then all of them might derive the same value of <varname>ID_NET_NAME_SLOT</varname>
           property. That could cause naming conflict if the property is selected as a device name. Now, we detect the
           situation, slot - bridge relation, and we don't produce the <varname>ID_NET_NAME_SLOT</varname> property to