1 files changed, 43 insertions, 127 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 0dbdd84..f048897 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
@@ -4,10 +4,11 @@
 <chapter id="advanced_conf">
   <title>Advanced Configurations</title>
 
-    <para>This chapter describes possible configurations for select advanced features
-    such as the Hugepage Reservation Service, UEFI Secure Boot and Bare Metal
-    Provisioning. These features are optional in the Enea NFV Access platform.
-    If you do not intend to use these features, skip this chapter.</para>
+  <para>This chapter describes possible configurations for select advanced
+  features such as the Hugepage Reservation Service, UEFI Secure Boot and Bare
+  Metal Provisioning. These features are optional in the Enea NFV Access
+  platform. If you do not intend to use these features, skip this
+  chapter.</para>
 
   <section id="hugepage_reservation">
     <title>Hugepage Reservation Service</title>
@@ -66,8 +67,8 @@
         <listitem>
           <para><literal>percent_os_alloc</literal>: Decides how much memory
           to try to reserve for userspace applications. The algorithm will try
-          to reserve at least the value of <literal>percent_os_alloc</literal> of the total
-          system memory for userspace applications.</para>
+          to reserve at least the value of <literal>percent_os_alloc</literal>
+          of the total system memory for userspace applications.</para>
         </listitem>
 
         <listitem>
@@ -117,8 +118,8 @@
     <section id="hugepage_customizing_man">
       <title>Customizing Manual Hugepage Reservation</title>
 
-      <para>The automatic algorithm can be disabled and hugepages in turn, configured
-      manually. To do this, comment the line which defines
+      <para>The automatic algorithm can be disabled and hugepages in turn,
+      configured manually. To do this, comment the line which defines
       <literal>hugepage_setup</literal> as <literal>auto</literal> and
       configure memory for each CPU socket in the following manner:</para>
 
@@ -149,20 +150,20 @@ node0.1048576kB = 3 </programlisting>
   <section id="uefi_secure_boot">
     <title>UEFI Secure Boot</title>
 
-      <para>Secure Boot was designed to enhance security in the pre-boot
-      environment. It prevents malicious software and applications from being
-      loaded during the system start-up process.</para>
+    <para>Secure Boot was designed to enhance security in the pre-boot
+    environment. It prevents malicious software and applications from being
+    loaded during the system start-up process.</para>
 
-      <para>The basic principle of UEFI Secure Boot is that it requires all
-      artifacts involved in the boot process (bootloaders, kernel, initramfs)
-      to be signed using a set of private keys. On a Secure Boot enabled uCPE
-      device these artifacts are checked against a set of public certificates
-      which correspond to these keys. If there are any mismatches the boot
-      process will fail at the stage(s) they are detected.</para>
+    <para>The basic principle of UEFI Secure Boot is that it requires all
+    artifacts involved in the boot process (bootloaders, kernel, initramfs) to
+    be signed using a set of private keys. On a Secure Boot enabled uCPE
+    device these artifacts are checked against a set of public certificates
+    which correspond to these keys. If there are any mismatches the boot
+    process will fail at the stage(s) they are detected.</para>
 
-      <para>For more information about Secure Boot please refer to <ulink
-      url="https://www.uefi.org/sites/default/files/resources/UEFI_Secure_Boot_in_Modern_Computer_Security_Solutions_2013.pdf">Secure
-      Boot in Modern Computer Security Solutions</ulink>.</para>
+    <para>For more information about Secure Boot please refer to <ulink
+    url="https://www.uefi.org/sites/default/files/resources/UEFI_Secure_Boot_in_Modern_Computer_Security_Solutions_2013.pdf">Secure
+    Boot in Modern Computer Security Solutions</ulink>.</para>
 
     <section id="secure_boot_keys">
       <title>Enabling UEFI Secure Boot</title>
@@ -213,101 +214,16 @@ node0.1048576kB = 3 </programlisting>
         can be found on the EFI partition (usually the first partition of the
         drive) under <literal>/uefi_sb_keys</literal>.</para>
 
