X Tutup
Skip to content

Commit 409dee2

Browse files
jengelhkeszybz
jengelh
authored and
keszybz
committed
man: more grammar improvements
- place commas - expand contractions (this is written prose :) - add some missing words
1 parent 337fa16 commit 409dee2

18 files changed

+217
-210
lines changed

‎man/bootchart.conf.xml‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -72,7 +72,7 @@
7272
<varlistentry>
7373
<term><varname>Samples=500</varname></term>
7474
<listitem><para>Configure the amount of samples to
75-
record total before bootchart exits. Each sample will
75+
record in total before bootchart exits. Each sample will
7676
record at intervals defined by Frequency=.</para></listitem>
7777
</varlistentry>
7878

@@ -107,7 +107,7 @@
107107

108108
<varlistentry>
109109
<term><varname>Output=[path]</varname></term>
110-
<listitem><para>Configures the output folder for writing
110+
<listitem><para>Configures the output directory for writing
111111
the graphs. By default, bootchart writes the graphs to
112112
<filename>/run/log</filename>.</para></listitem>
113113
</varlistentry>
@@ -124,7 +124,7 @@
124124
<varlistentry>
125125
<term><varname>PlotMemoryUsage=no</varname></term>
126126
<listitem><para>If set to yes, enables logging and graphing
127-
of processes PSS memory consumption.</para></listitem>
127+
of processes' PSS memory consumption.</para></listitem>
128128
</varlistentry>
129129

130130
<varlistentry>

‎man/bootup.xml‎

Lines changed: 14 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -56,26 +56,27 @@
5656
and hand control over to a boot loader stored on a
5757
persistent storage device. This boot loader will then
5858
invoke an OS kernel from disk (or the network). In the
59-
Linux case this kernel (optionally) extracts and
60-
executes an initial RAM disk image (initrd) such as
61-
<citerefentry><refentrytitle>dracut</refentrytitle><manvolnum>8</manvolnum></citerefentry>
59+
Linux case, this kernel (optionally) extracts and
60+
executes an initial RAM disk image (initrd), such as
61+
generated by
62+
<citerefentry><refentrytitle>dracut</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
6263
which looks for the root file system (possibly using
6364
<citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>
6465
for this). After the root file system is found and
65-
mounted the initrd hands over control to the host's
66+
mounted, the initrd hands over control to the host's
6667
system manager (such as
6768
<citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>)
68-
stored on the OS image which is then responsible for
69+
stored on the OS image, which is then responsible for
6970
probing all remaining hardware, mounting all necessary
7071
file systems and spawning all configured
7172
services.</para>
7273

73-
<para>On shutdown the system manager stops all
74+
<para>On shutdown, the system manager stops all
7475
services, unmounts all file systems (detaching the
7576
storage technologies backing them), and then
7677
(optionally) jumps back into the initrd code which
7778
unmounts/detaches the root file system and the storage
78-
it resides on. As last step the system is powered down.</para>
79+
it resides on. As a last step, the system is powered down.</para>
7980

8081
<para>Additional information about the system boot
8182
process may be found in
@@ -90,7 +91,7 @@
9091
systems, services and drivers that are necessary for
9192
operation of the system. On
9293
<citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>
93-
systems this process is split up in various discrete
94+
systems, this process is split up in various discrete
9495
steps which are exposed as target units. (See
9596
<citerefentry><refentrytitle>systemd.target</refentrytitle><manvolnum>5</manvolnum></citerefentry>
9697
for detailed information about target units.) The
@@ -99,17 +100,17 @@
99100
deterministic, but still adheres to a limited amount
100101
of ordering structure.</para>
101102

102-
<para>When systemd starts up the system it will
103+
<para>When systemd starts up the system, it will
103104
activate all units that are dependencies of
104105
<filename>default.target</filename> (as well as
105106
recursively all dependencies of these
106-
dependencies). Usually
107+
dependencies). Usually,
107108
<filename>default.target</filename> is simply an alias
108109
of <filename>graphical.target</filename> or
109-
<filename>multi-user.target</filename> depending on
110+
<filename>multi-user.target</filename>, depending on
110111
whether the system is configured for a graphical UI or
111112
only for a text console. To enforce minimal ordering
112-
between the units pulled in a number of well-known
113+
between the units pulled in, a number of well-known
113114
target units are available, as listed on
114115
<citerefentry><refentrytitle>systemd.special</refentrytitle><manvolnum>7</manvolnum></citerefentry>.</para>
115116

@@ -178,7 +179,7 @@
178179
<refsect1>
179180
<title>Bootup in the Initial RAM Disk (initrd)</title>
180181
<para>The initial RAM disk implementation (initrd) can
181-
be set up using systemd as well. In this case boot up
182+
be set up using systemd as well. In this case, boot up
182183
inside the initrd follows the following
183184
structure.</para>
184185

‎man/crypttab.xml‎

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -83,15 +83,15 @@
8383
underlying block device, or a specification of a block
8484
device via <literal>UUID=</literal> followed by the
8585
UUID. If the block device contains a LUKS signature,
86-
it is opened as a LUKS encrypted partition; otherwise
86+
it is opened as a LUKS encrypted partition; otherwise,
8787
it is assumed to be a raw dm-crypt partition.</para>
8888

8989
<para>The third field specifies the encryption
9090
password. If the field is not present or the password
9191
is set to none, the password has to be manually
92-
entered during system boot. Otherwise the field is
92+
entered during system boot. Otherwise, the field is
9393
interpreted as a path to a file containing the
94-
encryption password. For swap encryption
94+
encryption password. For swap encryption,
9595
<filename>/dev/urandom</filename> or the hardware
9696
device <filename>/dev/hw_random</filename> can be used
9797
as the password file; using
@@ -239,7 +239,7 @@
239239
<listitem><para>The system will not
240240
wait for the device to show up and be
241241
unlocked at boot, and not fail the
242-
boot if it doesn't show
242+
boot if it does not show
243243
up.</para></listitem>
244244
</varlistentry>
245245

@@ -282,7 +282,7 @@
282282
</variablelist>
283283

284284
<para>At early boot and when the system manager
285-
configuration is reloaded this file is translated into
285+
configuration is reloaded, this file is translated into
286286
native systemd units
287287
by <citerefentry><refentrytitle>systemd-cryptsetup-generator</refentrytitle><manvolnum>8</manvolnum></citerefentry>.</para>
288288
</refsect1>

0 commit comments

Comments
 (0)
X Tutup