8 files changed, 91 insertions, 64 deletions

diff --git a/doc/book-enea-nfv-access-getting-started/doc/device_configuration_and_provisioning.xml b/doc/book-enea-nfv-access-getting-started/doc/device_configuration_and_provisioning.xml
index 3b7c5f8..6115af0 100644
--- a/doc/book-enea-nfv-access-getting-started/doc/device_configuration_and_provisioning.xml
+++ b/doc/book-enea-nfv-access-getting-started/doc/device_configuration_and_provisioning.xml
@@ -146,11 +146,11 @@
         </listitem>
 
         <listitem>
-          <para>Type: dpdk, sr-iov</para>
+          <para>Type: dpdk</para>
         </listitem>
 
         <listitem>
-          <para>Networking-type: dpdk, SR-IOV</para>
+          <para>Networking-type: dpdk</para>
         </listitem>
 
         <listitem>
@@ -284,7 +284,7 @@
     <para>During the automatic installation process when the
     <literal>Automatic install</literal> step is reached, enter the option
     menu <literal>Customize kernel parameters</literal> and set the
-    <literal>uCPE Manager IP</literal> address. Please check <xref
+    <literal>uCPE Manager IP address</literal>. Please check <xref
     linkend="install_ena_stick" />, step 7 for how to set the uCPE Manager IP
     address at boot time. The Device ID will be listed in the installer under
     the <literal>Customize kernel parameters</literal> menu.</para>
diff --git a/doc/book-enea-nfv-access-getting-started/doc/getting_started_nfv_access.xml b/doc/book-enea-nfv-access-getting-started/doc/getting_started_nfv_access.xml
index d340e56..72c5570 100644
--- a/doc/book-enea-nfv-access-getting-started/doc/getting_started_nfv_access.xml
+++ b/doc/book-enea-nfv-access-getting-started/doc/getting_started_nfv_access.xml
@@ -374,7 +374,7 @@ sdb            8:0            0     111.8G  0  disk
              <note>
               <para>Modifying any of the Default parameters (e.g Core
               isolation, 1G huge page count, etc.) will automatically update
-              the kernel paramters string. Updating the Custom
+              the kernel parameters string. Updating the Custom
               parameters within the kernel string directly will override any
               values set previously for the Default parameters.</para>
              </note>
diff --git a/doc/book-enea-nfv-access-getting-started/doc/getting_started_ucpe_manager.xml b/doc/book-enea-nfv-access-getting-started/doc/getting_started_ucpe_manager.xml
index 2644f8a..9bee9e6 100644
--- a/doc/book-enea-nfv-access-getting-started/doc/getting_started_ucpe_manager.xml
+++ b/doc/book-enea-nfv-access-getting-started/doc/getting_started_ucpe_manager.xml
@@ -87,8 +87,7 @@
       </listitem>
 
       <listitem>
-        <para>Download the NFV Access images archive(s) from the portal:
-        <filename>Enea_NFV_Access_[release_version][release_date].zip</filename>.</para>
+        <para>Download the NFV Access images archive(s) from the portal:<filename>Enea_NFV_Access_[release_version][release_date].zip</filename>.</para>
       </listitem>
     </orderedlist>
   </section>
@@ -124,10 +123,10 @@
 
     <para>Verify that the installation has succeeded:</para>
 
-    <itemizedlist>
+    <orderedlist>
       <listitem>
         <para>Point your browser to the server machine running the uCPE
-        Manger: <literal>https://localhost</literal>.</para>
+        Manager: <literal>https://localhost</literal>.</para>
       </listitem>
 
       <listitem>
@@ -135,6 +134,6 @@
         role="bold">admin</emphasis> and password: <emphasis
         role="bold">admin</emphasis>.</para>
       </listitem>
-    </itemizedlist>
+    </orderedlist>
   </section>
 </chapter>
diff --git a/doc/book-enea-nfv-access-getting-started/doc/images/In-bandManagement.png b/doc/book-enea-nfv-access-getting-started/doc/images/In-bandManagement.png
index 5d3a505..9bb98a2 100755
--- a/doc/book-enea-nfv-access-getting-started/doc/images/In-bandManagement.png
+++ b/doc/book-enea-nfv-access-getting-started/doc/images/In-bandManagement.png
diff --git a/doc/book-enea-nfv-access-getting-started/doc/images/In-bandManagement2.png b/doc/book-enea-nfv-access-getting-started/doc/images/In-bandManagement2.png
index b6ea8b3..f1c5c91 100755
--- a/doc/book-enea-nfv-access-getting-started/doc/images/In-bandManagement2.png
+++ b/doc/book-enea-nfv-access-getting-started/doc/images/In-bandManagement2.png
diff --git a/doc/book-enea-nfv-access-getting-started/doc/images/sriov_interface_type.png b/doc/book-enea-nfv-access-getting-started/doc/images/sriov_interface_type.png
index 0a0e5d9..fbbe289 100755
--- a/doc/book-enea-nfv-access-getting-started/doc/images/sriov_interface_type.png
+++ b/doc/book-enea-nfv-access-getting-started/doc/images/sriov_interface_type.png
diff --git a/doc/book-enea-nfv-access-getting-started/doc/in_band_management.xml b/doc/book-enea-nfv-access-getting-started/doc/in_band_management.xml
index 358ed44..da6b2ee 100644
--- a/doc/book-enea-nfv-access-getting-started/doc/in_band_management.xml
+++ b/doc/book-enea-nfv-access-getting-started/doc/in_band_management.xml
@@ -8,15 +8,19 @@
   network devices, over the same network used by the traffic being
   filtered.</para>
 
