tree-wide: fix "the the" and "a a"

10 files changed, 12 insertions, 12 deletions

diff --git a/man/crypttab.xml b/man/crypttab.xml
index b130c32b11..e8c538cc85 100644
--- a/man/crypttab.xml
+++ b/man/crypttab.xml
@@ -629,7 +629,7 @@
         <term><option>fido2-rp=</option></term>
 
         <listitem><para>Takes a string, configuring the FIDO2 Relying Party (rp) for the FIDO2 unlock
-        operation. If not specified <literal>io.systemd.cryptsetup</literal> is used, except if the the LUKS2
+        operation. If not specified <literal>io.systemd.cryptsetup</literal> is used, except if the LUKS2
         JSON token header contains a different value. It should normally not be necessary to override
         this.</para></listitem>
       </varlistentry>
diff --git a/man/org.freedesktop.hostname1.xml b/man/org.freedesktop.hostname1.xml
index d4af4f3737..4f51cd5e80 100644
--- a/man/org.freedesktop.hostname1.xml
+++ b/man/org.freedesktop.hostname1.xml
@@ -193,7 +193,7 @@ node /org/freedesktop/hostname1 {
     <para>The <varname>HostnameSource</varname> property exposes the origin of the currently configured
     hostname. One of <literal>static</literal> (set from <filename>/etc/hostname</filename>),
     <literal>transient</literal> (a non-permanent hostname from an external source),
-    <literal>default</literal> (the value from <filename>os-release</filename> or the the compiled-in
+    <literal>default</literal> (the value from <filename>os-release</filename> or the compiled-in
     fallback).</para>
 
     <para>The <varname>IconName</varname> property exposes the <emphasis>icon name</emphasis> following the
diff --git a/man/repart.d.xml b/man/repart.d.xml
index 1773e05882..1ea25fe0b2 100644
--- a/man/repart.d.xml
+++ b/man/repart.d.xml
@@ -440,7 +440,7 @@
         source to copy from — if its partition type is set to <literal>root</literal> as well. If the
         declared type is <literal>usr</literal> the partition backing <filename>/usr/</filename> is used as
         source to copy blocks from — if its partition type is set to <literal>usr</literal> too. The logic is
-        capable of automatically tracking down the the backing partitions for encrypted and Verity-enabled
+        capable of automatically tracking down the backing partitions for encrypted and Verity-enabled
         volumes. <literal>CopyBlocks=auto</literal> is useful for implementing "self-replicating" systems,
         i.e. systems that are their own installer.</para>
 
diff --git a/man/sd_bus_error.xml b/man/sd_bus_error.xml
index aa4822818a..5697ce7323 100644
--- a/man/sd_bus_error.xml
+++ b/man/sd_bus_error.xml
@@ -295,7 +295,7 @@
     <parameter>name</parameter> parameter otherwise. The functions
     <function>sd_bus_error_set_errno()</function>, <function>sd_bus_error_set_errnof()</function> and
     <function>sd_bus_error_set_errnofv()</function>, return <constant>0</constant> when the specified error
-    value is <constant>0</constant>, and a a negative errno-like value corresponding to the
+    value is <constant>0</constant>, and a negative errno-like value corresponding to the
     <parameter>error</parameter> parameter otherwise. If an error occurs internally, one of the negative
     error values listed below will be returned.</para>
 
diff --git a/man/systemd-coredump.xml b/man/systemd-coredump.xml
index 8719ddaae9..bb84cf5f93 100644
--- a/man/systemd-coredump.xml
+++ b/man/systemd-coredump.xml
@@ -340,7 +340,7 @@ flags:   ...
       <varlistentry>
         <term><varname>COREDUMP_FILENAME=</varname></term>
 
-        <listitem><para>When the core is stored externally, the path the the core file.</para>
+        <listitem><para>When the core is stored externally, the path to the core file.</para>
         </listitem>
       </varlistentry>
 
diff --git a/man/systemd-firstboot.xml b/man/systemd-firstboot.xml
index 46fe0a0682..87cf98c31a 100644
--- a/man/systemd-firstboot.xml
+++ b/man/systemd-firstboot.xml
@@ -307,8 +307,8 @@
       <varlistentry>
         <term><literal>passwd.shell.root</literal></term>
 
-        <listitem><para>Specifies the shell binary to use for the the specified account when creating
-        it. Equivalent to the credential of the same name defined for the
+        <listitem><para>Specifies the shell binary to use for the specified account when creating it.
+        Equivalent to the credential of the same name defined for the
         <citerefentry><refentrytitle>systemd-sysusers.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>
         service.</para></listitem>
       </varlistentry>
diff --git a/man/systemd-sysusers.xml b/man/systemd-sysusers.xml
index 466a460151..b4500d1448 100644
--- a/man/systemd-sysusers.xml
+++ b/man/systemd-sysusers.xml
@@ -161,7 +161,7 @@
       <varlistentry>
         <term><literal>passwd.shell.<replaceable>user</replaceable></literal></term>
 
-        <listitem><para>Specifies the shell binary to use for the the specified account when creating it.</para></listitem>
+        <listitem><para>Specifies the shell binary to use for the specified account when creating it.</para></listitem>
       </varlistentry>
     </variablelist>
 
diff --git a/man/systemd.exec.xml b/man/systemd.exec.xml
index 1789d97ce3..64dcbbedea 100644
--- a/man/systemd.exec.xml
+++ b/man/systemd.exec.xml
@@ -3018,7 +3018,7 @@ StandardInputData=SWNrIHNpdHplIGRhIHVuJyBlc3NlIEtsb3BzLAp1ZmYgZWVtYWwga2xvcHAncy
           in the system manager. When compiled for systems with "unmerged <filename>/usr/</filename>"
           (<filename>/bin</filename> is not a symlink to <filename>/usr/bin</filename>),
           <literal>:<filename>/sbin</filename>:<filename>/bin</filename></literal> is appended. In case of
-          the the user manager, a different path may be configured by the distribution. It is recommended to
+          the user manager, a different path may be configured by the distribution. It is recommended to
           not rely on the order of entries, and have only one program with a given name in
           <varname>$PATH</varname>.</para></listitem>
         </varlistentry>
diff --git a/man/systemd.socket.xml b/man/systemd.socket.xml
index 520a906249..b669e7d15d 100644
--- a/man/systemd.socket.xml
+++ b/man/systemd.socket.xml
@@ -99,8 +99,8 @@
     <citerefentry><refentrytitle>systemd.exec</refentrytitle><manvolnum>5</manvolnum></citerefentry>), receiving only
     the sockets configured through socket-activation from the host's namespace. In such a set-up communication within
     the host's network namespace is only permitted through the activation sockets passed in while all sockets allocated
-    from the service code itself will be associated with the service's own namespace, and thus possibly subject to a a
-    much more restrictive configuration.</para>
+    from the service code itself will be associated with the service's own namespace, and thus possibly subject to a
+    restrictive configuration.</para>
   </refsect1>
 
   <refsect1>
diff --git a/src/partition/repart.c b/src/partition/repart.c
index d0ee02067b..589acaa49d 100644
--- a/src/partition/repart.c
+++ b/src/partition/repart.c
@@ -4886,7 +4886,7 @@ static int run(int argc, char *argv[]) {
                         if (!arg_node)
                                 return log_oom();
 
-                        /* Remember that the the device we are about to manipulate is actually the one we
+                        /* Remember that the device we are about to manipulate is actually the one we
                          * allocated here, and thus to increase its backing file we know what to do */
                         node_is_our_loop = true;
                 }