summaryrefslogtreecommitdiffstats
path: root/man/systemd.generator.xml
diff options
context:
space:
mode:
authorJan Engelhardt <jengelh@inai.de>2014-08-03 07:11:12 +0200
committerJan Engelhardt <jengelh@inai.de>2015-11-06 13:00:02 +0100
commitb938cb902c3b5bca807a94b277672c64d6767886 (patch)
tree267bd1d61268865fa405b3e5a3027041f7f3a183 /man/systemd.generator.xml
parentMerge pull request #1761 from ssahani/word (diff)
downloadsystemd-b938cb902c3b5bca807a94b277672c64d6767886.tar.xz
systemd-b938cb902c3b5bca807a94b277672c64d6767886.zip
doc: correct punctuation and improve typography in documentation
Diffstat (limited to 'man/systemd.generator.xml')
-rw-r--r--man/systemd.generator.xml16
1 files changed, 8 insertions, 8 deletions
diff --git a/man/systemd.generator.xml b/man/systemd.generator.xml
index 4514c1afdf..b475ecd01d 100644
--- a/man/systemd.generator.xml
+++ b/man/systemd.generator.xml
@@ -96,7 +96,7 @@
<filename>/dev/null</filename> or an empty file can be used to
mask a generator, thereby preventing it from running. Please note
that the order of the two directories with the highest priority is
- reversed with respect to the unit load path and generators in
+ reversed with respect to the unit load path, and generators in
<filename>/run</filename> overwrite those in
<filename>/etc</filename>.</para>
@@ -187,9 +187,9 @@
<para>
Generators should only be used to generate unit files, not
any other kind of configuration. Due to the lifecycle
- logic mentioned above generators are not a good fit to
+ logic mentioned above, generators are not a good fit to
generate dynamic configuration for other services. If you
- need to generate dynamic configuration for other services
+ need to generate dynamic configuration for other services,
do so in normal services you order before the service in
question.
</para>
@@ -199,7 +199,7 @@
<para>
Since
<citerefentry project='man-pages'><refentrytitle>syslog</refentrytitle><manvolnum>3</manvolnum></citerefentry>
- is not available (see above) log messages have to be
+ is not available (see above), log messages have to be
written to <filename>/dev/kmsg</filename> instead.
</para>
</listitem>
@@ -221,17 +221,17 @@
Generators may write out dynamic unit files or just hook
unit files into other units with the usual
<filename>.wants/</filename> or
- <filename>.requires/</filename> symlinks. Often it is
+ <filename>.requires/</filename> symlinks. Often, it is
nicer to simply instantiate a template unit file from
<filename>/usr</filename> with a generator instead of
- writing out entirely dynamic unit files. Of course this
+ writing out entirely dynamic unit files. Of course, this
works only if a single parameter is to be used.
</para>
</listitem>
<listitem>
<para>
- If you are careful you can implement generators in shell
+ If you are careful, you can implement generators in shell
scripts. We do recommend C code however, since generators
delay are executed synchronously and hence delay the
entire boot if they are slow.
@@ -308,7 +308,7 @@
temporarily redirects <filename>default.target</filename> to
<filename>system-update.target</filename> if a system update is
scheduled. Since this needs to override the default user
- configuration for <filename>default.target</filename> it uses
+ configuration for <filename>default.target</filename>, it uses
argv[2]. For details about this logic, see
<ulink url="http://www.freedesktop.org/wiki/Software/systemd/SystemUpdates">Implementing
Offline System Updates</ulink>.</para>