GettingStarted: updated introduction

- fixed minor typos

Change-Id: I4c64035e8305e98af2b6ee7d372f8172368f3ee3
Signed-off-by: Sona Sarmadi <sona.sarmadi@enea.com>

4 files changed, 22 insertions, 74 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 d68a342..e7c7a34 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
@@ -226,7 +226,7 @@
       refer to the Enea NFV Access Reference Guide provided with your release.</para>
 
       <para>This step needs to be done each time the uCPE Manager host changes
-      the IP address.</para>
+      its IP address.</para>
     </note>
 
     <para>An offline configuration can be prepared in advance for the uCPE
@@ -564,7 +564,7 @@
         name, and optionally a description, used by the uCPE Manager
         only.</para>
 
-        <para><emphasis role="bold">Cloud-Init Tab</emphasis></para>
+        <para><emphasis role="bold">Cloud Init Tab</emphasis></para>
 
         <para>Click the <literal>Clout Init</literal> tab to provide the
         Clout-Init configuration.</para>
@@ -666,7 +666,7 @@
       <title>Instantiating a VNF</title>
 
       <para>Once the VNF bundle has been onboarded, you can instantiate a VNF
-      on a specific uCPE host:</para>
+      on a specific uCPE host.</para>
 
       <para>Launch the <literal>VNF instance</literal> table by choosing the
       <literal>Instances</literal> option from the <literal>VNF</literal>
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 ccb49e6..7f0aa78 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
@@ -4,10 +4,6 @@
 <chapter id="plat-release-content">
   <title>Getting Started with Enea NFV Access</title>
 
-  <para>Enea NFV Access is a virtualization and management platform for white
-  box uCPEs. It scales from ultra-low to high end CPEs, providing minimal
-  footprint and maximum networking performance. The NFV Access platform can be
-  deployed on a large number of devices with various hardware configurations.</para>
   <section id="access_installer">
     <title>Enea NFV Access Installer</title>
 
@@ -22,9 +18,9 @@
       USB stick (16GB or larger), a development machine with root
       permissions(Linux or Windows) and a target device.</para>
 
-      <para>Minimal requirements for white box for NFV Access:</para>
+      <para>Minimal requirements for NFV Access:</para>
 
-      <itemizedlist>
+      <itemizedlist spacing="compact">
         <listitem>
           <para>EFI and virtualization support</para>
         </listitem>
@@ -336,7 +332,7 @@ of=/dev/sdb bs=4M conv=fsync</programlisting></para>
               <para><emphasis role="bold">Default
               Parameters</emphasis>:</para>
 
-              <itemizedlist>
+              <itemizedlist spacing="compact">
                 <listitem>
                   <para>Core isolation. Isolates the selected range of cores
                   from the kernel scheduler.</para>
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 dba3f67..c31cea3 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
@@ -165,7 +165,7 @@
   </figure>
 
   <para>The VNF can be reached on the same IP address as the device, e.g.
-  <literal> https://&lt;WAN_IP&gt;</literal> if a HTTP server is present
+  <literal>https://&lt;WAN_IP&gt;</literal> if a HTTP server is present
    on that VNF.</para>
 
   <note>
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 1f5bb0b..bdaa534 100644
--- a/doc/book-enea-nfv-access-getting-started/doc/introduction.xml
+++ b/doc/book-enea-nfv-access-getting-started/doc/introduction.xml
@@ -14,48 +14,32 @@
   for important details about formats and how to do! The idea is that ELTF
   will auto-create/update it.</remark></para>
 
-  <para>Enea NFV Access seeks to demonstrate a means for which a Network
-  Functions Virtualization architecture can be created and managed
-  effectively, suited to your custom needs. It accomplishes this task by
-  teaming two key products together: NFV Access and the uCPE Manager. For
-  evaluation purposes, it also includes VNF examples.</para>
-
-  <para>The purpose of Enea NFV Access is the evaluation of the following
-  features:</para>
+  <para>Enea NFV Access for universal Customer Premise Equipment (uCPE) is a
+  virtualization and management platform, which allows end-users to introduce,
+  instantiate, and run third-party VNFs onto their systems. The solution is
+  comprised of two major components working in close cooperation:</para>
 
   <itemizedlist>
     <listitem>
-      <para>Platform Characteristics</para>
+      <para>The Enea NFV Access runtime platform, which acts as the host for
+      Virtualized Network Functions (VNFs) and provides management over
+      NETCONF.</para>
     </listitem>
 
     <listitem>
-      <para>VNF Performance</para>
-    </listitem>
-
-    <listitem>
-      <para>VNF On-boarding over EdgeLink NETCONF</para>
-    </listitem>
-
-    <listitem>
-      <para>Alarms and Events Management</para>
-    </listitem>
-
-    <listitem>
-      <para>Zero Touch Provisioning</para>
-    </listitem>
-
-    <listitem>
-      <para>Debugging and Logging</para>
+      <para>The Enea uCPE Manager, a solution that runs on an external server,
+      providing VNF Management functionality and managing large numbers of
+      uCPEs.</para>
     </listitem>
   </itemizedlist>
 
   <section id="nfv_access">
-    <title>Enea NFV Access</title>
+    <title>Enea NFV Access runtime platform</title>
 
-    <para>Enea NFV Access is a lightweight, multi-architecture virtualization
-    platform, supporting Virtual Machines (KVM / QEMU) and container(s)
-    (Docker). Designed for a low footprint and fast boot by only providing
-    essential functionality.</para>
+    <para>Enea NFV Access runtime platform is a lightweight,
+    multi-architecture virtualization platform, supporting Virtual Machines
+    (KVM / QEMU) and container(s) (Docker). Designed for a low footprint and
+    fast boot by only providing essential functionality.</para>
 
     <para>The NFV Access virtualized data plane has DPDK and accelerated OVS
     as its primary components. The data plane is highly optimized for
@@ -73,37 +57,6 @@
         </imageobject>
       </mediaobject>
     </figure>
-
-    <para>Enea NFV Access provides the following key features:</para>
-
-    <itemizedlist>
-      <listitem>
-        <para>Low footprint</para>
-      </listitem>
-
-      <listitem>
-        <para>Fast boot</para>
-      </listitem>
-
-      <listitem>
-        <para>Datapath optimizations</para>
-      </listitem>
-
-      <listitem>
-        <para>SW update</para>
-      </listitem>
-
-      <listitem>
-        <para>In-band management</para>
-      </listitem>
-    </itemizedlist>
-    <para>For additional information about features provided in Enea NFV
-    Access, refer to the Enea NFV Access Reference Guide
-    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>
-
   </section>
 
   <section id="ucpe_manager">
@@ -138,6 +91,5 @@
         <para>Alarms / Events management and monitoring</para>
       </listitem>
     </itemizedlist>
-
   </section>
 </chapter>