1 files changed, 54 insertions, 35 deletions

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