shaba/systemd
1
0
Fork 0
mirror of https://github.com/systemd/systemd.git synced 2024-12-22 17:35:35 +03:00
Code

man: typo fixes

Browse Source
This commit is contained in:
Thomas Hindoe Paaboel Andersen 2015-07-25 23:15:05 +02:00
parent 3460810e8c
commit dd2b607b7d
12 changed files with 20 additions and 20 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
man/coredump.conf.xml
View File

@ -58,7 +58,7 @@
<refsect1>
<title>Description</title>
<para>These files configure the behaviour of
<para>These files configure the behavior of
<citerefentry><refentrytitle>systemd-coredump</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
a handler for core dumps invoked by the kernel.</para>
</refsect1>

2
man/custom-html.xsl
View File

@ -125,7 +125,7 @@
<!--
- helper template to do conflict resolution between various headings with the same inferred ID attribute/tag from the headerlink template
- this conflict resolution is necessary to prevent malformed HTML ouput (multiple id attributes with the same value)
- this conflict resolution is necessary to prevent malformed HTML output (multiple id attributes with the same value)
- and it fixes xsltproc warnings during compilation of HTML man pages
-
- A simple top-to-bottom numbering scheme is implemented for nodes with the same ID value to derive unique ID values for HTML output.

4
man/machinectl.xml
View File

@ -593,7 +593,7 @@
<filename>/var/lib/machines/</filename>, that is named after
the specified URL and its HTTP etag. A writable snapshot is
then taken from this subvolume, and named after the specified
local name. This behaviour ensures that creating multiple
local name. This behavior ensures that creating multiple
container instances of the same URL is efficient, as multiple
downloads are not necessary. In order to create only the
read-only image, and avoid creating its writable snapshot,
@ -639,7 +639,7 @@
machine name. To omit creation of the local, writable copy
pass <literal>-</literal> as local machine name.</para>
<para>Similar to the behaviour of <command>pull-tar</command>,
<para>Similar to the behavior of <command>pull-tar</command>,
the read-only image is prefixed with
<filename>.raw-</filename>, and thus not shown by
<command>list-images</command>, unless <option>--all</option>

4
man/sd-bus-errors.xml
View File

@ -138,7 +138,7 @@
<term><varname>SD_BUS_ERROR_FAILED</varname></term>
<listitem><para>A generic error indication. See the error
message for further details. This error name should be
avoided, in favour of a more expressive error
avoided, in favor of a more expressive error
name.</para></listitem>
</varlistentry>
@ -186,7 +186,7 @@
</varlistentry>
<varlistentry>
<term><varname>SD_BUS_ERROR_ACCESS_DENIED</varname></term>
<listitem><para>Access to a resource has bee denied, due to security restrictions.</para></listitem>
<listitem><para>Access to a resource has been denied, due to security restrictions.</para></listitem>
</varlistentry>
<varlistentry>
<term><varname>SD_BUS_ERROR_AUTH_FAILED</varname></term>

8
man/sd_bus_message_append_array.xml
View File

@ -49,7 +49,7 @@
<refname>sd_bus_message_append_array_iovec</refname>
<refname>sd_bus_message_append_array_space</refname>
<refpurpose>Appaned an array of fields to a D-Bus
<refpurpose>Append an array of fields to a D-Bus
message</refpurpose>
</refnamediv>
@ -125,7 +125,7 @@
<parameter>m</parameter>, similar to
<function>sd_bus_message_append_array()</function>. The contents
of the memory file descriptor <parameter>memfd</parameter>
starting at the specified offset and and of the specified size is
starting at the specified offset and of the specified size is
used as the contents of the array. The offset and size must be a
multiple of the size of the type
<parameter>type</parameter>. However, as a special exception, if
@ -173,7 +173,7 @@
<parameter>p</parameter>. The caller should subsequently write the
array contents to this memory. Modifications of the memory
pointed to should only occur until the next operation on the bus
message is invoked, most imporantly the memory should not be
message is invoked, most importantly the memory should not be
altered anymore when another field has been added to the message
or the message has been sealed.</para>
</refsect1>
@ -182,7 +182,7 @@
<title>Return Value</title>
<para>On success, these calls return 0 or a positive integer. On
failure, they returns a negative errno-style error code.</para>
failure, they return a negative errno-style error code.</para>
</refsect1>
<xi:include href="sd_bus_message_append_basic.xml" xpointer="errors" />

