From 1c74bdc70f6989afba9ad5caf70ee07591c91439 Mon Sep 17 00:00:00 2001
From: teastep <teastep@fbd18981-670d-0410-9b5c-8dc0c1a9a2bb>
Date: Tue, 8 Mar 2005 19:51:15 +0000
Subject: [PATCH] Documentation updates for error messages

git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@1989 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
---
 Shorewall-docs2/ErrorMessages.xml | 9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)

diff --git a/Shorewall-docs2/ErrorMessages.xml b/Shorewall-docs2/ErrorMessages.xml
index ed9f028ea..5e84c73b7 100644
--- a/Shorewall-docs2/ErrorMessages.xml
+++ b/Shorewall-docs2/ErrorMessages.xml
@@ -530,10 +530,11 @@
           <para>This almost always means that you are trying to use a
           Shorewall feature that your iptables and/or kernel do not support.
           Beginning with version 2.2.0, Shorewall follows this message with a
-          copy of the rule that is failing. Most commonly, the problem is that
-          one of the match types (keyword following "-m" in the command) isn't
-          supported by your iptables/kernel. The output of "shorewall check"
-          shows you what your iptables/kernel support:</para>
+          copy of the iptables command that is failing. Most commonly, the
+          problem is that one of the match types (keyword following "-m" in
+          the command) isn't supported by your iptables/kernel. The output of
+          "shorewall check" shows you what your iptables/kernel
+          support:</para>
 
           <programlisting>gateway:~# shorewall check
 Loading /usr/share/shorewall/functions...