Fixing overlapping footer issues

in eg. usescase manual.

Change-Id: Iee8b37dfd725c060695f0511e84c267dbd82336d
Signed-off-by: mrpa <miruna.paun@enea.com>

4 files changed, 167 insertions, 133 deletions

diff --git a/doc/book-enea-nfv-access-example-usecases/doc/128t_vnf_router.xml b/doc/book-enea-nfv-access-example-usecases/doc/128t_vnf_router.xml
index ceae04f..9b63248 100644
--- a/doc/book-enea-nfv-access-example-usecases/doc/128t_vnf_router.xml
+++ b/doc/book-enea-nfv-access-example-usecases/doc/128t_vnf_router.xml
@@ -48,7 +48,7 @@
       <title>Use-case Setup</title>
 
       <para><emphasis role="bold">Configuring Network Interfaces on uCPE
-      devices:</emphasis><orderedlist spacing="compact">
+      devices:</emphasis><orderedlist>
           <listitem>
             <para>Log into the uCPE Manager with both username and password
             values: <literal>admin</literal>.</para>
@@ -130,9 +130,10 @@
                   <row>
                     <entry>Device ID</entry>
 
-                    <entry>Also configured during installation of the device (E.g.: Target-15).</entry>
+                    <entry>Also configured during installation of the device
+                    (E.g.: Target-15).</entry>
                   </row>
-                  
+
                   <row>
                     <entry>OK</entry>
 
@@ -151,14 +152,12 @@
 
           <listitem>
             <para>Configure the virtualization infrastructure for 128T VNF by
-            creating three OVS bridges and a host interface.</para>
+            creating three OVS bridges and a host interface:</para>
 
             <para>Add the Host Interface by selecting the trgt device, then
-            <literal>Configuration -&gt; External Interfaces -&gt; Configuration
-            -&gt; Add</literal>.</para>
-              
-              <para>Fill in the required fields with the following
-            data:</para>
+            <literal>Configuration -&gt; External Interfaces -&gt;
+            Configuration -&gt; Add</literal>, and fill in the required fields
+            with the following data:</para>
 
             <table>
               <title>Host Interface Details</title>
@@ -207,11 +206,10 @@
                 </tbody>
               </tgroup>
             </table>
-            
+
             <para>Select the trgt device then: <literal>Configuration -&gt;
-              OpenVSwitch -&gt; Bridges -&gt; Add</literal>.</para>
-            
-            <para>Fill in the required fields for each bridge with the following data from each
+            OpenVSwitch -&gt; Bridges -&gt; Add</literal>, and fill in the
+            required fields for each bridge with the following data from each
             table:</para>
 
             <table>
@@ -313,7 +311,7 @@
                 </tbody>
               </tgroup>
             </table>
-          
+
             <table>
               <title>lan_br Bridge Details</title>
 
@@ -687,8 +685,8 @@
         </listitem>
 
         <listitem>
-          <para>Select the trgt uCPE device -&gt; Configuration -&gt;
-          External Interfaces -&gt; Configuration. Select all interfaces -&gt;
+          <para>Select the trgt uCPE device -&gt; Configuration -&gt; External
+          Interfaces -&gt; Configuration. Select all interfaces -&gt;
           Delete.</para>
         </listitem>
 
@@ -699,4 +697,4 @@
       </orderedlist>
     </section>
   </section>
-</chapter>
+</chapter>
\ No newline at end of file
diff --git a/doc/book-enea-nfv-access-example-usecases/doc/forti_vnf_examples.xml b/doc/book-enea-nfv-access-example-usecases/doc/forti_vnf_examples.xml
index a56fc0a..b5e7803 100644
--- a/doc/book-enea-nfv-access-example-usecases/doc/forti_vnf_examples.xml
+++ b/doc/book-enea-nfv-access-example-usecases/doc/forti_vnf_examples.xml
@@ -27,7 +27,7 @@
 
       <para>System requirements for the uCPE device:</para>
 
-      <itemizedlist>
+      <itemizedlist spacing="compact">
         <listitem>
           <para>4 x Network Interfaces</para>
         </listitem>
@@ -43,16 +43,17 @@
 
       <para>The following file(s) are needed for this example use-case:</para>
 
-      <itemizedlist>
+      <itemizedlist spacing="compact">
         <listitem>
