[systemd-commits] 2 commits - man/journald.conf.xml man/systemd.kill.xml man/systemd-machined.service.xml man/systemd-run.xml
Zbigniew JÄdrzejewski-Szmek
zbyszek at kemper.freedesktop.org
Sun Aug 4 18:47:40 PDT 2013
man/journald.conf.xml | 2 +-
man/systemd-machined.service.xml | 2 +-
man/systemd-run.xml | 6 +++---
man/systemd.kill.xml | 4 ++--
4 files changed, 7 insertions(+), 7 deletions(-)
New commits:
commit 9cfda9644094e8d0fdd9f8b74ade9868514a6a70
Author: Michael Scherer <misc at zarb.org>
Date: Sun Aug 4 22:36:42 2013 +0200
man: fix typo in documentation of systemd-machined
diff --git a/man/systemd-machined.service.xml b/man/systemd-machined.service.xml
index abe221a..352b4a0 100644
--- a/man/systemd-machined.service.xml
+++ b/man/systemd-machined.service.xml
@@ -45,7 +45,7 @@
<refnamediv>
<refname>systemd-machined.service</refname>
<refname>systemd-machined</refname>
- <refpurpose>Virtual machine and container registartion manager</refpurpose>
+ <refpurpose>Virtual machine and container registration manager</refpurpose>
</refnamediv>
<refsynopsisdiv>
commit d6ee7fa24f5437b7bb2e12f94e0cb828ed25943a
Author: Jan Engelhardt <jengelh at inai.de>
Date: Mon Aug 5 01:13:28 2013 +0200
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 9219b3d..7aa2e78 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 e1e8851..6b0189c 100644
--- a/man/systemd-run.xml
+++ b/man/systemd-run.xml
@@ -151,7 +151,7 @@ along with systemd; If not, see <http://www.gnu.org/licenses/>.
<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
@@ -164,10 +164,10 @@ along with systemd; If not, see <http://www.gnu.org/licenses/>.
<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
- 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>
diff --git a/man/systemd.kill.xml b/man/systemd.kill.xml
index 517a891..ab3d28f 100644
--- a/man/systemd.kill.xml
+++ b/man/systemd.kill.xml
@@ -123,8 +123,8 @@
<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>
More information about the systemd-commits
mailing list