Updated the ATFH UG, Test Spec and Example UC books

with name change references.

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

4 files changed, 100 insertions, 79 deletions

diff --git a/doc/book-enea-edge-auto-fw-th-user-guide/doc/automation_framework_test_harness.xml b/doc/book-enea-edge-auto-fw-th-user-guide/doc/automation_framework_test_harness.xml
index 33acaee..8113c3a 100644
--- a/doc/book-enea-edge-auto-fw-th-user-guide/doc/automation_framework_test_harness.xml
+++ b/doc/book-enea-edge-auto-fw-th-user-guide/doc/automation_framework_test_harness.xml
@@ -5,6 +5,12 @@
   <section id="auto_fw">
     <title>Automation Framework</title>
 
+    <note>
+      <para>The NFVA and uCPE Manager terms from this document and from the
+      source code are references to the Enea Edge Runtime and the Enea Edge
+      Management application components, respectively.</para>
+    </note>
+
     <para>All Automation Framework sources are under the
     <literal>&lt;AF-TH-install-dir&gt;/automation_framework</literal>
     directory.</para>
@@ -1862,7 +1868,7 @@ Options:
         format:</emphasis><programlisting>[
  {
  "name": "Upload NFVA image on uCPE Manager",
- "args": "-f /tmp/enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2 -t xeon_d"
+ "args": "-f /tmp/enea-edge-runtime-xeon_d.ostree.tar.bz2 -t xeon_d"
  }
 ]</programlisting></para>
       </section>
@@ -1874,7 +1880,7 @@ Options:
         executed individually by running the following command line:</para>
 
         <programlisting>$ python uploadImage.py -u admin -p admin -H localhost \
--f /tmp/enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2 -t xeon_d
+-f /tmp/enea-edge-runtime-xeon_d.ostree.tar.bz2 -t xeon_d
 2020-02-28 11:38:42,754 - DEBUG: Started logging
 2020-02-28 11:38:42,755 - INFO: Upload NFVA image on uCPE Manager
 2020-02-28 11:38:43,307 - DEBUG: Login successful on host 'localhost'
@@ -1882,7 +1888,7 @@ Options:
 2020-02-28 11:41:29,148 - INFO: Verify image validation flag
 2020-02-28 11:41:29,149 - INFO: Valid flag: True
 2020-02-28 11:41:29,344 - INFO: The image \
-'enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2' was successfully uploaded
+'enea-edge-runtime-xeon_d.ostree.tar.bz2' was successfully uploaded
 2020-02-28 11:41:29,344 - INFO: Done
 2020-02-28 11:41:29,388 - DEBUG: Logging out and exiting...</programlisting>
       </section>
@@ -1933,7 +1939,7 @@ Options:
         format:</emphasis><programlisting>[
  {
  "name": "Delete NFVA image on uCPE Manager",
- "args": "-i enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2"
+ "args": "-i enea-edge-runtime-xeon_d.ostree.tar.bz2"
  }
 ]</programlisting></para>
       </section>
@@ -1945,17 +1951,17 @@ Options:
         executed individually by running the following command line:</para>
 
         <programlisting>$ python deleteUpgradeFile.py -u admin -p admin -H localhost -i \
-enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2
+enea-edge-runtime-xeon_d.ostree.tar.bz2
 2020-02-28 12:06:20,111 - DEBUG: Started logging
 2020-02-28 12:06:20,112 - INFO: Delete NFVA image from uCPE Manager
 2020-02-28 12:06:20,210 - DEBUG: Login successful on host 'localhost'
 2020-02-28 12:06:20,211 - DEBUG: Session token is: 594b2d50-5a1a-11ea-a3de-5652b3ac1c30
 2020-02-28 12:06:20,255 - INFO: The image \
-'enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2' was successfully found
+'enea-edge-runtime-xeon_d.ostree.tar.bz2' was successfully found
 2020-02-28 12:06:20,256 - INFO: The oid for \
