From f4f3dbc70b6df83a75d9182ea160b82a2d273f1f Mon Sep 17 00:00:00 2001
From: Michael Meckelein <mmeckelein@hq.adiscon.com>
Date: Fri, 18 Jan 2008 14:35:58 +0000
Subject: small text change

---
 doc/rsyslog_conf.html | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

(limited to 'doc/rsyslog_conf.html')

diff --git a/doc/rsyslog_conf.html b/doc/rsyslog_conf.html
index 2d79f249..fe813ab3 100644
--- a/doc/rsyslog_conf.html
+++ b/doc/rsyslog_conf.html
@@ -237,8 +237,7 @@ In its current form, output channels primarily provide the ability to size-limit
 an output file. To do so, specify a maximum size. When this size is reached, 
 rsyslogd will execute the action-on-max-size command and then reopen the file 
 and retry. The command should be something like a 
-<a href="log_rotation_fix_size.html">log rotation script</a> or a 
-similar thing.</p>
+<a href="log_rotation_fix_size.html">log rotation script</a> or a similar thing.</p>
 <p>If there is no action-on-max-size command or the command did not resolve the 
 situation, the file is closed and never reopened by rsyslogd (except, of course, 
 by huping it). This logic was integrated when we first experienced severe issues 
-- 
cgit