daandemeyer / rpms / systemd

Forked from rpms/systemd 2 years ago
Clone
803fb7
From 363e3817cc3462c42e837677768f10fa549966f7 Mon Sep 17 00:00:00 2001
803fb7
From: =?UTF-8?q?Zbigniew=20J=C4=99drzejewski-Szmek?= <zbyszek@in.waw.pl>
803fb7
Date: Sat, 9 May 2015 19:46:15 -0400
803fb7
Subject: [PATCH] man: fix typos in previous comimt
803fb7
803fb7
Cherry-picked from: 7703bd4d
803fb7
Resolves: #1177336
803fb7
---
803fb7
 man/journald.conf.xml | 6 +++---
803fb7
 1 file changed, 3 insertions(+), 3 deletions(-)
803fb7
803fb7
diff --git a/man/journald.conf.xml b/man/journald.conf.xml
803fb7
index abfe3130d..2cbe58bc1 100644
803fb7
--- a/man/journald.conf.xml
803fb7
+++ b/man/journald.conf.xml
803fb7
@@ -361,7 +361,7 @@
803fb7
     <title>Forwarding to traditional syslog daemons</title>
803fb7
 
803fb7
     <para>
803fb7
-      Journal events can be transfered to a different logging daemon
803fb7
+      Journal events can be transferred to a different logging daemon
803fb7
       in two different ways. In the first method, messages are
803fb7
       immediately forwarded to a socket
803fb7
       (<filename>/run/systemd/journal/syslog</filename>), where the
803fb7
@@ -375,9 +375,9 @@
803fb7
       to access all messages since the start of the system. In
803fb7
       addition, full structured meta-data is available to it. This
803fb7
       method of course is available only if the messages are stored in
803fb7
-      a journal file at all. So it will work if
803fb7
+      a journal file at all. So it will not work if
803fb7
       <varname>Storage=none</varname> is set. It should be noted that
803fb7
-      usualy the <emphasis>second</emphasis> method is used by syslog
803fb7
+      usually the <emphasis>second</emphasis> method is used by syslog
803fb7
       daemons, so the <varname>Storage=</varname> option, and not the
803fb7
       <varname>ForwardToSyslog=</varname> option, is relevant for them.
803fb7
     </para>