chiark / gitweb /
man: wording and grammar updates
authorJan Engelhardt <jengelh@inai.de>
Sun, 4 Aug 2013 23:13:28 +0000 (01:13 +0200)
committerZbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>
Mon, 5 Aug 2013 01:46:27 +0000 (21:46 -0400)
This includes regularly-submitted corrections to comma setting and
orthographical mishaps that appeared in man/ in recent commits.

man/journald.conf.xml
man/systemd-run.xml
man/systemd.kill.xml

index 9219b3daaf081b4dd5357fd530bf74c2a35e8f13..7aa2e78ed34bf0177674acfebcf1981b49691057 100644 (file)
                                 syncing is unconditionally done
                                 immediately after a log message of
                                 priority CRIT, ALERT or EMERG has been
                                 syncing is unconditionally done
                                 immediately after a log message of
                                 priority CRIT, ALERT or EMERG has been
-                                logged, this setting hence applies
+                                logged. This setting hence applies
                                 only to messages of the levels ERR,
                                 WARNING, NOTICE, INFO, DEBUG. The
                                 default timeout is 5 minutes.
                                 only to messages of the levels ERR,
                                 WARNING, NOTICE, INFO, DEBUG. The
                                 default timeout is 5 minutes.
index e1e885178d9b915169d5ea6c36e373d4a42162f5..6b0189c25d60f4851d01bbc7d0e19b44f8dfbc6d 100644 (file)
@@ -151,7 +151,7 @@ along with systemd; If not, see <http://www.gnu.org/licenses/>.
       <varlistentry>
         <term><option>--remain-after-exit</option></term>
 
       <varlistentry>
         <term><option>--remain-after-exit</option></term>
 
-        <listitem><para>After the service's process terminated keep
+        <listitem><para>After the service's process has terminated, keep
         the service around until it is explicitly stopped. This is
         useful to collect runtime information about the service after
         it finished running. Also see
         the service around until it is explicitly stopped. This is
         useful to collect runtime information about the service after
         it finished running. Also see
@@ -164,10 +164,10 @@ along with systemd; If not, see <http://www.gnu.org/licenses/>.
       <varlistentry>
         <term><option>--send-sighup</option></term>
 
       <varlistentry>
         <term><option>--send-sighup</option></term>
 
-        <listitem><para>When terminating the scope unit send a SIGHUP
+        <listitem><para>When terminating the scope unit, send a SIGHUP
         immediately after SIGTERM. This is useful to indicate to
         shells and shell-like processes that the connection has been
         immediately after SIGTERM. This is useful to indicate to
         shells and shell-like processes that the connection has been
-        sewered. Also see <varname>SendSIGHUP=</varname> in
+        severed. Also see <varname>SendSIGHUP=</varname> in
         <citerefentry><refentrytitle>systemd.kill</refentrytitle><manvolnum>5</manvolnum></citerefentry>.
         </para>
         </listitem>
         <citerefentry><refentrytitle>systemd.kill</refentrytitle><manvolnum>5</manvolnum></citerefentry>.
         </para>
         </listitem>
index 517a891777658968b7b1426414f5a36d9f5832c0..ab3d28f23a8df490cad1d8ff63853bca2d3ad148 100644 (file)
                                 <constant>SIGHUP</constant> (if
                                 enabled with
                                 <varname>SendSIGHUP=</varname>). If
                                 <constant>SIGHUP</constant> (if
                                 enabled with
                                 <varname>SendSIGHUP=</varname>). If
-                                then after a delay (configured via the
-                                <varname>TimeoutStopSec=</varname> option)
+                                then, after a delay (configured via the
+                                <varname>TimeoutStopSec=</varname> option),
                                 processes still remain, the
                                 termination request is repeated with
                                 the <constant>SIGKILL</constant>
                                 processes still remain, the
                                 termination request is repeated with
                                 the <constant>SIGKILL</constant>