-        <para><emphasis role="bold">How to manually enroll Enea
-        Certificates</emphasis></para>
-
-        <orderedlist>
-          <listitem>
-            <para>Reboot the uCPE device and press <literal>DEL</literal> to
-            enter into BIOS.</para>
-          </listitem>
-
-          <listitem>
-            <para>Select <literal>Secure Boot Mode</literal> -&gt;
-            <literal>Custom</literal>.</para>
-          </listitem>
-
-          <listitem>
-            <para>Select <literal>Key Management</literal> from the
-            <literal>Security</literal> menu.</para>
-          </listitem>
-
-          <listitem>
-            <para>Enroll the <literal>Platform Key (PK)</literal>:
-            <itemizedlist>
-                <listitem>
-                   Select <literal>Set New Key</literal> -&gt; 
-                  <literal>File from a file system</literal>.                   . 
-                </listitem>
-
-                <listitem>
-                   Specify the folder: <literal>&lt;user-keys&gt;/&lt;uefi_sb_keys&gt;/PK.esl</literal>
-              </listitem>
-
-                <listitem>
-                   Select <literal>Public Key Certificate</literal> and then <literal>Ok</literal>. 
-                </listitem>
-              </itemizedlist></para>
-          </listitem>
-
-          <listitem>
-            <para>Enroll the <literal>Key Exchange key (KEK)</literal>:
-            <itemizedlist>
-                <listitem>
-                   Select <literal>Set New Key</literal> -&gt; <literal>File from a file system</literal>.
-                </listitem>
-
-                <listitem>
-                   Specify the folder: <literal>&lt;user-keys&gt;/&lt;uefi_sb_keys&gt;/KEK.esl</literal>
-                </listitem>
-
-                <listitem>
-                   Select <literal>Public Key Certificate</literal> and then <literal>Ok</literal>. 
-                </listitem>
-              </itemizedlist></para>
-          </listitem>
-
-          <listitem>
-            <para>Enroll the <literal>Authorized Signature (DB)</literal>:
-            <itemizedlist>
-                <listitem>
-                   Select <literal>Set New Key</literal> -&gt; <literal>File from a file system</literal>. 
-                </listitem>
-
-                <listitem>
-                   Specify the folder: <literal>&lt;user-keys&gt;/&lt;uefi_sb_keys&gt;/DB.esl</literal>
-                </listitem>
-
-                <listitem>
-                   Select <literal>Public Key Certificate</literal> and then <literal>Ok</literal>. 
-                </listitem>
-              </itemizedlist></para>
-          </listitem>
-        </orderedlist>
-
-        <note>
-          <para>Details on how to provision the certificates may vary with
-          different versions of UEFI firmware.</para>
-        </note>
+        <para>These certificates need to be manually enrolled in BIOS. The
+        exact details on how to proceed may vary depending the version of the 
+          UEFI firmware.</para>
       </section>
 
       <section id="enable_secure_boot">
         <title>Enabling Secure Boot in BIOS</title>
 
-        <para>Once the certificates are provisioned we can enable the Secure
-        Boot feature:</para>
-
-        <orderedlist>
-          <listitem>
-            <para>Within BIOS, select the <literal>Security option</literal> from the top
-            menu.</para>
-          </listitem>
-
-          <listitem>
-            <para>Set the <literal>Boot Menu</literal> -&gt;
-            <literal>Enabled.</literal></para>
-          </listitem>
-        </orderedlist>
+        <para>Once the certificates are enrolled, Secure Boot needs to be
+        enabled in BIOS and the device rebooted.</para>
       </section>
     </section>
   </section>
@@ -315,21 +231,21 @@ node0.1048576kB = 3 </programlisting>
   <section id="bare_meta_prov">
     <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 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 (PXE) booting.</para>
-
-      <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
-      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
-      root filesystem. When the installation is complete, the uCPE device is
-      automatically rebooted into Enea NFV Access Run Time Platform.</para>
+    <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
+    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
+    (PXE) booting.</para>
+
+    <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
+    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
+    root filesystem. When the installation is complete, the uCPE device is
+    automatically rebooted into Enea NFV Access Run Time Platform.</para>
 
     <section id="bare_meta_prov_prereq">
       <title>Prerequisites</title>
@@ -438,8 +354,8 @@ node0.1048576kB = 3 </programlisting>
 
           <listitem>
             <para><literal>notify_path</literal>. Location where notification
-            files will be placed, specified in <literal>Server IP:directory</literal>
-            format.</para>
+            files will be placed, specified in <literal>Server
+            IP:directory</literal> format.</para>
           </listitem>
         </itemizedlist>