From 70fa9c5f1c05812c24eea0efe56f76549b40ba31 Mon Sep 17 00:00:00 2001
From: Linus Nordberg <linus@nordu.net>
Date: Mon, 12 Dec 2011 14:16:47 +0100
Subject: [PATCH] Rephrase the FTicksSyslogFacility documentation slightly.

---
 radsecproxy.conf.5.xml | 17 +++++++++--------
 1 file changed, 9 insertions(+), 8 deletions(-)

diff --git a/radsecproxy.conf.5.xml b/radsecproxy.conf.5.xml
index 0b7ee05..4db6672 100644
--- a/radsecproxy.conf.5.xml
+++ b/radsecproxy.conf.5.xml
@@ -246,16 +246,17 @@ blocktype name {
         <term><literal>FTicksSyslogFacility</literal></term>
         <listitem>
 	  <para>
-	    The FTicksSyslogFacility option is used to specify 
-	    a dedicated syslog facility for F-Ticks messages.
-	    This allows easy filtering of F-Ticks messages.
-	    By default, if FTicksSyslogFacility is not given,
-	    F-Ticks messages are written to the LogDestination. 
+	    The FTicksSyslogFacility option is used to specify a
+	    dedicated syslog facility for F-Ticks messages.  This
+	    allows for easier filtering of F-Ticks messages.  If no
+	    FTicksSyslogFacility option is given, F-Ticks messages are
+	    written to what the LogDestination option specifies.
 	  </para>
 	  <para>
-	    For F-Ticks messages always LOG_DEBUG level is used.
-	    Note that FTicksSyslogFacility value specifying a file 
-	    (via file:/// prefix) is ignored.
+	    F-Ticks messages are always logged using the log level
+	    LOG_DEBUG.  Note that specifying a file in
+	    FTicksSyslogFacility (using the file:/// prefix) is
+	    not supported.
 	  </para>
 	</listitem>
       </varlistentry>
-- 
2.1.4