-'enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2' image name is as follows: \
-VcpeAgent/xeon_d/enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2
-2020-02-28 12:06:20,449 - INFO: The 'enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2' \
+'enea-edge-runtime-xeon_d.ostree.tar.bz2' image name is as follows: \
+VcpeAgent/xeon_d/enea-edge-runtime-xeon_d.ostree.tar.bz2
+2020-02-28 12:06:20,449 - INFO: The 'enea-edge-runtime-xeon_d.ostree.tar.bz2' \
 image was successfully removed
 2020-02-28 12:06:20,479 - INFO: Done
 2020-02-28 12:06:20,517 - DEBUG: Logging out and exiting...</programlisting>
@@ -2016,7 +2022,7 @@ Options:
         <programlisting>[
  {
  "name": "Install and activate NFVA image on uCPE device from uCPE Manager",
- "args": "-i enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2 -t xeon_d -d inteld1521-16"
+ "args": "-i enea-edge-runtime-xeon_d.ostree.tar.bz2 -t xeon_d -d inteld1521-16"
  }
 ]</programlisting>
       </section>
@@ -2028,7 +2034,7 @@ Options:
         executed individually by running the following command line:</para>
 
         <programlisting>$ python installAndActivate.py -u admin -p admin -H localhost -i \
-enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2 -t xeon_d -d inteld1521-16
+enea-edge-runtime-xeon_d.ostree.tar.bz2 -t xeon_d -d inteld1521-16
 2020-02-28 12:36:46,137 - DEBUG: Started logging
 2020-02-28 12:36:46,138 - INFO: Install and activate NFVA image from uCPE Manager
 2020-02-28 12:36:46,288 - DEBUG: Login successful on host 'localhost'
@@ -2037,29 +2043,29 @@ enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2 -t xeon_d -d inteld1521-16
 2020-02-28 12:36:46,459 - INFO: Display info about NFVA installation \
 [inteld1521-16:1001:172.24.12.152] Install Started
 2020-02-28 12:36:46,492 - INFO: Transferring Image: \
-enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2
+enea-edge-runtime-xeon_d.ostree.tar.bz2
 2020-02-28 12:36:56,552 - INFO: Verifying Release [1]
 2020-02-28 12:37:06,599 - INFO: Verifying Release [2]
 2020-02-28 12:37:16,652 - INFO: Validating Upgrade to \
-enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2
+enea-edge-runtime-xeon_d.ostree.tar.bz2
 2020-02-28 12:37:26,713 - INFO: Validating upgrade to \
-enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2 [3]
+enea-edge-runtime-xeon_d.ostree.tar.bz2 [3]
 2020-02-28 12:37:36,770 - INFO: Validating upgrade to \
-enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2 [5]
+enea-edge-runtime-xeon_d.ostree.tar.bz2 [5]
 2020-02-28 12:37:46,819 - INFO: Validating upgrade to \
-enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2 [7]
+enea-edge-runtime-xeon_d.ostree.tar.bz2 [7]
 2020-02-28 12:37:56,879 - INFO: Validating upgrade to \
-enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2 [9]
+enea-edge-runtime-xeon_d.ostree.tar.bz2 [9]
 2020-02-28 12:38:06,920 - INFO: Validating upgrade to \
-enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2 [11]
+enea-edge-runtime-xeon_d.ostree.tar.bz2 [11]
 2020-02-28 12:38:16,975 - INFO: Validating upgrade to \
-enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2 [13]
+enea-edge-runtime-xeon_d.ostree.tar.bz2 [13]
 2020-02-28 12:38:27,019 - INFO: Validating upgrade to \
-enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2 [15]
+enea-edge-runtime-xeon_d.ostree.tar.bz2 [15]
 2020-02-28 12:38:37,091 - INFO: Validating upgrade to \
-enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2 [18]
+enea-edge-runtime-xeon_d.ostree.tar.bz2 [18]
 2020-02-28 12:38:47,133 - INFO: Validating upgrade to \
-enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2 [20]
+enea-edge-runtime-xeon_d.ostree.tar.bz2 [20]
 2020-02-28 12:38:57,186 - INFO: Waiting for release to become active
 2020-02-28 12:39:07,231 - INFO: Upgrade Request Complete
 2020-02-28 12:39:17,242 - INFO: Installation completed!
diff --git a/doc/book-enea-edge-example-usecases/doc/128t_vnf_router.xml b/doc/book-enea-edge-example-usecases/doc/128t_vnf_router.xml
index 993da22..f722aef 100644
--- a/doc/book-enea-edge-example-usecases/doc/128t_vnf_router.xml
+++ b/doc/book-enea-edge-example-usecases/doc/128t_vnf_router.xml
@@ -692,7 +692,7 @@
       <orderedlist>
         <listitem>
           <para>Select the trgt uCPE device -&gt; VNF -&gt; Instances -&gt;
