From 6539dd7c42946d9ba5dc43028b8b5785eb2db3c5 Mon Sep 17 00:00:00 2001
From: micah <micah@riseup.net>
Date: Wed, 11 Jan 2017 15:07:35 -0500
Subject: [PATCH] Document how restart actions work (#5052)

When a user is trying to understand what is going on with a restart action, it is useful to explicitly describe how the action is run. It may seem obvious, but it is helpful to be explicit so one knows there isn't a special ExecRestart= or similar option that they could be looking at.
---
 man/systemctl.xml | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/man/systemctl.xml b/man/systemctl.xml
index acf9751..1440d71 100644
--- a/man/systemctl.xml
+++ b/man/systemctl.xml
@@ -760,18 +760,18 @@ kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
           <term><command>restart <replaceable>PATTERN</replaceable>…</command></term>
 
           <listitem>
-            <para>Restart one or more units specified on the command
-            line. If the units are not running yet, they will be
-            started.</para>
+            <para>Stop and then start one or more units specified on the
+            command line. If the units are not running yet, they will
+            be started.</para>
           </listitem>
         </varlistentry>
         <varlistentry>
           <term><command>try-restart <replaceable>PATTERN</replaceable>…</command></term>
 
           <listitem>
-            <para>Restart one or more units specified on the command
-            line if the units are running. This does nothing if units are not
-            running.</para>
+            <para>Stop and then start one or more units specified on the
+            command line if the units are running. This does nothing
+            if units are not running.</para>
             <!-- Note that we don't document condrestart here, as that is just compatibility support, and we generally
                  don't document that. -->
           </listitem>
-- 
2.7.4