From fbce11397f4d19821a9dfe66ee3ebe11cad90057 Mon Sep 17 00:00:00 2001 From: Jan Engelhardt Date: Sun, 21 Jul 2013 06:53:14 +0200 Subject: man: wording and grammar updates This includes regularly-submitted corrections to comma setting and orthographical mishaps that appeared in man/ in recent commits. --- man/systemd.xml | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) (limited to 'man/systemd.xml') diff --git a/man/systemd.xml b/man/systemd.xml index 06d2ecf6f8..1e54eac926 100644 --- a/man/systemd.xml +++ b/man/systemd.xml @@ -294,18 +294,18 @@ systemd.unit5, however some are created automatically from other configuration, dynamically from system state or - programmatically at runtime. Units may be 'active' - (meaning started, bound, plugged in, ... depending on - the unit type, see below), or 'inactive' (meaning + programmatically at runtime. Units may be "active" + (meaning started, bound, plugged in, ..., depending on + the unit type, see below), or "inactive" (meaning stopped, unbound, unplugged, ...), as well as in the process of being activated or deactivated, i.e. between the two states (these states are called - 'activating', 'deactivating'). A special 'failed' - state is available as well which is very similar to - 'inactive' and is entered when the service failed in + "activating", "deactivating"). A special "failed" + state is available as well, which is very similar to + "inactive" and is entered when the service failed in some way (process returned error code on exit, or crashed, or an operation timed out). If this state is - entered the cause will be logged, for later + entered, the cause will be logged, for later reference. Note that the various unit types may have a number of additional substates, which are mapped to the five generalized unit states described -- cgit v1.2.3-54-g00ecf