-          128T -&gt; Delete.</para>
+          <literal>128T_trgt_1</literal> -&gt; Delete.</para>
         </listitem>
 
         <listitem>
@@ -707,7 +707,7 @@
         </listitem>
 
         <listitem>
-          <para>VNF -&gt; Descriptors, select all bundles -&gt;
+          <para>VNF -&gt; Descriptors, select <literal>128T</literal> -&gt;
           Offboard.</para>
         </listitem>
       </orderedlist>
diff --git a/doc/book-enea-edge-example-usecases/doc/service_chaining_128t_fortigate.xml b/doc/book-enea-edge-example-usecases/doc/service_chaining_128t_fortigate.xml
index 1412d68..3208168 100644
--- a/doc/book-enea-edge-example-usecases/doc/service_chaining_128t_fortigate.xml
+++ b/doc/book-enea-edge-example-usecases/doc/service_chaining_128t_fortigate.xml
@@ -1055,8 +1055,8 @@
         </listitem>
 
         <listitem>
-          <para>VNF -&gt; Descriptors. Select all bundles -&gt;
-          Offboard.</para>
+          <para>VNF -&gt; Select one by one, the Fortigate and 128T VNF
+          Descriptors -&gt; Offboard.</para>
         </listitem>
       </orderedlist>
     </section>
diff --git a/doc/book-enea-edge-system-test-specification/doc/sample_test_cases.xml b/doc/book-enea-edge-system-test-specification/doc/sample_test_cases.xml
index 9fa6bda..c32a784 100644
--- a/doc/book-enea-edge-system-test-specification/doc/sample_test_cases.xml
+++ b/doc/book-enea-edge-system-test-specification/doc/sample_test_cases.xml
@@ -1,10 +1,16 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
+<?xml version="1.0" encoding="UTF-8"?>
 <chapter id="sample_testcases">
   <title>Sample Test Cases</title>
 
   <para>The test cases specified in this chapter are implemented as a Sample
   Test Suite included in the TH.</para>
 
+  <note>
+    <para>The NFVA and uCPE Manager terms from this document and from the
+    source code are references to the Enea Edge Runtime and the Enea Edge
+    Management application components, respectively.</para>
+  </note>
+
   <section id="vnf_dev_net_smoke">
     <title>VNF, Device and Network Smoke Test Cases</title>
 
@@ -61,7 +67,8 @@ vnfd=&lt;VNF-Descriptor-name&gt;"</programlisting></para>
       <title>VNF - Offboard a VNF</title>
 
       <para><emphasis role="bold">Description:</emphasis> Removing a VNF
-      Descriptor from the Enea Edge Management. For details please refer to:</para>
+      Descriptor from the Enea Edge Management. For details please refer
+      to:</para>
 
       <itemizedlist>
         <listitem>
@@ -125,8 +132,8 @@ vnfd=&lt;VNF-Descriptor-name&gt;"</programlisting></para>
     <section id="device_upload_image">
       <title>Device - Upload a Edge image</title>
 
-      <para><emphasis role="bold">Description:</emphasis> Upload a Edge
-      image file onto the Enea Edge Management. For details please refer to:</para>
+      <para><emphasis role="bold">Description:</emphasis> Upload a Edge image
+      file onto the Enea Edge Management. For details please refer to:</para>
 
       <itemizedlist>
         <listitem>
@@ -150,7 +157,7 @@ vnfd=&lt;VNF-Descriptor-name&gt;"</programlisting></para>
 image_path="&lt;Image-path&gt;" -e upgrade_type="&lt;Upgrade-type&gt;"</programlisting></para>
 
       <para><emphasis role="bold">Example:</emphasis> <programlisting>ansible-playbook playbooks/uploadImage.yml -e \
-image_path="/tmp/enea-nfv-access-xeon-d6.rootfs.ostree.tar.bz2" -e \
+image_path="/tmp/enea-edge-runtime-xeon_d.ostree.tar.bz2" -e \
 upgrade_type="xeon_d"</programlisting></para>
 
       <para><emphasis role="bold">Result:</emphasis> Output of the test case
