]> git.ipfire.org Git - thirdparty/systemd.git/commitdiff
man: improvements to comma placement
authorJan Engelhardt <jengelh@inai.de>
Thu, 26 Dec 2013 01:47:44 +0000 (02:47 +0100)
committerZbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>
Thu, 26 Dec 2013 03:53:46 +0000 (22:53 -0500)
This is a recurring submission and includes corrections to:
comma placement.

42 files changed:
man/halt.xml
man/hostnamectl.xml
man/journalctl.xml
man/sd-daemon.xml
man/sd-readahead.xml
man/sd_booted.xml
man/sd_bus_message_get_cookie.xml
man/sd_bus_request_name.xml
man/sd_get_seats.xml
man/sd_is_fifo.xml
man/sd_listen_fds.xml
man/sd_login_monitor_new.xml
man/sd_notify.xml
man/sd_readahead.xml
man/sd_seat_get_active.xml
man/sd_session_is_active.xml
man/sd_uid_get_state.xml
man/sd_watchdog_enabled.xml
man/shutdown.xml
man/systemctl.xml
man/systemd-analyze.xml
man/systemd-ask-password.xml
man/systemd-cat.xml
man/systemd-cgls.xml
man/systemd-cgtop.xml
man/systemd-coredumpctl.xml
man/systemd-delta.xml
man/systemd-machine-id-setup.xml
man/systemd-notify.xml
man/systemd-tmpfiles.xml
man/systemd-tty-ask-password-agent.xml
man/systemd.device.xml
man/systemd.exec.xml
man/systemd.mount.xml
man/systemd.service.xml
man/systemd.special.xml
man/systemd.swap.xml
man/systemd.timer.xml
man/systemd.unit.xml
man/systemd.xml
man/telinit.xml
man/timedatectl.xml

index 2a13d3c635467e03be4522ae9764482ecf3e1fab..f54a8648adac7d55f660be3f27ea9aa9afc48c26 100644 (file)
         <refsect1>
                 <title>Exit status</title>
 
-                <para>On success 0 is returned, a non-zero failure
+                <para>On success, 0 is returned, a non-zero failure
                 code otherwise.</para>
         </refsect1>
 
index 29914b8c8d4d646358f003f4d044a9d3c484d375..4bc05f52ce79cc4e1088c817eea4903b9c2e2c1c 100644 (file)
         <refsect1>
                 <title>Exit status</title>
 
-                <para>On success 0 is returned, a non-zero failure
+                <para>On success, 0 is returned, a non-zero failure
                 code otherwise.</para>
         </refsect1>
 
index 2de72523ccc51da35f18a703d0385eb2e9cb1f27..6a972109c5dd5f043f697d68ee81b39ea6d1d1d4 100644 (file)
                                 matching <replaceable>GLOB</replaceable>
                                 instead of the default runtime and
                                 system journal paths. May be specified
-                                multiple times, in which case, files will
+                                multiple times, in which case files will
                                 be suitably interleaved.</para></listitem>
                         </varlistentry>
 
index 74fe435ac45ddca21767212a3bf4ab2d7a34312b..ed85debd77224f3d4a4f397011c82459f791fb7a 100644 (file)
@@ -83,7 +83,7 @@
                 <citerefentry><refentrytitle>sd_booted</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
                 <citerefentry><refentrytitle>sd_is_fifo</refentrytitle><manvolnum>3</manvolnum></citerefentry>
                 for more information about the functions
-                implemented. In addition to these functions a couple
+                implemented. In addition to these functions, a couple
                 of logging prefixes are defined as macros:</para>
 
                 <programlisting>#define SD_EMERG   "&lt;0&gt;"  /* system is unusable */
                 implementation. See the respective function man pages
                 for details.</para>
 
