From 3a2da7380858756739c154faeb477a36463ca433 Mon Sep 17 00:00:00 2001
From: Tom Eastep <teastep@shorewall.net>
Date: Sat, 15 Jan 2011 15:56:20 -0800
Subject: [PATCH] Document INCLUDE changes in the basics doc

---
 docs/configuration_file_basics.xml | 18 +++++++++++++++---
 1 file changed, 15 insertions(+), 3 deletions(-)

diff --git a/docs/configuration_file_basics.xml b/docs/configuration_file_basics.xml
index 0ca0c5805..57431db7a 100644
--- a/docs/configuration_file_basics.xml
+++ b/docs/configuration_file_basics.xml
@@ -694,7 +694,7 @@ ACCEPT      net:\
       </listitem>
     </itemizedlist>
 
-    <para>When used in these scripts, the included files are copied into the
+    <para>When used in these scripts, the INCLUDEd files are copied into the
     compiled firewall script.</para>
 
     <caution>
@@ -713,8 +713,20 @@ ACCEPT      net:\
       <filename>params</filename> file from being copied into the compiled
       script. With EXPORTPARAMS=No, it is perfectly okay to use INCLUDE in the
       <filename>params</filename> file. Note that with Shorewall 4.4.17 and
-      later, the variables set at compile time are available at run-time even
-      with EXPORTPARAMS=No.</para>
+      later: </para>
+
+      <itemizedlist>
+        <listitem>
+          <para>The variables set at compile time are available at run-time
+          even with EXPORTPARAMS=No.</para>
+        </listitem>
+
+        <listitem>
+          <para>The INCLUDE directive in the <filename>params</filename> file
+          is processed at compile time and the INCLUDEd file is copied into
+          the compiled script.</para>
+        </listitem>
+      </itemizedlist>
     </caution>
 
     <example id="include">