@@ -194,7 +201,7 @@ A file with the same name is already uploaded.</programlisting></para>
 image_name="&lt;Image-name&gt;"</programlisting></para>
 
       <para><emphasis role="bold">Example:</emphasis> <programlisting>ansible-playbook playbooks/deleteUpgradeFile.yml -e \
-image_name="enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2"</programlisting></para>
+image_name="enea-edge-runtime-xeon_d.ostree.tar.bz2"</programlisting></para>
 
       <para><emphasis role="bold">Result:</emphasis> Output of the test case
       run using the Test Harness:<programlisting>TASK [Remove NFVA image -- Run deleteUpgradeFile.py module from automation_framework]
@@ -255,8 +262,8 @@ localhost                  : ok=1    changed=1    unreachable=0    failed=0</pro
 
       <para><emphasis role="bold">Preconditions:</emphasis> <itemizedlist>
           <listitem>
-            <para>The device must be previously added to the Enea Edge Management
-            instance.</para>
+            <para>The device must be previously added to the Enea Edge
+            Management instance.</para>
           </listitem>
 
           <listitem>
@@ -274,7 +281,7 @@ image_name="&lt;Image_name&gt;" -e upgrade_type="&lt;Upgrade_type&gt;" -e \
 device="&lt;Device-name&gt;"</programlisting></para>
 
       <para><emphasis role="bold">Example:</emphasis> <programlisting>ansible-playbook playbooks/installAndActivate.yml -e \
-image_name="enea-nfv-access-xeon-d6.rootfs.ostree.tar.bz2" -e \
+image_name="enea-edge-runtime-xeon_d.ostree.tar.bz2" -e \
 upgrade_type=xeon_d -e device=inteld1521-16"</programlisting></para>
 
       <para><emphasis role="bold">Result:</emphasis> Output of the test case
@@ -291,12 +298,12 @@ Duplicate entry - Release already installed</programlisting></para>
     </section>
 
     <section id="dev_upload_inst_activ">
-      <title>Device - Upload, Install and Activate a Edge image on a
-      uCPE device</title>
+      <title>Device - Upload, Install and Activate a Edge image on a uCPE
+      device</title>
 
       <para><emphasis role="bold">Description:</emphasis> Upload, install and
-      activate a Edge image on a uCPE device from the Enea Edge Management. For
-      details please refer to:</para>
+      activate a Edge image on a uCPE device from the Enea Edge Management.
+      For details please refer to:</para>
 
       <itemizedlist>
         <listitem>
@@ -335,8 +342,8 @@ Duplicate entry - Release already installed</programlisting></para>
 
       <itemizedlist>
         <listitem>
-          <para>The device has to be previously added to the Enea Edge Management
-          instance.</para>
+          <para>The device has to be previously added to the Enea Edge
+          Management instance.</para>
         </listitem>
 
         <listitem>
@@ -357,8 +364,8 @@ image_name="&lt;Image-name&gt;" -e upgrade_type="&lt;Upgrade-type&gt;"</programl
 
       <para><emphasis role="bold">Example:</emphasis> <programlisting>ansible-playbook playbooks/installNFVAImage.yml -e \
 device="inteld1521-16" -e \
-image_path=/tmp/enea-nfv-access-xeon-d5.rootfs.ostree.tar.bz2 -e \
-image_name=enea-nfv-access-xeon-d5.rootfs.ostree.tar.bz2 -e \
+image_path=/tmp/enea-edge-runtime-xeon_d.ostree.tar.bz2 -e \
+image_name=enea-edge-runtime-xeon_d.ostree.tar.bz2 -e \
 upgrade_type=xeon_d</programlisting></para>
 
       <para><emphasis role="bold">Result:</emphasis> Output of the test case
@@ -388,8 +395,8 @@ upgrade_type=xeon_d</programlisting></para>
 
       <itemizedlist>
         <listitem>
-          <para>The device has to be previously added to the Enea Edge Management
-          instance.</para>
+          <para>The device has to be previously added to the Enea Edge
+          Management instance.</para>
         </listitem>
 
         <listitem>