-                <para>In addition, for details about the algorithms
+                <para>In addition, for details about the algorithms,
                 check the liberally licensed reference implementation
                 sources:
                 <ulink url="http://cgit.freedesktop.org/systemd/systemd/plain/src/libsystemd-daemon/sd-daemon.c"/>
index f8a0a0b55925d01e5d4e42a54d0892bd522751cb..bcc46b24d8d4d391844e0962f609a69ee43d4328 100644 (file)
@@ -83,7 +83,7 @@
                 reference implementation. See the respective function
                 man pages for details.</para>
 
-                <para>In addition, for details about the algorithms
+                <para>In addition, for details about the algorithms,
                 check the liberally licensed reference implementation
                 sources:
                 <ulink url="http://cgit.freedesktop.org/systemd/systemd/plain/src/readahead/sd-readahead.c"/>
index 6f8cc95ca70dea97964ca342a4554cdfa8ba4183..1e38d2abd3fd516de90f2d4490f738ecf60cf99c 100644 (file)
                 file. Alternatively, applications consuming these APIs
                 may copy the implementation into their source
                 tree. For more details about the reference
-                implementation see
+                implementation, see
                 <citerefentry><refentrytitle>sd-daemon</refentrytitle><manvolnum>3</manvolnum></citerefentry>.</para>
 
                 <para>If the reference implementation is used as
index db344bf1beb7686a6cc96dbe80296501e323d9b9..0e3c4ba723a4eaf1ebee3ec7acc9ae2775569a7d 100644 (file)
@@ -78,7 +78,7 @@
                 <para><function>sd_bus_message_get_reply_cookie()</function>
                 returns the transaction cookie of the message the
                 specified message is a response to. When a reply
-                message is generated for a method call message its
+                message is generated for a method call message, its
                 cookie is copied over into this field. Note that while
                 every message that is transferred is identified by a
                 cookie, only response messages carry a reply cookie
@@ -96,7 +96,7 @@
                 integer. On failure, these calls return a negative
                 errno-style error code.</para>
 
-                <para>On success the cookie/reply cookie is returned
+                <para>On success, the cookie/reply cookie is returned
                 in the specified 64bit unsigned integer variable.</para>
         </refsect1>
 
index 7fae7becf4f157b01e31aab670e2e08f9a84fb95..c84b0b62fa94b38191f049a33151a06c9270c06e 100644 (file)
@@ -87,7 +87,7 @@
                                 <varname>SD_BUS_NAME_REPLACE_EXISTING</varname>
                                 flag set. If
                                 <varname>SD_BUS_NAME_ALLOW_REPLACEMENT</varname>
-                                is not set on the original request
+                                is not set on the original request,
                                 such a request by other peers will be
                                 denied.</para></listitem>
                         </varlistentry>
                 errno-style error code.</para>
 
                 <para>If <varname>SD_BUS_NAME_QUEUE</varname> is
-                specified <function>sd_bus_request_name()</function>
+                specified, <function>sd_bus_request_name()</function>
                 will return 0 when the name is already taken by
                 another peer and the client has been added to the
-                queue for the name. In that case the caller can
+                queue for the name. In that case, the caller can
                 subscribe to <literal>NameOwnerChanged</literal>
                 signals to be notified when the name is successfully
                 acquired. <function>sd_bus_request_name()</function>
index 1e55af3bdf33defbd6f7f9bba05196ad8bf5308e..f0e7655d4c97ad2dc9996a3c72cd2d7add2ee6c2 100644 (file)
         <refsect1>
                 <title>Return Value</title>
 
-                <para>On success <function>sd_get_seats()</function>,
+                <para>On success, <function>sd_get_seats()</function>,
                 <function>sd_get_sessions()</function>,
                 <function>sd_get_uids()</function> and
                 <function>sd_get_machine_names()</function> return the
index 5e79453cecd7ee97e1a655d5ac0069addec17414..4bb2236fceb4a398ddf48874bfca3bcd344a7f2a 100644 (file)
                 file. Alternatively, applications consuming these APIs
                 may copy the implementation into their source
                 tree. For more details about the reference
