From: Jan Engelhardt Date: Sun, 4 Aug 2013 23:13:28 +0000 (+0200) Subject: man: wording and grammar updates X-Git-Tag: v207~177 X-Git-Url: https://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=elogind.git;a=commitdiff_plain;h=d6ee7fa24f5437b7bb2e12f94e0cb828ed25943a;ds=sidebyside man: wording and grammar updates This includes regularly-submitted corrections to comma setting and orthographical mishaps that appeared in man/ in recent commits. --- diff --git a/man/journald.conf.xml b/man/journald.conf.xml index 9219b3daa..7aa2e78ed 100644 --- a/man/journald.conf.xml +++ b/man/journald.conf.xml @@ -355,7 +355,7 @@ 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. diff --git a/man/systemd-run.xml b/man/systemd-run.xml index e1e885178..6b0189c25 100644 --- a/man/systemd-run.xml +++ b/man/systemd-run.xml @@ -151,7 +151,7 @@ along with systemd; If not, see . - After the service's process terminated keep + 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 @@ -164,10 +164,10 @@ along with systemd; If not, see . - When terminating the scope unit send a SIGHUP + 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 - sewered. Also see SendSIGHUP= in + severed. Also see SendSIGHUP= in systemd.kill5. diff --git a/man/systemd.kill.xml b/man/systemd.kill.xml index 517a89177..ab3d28f23 100644 --- a/man/systemd.kill.xml +++ b/man/systemd.kill.xml @@ -123,8 +123,8 @@ SIGHUP (if enabled with SendSIGHUP=). If - then after a delay (configured via the - TimeoutStopSec= option) + then, after a delay (configured via the + TimeoutStopSec= option), processes still remain, the termination request is repeated with the SIGKILL