1 files changed, 42 insertions, 29 deletions

diff --git a/doc/book-enea-nfv-access-release-info/doc/about_release.xml b/doc/book-enea-nfv-access-release-info/doc/about_release.xml
index f056135..cb2e211 100644
--- a/doc/book-enea-nfv-access-release-info/doc/about_release.xml
+++ b/doc/book-enea-nfv-access-release-info/doc/about_release.xml
@@ -8,25 +8,28 @@
   href="eltf_params_updated.xml" xmlns:xi="http://www.w3.org/2001/XInclude"
   xpointer="element(EneaLinux_REL_VER/1)" /> includes optimizations to the
   FCAPS framework, DPDK, cross-developement on both an SDK and an eSDK,
-  USB-stick based installation, and various other optimizations,
-  security patches and documentation updated accordingly.</para>
-
-  <para><remark> INFO <emphasis role="bold">eltf_params_updated.xml</emphasis>
-  contains many parameters in the book, also in the open source books, and
-  MUST be created FROM <emphasis
-  role="bold">eltf_params_template.xml</emphasis>. The parameters are
-  automatically used in the books, via xi:include statements, similar to how
-  parameters from pardoc-distro.xml are included in the book. Read the file
-  <emphasis role="bold">eltf_params_updated_template_how_to_use.txt</emphasis>
-  for important details about formats and how to do! The idea is that ELTF
-  will auto-create/update it.</remark></para>
+  USB-stick based installation, and various other optimizations, security
+  patches and documentation updated accordingly.</para>
+
+  <para>
+    <remark>INFO <emphasis role="bold">eltf_params_updated.xml</emphasis>
+    contains many parameters in the book, also in the open source books, and
+    MUST be created FROM <emphasis
+    role="bold">eltf_params_template.xml</emphasis>. The parameters are
+    automatically used in the books, via xi:include statements, similar to how
+    parameters from pardoc-distro.xml are included in the book. Read the file
+    <emphasis
+    role="bold">eltf_params_updated_template_how_to_use.txt</emphasis> for
+    important details about formats and how to do! The idea is that ELTF will
+    auto-create/update it.</remark>
+  </para>
 
   <section id="release-content">
     <title>Enea NFV Access Release Content</title>
 
     <para>The release directory structure is detailed below:</para>
 
-    <programlisting condition="intel">-- Documentation/
+    <programlisting>-- Documentation/
    /* Enea NFV Access documentation */
 -- x86-64 /* architecture */
         -- xeon-d/
@@ -96,8 +99,8 @@
                         -- docker-pxe-ramboot
                            /* tools and files used in buidling a boot setup  */</programlisting>
 
-    <para condition="hidden">For each combination of image and target, the following set of
-    artifacts is available:</para>
+    <para condition="hidden">For each combination of image and target, the
+    following set of artifacts is available:</para>
 
     <programlisting condition="hidden">-- bzImage
    /* kernel image */
@@ -134,12 +137,13 @@
    /* external kernel modules */</programlisting>
   </section>
 
-  <remark>INFO Below is a complete section
-  with ID "eltf-target-tables-section" included from
-  elft_params_updated.xml. It contains a variable number of target tables
-  and the section title should be "Supported Targets with Parameters". It
-  has have a short sentence about what it is in the beginning. The subtitles
-  shall have the directory name of the target in the manifest.</remark>
+  <remark>INFO Below is a complete section with ID
+  "eltf-target-tables-section" included from elft_params_updated.xml. It
+  contains a variable number of target tables and the section title should be
+  "Supported Targets with Parameters". It has have a short sentence about what
+  it is in the beginning. The subtitles shall have the directory name of the
+  target in the manifest.</remark>
+
   <xi:include href="eltf_params_updated.xml"
               xmlns:xi="http://www.w3.org/2001/XInclude"
               xpointer="element(eltf-target-tables-section)" />
@@ -163,7 +167,7 @@
         Access release content.</para>
       </listitem>
 
-      <listitem condition="intel">
+      <listitem>
         <para><xi:include href="../../s_docbuild/olinkdb/pardoc-common.xml"
         xmlns:xi="http://www.w3.org/2001/XInclude"
         xpointer="element(book_enea_nfv_access_guide_intel/1)" />. Describes
@@ -172,9 +176,11 @@
       </listitem>
 
       <listitem condition="arm">
-        <para><phrase><olink targetdoc="book_enea_nfv_access_guide">Enea NFV
-        Access Guide</olink></phrase>. Describes how to use Enea NFV Access,
-        provides use cases and benchmark results.</para>
+        <para><phrase>
+            <olink targetdoc="book_enea_nfv_access_guide">Enea NFV Access
+            Guide</olink>
+          </phrase>. Describes how to use Enea NFV Access, provides use cases
+        and benchmark results.</para>
       </listitem>
 
       <listitem>
@@ -186,9 +192,17 @@
       </listitem>
 
       <listitem>
+        <para>Enea NFV Access eSDK Open Source Report.</para>
+      </listitem>
+
+      <listitem>
+        <para>Enea NFV Access SDK Open Source Report.</para>
+      </listitem>
+
+      <listitem>
         <para>Enea Element On-Device Management Kick Start Guide. Use this
-        guide to learn about the Element ODM software product, and install
-        and use Element ODM on both development and target platforms.</para>
+        guide to learn about the Element ODM software product, and install and
+        use Element ODM on both development and target platforms.</para>
       </listitem>
 
       <listitem>
@@ -209,5 +223,4 @@
       </listitem>
     </itemizedlist>
   </section>
-
-</chapter>
+</chapter>
\ No newline at end of file