-  <para>In some situations, In-band Management can represent a significant
-  risk to the administrator if certain precautions are not taken. These risks
-  center predominantly around the use of unencrypted communications channels.
-  In other cases, In-Band Management is the only option available to both
-  control and configure the device, while also allowing for data-path traffic
-  to pass over the same physical interface. This use-case is required on a
-  setup with a poor infrastructure configuration. The main requirement for
-  this use-case solution is to have all traffic pass through a defined WAN
-  physical port. Three types of traffic are mentioned:</para>
+  <para>In some situations, In-Band Management is the only option available to
+  both control and configure the device, while also allowing for data-path
+  traffic to pass over the same physical interface. In-band Management can
+  represent a significant risk to the administrator if certain precautions are
+  not taken. These risks center predominantly around the use of unencrypted
+  communications channels. However this use case (i.e. all traffic going over
+  the same physical interface) is required on a setup with a poor
+  infrastructure configuration.</para>
+
+  <para>The main requirement for this use case solution is to have all traffic
+  pass through a defined WAN physical port.</para>
+
+  <para>Three types of traffic are mentioned:</para>
 
   <itemizedlist>
     <listitem>
@@ -25,35 +29,41 @@
     </listitem>
 
     <listitem>
-      <para>VNFs configuration - like enabling or disabling features of VNF
-      like enabling/disabling firewall or VPN setup.</para>
+      <para>VNF(s) configuration - enabling or disabling features of a VNF.
+      E.g. enabling/disabling the firewall or VPN setup.</para>
     </listitem>
 
     <listitem>
-      <para>Data-path - all the other traffic that is not used in control
-      plane and needs to reach a LAN network. </para>
+      <para>Data-path - all the other traffic that is not used in the control
+      plane and needs to reach a LAN network.</para>
     </listitem>
   </itemizedlist>
 
-  <para>For use-cases where latency is very important, it is recommended to
-  use out-of-band management with a dedicated physical interface for the
-  data-path.</para>
-
-  <para>Enea solution for in-band management is based on Open vSwitch bridge
-  which controll all the traffic passing the WAN physical port. NFV Access
-  assume that the activate connection with uCPE Manager is the one to be used
-  for in-band management. Physical port used by activate connection willbe
-  attached to the in-band management WAN bridge. The communication with uCPE
-  Manager should not be affected in the sense it is re-stablished
-  automatically after in-band management activation.</para>
-
-  <para>All network traffic except the one from uCPE Manager will be sent
-  towards VNF or dropped in case there is no VNF instantiated on the NFV
-  Access device. The VNF connected to WAN bridge must be configured for
-  in-band management since the traffic from VNF manager and data-path will be
-  sent to only one port(WAN) of the VNF. Only one VNF must be connected to the
-  in-band management WAN bridge. Please make sure the VNF accept in-band
-  management.</para>
+  <note>
+    <para>For use-cases where latency is very important, it is recommended to
+    use out-of-band management with a dedicated physical interface for the
+    data-path.</para>
+  </note>
+
+  <para>The solution provided by Enea for In-band management is based upon
+  Open vSwitch bridges which control all traffic passing through the WAN
+  physical port. Note that the NFV Access platform will assume that the
+  activated connection with the uCPE Manager should be used for In-band
+  management. The physical port used by the active connection will be attached
+  to the In-band management WAN bridge. Communication with the uCPE Manager
+  should not be affected, it is reestablished automatically after In-band
+  management activation.</para>
+
+  <para>All network traffic, with the exception of any received from the uCPE
+  Manager, will be sent towards the VNF or dropped if there is no VNF
+  instantiated on the NFV Access device. The VNF connected to the WAN bridge
+  must be configured for In-band management since traffic from the VNF manager
+  and data-path will be sent to only to one port (WAN) of the VNF.</para>
+
+  <note>
+    <para>Only one VNF must be connected to the In-band management WAN bridge.
+    Please make sure the VNF accepts in-band management.</para>
+  </note>
 
   <figure>
     <title>Enea In-band Management solution</title>
@@ -67,17 +77,18 @@
   </figure>
 
   <table>