2
man/sd_bus_negotiate_fds.xml
View File

@ -152,7 +152,7 @@
<refsect1>
<title>Return Value</title>
<para>On success, these functions returns 0 or a
<para>On success, these functions return 0 or a
positive integer. On failure, they return a negative errno-style
error code.</para>
</refsect1>

4
man/systemd-coredump.xml
View File

@ -67,7 +67,7 @@
overridden to use a different setting following normal
<citerefentry><refentrytitle>sysctl.d</refentrytitle><manvolnum>5</manvolnum></citerefentry> rules.</para>
<para>The behaviour of a specific program upon reception of a
<para>The behavior of a specific program upon reception of a
signal is governed by a few factors which are described in detail
in <citerefentry project='man-pages'><refentrytitle>core</refentrytitle><manvolnum>5</manvolnum></citerefentry>.
In particular, the coredump will only be processed when the
@ -81,7 +81,7 @@
including a backtrace if possible, and store the core (contents of
process' memory contents) in an external file on disk in
<filename>/var/lib/systemd/coredump</filename>, or directly in
the journal. This behaviour may be modified using
the journal. This behavior may be modified using
<citerefentry><refentrytitle>coredump.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry>.</para>
<para>Apart from the

2
man/systemd-journald.service.xml
View File

@ -203,7 +203,7 @@
<listitem><para>Configure
<command>systemd-journald</command>
behaviour. See
behavior. See
<citerefentry><refentrytitle>journald.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry>.
</para></listitem>
</varlistentry>

2
man/systemd.journal-fields.xml
View File

@ -73,7 +73,7 @@
<para>The human-readable message string for this entry. This
is supposed to be the primary text shown to the user. It is
usually not translated (but might be in some cases), and is
not supposed to be parsed for meta data.</para>
not supposed to be parsed for metadata.</para>
</listitem>
</varlistentry>

6
man/systemd.netdev.xml
View File

@ -500,7 +500,7 @@
A Flow Label of zero is used to indicate packets that have
not been labeled. Takes following values.
When <literal>inherit</literal> it uses the original flowlabel,
or can be configured to any value betwen 0 to 0xFFFFF.</para>
or can be configured to any value between 0 to 0xFFFFF.</para>
</listitem>
</varlistentry>
<varlistentry>
@ -679,7 +679,7 @@
<listitem>
<para>Specifies the frequency that Media Independent
Interface link monitoring will occur. A value of zero
disables MII link monitoring. This values is rounded down to
disables MII link monitoring. This value is rounded down to
the nearest millisecond. The default value is 0.</para>
</listitem>
</varlistentry>
@ -823,7 +823,7 @@
<listitem>
<para> Specify the number of packets to transmit through a slave before
moving to the next one. When set to 0 then a slave is chosen at
random.The valid range is (0 - 65535). Defaults to 1. This option
random. The valid range is (0 - 65535). Defaults to 1. This option
has effect only in balance-rr mode.
</para>
</listitem>

2
man/systemd.network.xml
View File

@ -288,7 +288,7 @@
<term><varname>BindCarrier=</varname></term>
<listitem>
<para>A port or a list of ports. When set, controls the
behaviour of the current interface. When all ports in the list
behavior of the current interface. When all ports in the list
are in an operational down state, the current interface is brought
down. When at least one port has carrier, the current interface
is brought up.

2
man/systemd.socket.xml
View File

@ -462,7 +462,7 @@
and the kernel will ignore initial ACK packets without any
data. The argument specifies the approximate amount of time
the kernel should wait for incoming data before falling back
to the normal behaviour of honouring empty ACK packets. This
to the normal behavior of honouring empty ACK packets. This
option is beneficial for protocols where the client sends the
data first (e.g. HTTP, in contrast to SMTP), because the
server process will not be woken up unnecessarily before it