update Definitions and Acronyms

- Fix some typo.
- Replace "Automatic Addition" with "Device Call Home Connection"
  to be consistent on terminology.

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

2 files changed, 77 insertions, 9 deletions

diff --git a/doc/book-enea-nfv-access-getting-started/doc/definitions_and_acronyms.xml b/doc/book-enea-nfv-access-getting-started/doc/definitions_and_acronyms.xml
index f67cfe4..8851aed 100644
--- a/doc/book-enea-nfv-access-getting-started/doc/definitions_and_acronyms.xml
+++ b/doc/book-enea-nfv-access-getting-started/doc/definitions_and_acronyms.xml
@@ -19,23 +19,26 @@
           <row>
             <entry>Enea NFV Access</entry>
 
-            <entry>The Enea NFV Access Run Time Platform (with ODM) and uCPE
+            <entry>The Enea NFV Access Run Time Platform and uCPE
             Manager.</entry>
           </row>
 
           <row>
             <entry>Enea NFV Access Run Time Platform</entry>
+
             <entry>A lightweight, multi-architecture virtualization platform,
             supporting Virtual Machines (KVM / QEMU).</entry>
           </row>
 
           <row>
             <entry>Enea uCPE Manager</entry>
+
             <entry>Enea Universal Customer Premises Equipment Manager.</entry>
           </row>
 
           <row>
             <entry>uCPE device</entry>
+
             <entry>A whitebox (e.g. Intel XeonD) running Enea NFV Access Run
             Time platform.</entry>
           </row>
@@ -57,14 +60,79 @@
 
         <tbody>
           <row>
-            <entry>ODM</entry>
-            <entry>On Device Management.</entry>
+            <entry>API</entry>
+
+            <entry>Application Programming Interface.</entry>
+          </row>
+
+          <row>
+            <entry>DPDK</entry>
+
+            <entry>Data Plane Development Kit.</entry>
+          </row>
+
+          <row>
+            <entry>EFI</entry>
+
+            <entry>Extensible Firmware Interface.</entry>
+          </row>
+
+          <row>
+            <entry>NETCONF</entry>
+
+            <entry>Network Configuration Protocol.</entry>
+          </row>
+
+          <row>
+            <entry>NFV</entry>
+
+            <entry>Network Functions Virtualization.</entry>
           </row>
 
           <row>
             <entry>OVS</entry>
+
             <entry>Open vSwitch.</entry>
           </row>
+
+          <row>
+            <entry>UEFI</entry>
+
+            <entry>Unified Extensible Firmware Interface.</entry>
+          </row>
+
+          <row>
+            <entry>SR-IOV</entry>
+
+            <entry>Single Root Input/Output Virtualization.</entry>
+          </row>
+
+          <row>
+            <entry>PCI</entry>
+
+            <entry>Peripheral Component Interconnect.</entry>
+          </row>
+
+          <row>
+            <entry>PCI Passthrough</entry>
+
+            <entry>PCI Passthrough allows for use of a physical PCI device, 
+              e.g. a network card inside a VM.
+            If you "PCI passthrough" a device, the device is not available to
+            the host anymore.</entry>
+          </row>
+
+          <row>
+            <entry>REST</entry>
+
+            <entry>Representational State Transfer.</entry>
+          </row>
+
+          <row>
+            <entry>VNF</entry>
+
+            <entry>Virtual Network Function.</entry>
+          </row>
         </tbody>
       </tgroup>
     </table>
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 7b29ef9..29b6dbb 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
@@ -243,8 +243,8 @@ of=/dev/sdb bs=4M conv=fsync</programlisting></para>
       <para>Installing the Run Time Platform can be done in two ways: 
         Automatic and Manual, depending on the features you wish to enable. 
         Please note that in order to enable features such as Zero Touch 
-        Provisioning or Automatic Addition of uCPE devices in the Enea uCPE 
-        Manager, Manual installation must be used.</para>
+        Provisioning or Device Call Home Connection of uCPE devices in the
+        Enea uCPE Manager, Manual installation must be used.</para>
       
       <para><emphasis role="bold">How to install the Enea NFV Access Run Time
       Platform using a bootable USB stick image</emphasis></para>
@@ -313,7 +313,7 @@ of=/dev/sdb bs=4M conv=fsync</programlisting></para>
             <listitem>
               <para><emphasis role="bold">Manual install</emphasis>. Gives the
               user the possibility of choosing where GRUB and NFV Access will
-              be installed and what parameters can be set. Features like ZT Provisioning etc.
+              be installed and what parameters can be set. Features like ZTP Provisioning etc.
               can be enabled as well.</para>
 
               <para>Kernel parameters can be customized by selecting the
@@ -341,7 +341,7 @@ of=/dev/sdb bs=4M conv=fsync</programlisting></para>
                   <note>
                     <para>In case the number of hugepages is not specified during
                     this step, hugepages will be allocated by the NFV Access
-                    Hugepage Reservation Service, based on an algoritm which
+                    Hugepage Reservation Service, based on an algorithm which
                     takes into consideration the size of RAM memory. For further
                     information, please see section 
                       <olink targetdoc="book_enea_nfv_access_getting_started"
@@ -354,7 +354,7 @@ of=/dev/sdb bs=4M conv=fsync</programlisting></para>
 
                 <listitem>
                   <para>uCPE Manager IP address. The IP address used to connect
-                    to the uCPE Manager during Automatic Addition.</para>
+                    to the uCPE Manager during Device Call Home Connection.</para>
                 </listitem>
 
                 <listitem>
@@ -407,7 +407,7 @@ of=/dev/sdb bs=4M conv=fsync</programlisting></para>
       BIOS/UEFI) to boot the system from the media storage device where NFV
       Access was installed.</para>
 
-      <para>If the uCPE Manager uses the Automatic Addition method for enrolling
+      <para>If the uCPE Manager uses the Device Call Home Connection method for enrolling
       the uCPE devices, the uCPE Manager IP address has to be configured in NFV
       Access, by setting <literal>vcpemgr=&lt;IP&gt;</literal> as a kernel
       boot parameter in the GRUB configuration file. This step is not required