-          <para>FortiGate VNF image. Please contact Fortinet to get a VNF image and
-          its license file.</para>
+          <para>FortiGate VNF image. Please contact Fortinet to get a VNF
+          image and its license file.</para>
         </listitem>
 
-        <listitem><para>VNF Configuration file(s), provided with your Enea NFV Access
-        release: <filename>fortigate-basic-fw.conf</filename>.</para>
+        <listitem>
+          <para>VNF Configuration file(s), provided with your Enea NFV Access
+          release: <filename>fortigate-basic-fw.conf</filename>.</para>
         </listitem>
-        </itemizedlist>
+      </itemizedlist>
     </section>
 
     <section id="exam_setup_fortifirewall">
@@ -72,9 +73,11 @@
       <para><emphasis role="bold">Network Configuration</emphasis>:</para>
 
       <para>Since the firewall uses three External Network Interfaces, three
-      bridges need to be configured. Each bridge provides the ability to connect a physical network interface to the virtual network interface of a VM.</para>
+      bridges need to be configured. Each bridge provides the ability to
+      connect a physical network interface to the virtual network interface of
+      a VM.</para>
 
-        <para><emphasis role="bold">Setup of the uCPE device:</emphasis></para>
+      <para><emphasis role="bold">Setup of the uCPE device:</emphasis></para>
 
       <orderedlist>
         <listitem>
@@ -90,7 +93,8 @@
         </listitem>
 
         <listitem>
-          <para>Connect ETH0 to the Lab Network (for Enea uCPE Manager communications).</para>
+          <para>Connect ETH0 to the Lab Network (for Enea uCPE Manager
+          communications).</para>
         </listitem>
 
         <listitem>
@@ -103,23 +107,22 @@
           <para>Create three OVS bridges, one for each DPDK network interface
           (WAN, LAN1 and LAN2).</para>
 
-      <para>Alternatively, the firewall can be setup to use bridges as
-      connection points for the FortiGate VNF, by replacing the OVS-DPDK
-      bridges with SR-IOV connection points.</para>
-
-      <para>Please note that while previously three physical interfaces were
-      presumed necessary for VNF connection, in the case of a firewall setup
-      only two physical interfaces are required for the data path (one for WAN
-      and one for LAN).</para>
+          <para>Alternatively, the firewall can be setup to use bridges as
+          connection points for the FortiGate VNF, by replacing the OVS-DPDK
+          bridges with SR-IOV connection points.</para>
 
-      <para>Only two interfaces will be configured as DPDK, with two bridges
-      created, one for each type of connection.</para>
+          <para>Please note that while previously three physical interfaces
+          were presumed necessary for VNF connection, in the case of a
+          firewall setup only two physical interfaces are required for the
+          data path (one for WAN and one for LAN). Only two interfaces will be
+          configured as DPDK, with two bridges created, one for each type of
+          connection.</para>
 
-      <note>
-        <para>At VNF instantiation instead of assigning distinct bridges for
-        each LAN interface, only one will be used for both LAN1 and LAN2, with
-        no changes in WAN interface configuration.</para>
-      </note>
+          <note>
+            <para>At VNF instantiation instead of assigning distinct bridges
+            for each LAN interface, only one will be used for both LAN1 and
+            LAN2, with no changes in WAN interface configuration.</para>
+          </note>
         </listitem>
       </orderedlist>
 
@@ -147,8 +150,8 @@
         </listitem>
 
         <listitem>
-          <para><emphasis role="bold">Interfaces</emphasis>: Add 3
-          interfaces (wan, lan1 and lan2).</para>
+          <para><emphasis role="bold">Interfaces</emphasis>: Add 3 interfaces
+          (wan, lan1 and lan2).</para>
         </listitem>
 
         <listitem>
@@ -221,9 +224,9 @@
 
           <note>
             <para>The names of the ports used during instantiation need to be
-            the same as the ones described above, as the same names will be used in
-            the configuration files provided for this example use-case.
-            </para>
+            the same as the ones described above, as the same names will be
+            used in the configuration files provided for this example
+            use-case.</para>
           </note>
         </listitem>
       </itemizedlist>
@@ -276,7 +279,7 @@
       <para>Two uCPE devices will be needed for this setup. The system
       requirements for each uCPE device are:</para>
 
-      <itemizedlist>
+      <itemizedlist spacing="compact">
         <listitem>
           <para>4 x Network Interfaces</para>
         </listitem>
