1 files changed, 54 insertions, 48 deletions

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 e8c65eb..fbf7091 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
@@ -2,17 +2,17 @@
 <chapter id="vnf_mg">
   <title>VNF Management</title>
 
-  <para>The Enea uCPE Manager is responsible for onboarding, configuring (e.g.
-  CloudInit) and ensuring life cycle management of VNFs that are instantiated
-  and run on the various uCPE devices.</para>
+  <para>The Enea Edge Management is responsible for onboarding, configuring
+  (e.g. CloudInit) and ensuring life cycle management of VNFs that are
+  instantiated and run on the various uCPE devices.</para>
 
   <section id="onboarding_a_vnf">
     <title>Onboarding a VNF</title>
 
-    <para>The onboarding of a VNF means adding it to the Enea uCPE Manager VNF
-    Catalogue and preparing it for instantiation (deployment on connected uCPE
-    devices). This is accomplished using the Enea uCPE Manager Onboarding
-    graphical user interface.</para>
+    <para>The onboarding of a VNF means adding it to the Enea Edge Management
+    VNF Catalogue and preparing it for instantiation (deployment on connected
+    uCPE devices). This is accomplished using the Enea Edge Management
+    Onboarding graphical user interface.</para>
 
     <para>Typically, the Getting Started Guide of a VNF, provided by the VNF
     vendor, contains all necessary information needed to onboard a VNF.</para>
@@ -35,8 +35,8 @@
           <note>
             <para>There are no standard ways of managing VNF licenses,
             therefore no general guidelines can be provided. One example of
-            license handling that can be employed in the Enea uCPE Manager is
-            the adding of a license during the Cloud-Init setup.</para>
+            license handling that can be employed in the Enea Edge Management
+            is the adding of a license during the Cloud-Init setup.</para>
           </note>
         </listitem>
 
@@ -109,32 +109,35 @@
     </section>
 
     <section id="onboard_in_ucpemg">
-      <title>Onboarding into the Enea uCPE Manager</title>
+      <title>Onboarding into the Enea Edge Management</title>
 
-      <para><emphasis role="bold">How to onboard a VNF into the Enea uCPE
-      Manager </emphasis></para>
+      <para><emphasis role="bold">How to onboard a VNF into the Enea Edge
+      Management </emphasis></para>
 
       <orderedlist>
         <listitem>
-          <para>Select from the top toolbar <emphasis role="bold">VNF</emphasis> 
-                  and then <emphasis role="bold">Descriptors</emphasis>.</para>
+          <para>Select from the top toolbar <emphasis
+          role="bold">VNF</emphasis> and then <emphasis
+          role="bold">Descriptors</emphasis>.</para>
         </listitem>
 
         <listitem>
-          <para>Click the <emphasis role="bold">On-board</emphasis> button.</para>
+          <para>Click the <emphasis role="bold">On-board</emphasis>
+          button.</para>
         </listitem>
 
         <listitem>
-          <para>When prompted by the UI, make sure the <emphasis role="bold">VM
-          Image</emphasis> radio button at the top of the onboarding screen is
-          selected, it will trigger a popup menu window.</para>
+          <para>When prompted by the UI, make sure the <emphasis
+          role="bold">VM Image</emphasis> radio button at the top of the
+          onboarding screen is selected, it will trigger a popup menu
+          window.</para>
         </listitem>
       </orderedlist>
 
       <para>This window contains data fields where both necessary and optional
       information about the VNF can be supplied. After doing so, press the
-      Onboard button, the Enea uCPE Manager will create the VNF descriptor and
-      add it to its VNF Catalog.</para>
+      Onboard button, the Enea Edge Management will create the VNF descriptor
+      and add it to its VNF Catalog.</para>
 
       <figure>
         <title>Onboard a VNF</title>
@@ -153,8 +156,8 @@
         <listitem>
           <para><emphasis role="bold">VM Image File</emphasis>. This is the
           Virtual Machine image file for the VNF. Typically, it is a QCOW
-          image. Press <emphasis role="bold">Choose File</emphasis> and select the image you
-          wish to upload.</para>
+          image. Press <emphasis role="bold">Choose File</emphasis> and select
+          the image you wish to upload.</para>
         </listitem>
 
         <listitem>
@@ -171,7 +174,7 @@
         <listitem>
           <para><emphasis role="bold">Description</emphasis>. This field
           contains any description provided and is only displayed in the GUI
-          tables in the Enea uCPE Manager.</para>
+          tables in the Enea Edge Management.</para>
         </listitem>
 
         <listitem>
@@ -203,14 +206,14 @@
 
       <para><emphasis role="bold">Interfaces Tab</emphasis></para>
 
-      <para>Click on the <emphasis role="bold">Interfaces</emphasis> tab to show the
-      Interfaces table.</para>
+      <para>Click on the <emphasis role="bold">Interfaces</emphasis> tab to
+      show the Interfaces table.</para>
 
       <para>This table will contain the interfaces required by this VNF to be
       configured, when creating an instance. Consult the VNF vendor to
       determine which and how many are required. Each interface requires a