@@ -413,7 +420,8 @@ upgrade_type=xeon_d</programlisting></para>
       <title>Device - Remove a Device</title>
 
       <para><emphasis role="bold">Description:</emphasis> Removing a uCPE
-      device from the Enea Edge Management. For details please refer to:</para>
+      device from the Enea Edge Management. For details please refer
+      to:</para>
 
       <itemizedlist>
         <listitem>
@@ -429,8 +437,8 @@ upgrade_type=xeon_d</programlisting></para>
 
       <itemizedlist>
         <listitem>
-          <para>The device has to be previously added to the Enea Edge Management
-          instance.</para>
+          <para>The device has to be previously added to the Enea Edge
+          Management instance.</para>
         </listitem>
 
         <listitem>
@@ -517,7 +525,8 @@ upgrade_type=xeon_d</programlisting></para>
 
       <itemizedlist>
         <listitem>
-          <para>A NIC is bound to a device in a Enea Edge Management instance.</para>
+          <para>A NIC is bound to a device in a Enea Edge Management
+          instance.</para>
         </listitem>
 
         <listitem>
@@ -638,8 +647,8 @@ bridge=&lt;Bridge-name&gt;"</programlisting></para>
 
       <para><emphasis role="bold">Precondition: </emphasis></para>
 
-      <para>A device must have been previously added and connected to the Enea Edge
-      Management instance.</para>
+      <para>A device must have been previously added and connected to the Enea
+      Edge Management instance.</para>
 
       <para><emphasis role="bold">Action:</emphasis> Run the
       <filename>configDPDK.yml</filename> Ansible Playbook with the
@@ -693,12 +702,12 @@ DEBUG: "{{ scriptName }} was uploaded to Enea Edge Management!"</programlisting>
     </section>
 
     <section id="cs_upload_device">
-      <title>Custom Scripts - Upload a Custom Script from the Enea Edge Management to
-      a Device</title>
+      <title>Custom Scripts - Upload a Custom Script from the Enea Edge
+      Management to a Device</title>
 
       <para><emphasis role="bold">Description:</emphasis> Upload a Custom
-      Script from the Enea Edge Management to a Device. For details please refer
-      to:</para>
+      Script from the Enea Edge Management to a Device. For details please
+      refer to:</para>
 
       <itemizedlist>
         <listitem>
@@ -719,8 +728,8 @@ DEBUG: "{{ scriptName }} was uploaded to Enea Edge Management!"</programlisting>
         </listitem>
 
         <listitem>
-          <para>A Custom Script must have been previously added to the Enea Edge
-          Management instance.</para>
+          <para>A Custom Script must have been previously added to the Enea
+          Edge Management instance.</para>
         </listitem>
       </itemizedlist>
 
@@ -745,7 +754,8 @@ DEBUG: "{{ scriptName }} was uploaded to {{ device }}!"</programlisting>
       Management</title>
 
       <para><emphasis role="bold">Description:</emphasis> Remove a Custom
-      Script from the Enea Edge Management. For details please refer to:</para>
+      Script from the Enea Edge Management. For details please refer
+      to:</para>
 
       <itemizedlist>
         <listitem>
@@ -827,7 +837,8 @@ DEBUG: "{{ scriptName }} from phase {{ phase }} was removed from {{ device }}!"<
       Store</title>
 
       <para><emphasis role="bold">Description:</emphasis> Adding an Offline
-      Config Store to the Enea Edge Management. For details please refer to:</para>
+      Config Store to the Enea Edge Management. For details please refer
+      to:</para>
 
       <itemizedlist>
         <listitem>
@@ -872,7 +883,8 @@ DEBUG: "{{ scriptName }} from phase {{ phase }} was removed from {{ device }}!"<
       Store</title>
 
       <para><emphasis role="bold">Description:</emphasis> Removing an Offline
-      Config Store from the Enea Edge Management. For details please refer to:</para>
+      Config Store from the Enea Edge Management. For details please refer
+      to:</para>
 
       <itemizedlist>
         <listitem>
@@ -887,7 +899,8 @@ DEBUG: "{{ scriptName }} from phase {{ phase }} was removed from {{ device }}!"<
       <para><emphasis role="bold">Precondition:</emphasis></para>
 
       <para>The Offline Configuration Store the user wishes to remove should
