Updated pictures and titles with CapitalizationEnea_NFV_Access_2.3.0_RC3

in Getting Started.

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

7 files changed, 49 insertions, 53 deletions

diff --git a/doc/book-enea-nfv-access-getting-started/doc/images/prep_deploy.png b/doc/book-enea-nfv-access-getting-started/doc/images/prep_deploy.png
index 67b96a9..4cd5015 100755
--- a/doc/book-enea-nfv-access-getting-started/doc/images/prep_deploy.png
+++ b/doc/book-enea-nfv-access-getting-started/doc/images/prep_deploy.png
diff --git a/doc/book-enea-nfv-access-getting-started/doc/images/prep_execution.png b/doc/book-enea-nfv-access-getting-started/doc/images/prep_execution.png
index f589495..5851621 100755
--- a/doc/book-enea-nfv-access-getting-started/doc/images/prep_execution.png
+++ b/doc/book-enea-nfv-access-getting-started/doc/images/prep_execution.png
diff --git a/doc/book-enea-nfv-access-getting-started/doc/installation_guide.xml b/doc/book-enea-nfv-access-getting-started/doc/installation_guide.xml
index acd53b4..d7771ca 100644
--- a/doc/book-enea-nfv-access-getting-started/doc/installation_guide.xml
+++ b/doc/book-enea-nfv-access-getting-started/doc/installation_guide.xml
@@ -8,7 +8,7 @@
   scenarios.</para>
 
   <section id="hw_reqs">
-    <title>Hardware requirements</title>
+    <title>Hardware Requirements</title>
 
     <para>The following hardware is needed for deploying the base
     configuration:</para>
@@ -306,7 +306,7 @@ userdel postgres</programlisting>
   </section>
 
   <section id="ucpe_config">
-    <title>uCPE Device configuration</title>
+    <title>uCPE Device Configuration</title>
 
     <section id="wan_lan_ports">
       <title>Determining the WAN and LAN ports</title>
@@ -322,7 +322,7 @@ userdel postgres</programlisting>
     </section>
 
     <section id="ucpe_identifier">
-      <title>Determining the DeviceId</title>
+      <title>Determining the Device ID</title>
 
       <para>Each uCPE device needs a unique identifier. This identifier is
       used to match the registration in the Enea uCPE Manager and the offline
@@ -390,7 +390,7 @@ userdel postgres</programlisting>
   </section>
 
   <section id="prep_deploy">
-    <title>Preparing the deployment</title>
+    <title>Preparing the Deployment</title>
 
     <section id="install_ucpe_mg">
       <title>Installing the Enea uCPE Manager</title>
@@ -669,7 +669,7 @@ of=/dev/sdb bs=4M conv=fsync</programlisting>
     </section>
 
     <section id="prep_phys_deploy">
-      <title>Preparing physical deployment for installation</title>
+      <title>Preparing Physical Deployment for Installation</title>
 
       <figure>
         <title>Preparing for Hardware Installation</title>
@@ -688,7 +688,7 @@ of=/dev/sdb bs=4M conv=fsync</programlisting>
     </section>
 
     <section id="install_ena_device">
-      <title>Installing Enea NFV Access - uCPE Device installation</title>
+      <title>Installing Enea NFV Access - uCPE Device Installation</title>
 
       <para>To initiate the installation of the Enea NFV Access Run Time
       Platform do the following:</para>
@@ -776,14 +776,14 @@ of=/dev/sdb bs=4M conv=fsync</programlisting>
       on the Enea uCPE Manager, as described below.</para>
 
       <note>
-        <para>If the USB stick was booted in UEFI mode, an UEFI boot entry is 
-          automatically created and the system will start booting from the 
-          hard drive without further user configuration.</para>
+        <para>If the USB stick was booted in UEFI mode, an UEFI boot entry is
+        automatically created and the system will start booting from the hard
+        drive without further user configuration.</para>
       </note>
     </section>
 
     <section id="prep_phys_exec">
-      <title>Preparing physical deployment for execution</title>
+      <title>Preparing Physical Deployment for Execution</title>
 
       <figure>
         <title>Preparing for Deployment Execution</title>
@@ -937,36 +937,23 @@ of=/dev/sdb bs=4M conv=fsync</programlisting>
       ID</literal>, the installation is complete, and the connection is
       established.</para>
 