@@ -292,15 +295,17 @@
 
       <para>The following files are needed for this example use-case:</para>
 
-      <itemizedlist>
+      <itemizedlist spacing="compact">
         <listitem>
-          <para>FortiGate VNF image. Please contact Fortinet to get a VNF image and
-          its license file.</para>
+          <para>FortiGate VNF image. Please contact Fortinet to get a VNF
+          image and its license file.</para>
         </listitem>
 
-        <listitem><para>VNF Configuration file(s), provided with your Enea NFV Access
-        release: <filename>fortigate-sdwan&lt;x&gt;.conf</filename>.</para></listitem>
-        </itemizedlist>
+        <listitem>
+          <para>VNF Configuration file(s), provided with your Enea NFV Access
+          release: <filename>fortigate-sdwan&lt;x&gt;.conf</filename>.</para>
+        </listitem>
+      </itemizedlist>
     </section>
 
     <section id="forti_examsetup_uc2">
@@ -316,12 +321,12 @@
           </imageobject>
         </mediaobject>
       </figure>
-      
-       <note>
-         <para>When connecting, the uCPE devices can use a back-to-back or a VPN connection. 
-           An appropriate interface with the required capabilities needs to be chosen for 
-           this purpose.</para>
-          </note>
+
+      <note>
+        <para>When connecting, the uCPE devices can use a back-to-back or a
+        VPN connection. An appropriate interface with the required
+        capabilities needs to be chosen for this purpose.</para>
+      </note>
 
       <para><emphasis role="bold">Network Configuration:</emphasis></para>
 
@@ -333,23 +338,28 @@
       <para>Each VNF instance will have a virtual interface for VNF
       management, for the WAN network and for LAN communication.</para>
 
-      <para><emphasis role="bold">Setup of an Intel Whitebox uCPE device</emphasis>:</para>
+      <para><emphasis role="bold">Setup of an Intel Whitebox uCPE
+      device</emphasis>:</para>
 
       <orderedlist>
-           <listitem>
-          <para>Connect the <literal>VNFMgr</literal> interfaces to the Lab Network for VNF management access.</para>
+        <listitem>
+          <para>Connect the <literal>VNFMgr</literal> interfaces to the Lab
+          Network for VNF management access.</para>
         </listitem>
 
         <listitem>
-          <para>Directly connect the <literal>WAN</literal> interfaces back to back (using a cable) or connected via VPN.</para>
+          <para>Directly connect the <literal>WAN</literal> interfaces back to
+          back (using a cable) or connected via VPN.</para>
         </listitem>
 
         <listitem>
-          <para>Connect the <literal>LAN</literal> interfaces to the Test Machine.</para>
+          <para>Connect the <literal>LAN</literal> interfaces to the Test
+          Machine.</para>
         </listitem>
 
         <listitem>
-          <para>Connect the <literal>ETH0</literal> interfaces to the Lab Network (for Enea uCPE Manager communications).</para>
+          <para>Connect the <literal>ETH0</literal> interfaces to the Lab
+          Network (for Enea uCPE Manager communications).</para>
         </listitem>
 
         <listitem>
@@ -434,9 +444,11 @@
         will fail.</para>
       </note>
 
-      <para><emphasis role="bold">Instantiating the FortiGate VNF</emphasis>:</para>
+      <para><emphasis role="bold">Instantiating the FortiGate
+      VNF</emphasis>:</para>
 
-      <para>Instantiate the FortiGate VNF by filling the required fields with the following values:</para>
+      <para>Instantiate the FortiGate VNF by filling the required fields with
+      the following values:</para>
 
       <itemizedlist spacing="compact">
         <listitem>
@@ -462,8 +474,9 @@
         <listitem>
           <para><emphasis role="bold">Configuration file</emphasis>: The
           SD-WAN example configuration files provided by Enea:
-          <literal>fortigate-sdwan1.conf</literal> for the FortiGate VNF on uCPE device 1 and
-          <literal>fortigate-sdwan2.conf</literal> for the FortiGate VNF on uCPE device 2.</para>
+          <literal>fortigate-sdwan1.conf</literal> for the FortiGate VNF on
+          uCPE device 1 and <literal>fortigate-sdwan2.conf</literal> for the
+          FortiGate VNF on uCPE device 2.</para>
         </listitem>
 
         <listitem>
