man: remove some trailing whitespace

diff --git a/man/coredump.conf.xml b/man/coredump.conf.xml
index 5f1b4ce028cc22e0e63c045433dba21aa63de958..d0f46cfe053fad15dd0fe87caaae8b1ad1783c7e 100644 (file)
--- a/man/coredump.conf.xml
+++ b/man/coredump.conf.xml
@@ -87,7 +87,7 @@
         which will be processed. Core dumps exceeding this size
         may be stored, but the backtrace will not be generated.
         Like other sizes in this same config file, the usual
-        suffixes to the base of 1024 are allowed (B, K, M, 
+        suffixes to the base of 1024 are allowed (B, K, M,
         G, T, P, and E.)</para>
 
         <para>Setting <varname>Storage=none</varname> and <varname>ProcessSizeMax=0</varname>
@@ -100,7 +100,7 @@
         <term><varname>JournalSizeMax=</varname></term>
 
         <listitem><para>The maximum (uncompressed) size in bytes of a
-        core to be saved. Unit suffixes are allowed just as in 
+        core to be saved. Unit suffixes are allowed just as in
         <option>ProcessSizeMax=</option></para></listitem>.
       </varlistentry>
 

diff --git a/man/journald.conf.xml b/man/journald.conf.xml
index 06583d5ed3f42838387972608deb2d0049c076e3..4b0dd90cbbdb7893ff4fb8fbf85b256c28929290 100644 (file)
--- a/man/journald.conf.xml
+++ b/man/journald.conf.xml
@@ -78,8 +78,8 @@
         the kernel log buffer, or a syslog socket will still work). Defaults to <literal>auto</literal> in
         the default journal namespace, and <literal>persistent</literal> in all others.</para>
 
-        <para>Note that journald will initially use volatile storage, until a call to 
-        <command>journalctl --flush</command> (or sending <constant>SIGUSR1</constant> to journald) will cause 
+        <para>Note that journald will initially use volatile storage, until a call to
+        <command>journalctl --flush</command> (or sending <constant>SIGUSR1</constant> to journald) will cause
         it to switch to persistent logging (under the conditions mentioned above). This is done automatically
         on boot via <literal>systemd-journal-flush.service</literal>.</para>
 

diff --git a/man/systemd-journald.service.xml b/man/systemd-journald.service.xml
index b66e6ea8ebcdf3214a083e3e5dc33fff800a1927..e797ca6e00a479429cf3196ffb699a2373b3cae8 100644 (file)
--- a/man/systemd-journald.service.xml
+++ b/man/systemd-journald.service.xml
@@ -80,8 +80,8 @@
     <citerefentry><refentrytitle>journald.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry> to configure
     where log data is placed, independently of the existence of <filename>/var/log/journal/</filename>.</para>
 
-    <para>Note that journald will initially use volatile storage, until a call to 
-    <command>journalctl --flush</command> (or sending <constant>SIGUSR1</constant> to journald) will cause 
+    <para>Note that journald will initially use volatile storage, until a call to
+    <command>journalctl --flush</command> (or sending <constant>SIGUSR1</constant> to journald) will cause
     it to switch to persistent logging (under the conditions mentioned above). This is done automatically
     on boot via <literal>systemd-journal-flush.service</literal>.</para>