system/systemd
system/systemd
1
0
Fork 0
mirror of https://github.com/systemd/systemd synced 2024-07-20 17:56:25 +00:00
Code Issues Actions 9 Packages Projects Releases Wiki Activity

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

Browse source
This commit is contained in:
Yu Watanabe 2021-06-30 20:53:14 +09:00
parent 857f0e0ae3
commit 3d62af7d23
10 changed files with 12 additions and 12 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
man/crypttab.xml
View file

@ -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>

2
man/org.freedesktop.hostname1.xml
View file

@ -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

2
man/repart.d.xml
View file

@ -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>

2
man/sd_bus_error.xml
View file

@ -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>

2
man/systemd-coredump.xml
View file

@ -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>

4
man/systemd-firstboot.xml
View file

@ -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>

2
man/systemd-sysusers.xml
View file

@ -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>

2
man/systemd.exec.xml
View file

@ -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>

4
man/systemd.socket.xml
View file

@ -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>

2
src/partition/repart.c
View file

@ -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;
}