@@ -494,10 +507,10 @@
       the second VNF instantiation.</para>
 
       <note>
-        <para>The names of the ports used during instantiation need to be the 
-          same as the ones described above, as the same names will be used in 
-          the configuration files provided for this example use-case.</para>
-          </note>
+        <para>The names of the ports used during instantiation need to be the
+        same as the ones described above, as the same names will be used in
+        the configuration files provided for this example use-case.</para>
+      </note>
     </section>
 
     <section id="forti_test_uc2">
@@ -518,8 +531,11 @@
         Machine-2.</para>
       </note>
 
-      <para>The Test Machine connected to <literal>uCPE device 1</literal> should be able to ping the Test Machine connected to <literal>uCPE device 2</literal> in this setup, over the WAN connection.  The FortiGate VNF management interface can be accessed from a web
-      browser on the Lab Machine. For more details please see <olink
+      <para>The Test Machine connected to <literal>uCPE device 1</literal>
+      should be able to ping the Test Machine connected to <literal>uCPE
+      device 2</literal> in this setup, over the WAN connection. The FortiGate
+      VNF management interface can be accessed from a web browser on the Lab
+      Machine. For more details please see <olink
       targetdoc="book_enea_nfv_access_example_usecases"
       targetptr="fortigate_webmg">FortiGate VNF Web Management, <xi:include
       href="../../s_docbuild/olinkdb/pardoc-names.xml"
@@ -587,7 +603,10 @@ virsh console &lt;id of FortiGate VNF&gt;</programlisting>
         <orderedlist>
           <listitem>
             <para>Deploy the FortiGate Firewall in its default
-            settings.</para><remark>Maybe more info about how to do it should be added here.</remark>
+            settings.</para>
+
+            <remark>Maybe more info about how to do it should be added
+            here.</remark>
           </listitem>
 
           <listitem>
diff --git a/doc/book-enea-nfv-access-example-usecases/doc/service_chaining_128t_fortigate.xml b/doc/book-enea-nfv-access-example-usecases/doc/service_chaining_128t_fortigate.xml
index 2c256a1..4719399 100644
--- a/doc/book-enea-nfv-access-example-usecases/doc/service_chaining_128t_fortigate.xml
+++ b/doc/book-enea-nfv-access-example-usecases/doc/service_chaining_128t_fortigate.xml
@@ -55,8 +55,7 @@
 
       <mediaobject>
         <imageobject>
-          <imagedata contentwidth="600"
-                     fileref="images/trgt_servicechain.png" />
+          <imagedata contentwidth="600" fileref="images/trgt_servicechain.png" />
         </imageobject>
       </mediaobject>
     </figure>
@@ -73,9 +72,8 @@
 
           <listitem>
             <para>Add the trgt uCPE device into the uCPE Manager:
-            <literal>Devices -&gt; Manage -&gt; Add</literal>.</para>
-
-            <para>Fill in the required fields with the following data:</para>
+            <literal>Devices -&gt; Manage -&gt; Add</literal>, and fill in the
+            required fields with the following data:</para>
 
             <table>
               <title>Device Details</title>
@@ -143,13 +141,14 @@
 
                     <entry>null</entry>
                   </row>
-                  
+
                   <row>
                     <entry>Device ID</entry>
 
-                    <entry>Also configured during installation of the device (E.g.: Target-15).</entry>
+                    <entry>Also configured during installation of the device
+                    (E.g.: Target-15).</entry>
                   </row>
-                  
+
                   <row>
                     <entry>OK</entry>
 
@@ -173,9 +172,8 @@
 
             <para>Add the Host Interface by selecting the trgt device, then
             <literal>Configuration -&gt; External Interfaces -&gt;
-            Configuration -&gt; Add</literal>.</para>
-
-            <para>Fill in the required fields with the following data:</para>
+            Configuration -&gt; Add</literal>, and fill in the required fields
+            with the following data:</para>
 
             <table>
               <title>Host Interface Details</title>
@@ -262,13 +260,13 @@
 
                     <entry><literal>ibm_br</literal></entry>
                   </row>
-                  
+
                   <row>
                     <entry>ovs-bridge-type</entry>
 
                     <entry>inbandMgmt</entry>
                   </row>
-                  
+
                   <row>
                     <entry>Create</entry>
 
