summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--man/journald.conf.xml2
-rw-r--r--man/systemd-run.xml6
-rw-r--r--man/systemd.kill.xml4
3 files changed, 6 insertions, 6 deletions
diff --git a/man/journald.conf.xml b/man/journald.conf.xml
index 9219b3daaf..7aa2e78ed3 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 e1e885178d..6b0189c25d 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 517a891777..ab3d28f23a 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>