-      exist in the Enea Edge Management. If it does not, the test will say so.</para>
+      exist in the Enea Edge Management. If it does not, the test will say
+      so.</para>
 
       <para><emphasis role="bold">Action:</emphasis> Run the
       <filename>removeConfigStore.yml</filename> Ansible Playbook with the
@@ -908,8 +921,8 @@ DEBUG: "{{ scriptName }} from phase {{ phase }} was removed from {{ device }}!"<
       Configuration Store</title>
 
       <para><emphasis role="bold">Description:</emphasis> Adding a network
-      bridge to an Offline Config Store in Enea Edge Management. For details please
-      refer to:</para>
+      bridge to an Offline Config Store in Enea Edge Management. For details
+      please refer to:</para>
 
       <itemizedlist>
         <listitem>
@@ -1027,7 +1040,8 @@ INFO: Done</programlisting>
         </listitem>
 
         <listitem>
-          <para>The device should be connected to the Enea Edge Management.</para>
+          <para>The device should be connected to the Enea Edge
+          Management.</para>
         </listitem>
       </itemizedlist>
 
@@ -1078,7 +1092,8 @@ INFO: Done</programlisting>
         </listitem>
 
         <listitem>
-          <para>The device should be connected to the Enea Edge Management.</para>
+          <para>The device should be connected to the Enea Edge
+          Management.</para>
         </listitem>
       </itemizedlist>
 
@@ -1109,7 +1124,8 @@ INFO: Done</programlisting>
     <title>VNF Deployment and Lifecycle</title>
 
     <para>The following details the automated suite that handles the testing
-    of the instantiation, lifecycle and destruction of a VNF for Enea Edge.</para>
+    of the instantiation, lifecycle and destruction of a VNF for Enea
+    Edge.</para>
 
     <section id="inst_vnfi">
       <title>Instantiating a VNFI</title>
@@ -1130,8 +1146,8 @@ INFO: Done</programlisting>
       <para><emphasis role="bold">Preconditions:</emphasis> <itemizedlist>
           <listitem>
             <para>A VNF Image is onboarded and a device is added and connected
-            to the Enea Edge Management. Depending on the VNF, other steps may be
-            required.</para>
+            to the Enea Edge Management. Depending on the VNF, other steps may
+            be required.</para>
           </listitem>
 
           <listitem>
@@ -1507,8 +1523,7 @@ FortigateFWInstance tested successfully!</programlisting></para>
               </listitem>
 
               <listitem>
-                <para><olink
-                targetdoc="book_enea_edge_auto_fw_th_user_guide"
+                <para><olink targetdoc="book_enea_edge_auto_fw_th_user_guide"
                 targetptr="python_testsuite">Python Unit-Test Suite in
                 <xi:include href="../../s_docbuild/olinkdb/pardoc-names.xml"
                 xmlns:xi="http://www.w3.org/2001/XInclude"
@@ -1763,23 +1778,23 @@ LAN-to-LAN connectivity (through VPN tunnel)tested successfully!</programlisting
       </listitem>
 
       <listitem>
-        <para>The custom script should have been previously saved in 
-          <literal>&lt;AF-TH-install-dir&gt;/lab_config/customScripts</literal>.</para>
+        <para>The custom script should have been previously saved in
+        <literal>&lt;AF-TH-install-dir&gt;/lab_config/customScripts</literal>.</para>
       </listitem>
-      
+
       <listitem>
-        <para>Add device settings in the <literal>hosts</literal> Ansible inventory file under 
-          <literal>[customScriptDevice]</literal> and remove the <literal>inteld1521-1</literal>
-          example.</para>
+        <para>Add device settings in the <literal>hosts</literal> Ansible
+        inventory file under <literal>[customScriptDevice]</literal> and
+        remove the <literal>inteld1521-1</literal> example.</para>
       </listitem>
     </itemizedlist>
-    
+
     <para><emphasis role="bold">Example:</emphasis></para>
-    
+
     <programlisting>[customScriptDevice]
 inteld1521-1 ansible_host=172.24.12.73 ansible_port=22 ansible_user=root \
       ansible_pass=root</programlisting>
-    
+
     <para><emphasis role="bold">Action:</emphasis> Run
     <filename>basicTest.yml</filename> (example data for
     <filename>test_success_after_always</filename>):</para>