@@ -1004,9 +1002,9 @@
       admin, and leaving the password blank.</para>
 
       <note>
-        <para>Make sure the WAN interface of the trgt device has access to
-        the internet. The Fortigate VNF requires internet access to validate
-        the license.</para>
+        <para>Make sure the WAN interface of the trgt device has access to the
+        internet. The Fortigate VNF requires internet access to validate the
+        license.</para>
       </note>
 
       <para>In order to validate the data path connect a test machine to the
@@ -1026,8 +1024,8 @@
 
       <orderedlist>
         <listitem>
-          <para>Select the trgt uCPE device -&gt; VNF -&gt; Instances.
-          Select the 128T and Fortigate VNFs -&gt; Delete.</para>
+          <para>Select the trgt uCPE device -&gt; VNF -&gt; Instances. Select
+          the 128T and Fortigate VNFs -&gt; Delete.</para>
         </listitem>
 
         <listitem>
@@ -1036,8 +1034,8 @@
         </listitem>
 
         <listitem>
-          <para>Select the trgt uCPE device -&gt; Configuration -&gt;
-          External Interfaces -&gt; Configuration. Select all interfaces -&gt;
+          <para>Select the trgt uCPE device -&gt; Configuration -&gt; External
+          Interfaces -&gt; Configuration. Select all interfaces -&gt;
           Delete.</para>
         </listitem>
 
@@ -1048,4 +1046,4 @@
       </orderedlist>
     </section>
   </section>
-</chapter>
+</chapter>
\ No newline at end of file
diff --git a/doc/book-enea-nfv-access-example-usecases/doc/vnf_chaining.xml b/doc/book-enea-nfv-access-example-usecases/doc/vnf_chaining.xml
index b003629..b8b0d5e 100644
--- a/doc/book-enea-nfv-access-example-usecases/doc/vnf_chaining.xml
+++ b/doc/book-enea-nfv-access-example-usecases/doc/vnf_chaining.xml
@@ -29,19 +29,21 @@
           <para>4 GB of RAM memory</para>
         </listitem>
       </itemizedlist>
-      
+
       <note>
-       <para>On each uCPE device, 3 interfaces need to be DPDK compliant and one
-            of these needs to be connected back-to-back to the other uCPE
-            device. This link simulates a WAN/uplink connection. Optionally,
-            one additional device (PC/laptop) can be connected on the LAN port
-            of each branch to run LAN-to-LAN connectivity tests.</para>
+        <para>On each uCPE device, 3 interfaces need to be DPDK compliant and
+        one of these needs to be connected back-to-back to the other uCPE
+        device. This link simulates a WAN/uplink connection. Optionally, one
+        additional device (PC/laptop) can be connected on the LAN port of each
+        branch to run LAN-to-LAN connectivity tests.</para>
       </note>
 
       <para>The following files are needed for this example use-case:</para>
-      
-      <note><para>To procure the VNF image files and their licenses, please contact each respective VNF
-      provider.</para></note>
+
+      <note>
+        <para>To procure the VNF image files and their licenses, please
+        contact each respective VNF provider.</para>
+      </note>
 
       <itemizedlist>
         <listitem>
@@ -51,15 +53,26 @@
         <listitem>
           <para>Juniper vSRX VNF image file.</para>
         </listitem>
-        
-        <listitem><para>VNF Configuration files, provided with your Enea NFV Access Release:</para>
+
+        <listitem>
+          <para>VNF Configuration files, provided with your Enea NFV Access
+          Release:</para>
+
           <itemizedlist spacing="compact">
-            <listitem><para><filename>vSRX-domain-update-script</filename>.</para></listitem>
-            <listitem><para><filename>vSRX-Site&lt;x&gt;.iso</filename>.</para></listitem>
-            <listitem><para><filename>FortiFW-Site&lt;x&gt;.conf</filename>.</para></listitem>
-          </itemizedlist>      
+            <listitem>
+              <para><filename>vSRX-domain-update-script</filename>.</para>
+            </listitem>
+
+            <listitem>
+              <para><filename>vSRX-Site&lt;x&gt;.iso</filename>.</para>
+            </listitem>
+
+            <listitem>
+              <para><filename>FortiFW-Site&lt;x&gt;.conf</filename>.</para>
+            </listitem>
+          </itemizedlist>
         </listitem>
