hwdb: remove too broad PNP* match from 20-acpi-vendor.hwdb

[elogind.git] / man / systemctl.xml

diff --git a/man/systemctl.xml b/man/systemctl.xml
index 84a149c3d086d61c9a5974bd72ef4a3dfdcddc63..07e7363ab2cf1f9f4e568dea884beee21f940b63 100644 (file)
--- a/man/systemctl.xml
+++ b/man/systemctl.xml
@@ -382,8 +382,8 @@ along with systemd; If not, see <http://www.gnu.org/licenses/>.
         <listitem>
           <para>When used with <command>kill</command>, choose which
           signal to send to selected processes. Must be one of the
-          well known signal specifiers such as SIGTERM, SIGINT or
-          SIGSTOP. If omitted defaults to
+          well known signal specifiers such as <constant>SIGTERM</constant>, <constant>SIGINT</constant> or
+          <constant>SIGSTOP</constant>. If omitted defaults to
           <option>SIGTERM</option>.</para>
         </listitem>
       </varlistentry>
@@ -453,7 +453,7 @@ along with systemd; If not, see <http://www.gnu.org/licenses/>.
 
         <listitem>
           <para>Execute operation remotely. Specify a hostname, or
-          username and hostname separated by @, to connect to. This
+          username and hostname separated by <literal>@</literal>, to connect to. This
           will use SSH to talk to the remote systemd
           instance.</para>
         </listitem>
@@ -819,9 +819,8 @@ kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
 
         <listitem>
           <para>Show manual pages for one or more units, if
-          available. If a PID is passed the manual pages for the unit
-          the process of the PID belongs to is
-          shown.</para>
+          available. If a PID is given the manual pages for the unit
+          the process belongs to are shown.</para>
         </listitem>
       </varlistentry>
 
@@ -859,13 +858,13 @@ kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
           created the systemd configuration is reloaded (in a way that
           is equivalent to <command>daemon-reload</command>) to ensure
           the changes are taken into account immediately. Note that
-          this does not have the effect that any of the units enabled
-          are also started at the same time. If this is desired a
-          separate <command>start</command> command must be invoked
-          for the unit. Also note that in case of instance enablement,
-          symlinks named same as instances are created in install
-          location, however they all point to the same template unit
-          file.</para>
+          this does <emphasis>not</emphasis> have the effect of also
+          starting starting any of the units beeing enabled. If this
+          is desired a separate <command>start</command> command must
+          be invoked for the unit. Also note that in case of instance
+          enablement, symlinks named same as instances are created in
+          install location, however they all point to the same
+          template unit file.</para>
 
           <para>This command will print the actions executed. This
           output may be suppressed by passing <option>--quiet</option>.