-      <note>
-        <para>In case of failure due to a misconfiguration or if a uCPE device
-        does not appear in the Enea uCPE Manager, a reinstallation is needed
-        .The user should remove all WAN cables, reinsert the USB stick,
-        reconnect the laptop using the ethernet cable, reboot the uCPE device
-        and then access the Web-installer
-        (<literal>http://172.16.1.1</literal>).</para>
-
-        <para>In case of management connection failure (e.g. due to a
-        misconfiguration), the uCPE device status will be seen as RED
-        (disconnected) in Enea uCPE Manager. Please check the accuracy of the
-        information provided when the uCPE device was registered in the Enea
-        uCPE Manager.</para>
-
-        <para>The uCPE device configuration can be amended. In order to do
-        that, please remove the WAN cable(s), reconnect the laptop to the LAN
-        interface of the uCPE device and reboot it. At this point, the
-        Web-installer can be accessed from the laptop as described in <olink
-        targetdoc="book_enea_nfv_access_getting_started"
-        targetptr="install_ena_device">Installing Enea NFV Access - uCPE
-        Device installation in the <xi:include
-        href="../../s_docbuild/olinkdb/pardoc-names.xml"
-        xmlns:xi="http://www.w3.org/2001/XInclude"
-        xpointer="element(book_enea_nfv_access_getting_started/1)" /></olink>
-        Manual.</para>
-      </note>
-
       <para>When a uCPE device is registered it can be manually added to the
       map for overview. Right-click on the map and select <literal>Place
       Device</literal> to put the uCPE device on the map.</para>
+
+      <para>In case of management connection failure (e.g. due to a
+      misconfiguration), the uCPE device status will be seen as RED
+      (disconnected) in the Enea uCPE Manager. The uCPE device configuration
+      can be corrected by removing the WAN cable(s), reconnecting the laptop
+      to the LAN interface of the uCPE device and rebooting it. At this point,
+      the Web-installer can be accessed from the laptop as described in <olink
+      targetdoc="book_enea_nfv_access_getting_started"
+      targetptr="install_ena_device">Installing Enea NFV Access - uCPE Device
+      installation in the <xi:include
+      href="../../s_docbuild/olinkdb/pardoc-names.xml"
+      xmlns:xi="http://www.w3.org/2001/XInclude"
+      xpointer="element(book_enea_nfv_access_getting_started/1)" /></olink>
+      Manual.</para>
     </section>
   </section>
 
diff --git a/doc/book-enea-nfv-access-getting-started/doc/log_collector.xml b/doc/book-enea-nfv-access-getting-started/doc/log_collector.xml
index 1c66db0..8b8be31 100644
--- a/doc/book-enea-nfv-access-getting-started/doc/log_collector.xml
+++ b/doc/book-enea-nfv-access-getting-started/doc/log_collector.xml
@@ -71,7 +71,7 @@
     </section>
 
     <section id="view_logs">
-      <title>View collected logs</title>
+      <title>View collected Logs</title>
 
       <para>A list with the archives containing already collected logs will be
       shown in the <literal>Device File Listing</literal> table:</para>
@@ -144,7 +144,7 @@
     </section>
 
     <section id="download_logs_locally">
-      <title>Downloading collected logs locally</title>
+      <title>Downloading collected Logs locally</title>
 
       <para>This option downloads a logs archive from the Enea uCPE Manager to
       a local (user) machine for analysis. The archive must first be available
@@ -186,7 +186,7 @@
     </section>
 
     <section id="delete_log_archive_dev">
-      <title>Deleting a logs archive from a uCPE device</title>
+      <title>Deleting a Logs Archive from a uCPE device</title>
 
       <para>Use this option when you want to delete unnecessary collected logs
       on the uCPE device.</para>
@@ -236,7 +236,7 @@
     </section>
 
     <section id="delete_archives_ucpem">
-      <title>Deleting logs archives from the Enea uCPE Manager</title>
+      <title>Deleting a Logs Archive from the Enea uCPE Manager</title>
 
       <para>This option deletes a logs archive from the Enea uCPE
       Manager.</para>
@@ -320,7 +320,7 @@
     </section>
 
     <section id="download_ucpemg_logs">
-      <title>Downloading Enea uCPE Manager logs</title>
+      <title>Downloading Enea uCPE Manager Logs</title>
 
       <para>Often, sending the Enea uCPE Manager logs together with collected
       uCPE device logs to the support team provides important information for
diff --git a/doc/book-enea-nfv-access-getting-started/doc/net_config_options.xml b/doc/book-enea-nfv-access-getting-started/doc/net_config_options.xml
index 873dc28..effe3da 100644
--- a/doc/book-enea-nfv-access-getting-started/doc/net_config_options.xml
+++ b/doc/book-enea-nfv-access-getting-started/doc/net_config_options.xml
@@ -6,7 +6,7 @@
   uCPE Manager GUI.</para>
 
   <section id="device_callhome_nat">
-    <title>Device Call Home Connection for deployment behind NAT</title>
+    <title>Device Call Home Connection for Deployment behind NAT</title>
 
     <para>The Device Call Home option enables the initiation of the connection
     between the uCPE Device and the Enea uCPE Manager, from the uCPE device.
@@ -228,6 +228,15 @@
             </figure>
           </listitem>
         </orderedlist>
+
+        <note>
+          <para>When changing the <literal>address-assignment</literal> from 
+            static to DHCP, if any of the <literal>ip-address</literal>, 
+            <literal>netmask</literal> or <literal>gateway</literal> fields 
+            have invalid values a validation error will be triggered. 
+            These fields must be empty or have the valid values for their 
+            respective address assignment.</para>          
+        </note>
       </section>
 
       <section id="man_configuration">
@@ -389,7 +398,7 @@
       </section>
 
       <section id="dataplane_bridge">
-        <title>Data-plane Bridge</title>
+        <title>Data-plane bridge</title>
 
         <para>Data-plane bridges are generic bridges used for the VNF
         data-plane. There are two supported sub-types:</para>
@@ -428,7 +437,7 @@
   </section>
 
   <section id="zero_touch_prov">
-    <title>Zero Touch Provisioning - Creating an offline configuration</title>
+    <title>Zero Touch Provisioning - Creating an Offline Configuration</title>
 
     <para>Zero-Touch Provisioning (ZTP) refers to the process of when a device
     starts up for the first time and its initial configuration is pushed down
diff --git a/doc/book-enea-nfv-access-getting-started/doc/upgrade_ena.xml b/doc/book-enea-nfv-access-getting-started/doc/upgrade_ena.xml
index 3706548..42589e0 100644
--- a/doc/book-enea-nfv-access-getting-started/doc/upgrade_ena.xml
+++ b/doc/book-enea-nfv-access-getting-started/doc/upgrade_ena.xml
@@ -71,7 +71,7 @@ Enea_NFV_Access_uCPEManager_&lt;version&gt;-build&lt;build_number&gt;.tar.gz</pr
     </itemizedlist>
 
     <section id="restore_prev_ucpe_install">
-      <title>Restoring a previous Enea uCPE Manager installation</title>
+      <title>Restoring a previous Enea uCPE Manager Installation</title>
 
       <para><emphasis role="bold">How to restore a previous Enea uCPE Manager
       installation</emphasis></para>
@@ -128,7 +128,7 @@ Enea_NFV_Access_uCPEManager_&lt;version&gt;-build&lt;build_number&gt;.tar.gz</pr
     </section>
 
     <section id="uninstall_ucpem_install">
-      <title>Uninstalling an existing Enea uCPE Manager installation</title>
+      <title>Uninstalling an existing Enea uCPE Manager Installation</title>
 
       <para><emphasis role="bold">How to uninstall an existing Enea uCPE
       Manager installation</emphasis></para>
@@ -190,13 +190,13 @@ Enea_NFV_Access_uCPEManager_&lt;version&gt;-build&lt;build_number&gt;.tar.gz</pr
   </section>
 
   <section id="upgrade_devices">
-    <title>uCPE device upgrades</title>
+    <title>uCPE device Upgrades</title>
 
     <para>A uCPE device can be upgraded using the Enea uCPE Manager
     GUI.</para>
 
     <section id="device_up_process">
-      <title>The uCPE device upgrade process</title>
+      <title>The uCPE device Upgrade Process</title>
 
       <para>The Device Upgrade/Install option performs the following
       operations to the uCPE device:</para>
@@ -220,7 +220,7 @@ Enea_NFV_Access_uCPEManager_&lt;version&gt;-build&lt;build_number&gt;.tar.gz</pr
     </section>
 
     <section id="mg_upgrade">
-      <title>Managing the Device Upgrade</title>
+      <title>Managing the device Upgrade</title>
 
       <para>Before an installation or upgrade can be completed, certain
       configuration data must be set. Files also need to be uploaded to the
@@ -419,7 +419,7 @@ Enea_NFV_Access_uCPEManager_&lt;version&gt;-build&lt;build_number&gt;.tar.gz</pr
       </section>
 
       <section id="upgrade_status">
-        <title>uCPE device upgrade status</title>
+        <title>uCPE device Upgrade Status</title>
 
         <para>The status of the installation and upgrade can be viewed in the
         <literal>Upgrade Operations</literal> tab. Ongoing or scheduled
@@ -524,7 +524,7 @@ Enea_NFV_Access_uCPEManager_&lt;version&gt;-build&lt;build_number&gt;.tar.gz</pr
       </section>
 
       <section id="related_functionality">
-        <title>Related Functionality for a uCPE device upgrade</title>
+        <title>Related Functionality for a uCPE device Upgrade</title>
 
         <para>Each uCPE device can receive image files and use them to
         upgrade. This can be done by selecting the uCPE device in the
diff --git a/doc/book-enea-nfv-access-getting-started/doc/vnf_mg.xml b/doc/book-enea-nfv-access-getting-started/doc/vnf_mg.xml
index dd90884..2dfe248 100644
--- a/doc/book-enea-nfv-access-getting-started/doc/vnf_mg.xml
+++ b/doc/book-enea-nfv-access-getting-started/doc/vnf_mg.xml
@@ -445,7 +445,7 @@
             SSH</literal> configuration panel. By default, the start port will
             be <literal>7000</literal> and the maximum number of ports
             allocated to all devices is 10. Only one port per device is
-            allowed. </para>
+            allowed.</para>
 
             <para>When the SSH window is closed, the tunnel configuration is
             deleted on the uCPE device and the tunnel is destroyed, so that