7 files changed, 37 insertions, 44 deletions

diff --git a/doc/book-enea-nfv-access-getting-started/doc/advanced_configurations.xml b/doc/book-enea-nfv-access-getting-started/doc/advanced_configurations.xml
index c03f657..6be1205 100644
--- a/doc/book-enea-nfv-access-getting-started/doc/advanced_configurations.xml
+++ b/doc/book-enea-nfv-access-getting-started/doc/advanced_configurations.xml
@@ -12,7 +12,7 @@
     <title>Bare Metal Provisioning</title>
 
     <para>Bare Metal Provisioning can be used for automated deployment of the
-    Enea NFV Access Run Time Platform on a large number of uCPE devices. The
+    Enea NFV Access Runtime Platform on a large number of uCPE devices. The
     uCPE devices may have no previous operating system installed, or are
     reinstalled without preserving any existing data. Enea NFV Access Bare
     Metal Provisioning is based on standardized Pre-Boot Execution environment
@@ -20,12 +20,12 @@
 
     <para>The Bare Metal Provisioning process begins by PXE booting an Enea
     NFV Access installer <literal>initramfs</literal> image. The installer
-    downloads a configuration file, as well as the Enea NFV Access Run Time
+    downloads a configuration file, as well as the Enea NFV Access Runtime
     Platform image and then proceeds to install the system by dividing the
     disk into 2 partitions: a GPT partition containing the GRUB boot loader
-    and a second partition containing the Enea NFV Access Run Time Platform
+    and a second partition containing the Enea NFV Access Runtime Platform
     root filesystem. When the installation is complete, the uCPE device is
-    automatically rebooted into Enea NFV Access Run Time Platform.</para>
+    automatically rebooted into Enea NFV Access Runtime Platform.</para>
 
     <note>
       <para>The <literal>.hddimg</literal>, <literal>initramfs</literal>, and
@@ -56,7 +56,7 @@
 
         <listitem>
           <para>The uCPE devices are preconfigured in BIOS to boot from the
-          hard drive where the Enea NFV Access Run Time Platform will be
+          hard drive where the Enea NFV Access Runtime Platform will be
           installed.</para>
         </listitem>
 
@@ -93,7 +93,7 @@
         </listitem>
 
         <listitem>
-          <para>Compress the Enea NFV Access Run Time Platform
+          <para>Compress the Enea NFV Access Runtime Platform
           <literal>.hddimg</literal> image for the uCPE device architecture
           using <literal>gzip</literal> and copy the resulting
           <literal>hddimg.gz</literal> file to the HTTP server.</para>
@@ -113,7 +113,7 @@
         <itemizedlist>
           <listitem>
             <para><literal>image_url</literal>. The HTTP server URL used for
-            downloading the Enea NFV Access Run Time Platform image.</para>
+            downloading the Enea NFV Access Runtime Platform image.</para>
           </listitem>
         </itemizedlist>
 
@@ -122,7 +122,7 @@
         <itemizedlist>
           <listitem>
             <para><literal>install_drive</literal>. The name of the drive