-    <title>Setup Prerequisites:</title>
+    <title>Setup Prerequisites</title>
 
     <tgroup cols="2">
       <colspec align="left" colwidth="2*" />
+
       <colspec align="left" colwidth="4*" />
 
       <tbody>
         <row>
           <entry>WAN port</entry>
 
-          <entry>physical port supported by DPDK</entry>
+          <entry>Physical port supported by DPDK</entry>
         </row>
 
         <row>
@@ -90,30 +101,47 @@
         <row>
           <entry>uCPE Manager</entry>
 
-          <entry>uCPE Manager IP address must be public(accesible for targets)
+          <entry>uCPE Manager IP address must be public (accessible for target)
           and static</entry>
         </row>
       </tbody>
     </tgroup>
   </table>
 
-  <para>In order to activate in-band management from uCPE Manager follow the
-  next steps: &lt;select the device&gt; -&gt; Configuration -&gt; OpenVSwitch
-  -&gt; Bridges -&gt; Add</para>
+  <para><emphasis role="bold">How to activate In-band Management from the uCPE
+  Manager</emphasis></para>
+
+  <orderedlist>
+    <listitem>
+      <para>Select the device.</para>
+    </listitem>
+
+    <listitem>
+      <para>Select Configuration.</para>
+    </listitem>
+
+    <listitem>
+      <para>Click OpenvSwitch.</para>
+    </listitem>
+
+    <listitem>
+      <para> Select the Bridges option, then click Add.</para>
+    </listitem>
+  </orderedlist>
 
   <table>
     <title>In-band management WAN DPDK bridge configuration</title>
 
     <tgroup cols="2">
-     <colspec align="left" colwidth="2*" />
-     <colspec align="left" colwidth="4*" />
+      <colspec align="left" colwidth="2*" />
+
+      <colspec align="left" colwidth="4*" />
 
       <tbody>
         <row>
           <entry>name</entry>
 
-          <entry>&lt;provide a name for the WAN bridge ex:
-          "ibm-wan-br"&gt;</entry>
+          <entry>Provide a name for the WAN bridge e.g. "ibm-wan-br"</entry>
         </row>
 
         <row>
@@ -125,7 +153,7 @@
         <row>
           <entry>mgmt-address</entry>
 
-          <entry>IPv4 &lt;add IP address of uCPE Manager machine&gt;</entry>
+          <entry>IPv4 (add IP address of uCPE Manager machine)</entry>
         </row>
 
         <row>
@@ -137,11 +165,11 @@
     </tgroup>
   </table>
 
-  <para>At this point the connection between device and uCPE Manager will be
-  re-created and all traffic pass through the new bridge(ibm-wan-br). User
+  <para>The connection between the device and uCPE Manager will be recreated
+  and all traffic will pass through the new bridge (ibm-wan-br). The user
   should be able to continue device configuration. The WAN port of the very
-  first instantiated VNF must be connected to the ibm-wan-br and it should
-  receive the same IP address with the WAN interfaces of the device. </para>
+  first instantiated VNF must be connected to ibm-wan-br and it should receive
+  the same IP address as the WAN interfaces of the device.</para>
 
   <figure>
     <title>Enea In-band Management solution</title>
@@ -154,11 +182,11 @@
     </mediaobject>
   </figure>
 
-  <para>The VNF can be reached on the same IP as of the device(ex.
-  https://&lt;WAN_IP&gt;).</para>
+  <para>The VNF can be reached on the same IP address as the device, e.g.
+  <literal> https://&lt;WAN_IP&gt;</literal>.</para>
 
   <note>
-    <para>In-band management bridge must be re-created in case uCPE Manager IP
-    is changed!</para>
+    <para>The In-band management bridge must be recreated each time the uCPE
+    Manager IP is changed.</para>
   </note>
 </chapter>
diff --git a/doc/book-enea-nfv-access-getting-started/doc/introduction.xml b/doc/book-enea-nfv-access-getting-started/doc/introduction.xml
index 3d8474b..46159d1 100644
--- a/doc/book-enea-nfv-access-getting-started/doc/introduction.xml
+++ b/doc/book-enea-nfv-access-getting-started/doc/introduction.xml
@@ -102,10 +102,10 @@
       </listitem>
     </itemizedlist>
 
-    <para>For additional information about the features provided in Enea NFV
-    Access, refer to the Reference Guide <remark>make this into an olink
-    reference to the Ref Guide once the olink is updated with it's new book
-    ID.</remark>provided with your release. For how to install and run Enea
+    <para>For additional information about features provided in Enea NFV
+    Access, refer to the <olink targetdoc=
+    "book_enea_nfv_access_reference_guide_intel">Enea NFV Access Reference Guide</olink>
+    provided with your release. For how to install and run Enea
     NFV Access on supported devices, please refer to <xref
     linkend="plat-release-content">
     Chapter 4, Getting Started with Enea NFV Access</xref>.</para>