man: grammar fixes for introductory adverbs/phrases

1 files changed, 4 insertions, 4 deletions

diff --git a/man/systemd-journald.service.xml b/man/systemd-journald.service.xml
index 94df62fb50..3a9d804972 100644
--- a/man/systemd-journald.service.xml
+++ b/man/systemd-journald.service.xml
@@ -77,7 +77,7 @@
     necessary. Individual fields making up a log record stored in the journal may be up to 2⁶⁴-1 bytes in size.</para>
 
     <para>The journal service stores log data either persistently below <filename>/var/log/journal</filename> or in a
-    volatile way below <filename>/run/log/journal/</filename> (in the latter case it is lost at reboot). By default, log
+    volatile way below <filename>/run/log/journal/</filename> (in the latter case, it is lost at reboot). By default, log
     data is stored persistently if <filename>/var/log/journal/</filename> exists during boot, with an implicit fallback
     to volatile storage otherwise. Use <varname>Storage=</varname> in
     <citerefentry><refentrytitle>journald.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry> to configure
@@ -112,7 +112,7 @@ systemd-tmpfiles --create --prefix /var/log/journal</programlisting>
 
     <para>If <filename>systemd-journald.service</filename> is stopped, the stream connections associated with all
     services are terminated. Further writes to those streams by the service will result in <constant>EPIPE</constant>
-    errors. In order to react gracefully in this case it is recommended that programs logging to standard output/error
+    errors. In order to react gracefully in this case, it is recommended that programs logging to standard output/error
     ignore such errors. If the <constant>SIGPIPE</constant> UNIX signal handler is not blocked or turned off, such
     write attempts will also result in such process signals being generated, see
     <citerefentry project='man-pages'><refentrytitle>signal</refentrytitle><manvolnum>7</manvolnum></citerefentry>.
@@ -152,7 +152,7 @@ systemd-tmpfiles --create --prefix /var/log/journal</programlisting>
     consisting of one or more services from the rest of the system and a mechanism for improving
     performance. Multiple journal namespaces may exist simultaneously, each defining its own, independent log
     stream managed by its own instance of <command>systemd-journald</command>. Namespaces are independent of
-    each other, both in the data store and in the IPC interface. By default only a single 'default' namespace
+    each other, both in the data store and in the IPC interface. By default, only a single "default namespace
     exists, managed by <filename>systemd-journald.service</filename> (and its associated socket
     units). Additional namespaces are created by starting an instance of the
     <filename>systemd-journald@.service</filename> service template. The instance name is the namespace
@@ -169,7 +169,7 @@ systemd-tmpfiles --create --prefix /var/log/journal</programlisting>
     the native logging protocol of the journal and via stdout/stderr; the logging from all three transports
     is associated with the namespace.</para>
 
-    <para>By default only the default namespace will collect kernel and audit log messages.</para>
+    <para>By default, only the default namespace will collect kernel and audit log messages.</para>
 
     <para>The <command>systemd-journald</command> instance of the default namespace is configured through
     <filename>/etc/systemd/journald.conf</filename> (see below), while the other instances are configured