From 1708e4c1f2e3004a59ba8bb7b282f730675fb495 Mon Sep 17 00:00:00 2001
From: teastep <teastep@fbd18981-670d-0410-9b5c-8dc0c1a9a2bb>
Date: Sun, 19 Mar 2006 21:16:59 +0000
Subject: [PATCH] Clean up new XenMyWay

git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@3700 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
---
 docs/XenMyWay.xml | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/XenMyWay.xml b/docs/XenMyWay.xml
index ab370e119..aef13ba81 100644
--- a/docs/XenMyWay.xml
+++ b/docs/XenMyWay.xml
@@ -134,8 +134,8 @@
     and the firewall DomU already has three interfaces. Shorewall runs in
     Dom0, in the firewall domain and in the wireless gateway..</para>
 
-    <para>Below are the relevant configuration files for the three domains.
-    The "loopback.nloopbacks=..." entries are used to restrict the number of
+    <para>Below are the relevant configuration files for the four domains. The
+    "loopback.nloopbacks=..." entries are used to restrict the number of
     "veth<emphasis>n</emphasis>" devices that the Xen kernel creates. I use
     partitions on my hard drives for DomU storage devices.</para>
 
@@ -280,7 +280,7 @@ done</programlisting>
 
     <itemizedlist>
       <listitem>
-        <para>Allow traffic to flow unrestricted through the three bridges.
+        <para>Allow traffic to flow unrestricted through the four bridges.
         This is done by configuring the hosts connected to each bridge as a
         separate zone and relying on the implicit intra-zone ACCEPT policy to
         permit traffic through the bridge.</para>