-            where the Enea NFV Access Run Time Platform will be installed (e.g
+            where the Enea NFV Access Runtime Platform will be installed (e.g
             <literal>/dev/sda</literal>). If not set, the installer will use
             the largest detected (non-USB) drive on the uCPE device.</para>
           </listitem>
@@ -180,7 +180,7 @@ ipmitool -U &lt;user&gt; -P &lt;password&gt; -H &lt;uCPE device IPMI IP address&
 
       <para>The uCPE devices should be configured in BIOS to boot from the
       installation drive first in order to automatically start the Enea NFV
-      Access Run Time Platform when the installation is finished.</para>
+      Access Runtime Platform when the installation is finished.</para>
     </section>
   </section>
 
@@ -247,7 +247,7 @@ ipmitool -U &lt;user&gt; -P &lt;password&gt; -H &lt;uCPE device IPMI IP address&
         </itemizedlist>
 
         <para>The Enea UEFI Secure Boot certificates are installed together
-        with the Enea NFV Access Run Time Platform onto the hard drive. They
+        with the Enea NFV Access Runtime Platform onto the hard drive. They
         can be found on the EFI partition (usually the first partition of the
         drive) under <literal>/uefi_sb_keys</literal>.</para>
 
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 4cd5015..2db2487 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 5851621..404760b 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 d7771ca..b82d48b 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
@@ -30,7 +30,7 @@
       <listitem>
         <para>One or more uCPE devices.</para>
 
-        <para>Whitebox devices where the Enea NFV Access Run Time Platform
+        <para>Whitebox devices where the Enea NFV Access Runtime Platform
         will be installed, containing a minimum of 2 cores and 4 GB RAM and at
         least two ethernet ports that will be configured as WAN and LAN during
         deployment.</para>
@@ -38,7 +38,7 @@
         <para>When hosting an entire solution including one or several network
         services, the hardware must also have the resources to host one or
         more VNFs. During a typical evaluation, a dual VNF service on the Enea
-        NFV Access Run Time Platform needs a CPU with 4-8 cores and at least 8
+        NFV Access Runtime Platform needs a CPU with 4-8 cores and at least 8
         GB RAM. The supported Intel CPUs of Enea NFV Access are documented in
         the <xi:include href="../../s_docbuild/olinkdb/pardoc-common.xml"
         xmlns:xi="http://www.w3.org/2001/XInclude"
@@ -57,7 +57,7 @@
 
         <itemizedlist>
           <listitem>
-            <para>Installing the Enea NFV Access Run Time Platform on uCPE
+            <para>Installing the Enea NFV Access Runtime Platform on uCPE
             Devices.</para>
           </listitem>
 
@@ -96,7 +96,7 @@
 
       <programlisting>sudo systemctl stop firewalld
 sudo systemctl disable firewalld
-sudo systemctl mask -now firewalld</programlisting>
+sudo systemctl mask now firewalld</programlisting>
 
       <para>For an advanced firewall configuration, the following ports need
       to be opened:</para>
@@ -368,7 +368,7 @@ userdel postgres</programlisting>
       </itemizedlist>
 
       <para>The boot order may also need to be modified to support
-      installation and execution of the Enea NFV Access Run Time Platform on
+      installation and execution of the Enea NFV Access Runtime Platform on
       the uCPE device.</para>
 
       <para>The following boot order is recommended for a base
@@ -617,9 +617,9 @@ SystemBackup_MMMDD_YYYY_HHMM_SS.zip</programlisting>
 
     <section id="prep_usb_ena">
       <title>Preparing the USB stick for installation of the Enea NFV Access
-      Run Time Platform</title>
+      Runtime Platform</title>
 
-      <para>To install the Enea NFV Access Run Time Platform, create a
+      <para>To install the Enea NFV Access Runtime Platform, create a
       bootable USB stick with the image you intend to install.</para>
 
       <para>In the example below, step by step instructions are provided for
@@ -682,7 +682,7 @@ of=/dev/sdb bs=4M conv=fsync</programlisting>
       </figure>
 
       <para>While the uCPE device is powered off, in order to install and
-      configure the Enea NFV Access Run Time using the prepared USB stick,
+      configure the Enea NFV Access Runtime using the prepared USB stick,
       connect the laptop to a uCPE device LAN port. For this purpose, a Layer
       2 switch or direct cable connection can be used.</para>
     </section>
@@ -690,7 +690,7 @@ of=/dev/sdb bs=4M conv=fsync</programlisting>
     <section id="install_ena_device">
       <title>Installing Enea NFV Access - uCPE Device Installation</title>
 
-      <para>To initiate the installation of the Enea NFV Access Run Time
+      <para>To initiate the installation of the Enea NFV Access Runtime
       Platform do the following:</para>
 
       <orderedlist>
@@ -754,17 +754,6 @@ of=/dev/sdb bs=4M conv=fsync</programlisting>
               <para>Plug-in additional WAN interfaces (if applicable) and
               provide their Layer 3 configuration.</para>
             </listitem>
-
-            <listitem>
-              <para>The Static or Dynamic IP.</para>
-
-              <note>
-                <para>No LAN ports should be connected nor configured at this
-                time. The LAN port used to access the Web-installer from the
-                laptop will not be shown and cannot be configured in the
-                Web-Installer.</para>
-              </note>
-            </listitem>
           </itemizedlist>
         </listitem>
       </orderedlist>
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 d403abf..5f8a5ad 100644
--- a/doc/book-enea-nfv-access-getting-started/doc/introduction.xml
+++ b/doc/book-enea-nfv-access-getting-started/doc/introduction.xml
@@ -32,7 +32,7 @@
 
     <itemizedlist>
       <listitem>
-        <para>The Enea NFV Access Run Time Platform, which acts as the host
+        <para>The Enea NFV Access Runtime Platform, which acts as the host
         for Virtualized Network Functions (VNFs) and provides management over
         NETCONF.</para>
       </listitem>
@@ -58,9 +58,9 @@
     with your release.</para>
 
     <section id="nfv_access">
-      <title>Enea NFV Access Run Time Platform</title>
+      <title>Enea NFV Access Runtime Platform</title>
 
-      <para>Enea NFV Access Run Time Platform is a lightweight,
+      <para>Enea NFV Access Runtime Platform is a lightweight,
       multi-architecture virtualization platform built on de-facto standards
       in an SDN/NFV ecosystem. It is designed for a high networking
       performance with minimal hardware footprint, by only providing relevant
@@ -99,6 +99,10 @@
 
       <itemizedlist>
         <listitem>
+          <para>Enea NFV Access Runtime Platform Software Management</para>
+        </listitem>
+
+        <listitem>
           <para>VNF Onboarding</para>
         </listitem>
 
@@ -139,12 +143,12 @@
             <row>
               <entry>Enea NFV Access</entry>
 
-              <entry>The Enea NFV Access Run Time Platform and the Enea uCPE
+              <entry>The Enea NFV Access Runtime Platform and the Enea uCPE
               Manager.</entry>
             </row>
 
             <row>
-              <entry>Enea NFV Access Run Time Platform</entry>
+              <entry>Enea NFV Access Runtime Platform</entry>
 
               <entry>A lightweight, multi-architecture virtualization
               platform, supporting Virtual Machines.</entry>
@@ -160,7 +164,7 @@
             <row>
               <entry>uCPE device</entry>
 
-              <entry>A whitebox running the Enea NFV Access Run Time
+              <entry>A whitebox running the Enea NFV Access Runtime
               Platform.</entry>
             </row>
           </tbody>
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 effe3da..1d51537 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
@@ -230,12 +230,12 @@
         </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>          
+          <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>
 
@@ -702,7 +702,7 @@
             <para>The status of execution for the scripts can be seen by
             opening the <literal>Fault</literal> -&gt;
             <literal>Events</literal> screen and filtering by device and/or
-            the event name <filename>Custom</filename>.</para>
+            the event name <filename>CustomScriptExecuted</filename>.</para>
           </note>
         </listitem>
       </orderedlist>
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 42589e0..01fd8ec 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
@@ -4,7 +4,7 @@
 
   <para>Enea provides regular releases that will require the upgrading of Enea
   NFV Access components. The Enea uCPE Manager must be upgraded first,
-  followed by upgrading Enea NFV Access Run Time on the uCPE devices.</para>
+  followed by upgrading Enea NFV Access Runtime on the uCPE devices.</para>
 
   <section id="upgrade_mg">
     <title>Upgrading the Enea uCPE Manager</title>