networkd: IPv6 router discovery - follow IPv6AcceptRouterAdvertisemnt=

[thirdparty/systemd.git] / man / systemd-coredump.xml

diff --git a/man/systemd-coredump.xml b/man/systemd-coredump.xml
index 5da3857c086f52f7105a66adcdf7297e67c97966..f1598461ef618b95535d96efda62370e9f37402a 100644 (file)
--- a/man/systemd-coredump.xml
+++ b/man/systemd-coredump.xml
@@ -67,12 +67,12 @@
     overridden to use a different setting following normal
     <citerefentry><refentrytitle>sysctl.d</refentrytitle><manvolnum>5</manvolnum></citerefentry> rules.</para>
 
-    <para>The behaviour of a specific program upon reception of a
+    <para>The behavior of a specific program upon reception of a
     signal is governed by a few factors which are described in detail
     in <citerefentry project='man-pages'><refentrytitle>core</refentrytitle><manvolnum>5</manvolnum></citerefentry>.
     In particular, the coredump will only be processed when the
     related resource limits are high enough. For programs started by
-    <command>systemd</command> those may be set using
+    <command>systemd</command>, those may be set using
     <varname>LimitCore=</varname> (see
     <citerefentry><refentrytitle>systemd.exec</refentrytitle><manvolnum>5</manvolnum></citerefentry>).
     </para>
@@ -81,7 +81,7 @@
     including a backtrace if possible, and store the core (contents of
     process' memory contents) in an external file on disk in
     <filename>/var/lib/systemd/coredump</filename>, or directly in
-    the journal. This behaviour may be modified using
+    the journal. This behavior may be modified using
     <citerefentry><refentrytitle>coredump.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry>.</para>
 
     <para>Apart from the