diff --git a/man/systemctl.xml b/man/systemctl.xml
index 6b2798ecde..ae0b046f7b 100644
--- a/man/systemctl.xml
+++ b/man/systemctl.xml
@@ -239,29 +239,31 @@ Jan 12 10:46:45 example.com bluetoothd[8900]: Current Time Service could not be
Jan 12 10:46:45 example.com bluetoothd[8900]: gatt-time-server: Input/output error (5)
- The dot ("●") uses color on supported terminals to summarize the unit state at a glance. Along with
- its color, its shape varies according to its state: inactive or
- maintenance is a white circle ("○"), active is a green dot ("●"),
- deactivating is a white dot, failed or error is
- a red cross ("×"), and reloading is a green clockwise circle arrow ("↻").
-
+ The dot ("●") uses color on supported terminals to summarize the unit state at a
+ glance. Along with its color, its shape varies according to its state:
+ inactive or maintenance is a white circle ("○"),
+ active is a green dot ("●"), deactivating is a white dot,
+ failed or error is a red cross ("×"), and
+ reloading is a green clockwise circle arrow ("↻").
- The "Loaded:" line in the output will show loaded if the unit has been loaded into
- memory. Other possible values for "Loaded:" include: error if there was a problem
- loading it, not-found if no unit file was found for this unit,
- bad-setting if an essential unit file setting could not be parsed and
- masked if the unit file has been masked. Along with showing the path to the unit file,
- this line will also show the enablement state. Enabled commands start at boot. See the full table of
- possible enablement states — including the definition of masked — in the documentation
- for the is-enabled command.
+ The "Loaded:" line in the output will show loaded if the unit has been
+ loaded into memory. Other possible values for "Loaded:" include: error if
+ there was a problem loading it, not-found if no unit file was found for this
+ unit, bad-setting if an essential unit file setting could not be parsed and
+ masked if the unit file has been masked. Along with showing the path to the
+ unit file, this line will also show the enablement state. Enabled units are included in the
+ dependency network between units, and thus are started at boot or via some other form of
+ activation. See the full table of possible enablement states — including the definition of
+ masked — in the documentation for the is-enabled command.
The "Active:" line shows active state. The value is usually active or
- inactive. Active could mean started, bound, plugged in, etc depending on the unit type.
- The unit could also be in process of changing states, reporting a state of activating or
- deactivating. A special failed state is entered when the service
- failed in some way, such as a crash, exiting with an error code or timing out. If the failed state is
- entered the cause will be logged for later reference.
+ inactive. Active could mean started, bound, plugged in, etc depending on the
+ unit type. The unit could also be in process of changing states, reporting a state of
+ activating or deactivating. A special
+ failed state is entered when the service failed in some way, such as a crash,
+ exiting with an error code or timing out. If the failed state is entered the cause will be logged
+ for later reference.