From 34f57ebc813dc576afb3d2f12fa6a26e7978ce3c Mon Sep 17 00:00:00 2001

From: =?UTF-8?q?Zbigniew=20J=C4=99drzejewski-Szmek?= <zbyszek@in.waw.pl>

Date: Sat, 9 May 2015 19:46:15 -0400

Subject: [PATCH] man: fix typos in previous comimt

(cherry picked from commit 7703bd4d2874a6becc2be60e284c4a547c28320b)

---

 man/journald.conf.xml | 6 +++---

 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/man/journald.conf.xml b/man/journald.conf.xml

index abfe3130dd..2cbe58bc15 100644

--- a/man/journald.conf.xml

+++ b/man/journald.conf.xml

@@ -361,7 +361,7 @@

     <title>Forwarding to traditional syslog daemons</title>

     <para>

-      Journal events can be transfered to a different logging daemon

+      Journal events can be transferred to a different logging daemon

       in two different ways. In the first method, messages are

       immediately forwarded to a socket

       (<filename>/run/systemd/journal/syslog</filename>), where the

@@ -375,9 +375,9 @@

       to access all messages since the start of the system. In

       addition, full structured meta-data is available to it. This

       method of course is available only if the messages are stored in

-      a journal file at all. So it will work if

+      a journal file at all. So it will not work if

       <varname>Storage=none</varname> is set. It should be noted that

-      usualy the <emphasis>second</emphasis> method is used by syslog

+      usually the <emphasis>second</emphasis> method is used by syslog

       daemons, so the <varname>Storage=</varname> option, and not the

       <varname>ForwardToSyslog=</varname> option, is relevant for them.

     </para>