-                implementation see
+                implementation, see
                 <citerefentry><refentrytitle>sd-daemon</refentrytitle><manvolnum>3</manvolnum></citerefentry>.</para>
 
                 <para>These functions continue to work as described,
index aaabdbf3e84480495fa8c87cdd955a946c242d1b..6a9e082180670dd1a8f8209083b331606f6f9178 100644 (file)
                 file. Alternatively, applications consuming these APIs
                 may copy the implementation into their source
                 tree. For more details about the reference
-                implementation see
+                implementation, see
                 <citerefentry><refentrytitle>sd-daemon</refentrytitle><manvolnum>3</manvolnum></citerefentry>.</para>
 
                 <para>If the reference implementation is used as
index f439d3e7b5af3418cca958f87c910b2164feb71c..14ff241d829cd1e8a7d66231541e73c94cc06a69 100644 (file)
@@ -198,13 +198,13 @@ else {
         <refsect1>
                 <title>Return Value</title>
 
-                <para>On success
+                <para>On success,
                 <function>sd_login_monitor_new()</function>,
                 <function>sd_login_monitor_flush()</function> and
                 <function>sd_login_monitor_get_timeout()</function>
-                return 0 or a positive integer. On success
+                return 0 or a positive integer. On success,
                 <function>sd_login_monitor_get_fd()</function> returns
-                a Unix file descriptor. On success
+                a Unix file descriptor. On success,
                 <function>sd_login_monitor_get_events()</function>
                 returns a combination of <constant>POLLIN</constant>,
                 <constant>POLLOUT</constant> and suchlike. On failure,
index cd4a437f3f17a92db25a3ab9dc9266384f54c34a..d21820f67b815d17f11009a744a1294a88d0cdb0 100644 (file)
                 <constant>libsystemd-daemon</constant> <citerefentry><refentrytitle>pkg-config</refentrytitle><manvolnum>1</manvolnum></citerefentry>
                 file. Alternatively, applications consuming these APIs
                 may copy the implementation into their source tree. For
-                more details about the reference implementation see
+                more details about the reference implementation, see
                 <citerefentry><refentrytitle>sd-daemon</refentrytitle><manvolnum>3</manvolnum></citerefentry>.</para>
 
                 <para>If the reference implementation is used as
index bb01bcfd896a650f59adb03a7560b4e952585591..98272997cb13a41a9451ffa5cd2a194ce7a8823e 100644 (file)
                 <filename>sd-readahead.h</filename> files. It is
                 recommended that applications consuming this API copy
                 the implementation into their source tree. For more
-                details about the reference implementation see
+                details about the reference implementation, see
                 <citerefentry><refentrytitle>sd-readahead</refentrytitle><manvolnum>3</manvolnum></citerefentry></para>
 
                 <para>If -DDISABLE_SYSTEMD is set during compilation,
index 23d582da92134610ea5fbef962286aca309de35c..c64ba13c3a6e7f7ef10ced084d38aa3f895a4d6f 100644 (file)
         <refsect1>
                 <title>Return Value</title>
 
-                <para> On success
+                <para> On success,
                 <function>sd_seat_get_active()</function>
-                returns 0 or a positive integer. On success
+                returns 0 or a positive integer. On success,
                 <function>sd_seat_get_sessions()</function> returns
                 the number of entries in the session identifier
                 array. If the test succeeds,
index d1f1a349d947f87a44b792b7eafce29177415c26..bff6b04eab7a95510f4a824f3ee91f58e9750c3b 100644 (file)
                 <para>If the test succeeds,
                 <function>sd_session_is_active()</function> and
                 <function>sd_session_is_remote()</function> return a
-                positive integer, if it fails 0.  On success
+                positive integer; if it fails, 0.  On success,
                 <function>sd_session_get_state()</function>,
                 <function>sd_session_get_uid()</function>,
                 <function>sd_session_get_seat()</function>,
index 0faa7651e50f76df784adcf5d7c81a2289be0389..30b254c805b6273d3e3406ae0fa7299aebb14545 100644 (file)
         <refsect1>
                 <title>Return Value</title>
 
-                <para>On success
+                <para>On success,
                 <function>sd_uid_get_state()</function> returns 0 or a
                 positive integer. If the test succeeds,
                 <function>sd_uid_is_on_seat()</function> returns a
-                positive integer, if it fails
+                positive integer; if it fails,
                 0. <function>sd_uid_get_sessions()</function> and
                 <function>sd_uid_get_seats()</function> return the
                 number of entries in the returned arrays. On failure,
index 5b0d7e21cb2b4fc2f303de33f5274b5069e66d51..cad92df7af2450cb799058eefd881942ee34feab 100644 (file)
@@ -80,7 +80,7 @@
                 inherited by child processes.</para>
 
                 <para>If the <parameter>usec</parameter> parameter is
-                non-NULL <function>sd_watchdog_enabled()</function>
+                non-NULL, <function>sd_watchdog_enabled()</function>
                 will return the timeout in Âµs for the watchdog
                 logic. The service manager will usually terminate a
                 service when it did not get a notification message
@@ -94,7 +94,7 @@
                 <literal>WATCHDOG=1</literal>.</para>
 
                 <para>To enable service supervision with the watchdog
-                logic use <varname>WatchdogSec=</varname> in service
+                logic, use <varname>WatchdogSec=</varname> in service
                 files. See
                 <citerefentry><refentrytitle>systemd.service</refentrytitle><manvolnum>5</manvolnum></citerefentry>
                 for details.</para>
                 errno-style error code. If the service manager expects
                 watchdog keep-alive notification messages to be sent,
                 &gt; 0 is returned, otherwise 0 is returned. Only if
-                the return value is &gt; 0 the
+                the return value is &gt; 0, the
                 <parameter>usec</parameter> parameter is valid after
                 the call.</para>
         </refsect1>
                 variable. The call will ignore these variables if
                 <varname>$WATCHDOG_PID</varname> does containe the PID
                 of the current process, under the assumption that in
-                that case the variables were set for a different
+                that case, the variables were set for a different
                 process further up the process tree.</para>
 
-                <para>For details about the algorithm check the
+                <para>For details about the algorithm, check the
                 liberally licensed reference implementation sources:
                 <ulink url="http://cgit.freedesktop.org/systemd/systemd/plain/src/libsystemd-daemon/sd-daemon.c"/>
                 and <ulink
                 file. Alternatively, applications consuming these APIs
                 may copy the implementation into their source
                 tree. For more details about the reference
-                implementation see
+                implementation, see
                 <citerefentry><refentrytitle>sd-daemon</refentrytitle><manvolnum>3</manvolnum></citerefentry>.</para>
 
                 <para>If the reference implementation is used as
index 795fb6632881b84863d4925f074d2f4a385be0d5..27e7e87b6c6c5b7327d0952ef0a145c9c38a0651 100644 (file)
         <refsect1>
                 <title>Exit status</title>
 
-                <para>On success 0 is returned, a non-zero failure
+                <para>On success, 0 is returned, a non-zero failure
                 code otherwise.</para>
         </refsect1>
 
index 6f51135c86e90c6a3d7e9cf62deac82780e1c9ec..7c9ffc81a3fa9d890db42a50da201c520cbc1a99 100644 (file)
@@ -238,7 +238,7 @@ along with systemd; If not, see <http://www.gnu.org/licenses/>.
         applications.</para>
 
         <para><literal>ignore-requirements</literal> is similar to
-        <literal>ignore-dependencies</literal> but only causes the
+        <literal>ignore-dependencies</literal>, but only causes the
         requirement dependencies to be ignored, the ordering
         dependencies will still be honoured.</para>
         </listitem>
@@ -1383,7 +1383,7 @@ kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
     <refsect2>
       <title>Parameter Syntax</title>
 
-    <para>For unit commands the specified
+    <para>For unit commands, the specified
     <replaceable>NAME</replaceable> should be the full name of the
     unit, or an abbreviated name which is automatically extended with
     the <literal>.service</literal> suffix.
@@ -1395,7 +1395,7 @@ kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
     <programlisting># systemctl status dev-sda.device
 # systemctl status home.mount</programlisting></para>
 
-    <para>For unit file commands the
+    <para>For unit file commands, the
     specified <replaceable>NAME</replaceable> should be the full name
     of the unit file, or the absolute path to the unit file.
     <programlisting># systemctl link /path/to/foo.service</programlisting>
index 1898ca6fb194e24f407e8dcd405ac66ab64549fd..cbf59e0a1a84c77d6a44ceb55f84b74def87aae0 100644 (file)
         <refsect1>
                 <title>Exit status</title>
 
-                <para>On success 0 is returned, a non-zero failure
+                <para>On success, 0 is returned, a non-zero failure
                 code otherwise.</para>
         </refsect1>
 
index 8af328dcfafdf391c7a6648005e5c3cb9ba20f00..79902cbd9ab02fa91e702688bfbb40a3a3bdc0d0 100644 (file)
         <refsect1>
                 <title>Exit status</title>
 
-                <para>On success 0 is returned, a non-zero failure
+                <para>On success, 0 is returned, a non-zero failure
                 code otherwise.</para>
         </refsect1>
 
index ffb1dfd50b2008e6788f8a215d92946b122a3d63..ba7a2cf0c75879c8db7255875f2ea15049564bfd 100644 (file)
         <refsect1>
                 <title>Exit status</title>
 
-                <para>On success 0 is returned, a non-zero failure
+                <para>On success, 0 is returned, a non-zero failure
                 code otherwise.</para>
         </refsect1>
 
index d4520e64d7fd6556a44bf4cf30fab20eddfc0db5..955e0da37c4aee2aaced792977a592e9788851c9 100644 (file)
         <refsect1>
                 <title>Exit status</title>
 
-                <para>On success 0 is returned, a non-zero failure
+                <para>On success, 0 is returned, a non-zero failure
                 code otherwise.</para>
         </refsect1>
 
index 01a0ae216343a9f2b8c39261ae40b94a344bbece..38bddf183c31ba32791d8b4cbc683b92195d69fd 100644 (file)
         <refsect1>
                 <title>Exit status</title>
 
-                <para>On success 0 is returned, a non-zero failure
+                <para>On success, 0 is returned, a non-zero failure
                 code otherwise.</para>
         </refsect1>
 
index 9ccb67d12d9afe0c30b1d79d303dcc26e4ddf7b6..67f75d1c531cfae9109c9dcc0eae1e9c1a1815a5 100644 (file)
 
         <refsect1>
                 <title>Exit status</title>
-                <para>On success 0 is returned, a non-zero failure
+                <para>On success, 0 is returned, a non-zero failure
                 code otherwise. Not finding any matching coredumps is treated
                 as failure.
                 </para>
index 4d3ab78040c5212c239312262de127b70b958be0..ebaa3492f4ab512061aa4696a097bdc550d40f57 100644 (file)
         <refsect1>
                 <title>Exit status</title>
 
-                <para>On success 0 is returned, a non-zero failure
+                <para>On success, 0 is returned, a non-zero failure
                 code otherwise.</para>
         </refsect1>
 
index bc38d551ca39b6f9618c5bec374be00e59b23daf..7b3aa7e9a07d4e847fa5c685c7321b5c6bfab519 100644 (file)
         <refsect1>
                 <title>Exit status</title>
 
-                <para>On success 0 is returned, a non-zero failure
+                <para>On success, 0 is returned, a non-zero failure
                 code otherwise.</para>
         </refsect1>
 
index a76934649ac6ec21cefa8203f09cdca8285a5a9e..e14977d054b74fa1610f67568cad86a8ce1f5bb0 100644 (file)
         <refsect1>
                 <title>Exit status</title>
 
-                <para>On success 0 is returned, a non-zero failure
+                <para>On success, 0 is returned, a non-zero failure
                 code otherwise.</para>
         </refsect1>
 
index 9b8932c635e8b743f65bd955680512cca55fd1b2..3d11c491d4d04bc0fe70e89e44c85d4729da1bc0 100644 (file)
         <refsect1>
                 <title>Exit status</title>
 
-                <para>On success 0 is returned, a non-zero failure
+                <para>On success, 0 is returned, a non-zero failure
                 code otherwise.</para>
         </refsect1>
 
index 31a18ba4b0b527ab42a2080d9717cfa4da008098..cb5fb43d9ca68b9dce8d70733b158ed74bc10865 100644 (file)
         <refsect1>
                 <title>Exit status</title>
 
-                <para>On success 0 is returned, a non-zero failure
+                <para>On success, 0 is returned, a non-zero failure
                 code otherwise.</para>
         </refsect1>
 
index 1bbd32248fce34226dd9359068ff2190d0d7d10b..fa7074aaf1950ffa03828bfe4214c3a5ad09c64e 100644 (file)
@@ -75,7 +75,7 @@
                 udev tag (by default all block and network devices,
                 and a few others). This may be used to define
                 dependencies between devices and other units. To tag a
-                udev device use <literal>TAG+="systemd"</literal> in
+                udev device, use <literal>TAG+="systemd"</literal> in
                 the udev rules file, see
                 <citerefentry><refentrytitle>udev</refentrytitle><manvolnum>7</manvolnum></citerefentry>
                 for details.</para>
index 207592dda70c7c42198d167b4a480edc4098b726..2778497647e5dcaf75b77875e25ff14b748f8e7b 100644 (file)
                                 processes and mounts private
                                 <filename>/tmp</filename> and
                                 <filename>/var/tmp</filename>
-                                directories inside it, that are not
+                                directories inside it that are not
                                 shared by processes outside of the
                                 namespace. This is useful to secure
                                 access to temporary files of the
index bd50f352e7481d77a362fc37affcaf8d2210b572..b181949b13d96efcbf4df54d7d6bf7f5b6be285a 100644 (file)
@@ -94,7 +94,7 @@
                 in a unit file
                 <filename>home-lennart.mount</filename>. For details
                 about the escaping logic used to convert a file system
-                path to a unit name see
+                path to a unit name, see
                 <citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry>.</para>
 
                 <para>Optionally, a mount unit may be accompanied by
index 94e72df9b47a48cbc09ceb18e78317b311e79bd4..8e6c20550dbe49f7bfc0c9525e7c266b2c7e4698 100644 (file)
                                 <literal>one</literal> and
                                 <literal>two two</literal>,
                                 respectively. Since two commands are
-                                specified
+                                specified,
                                 <varname>Type=oneshot</varname> must
                                 be used.</para>
 
index 863a029fe3bd74213de0eec931353e2164360092..76bb5cdcf32e392eea245f4a2ba9b0d462657c4c 100644 (file)
                 <filename>smartcard.target</filename>,
                 <filename>sound.target</filename>.</para>
 
-                <para>In addition the following special unit is
+                <para>In addition, the following special unit is
                 understood only when systemd runs as service instance:</para>
 
                 <variablelist>
index 041123285307564d9d56793fd767fddfda3eb4b6..492309e5363adfca1428462ba277e2004f1b816d 100644 (file)
@@ -85,7 +85,7 @@
                 <filename noindex='true'>/dev/sda5</filename> must be configured in a
                 unit file <filename>dev-sda5.swap</filename>. For
                 details about the escaping logic used to convert a
-                file system path to a unit name see
+                file system path to a unit name, see
                 <citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry>.</para>
 
                 <para>All swap units automatically get the appropriate
index 484287ccf67fc3f770f6883e8f7df6039e8b4d3e..7143f9f931990e8bd269450f6ff2a7d8c5126b59 100644 (file)
                                 also include time units. Example:
                                 "OnBootSec=5h 30min" means 5 hours and
                                 30 minutes after boot-up. For details
-                                about the syntax of time spans see
+                                about the syntax of time spans, see
                                 <citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry>.</para>
 
                                 <para>If a timer configured with
                                 event expressions. See
                                 <citerefentry><refentrytitle>systemd.time</refentrytitle><manvolnum>7</manvolnum></citerefentry>
                                 for more information on the syntax of
-                                calendar event expressions. Otherwise
+                                calendar event expressions. Otherwise,
                                 the semantics are similar to
                                 <varname>OnActiveSec=</varname> and
                                 related settings.</para>
                                 <varname>OnUnitInactiveSec=</varname>
                                 and ending the time configured with
                                 <varname>AccuracySec=</varname>
-                                later. Within this time window the
+                                later. Within this time window, the
                                 expiry time will be placed at a
                                 host-specific, randomized but stable
                                 position, that is synchronized between
                                 in networked installations, as well as
                                 optimizing power consumption to
                                 suppress unnecessary CPU wake-ups. To
-                                get best accuracy set this option to
+                                get best accuracy, set this option to
                                 1us. Note that the timer is still
                                 subject to the timer slack configured
                                 via
                                 setting. See
                                 <citerefentry><refentrytitle>prctl</refentrytitle><manvolnum>2</manvolnum></citerefentry>
                                 for details. To optimize power
-                                consumption make sure to set this
+                                consumption, make sure to set this
                                 value as high as possible and as low
                                 as necessary.</para></listitem>
                         </varlistentry>
index 54d5590c81994c49f8037a6f4967c4ca6d806f9d..02445703617bbf962ed29d4e26e7510597ee8cda 100644 (file)
                                 what the unit's purpose is, followed
                                 by how it is configured, followed by
                                 any other related documentation. This
-                                option may be specified more than once
+                                option may be specified more than once,
                                 in which case the specified list of
                                 URIs is merged. If the empty string is
                                 assigned to this option, the list is
                                 <varname>Requires=</varname> and
                                 <varname>RequiresOverridable=</varname>,
                                 respectively. However, if the units
-                                listed here are not started already
+                                listed here are not started already,
                                 they will not be started and the
                                 transaction will fail immediately.
                                 </para></listitem>
                                 listed in this option will be started
                                 if the configuring unit is. However,
                                 if the listed units fail to start
-                                or cannot be added to the transaction
+                                or cannot be added to the transaction,
                                 this has no impact on the validity of
                                 the transaction as a whole. This is
                                 the recommended way to hook start-up
                                 symlinks to a
                                 <filename>.wants/</filename> directory
                                 accompanying the unit file. For
-                                details see above.</para></listitem>
+                                details, see above.</para></listitem>
                         </varlistentry>
 
                         <varlistentry>
                                 <listitem><para>Configures requirement
                                 dependencies, very similar in style to
                                 <varname>Requires=</varname>, however
-                                in addition to this behavior it also
+                                in addition to this behavior, it also
                                 declares that this unit is stopped
                                 when any of the units listed suddenly
                                 disappears. Units can suddenly,
                                 be modified to be fixed (in case one
                                 or both jobs are not a required part
                                 of the transaction). In the latter
-                                case the job that is not the required
+                                case, the job that is not the required
                                 will be removed, or in case both are
-                                not required the unit that conflicts
+                                not required, the unit that conflicts
                                 will be started and the unit that is
                                 conflicted is
                                 stopped.</para></listitem>
                                 a common pattern to include a unit
                                 name in both the
                                 <varname>After=</varname> and
-                                <varname>Requires=</varname> option in
+                                <varname>Requires=</varname> option, in
                                 which case the unit listed will be
                                 started before the unit that is
                                 configured with these options. This
                                 directives (see
                                 <citerefentry><refentrytitle>systemd.exec</refentrytitle><manvolnum>5</manvolnum></citerefentry>
                                 for details). If a unit that has this
-                                setting set is started its processes
+                                setting set is started, its processes
                                 will see the same
                                 <filename>/tmp</filename>,
                                 <filename>/tmp/var</filename> and
                                 network namespace as one listed unit
                                 that is started. If multiple listed
-                                units are already started it is not
+                                units are already started, it is not
                                 defined which namespace is
                                 joined. Note that this setting only
                                 has an effect if
                       <row>
                         <entry><literal>%p</literal></entry>
                         <entry>Prefix name</entry>
-                        <entry>For instantiated units this refers to the string before the <literal>@</literal> character of the unit name. For non-instantiated units this refers to the name of the unit with the type suffix removed.</entry>
+                        <entry>For instantiated units, this refers to the string before the <literal>@</literal> character of the unit name. For non-instantiated units, this refers to the name of the unit with the type suffix removed.</entry>
                       </row>
                       <row>
                         <entry><literal>%P</literal></entry>
                       <row>
                         <entry><literal>%h</literal></entry>
                         <entry>User home directory</entry>
-                        <entry>This is the home directory of the configured user of the unit, or (if none is set) the user running the systemd user instance. Similar to <literal>%U</literal> this specifier is not available for units run by the systemd system instance, unless the configured user is the root user.</entry>
+                        <entry>This is the home directory of the configured user of the unit, or (if none is set) the user running the systemd user instance. Similar to <literal>%U</literal>, this specifier is not available for units run by the systemd system instance, unless the configured user is the root user.</entry>
                       </row>
                       <row>
                         <entry><literal>%s</literal></entry>
                         <entry>User shell</entry>
-                        <entry>This is the shell of the configured user of the unit, or (if none is set) the user running the systemd user instance. Similar to <literal>%U</literal> this specifier is not available for units run by the systemd system instance, unless the configured user is the root user.</entry>
+                        <entry>This is the shell of the configured user of the unit, or (if none is set) the user running the systemd user instance. Similar to <literal>%U</literal>, this specifier is not available for units run by the systemd system instance, unless the configured user is the root user.</entry>
                       </row>
                       <row>
                         <entry><literal>%m</literal></entry>
index 10ce375dae7f31232099bc9686b6b80960370eb9..acba820fdfb4ff5176fb96c29fe66b19d7768ab4 100644 (file)
                 <filename>/proc</filename>.</para>
 
                 <para>For more information about the concepts and
-                ideas behind systemd please refer to the <ulink
+                ideas behind systemd, please refer to the <ulink
                 url="http://0pointer.de/blog/projects/systemd.html">Original
                 Design Document</ulink>.</para>
 
index bb8093914ac5024e5287a4cda21c15c3231ab4e6..b20a60a4ca2da2a49f209c85b30961eb6f24c365 100644 (file)
         <refsect1>
                 <title>Exit status</title>
 
-                <para>On success 0 is returned, a non-zero failure
+                <para>On success, 0 is returned, a non-zero failure
                 code otherwise.</para>
         </refsect1>
 
index afcb716e4ea6b5c94ed06181cb0a7a23dd47ee69..beda30485465c32b7ae97d3d16525f357679438c 100644 (file)
         <refsect1>
                 <title>Exit status</title>
 
-                <para>On success 0 is returned, a non-zero failure
+                <para>On success, 0 is returned, a non-zero failure
                 code otherwise.</para>
         </refsect1>