1 files changed, 14 insertions, 19 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 a470845..a3b6779 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
@@ -7,27 +7,22 @@
   <para>This release of Enea NFV Access <xi:include
   href="eltf_params_updated.xml" xmlns:xi="http://www.w3.org/2001/XInclude"
   xpointer="element(EneaLinux_REL_VER/1)" /> provides a publicly available
-  Enea NFV Access distribution for a selected set of targets. This release is
-  generated from the yocto <xi:include href="eltf_params_updated.xml"
-  xmlns:xi="http://www.w3.org/2001/XInclude"
-  xpointer="element(Yocto_VER/1)" /> distribution using the branch <xi:include
-  href="eltf_params_updated.xml" xmlns:xi="http://www.w3.org/2001/XInclude"
-  xpointer="element(Yocto_NAME/1)" />.<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>
+  Enea NFV Access distribution for a selected set of targets.<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>NFV Access Release content</title>
 
-    <para>The NFV Access 1.0 Release contains along with other items,
-    documentation, pre-built kernels and images, a bootloader and a
-    SDK.</para>
+    <para>The current release contains along with other items, documentation,
+    pre-built kernels and images, a bootloader and a SDK.</para>
 
     <para>The directories structure is detailed below:</para>
 
@@ -151,7 +146,7 @@
         targetptr="book_enea_nfv_access_open_source">Enea NFV Access Open
         Source Report</olink> &ndash; A document containing the open source
         and license information pertaining to packages provided with Enea NFV
-        Access 1.0.</para>
+        Access.</para>
       </listitem>
 
       <listitem>
@@ -161,7 +156,7 @@
 
       <listitem>
         <para>Enea NFV Access Security Report &ndash; The document that lists
-        all security fixes included in the Enea NFV Access 1.0 release.</para>
+        all security fixes included in the Enea NFV Access release.</para>
       </listitem>
     </itemizedlist>
   </section>