dilim/systemd
1
0
Fork 0
mirror of https://github.com/systemd/systemd.git synced 2026-08-10 17:14:31 +00:00
Code Issues Packages Projects Releases Wiki Activity

tree-wide: fix some double word errors like "the the"

Browse Source 
By chance (because I had this mistake in my own commit) I noticed
that there are a bunch of duplicated works like "the the" in the
code and man-pages.

This commit fixes them and some similar issues with "and and" etc.

(cherry picked from commit c944af8459)
(cherry picked from commit 43a450377b)
(cherry picked from commit 73da3f8991)
This commit is contained in:
Michael Vogt
2026-07-09 12:34:01 +02:00
committed by Luca Boccassi
parent 7cdeadb723
commit 7d3b821797
10 changed files with 10 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
man/homectl.xml
View File

@@ -239,7 +239,7 @@
<listitem><para>Takes a boolean argument. By default the interactive user creation via
<command>firstboot --prompt-new-user</command> screen will show reverse color "chrome" bars at the
top and and the bottom of the terminal screen, which may be disabled by setting this option to
top and the bottom of the terminal screen, which may be disabled by setting this option to
false.</para>
<xi:include href="version-info.xml" xpointer="v259"/></listitem>

2
man/kernel-command-line.xml
View File

@@ -785,7 +785,7 @@
<varlistentry>
<term><varname>systemd.factory_reset=</varname></term>
<listitem><para>Controls whether to to boot into factory reset mode, implemented by
<listitem><para>Controls whether to boot into factory reset mode, implemented by
<citerefentry><refentrytitle>systemd-factory-reset-generator</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
<citerefentry><refentrytitle>systemd-repart</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
and other tools.</para>

2
man/systemd-firstboot.xml
View File

@@ -359,7 +359,7 @@
<term><option>--chrome=</option></term>
<listitem><para>Takes a boolean argument. By default the initial setup screen will show reverse color
"chrome" bars at the top and and the bottom of the terminal screen, which may be disabled by setting
"chrome" bars at the top and the bottom of the terminal screen, which may be disabled by setting
this option to false.</para>
<xi:include href="version-info.xml" xpointer="v259"/></listitem>

2
man/systemd-fstab-generator.xml
View File

@@ -149,7 +149,7 @@
<listitem><para>Takes the <filename>/usr/</filename> filesystem to be mounted by the initrd. If
<varname>mount.usrfstype=</varname> or <varname>mount.usrflags=</varname> is set, then the mount
configured via <varname>mount.usr=</varname> will default to the the same value set in
configured via <varname>mount.usr=</varname> will default to the same value set in
<varname>root=</varname>.</para>
<para>Set to <literal>dissect</literal> to explicitly request automatic <filename>/usr/</filename>

2
man/systemd.netdev.xml
View File

@@ -1059,7 +1059,7 @@ Ports=eth2</programlisting>
<literal>prp</literal>. Defaults to <literal>hsr</literal>.</para>
<para>Both protocols work by sending two copies of every outgoing frame, one for each of the two
ports. The destination node receives the two frames and and keeps only the first one. If a link
ports. The destination node receives the two frames and keeps only the first one. If a link
fails, only one of the two frames is received. HSR uses a ring topology where the two outgoing
frames are sent in opposite directions in the ring. PRP doesn't need a specific topology, but it
requires two completely redundant networks attached to the two ports.</para>

2
man/varlinkctl.xml
View File

@@ -331,7 +331,7 @@
functionality may be used to consume replies that come with associated file descriptors in a
reasonable way.</para>
<para>Now that if <option>--exec</option> is specified the the third parameter to
<para>Now that if <option>--exec</option> is specified the third parameter to
<command>call</command> is not optional (i.e. the method call parameters).</para>
<xi:include href="version-info.xml" xpointer="v258"/>

2
src/resolve/resolved-hook.c
View File

@@ -23,7 +23,7 @@
* of resolution requests we keep multiple connections open thus, but not too many. */
#define HOOK_IDLE_CONNECTIONS_MAX 4U
/* Encapsulates a specific hook, i.e. bound socket in in the /run/systemd/resolve.hook/ directory */
/* Encapsulates a specific hook, i.e. bound socket in the /run/systemd/resolve.hook/ directory */
typedef struct Hook {
unsigned n_ref;

2
src/shared/varlink-io.systemd.Login.c
View File

@@ -26,7 +26,7 @@ static SD_VARLINK_DEFINE_ENUM_TYPE(
SD_VARLINK_DEFINE_ENUM_VALUE(user_early_light),
SD_VARLINK_FIELD_COMMENT("Display manager greeter screen used for login"),
SD_VARLINK_DEFINE_ENUM_VALUE(greeter),
SD_VARLINK_FIELD_COMMENT("Similar, but a a lock screen"),
SD_VARLINK_FIELD_COMMENT("Similar, but a lock screen"),
SD_VARLINK_DEFINE_ENUM_VALUE(lock_screen),
SD_VARLINK_FIELD_COMMENT("Background session (that has no TTY, VT, Seat)"),
SD_VARLINK_DEFINE_ENUM_VALUE(background),

2
src/shared/varlink-io.systemd.Resolve.Hook.c
View File

@@ -39,7 +39,7 @@ static SD_VARLINK_DEFINE_METHOD(
ResolveRecord,
SD_VARLINK_FIELD_COMMENT("The question being looked up, i.e. a combination of resource record keys. Note that unlike DNS "
"queries on the wire these lookups can carry multiple key requests, albeit closely related ones. "
"Specifically, lookups for A+AAAA for the the same hostname are submitted as one question, as "
"Specifically, lookups for A+AAAA for the same hostname are submitted as one question, as "
"are lookups for TXT+SRV when doing DNS-SD resolution. Moreover, when looking up resources with "
"non-ASCII characters, they are placed together in a single question, once with labels encoded in "
"UTF-8, and once in IDNA. Hook implementations must be able to deal with these and other similar "

2
src/udev/udev-builtin-blkid.c
View File

@@ -186,7 +186,7 @@ static int find_gpt_root(UdevEvent *event, blkid_probe pr, const char *loop_back
* hence no need to bother with searching for ESP/XBOOTLDR */
need_esp_or_xbootldr = false;
} else
/* We now know the the ESP/xbootldr UUID, but we cannot be sure yet it's on this block
/* We now know the ESP/xbootldr UUID, but we cannot be sure yet it's on this block
* device, hence look for it among partitions now */
need_esp_or_xbootldr = true;
} else {