-      name, and optionally a description, used only by the Enea uCPE
-      Manager.</para>
+      name, and optionally a description, used only by the Enea Edge
+      Management.</para>
 
       <note>
         <para>CAUTION: The user MUST conserve the same order for the virtual
@@ -219,9 +222,9 @@
 
       <para><emphasis role="bold">Cloud Init Tab</emphasis></para>
 
-      <para>Click the <emphasis role="bold">Cloud Init</emphasis> tab to provide the
-      Cloud-Init configuration. There are three fields that need to be
-      populated:</para>
+      <para>Click the <emphasis role="bold">Cloud Init</emphasis> tab to
+      provide the Cloud-Init configuration. There are three fields that need
+      to be populated:</para>
 
       <orderedlist>
         <listitem>
@@ -273,7 +276,7 @@
           <para>The <literal>Content Files Table</literal> is ONLY used if
           <literal>ConfigDrive</literal> is chosen as the Cloud-Init
           Datasource. For each content file added, a <literal>Path</literal>
-          must be provided. When the Enea uCPE Manager is used to create an
+          must be provided. When the Enea Edge Management is used to create an
           instance for multiple VNFs, the user will be prompted to provide a
           data file for each entry in this table. Each type of VNF will
           require different cloud-init files, e.g.: a license file. The data
@@ -292,9 +295,9 @@
       <para>In this table, you can enter values for properties that will be
       used during instantiation of the VNF. The values will augment the
       default values in the <filename>domain.xml</filename> file used by
-      <literal>libvirt/virsh</literal> (running in Enea NFV Access) when
-      creating an instance of the VNF. Consult with the VNF Vendor or ENEA
-      support for values needed by specific VNFs.</para>
+      <literal>libvirt/virsh</literal> (running in Enea Edge) when creating an
+      instance of the VNF. Consult with the VNF Vendor or ENEA support for
+      values needed by specific VNFs.</para>
 
       <para><emphasis role="bold">Property Values</emphasis></para>
 
@@ -349,8 +352,8 @@
 
     <orderedlist>
       <listitem>
-        <para>Select from the top toolbar <emphasis role="bold">VNF</emphasis> and 
-        choose <emphasis role="bold">Instances</emphasis>.</para>
+        <para>Select from the top toolbar <emphasis role="bold">VNF</emphasis>
+        and choose <emphasis role="bold">Instances</emphasis>.</para>
       </listitem>
 
       <listitem>
@@ -406,13 +409,14 @@
       </listitem>
 
       <listitem>
-        <para>Hit the <emphasis role="bold">Create</emphasis> button to deploy the VNF and
-        run it on the specified uCPE device.</para>
+        <para>Hit the <emphasis role="bold">Create</emphasis> button to deploy
+        the VNF and run it on the specified uCPE device.</para>
       </listitem>
     </orderedlist>
 
-    <para>Selecting the <emphasis role="bold">VNF</emphasis> menu then choosing <emphasis role="bold">Events</emphasis> 
-        will show that the VNF was created and a connection was established.</para>
+    <para>Selecting the <emphasis role="bold">VNF</emphasis> menu then
+    choosing <emphasis role="bold">Events</emphasis> will show that the VNF
+    was created and a connection was established.</para>
   </section>
 
   <section id="enter_console">
@@ -425,8 +429,9 @@
 
     <orderedlist>
       <listitem>
-        <para>SSH to the uCPE device from the Enea uCPE Manager
-        (Access the <emphasis role="bold">Device</emphasis> menu and select <emphasis role="bold">SSH</emphasis>) using:</para>
+        <para>SSH to the uCPE device from the Enea Edge Management (Access the
+        <emphasis role="bold">Device</emphasis> menu and select <emphasis
+        role="bold">SSH</emphasis>) using:</para>
 
         <itemizedlist>
           <listitem>
@@ -440,12 +445,13 @@
             <para>For reverse ssh connections (ssh to a uCPE device behind
             NAT): the <literal>Username</literal> (default: root) and the
             <literal>Reverse ssh</literal> checkbox checked. The port will be
-            automatically choosen by the Enea uCPE Manager in the range
-            defined in the <emphasis role="bold">SSH</emphasis> configuration panel, 
-                        available when accessing <emphasis role="bold">System</emphasis>, then 
-                        <emphasis role="bold">Configuration</emphasis> and choosing <emphasis role="bold">Reverse
-            SSH</emphasis> . By default, the start port will
-            be <literal>7000</literal> and the maximum number of ports
+            automatically chosen by the Enea Edge Management in the range
+            defined in the <emphasis role="bold">SSH</emphasis> configuration
+            panel, available when accessing <emphasis
+            role="bold">System</emphasis>, then <emphasis
+            role="bold">Configuration</emphasis> and choosing <emphasis
+            role="bold">Reverse SSH</emphasis> . 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>