-        </itemizedlist>  
+      </itemizedlist>
     </section>
 
     <section id="exam_setup_chain">
@@ -74,7 +87,9 @@
                        fileref="images/uc_vnf_chaining.png" />
           </imageobject>
         </mediaobject>
-      </figure><remark>No info about vnf_mgmt_br?</remark>
+      </figure>
+
+      <remark>No info about vnf_mgmt_br?</remark>
 
       <para><emphasis role="bold">Network Configuration</emphasis>:</para>
 
@@ -127,8 +142,8 @@
           <note>
             <para>The networking setup (Steps 1-3) can be modeled using the
             Offline Configuration entry, so that it is automatically
-            provisioned on the uCPE device, once it gets enrolled into the management
-            system (uCPE Manager).</para>
+            provisioned on the uCPE device, once it gets enrolled into the
+            management system (uCPE Manager).</para>
           </note>
         </listitem>
       </orderedlist>
@@ -142,8 +157,8 @@
 
           <itemizedlist spacing="compact">
             <listitem>
-              <para>The Flavor selected must have at least 2 vCPUs and 4 GB RAM since vSRX is 
-                quite resource consuming.</para>
+              <para>The Flavor selected must have at least 2 vCPUs and 4 GB
+              RAM since vSRX is quite resource consuming.</para>
 
               <para>Tested in-house with 4 vCPUs/ 6 GB RAM.</para>
             </listitem>
@@ -154,19 +169,21 @@
             </listitem>
 
             <listitem>
-              <para>Select <literal>ISO</literal> as the Cloud-Init Datasource in the Cloud-Init 
-                tab.</para>
+              <para>Select <literal>ISO</literal> as the Cloud-Init Datasource
+              in the Cloud-Init tab.</para>
             </listitem>
+
             <listitem>
-            <para>Select <literal>cdrom</literal> as the Cloud-Init Disk Type in the Cloud-Init 
-              tab.</para></listitem>
+              <para>Select <literal>cdrom</literal> as the Cloud-Init Disk
+              Type in the Cloud-Init tab.</para>
+            </listitem>
           </itemizedlist>
         </listitem>
 
         <listitem>
           <para>Onboard Fortigate FW using the VNF Onboarding Wizard:</para>
 
-          <itemizedlist>
+          <itemizedlist spacing="compact">
             <listitem>
               <para>The Flavor selected can be quite light in resource
               consumption, e.g. 1 CPU and 1 GB RAM.</para>
@@ -178,12 +195,14 @@
             </listitem>
 
             <listitem>
-              <para>Select <literal>ConfigDrive</literal> as the Cloud-Init Datasource in the 
-                Cloud-Init tab.</para>
+              <para>Select <literal>ConfigDrive</literal> as the Cloud-Init
+              Datasource in the Cloud-Init tab.</para>
             </listitem>
 
-                        <listitem><para>Select <literal>cdrom</literal> as the Cloud-Init Disk 
-                          Type in the Cloud-Init tab.</para></listitem>
+            <listitem>
+              <para>Select <literal>cdrom</literal> as the Cloud-Init Disk
+              Type in the Cloud-Init tab.</para>
+            </listitem>
 
             <listitem>
               <para>Add <literal>license</literal> as the Cloud-Init content
@@ -250,8 +269,8 @@
 
           <itemizedlist>
             <listitem>
-              <para>Use <filename>FortiFW-Site1.conf</filename> as the Cloud-Init
-              file.</para>
+              <para>Use <filename>FortiFW-Site1.conf</filename> as the
+              Cloud-Init file.</para>
             </listitem>
 
             <listitem>
@@ -262,7 +281,7 @@
             <listitem>
               <para>Add virtual interfaces:</para>
 
-              <itemizedlist>
+              <itemizedlist spacing="compact">
                 <listitem>
                   <para>Management interface added to
                   <literal>vnf_mgmt_br</literal>.</para>
@@ -290,8 +309,8 @@
       </orderedlist>
 
       <para>At this point the service will be up and running on Site1. Repeat
-      the steps to instantiate a VNF for Site2, by changing the configuration files
-      accordingly.</para>
+      the steps to instantiate a VNF for Site2, by changing the configuration
+      files accordingly.</para>
 
       <para>After the service is deployed on both branches, the VPN tunnel is
       established and LAN to LAN visibility can be verified by connecting one