sd-bus: fix error handling when receiving invalid service name

[elogind.git] / man / coredump.conf.xml

diff --git a/man/coredump.conf.xml b/man/coredump.conf.xml
index c87cf68bc5c7d86a5ab07f3b1f06709888ee5ce7..5eb5c5f199cf5564c2cfd95604f25ff2bf14705e 100644 (file)
--- a/man/coredump.conf.xml
+++ b/man/coredump.conf.xml
@@ -1,4 +1,4 @@
-<?xml version='1.0'?> <!--*-nxml-*-->
+<?xml version='1.0'?> <!--*- Mode: nxml; nxml-child-indent: 2; indent-tabs-mode: nil -*-->
 <?xml-stylesheet type="text/xsl" href="http://docbook.sourceforge.net/release/xsl/current/xhtml/docbook.xsl"?>
 <!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
         "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
@@ -72,7 +72,7 @@
         <listitem><para>Controls where to store cores. One of
         <literal>none</literal>, <literal>external</literal>,
         <literal>journal</literal>, and <literal>both</literal>. When
-        <literal>none</literal> the coredumps will be logged but not
+        <literal>none</literal>, the coredumps will be logged but not
         stored permanently. When <literal>external</literal> (the
         default), cores will be stored in <filename>/var/lib/systemd/coredump</filename>.
         When <literal>journal</literal>, cores will be stored in
@@ -126,7 +126,7 @@
         to 15% of the total disk size). Note that the disk space used
         by coredumps might temporarily exceed these limits while
         coredumps are processed. Note that old coredumps are also
-        removed based on on time via
+        removed based on time via
         <citerefentry><refentrytitle>systemd-tmpfiles</refentrytitle><manvolnum>8</manvolnum></citerefentry>.</para></listitem>
       </varlistentry>
     </variablelist>