6 files changed, 240 insertions, 309 deletions

diff --git a/doc/book-enea-edge-release-info/doc/about_release.xml b/doc/book-enea-edge-release-info/doc/about_release.xml
index 349c955..076538f 100644
--- a/doc/book-enea-edge-release-info/doc/about_release.xml
+++ b/doc/book-enea-edge-release-info/doc/about_release.xml
@@ -6,19 +6,19 @@
 
   <para>Enea Edge is a complete Virtualization Infrastructure software
   platform designed for deployment on any white box uCPE device, and optimized
-  for common use-cases. It includes the Enea Edge Runtime deployed
-  on a white box, the Enea Edge Management application and the Enea Edge 
-    Automation, management and automation tools deployed in a 
-    private or public cloud.</para>
+  for common use-cases. It includes the Enea Edge Runtime deployed on a white
+  box, the Enea Edge Management application and the Enea Edge Automation,
+  management and automation tools deployed in a private or public
+  cloud.</para>
 
-  <para>The Enea Edge <xi:include
-  href="../../s_doceneacommon/doc/eltf_params_updated.xml"
+  <para>The Enea Edge <xi:include href="../../eltf_params_updated.xml"
   xmlns:xi="http://www.w3.org/2001/XInclude"
-  xpointer="element(EneaLinux_REL_VER/1)" /> Release includes new features, 
-    optimizations, corrections, and updates to the user documentation.. 
-    A list of major new features and improvements can be found in  
-    <xref linkend="relinfo-changes-other">Section 2.1 New Features and Improvements</xref>.</para>
-  
+  xpointer="element(EneaEdge_REL_VER/1)" /> Release includes new features,
+  optimizations, corrections, and updates to the user documentation. A list of
+  major new features and improvements can be found in <xref
+  linkend="relinfo-changes-other">Section 2.1 New Features and
+  Improvements</xref>.</para>
+
   <section id="release-content">
     <title>Enea Edge Release Content</title>
 
@@ -45,8 +45,7 @@
 
       <listitem>
         <para>Enea_Edge_AF-TH_&lt;version&gt;-build&lt;build_number&gt;.zip
-        (deprecated, see <xref linkend="relinfo-changes-other">Section 2.1 New
-        Features and Improvements</xref>.)</para>
+        (deprecated as of version 2.4.0.)</para>
       </listitem>
     </itemizedlist>
 
@@ -103,7 +102,7 @@
   it is in the beginning. The subtitles shall have the directory name of the
   target in the manifest.</remark>
 
-  <xi:include href="../../s_doceneacommon/doc/eltf_params_updated.xml"
+  <xi:include href="../../eltf_params_updated.xml"
               xmlns:xi="http://www.w3.org/2001/XInclude"
               xpointer="element(eltf-target-tables-section)" />
 
@@ -150,8 +149,7 @@
         xmlns:xi="http://www.w3.org/2001/XInclude"
         xpointer="element(book_enea_edge_auto_fw_th_user_guide/1)" />.
         Describes the Automation Framework and Test Harness for Enea Edge
-        (deprecated, see <xref linkend="relinfo-changes-other">Section 2.1 New
-        Features and Improvements</xref>).</para>
+        (deprecated).</para>
       </listitem>
 
       <listitem>
@@ -159,29 +157,7 @@
         xmlns:xi="http://www.w3.org/2001/XInclude"
         xpointer="element(book_enea_edge_system_test_specification/1)" />.
         Describes a sample Test Suite for System Testing of Enea Edge.
-        (deprecated, see <xref linkend="relinfo-changes-other">Section 2.1 New
-        Features and Improvements</xref>).</para>
-      </listitem>
-    </itemizedlist>
-  </section>
-
-  <section id="release-browsers">
-    <title>Supported Web Browsers</title>
-
-    <para>The current release supports using the following web
-    browsers:</para>
-
-    <itemizedlist>
-      <listitem>
-        <para>Google Chrome (tested with version 89).</para>
-      </listitem>
-
-      <listitem>
-        <para>Mozilla Firefox (tested with version 87).</para>
-      </listitem>
-
-      <listitem>
-        <para>Microsoft Edge (tested with version 89).</para>
+        (deprecated).</para>
       </listitem>
     </itemizedlist>
   </section>
diff --git a/doc/book-enea-edge-release-info/doc/book.xml b/doc/book-enea-edge-release-info/doc/book.xml
index 0b77f41..6897c6f 100644
--- a/doc/book-enea-edge-release-info/doc/book.xml
+++ b/doc/book-enea-edge-release-info/doc/book.xml
@@ -8,9 +8,9 @@
   Information</title>
 
   <subtitle>Release Version <xi:include
-  href="../../s_doceneacommon/doc/eltf_params_updated.xml"
+  href="../../eltf_params_updated.xml"
   xmlns:xi="http://www.w3.org/2001/XInclude"
-  xpointer="element(EneaLinux_REL_VER/1)" /></subtitle>
+  xpointer="element(EneaEdge_REL_VER/1)" /></subtitle>
 
   <!-- OLINKDBPATH_USED_BY_XMLMIND ../../s_docbuild/olinkdb  -->
 
diff --git a/doc/book-enea-edge-release-info/doc/getting_enea_nfv_access.xml b/doc/book-enea-edge-release-info/doc/getting_enea_nfv_access.xml
deleted file mode 100644
index 9eecd3c..0000000
--- a/doc/book-enea-edge-release-info/doc/getting_enea_nfv_access.xml
+++ /dev/null
@@ -1,54 +0,0 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
-"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
-<chapter id="relinfo-getting-enea-nfv-access">
-  <title>Getting Enea NFV Access</title>
-
-  <para>Enea NFV Access releases and updates are available as binaries ready
-  for download.</para>
-
-  <para><emphasis role="bold">Downloading Enea NFV Access</emphasis></para>
-<remark>Does the content below need to be revised to no longer make reference or mention to Enea Portal?</remark>
-  <orderedlist>
-    <listitem>
-      <para>Log in to the link above using the credentials provided by
-      Enea.</para>
-    </listitem>
-
-    <listitem>
-      <para>From the right corner of the top main menu, choose the
-      <literal>Access</literal> section.</para>
-    </listitem>
-
-    <listitem>
-      <para>The <literal>Files</literal> section on the left will display each
-      official release of Enea NFV Access, with the latest at the top.</para>
-
-      <para>Each release listing displays the dates for release and updates
-      available, along with a <literal>Download</literal> button that allows
-      you to directly save the version you wish to use.</para>
-    </listitem>
-
-    <listitem>
-      <para>By clicking on the link at the top of any listing of Enea NFV
-      Access, you'll access the changelog page for that version. At the bottom
-      of the page are clearly labeled region-specific zip files containing the
-      binary sources.</para>
-
-      <para>Documentation is also available at the bottom of the page.</para>
-    </listitem>
-
-    <listitem>
-      <para>On the right side of the main <literal>Access</literal> page is
-      the <literal>Online Documentation</literal> section, listing pdfs for
-      the latest versions of documentation. They can all be accessed for
-      indiviudual downloading without the need to download the binaries
-      first.</para>
-    </listitem>
-  </orderedlist>
-
-  <para>For details about the books delivered and their purpose, refer to
-  <xref linkend="relinfo-documentation" />. For information concerning the
-  contents of the release package, please see <xref
-  linkend="release-content" />.</para>
-</chapter>
diff --git a/doc/book-enea-edge-release-info/doc/known_bugs_and_limitations.xml b/doc/book-enea-edge-release-info/doc/known_bugs_and_limitations.xml
index 81816a5..13a8c23 100644
--- a/doc/book-enea-edge-release-info/doc/known_bugs_and_limitations.xml
+++ b/doc/book-enea-edge-release-info/doc/known_bugs_and_limitations.xml
@@ -4,38 +4,59 @@
 <chapter id="bugs-limitations">
   <title>Known Issues and Limitations in this Release</title>
 
-  <para>This chapter lists the known general issues and limitations that
-  affect the current release.</para>
+  <note>
+    <para>All issues may also affect previous releases.</para>
+  </note>
 
   <itemizedlist>
     <listitem>
-      <para><remark>LXCR-9904</remark>Enea Edge Runtime cannot be installed on
-      USB storage devices.</para>
+      <para><remark>ELCCR-1688, ELCCR-1809</remark>It is possible to end up
+      with a corrupted VM image from the download operation. If that happens,
+      the VNF instantiation will fail. The corrupted image has to be manually
+      removed from <literal>/var/odm/vm_images/startup/</literal>.</para>
     </listitem>
 
     <listitem>
-      <para><remark>LXCR-9799</remark>Proper boot order is not ensured if a
-      uCPE device has more than one HDD attached.</para>
+      <para><remark>ELCCR-1733</remark>Logging into the Enea Edge Management
+      application over HTTP can fail, producing the error <literal>You have
+      been automatically logged out</literal>. If this happens, the user
+      should clear the <literal>JSESSIONID</literal> browser's cookie or close
+      and restart the browser.</para>
     </listitem>
 
     <listitem>
-      <para><remark>ELCCR-527</remark>Cancelling a file upload in the Enea
-      Edge Management will require the user to close and reopen the upload
-      window for the next upload to work.</para>
+      <para><remark>ELCCR-1753</remark>When using tap interfaces for
+      communicating over the bridge, port numbers assigned to VM interfaces
+      can change when the VMs are restarted. The only currently known
+      workaround is rebooting the uCPE device.</para>
     </listitem>
-
+    
     <listitem>
-      <para><remark>ELCCR-577</remark>If the Enea Edge Management application
-      is restored from a backup made on a release version older than Enea NFV
-      Access 2.2.3, VNFs cannot be instantiated from the GUI.</para>
+      <para><remark>ELCCR-1999</remark>Attempting to upload multiple files 
+        simultaneously (e.g. a VNF image and custom scripts) in the Enea Edge
+        Management application will cause all upload operations to be canceled. 
+        In order to avoid this limitation, please wait until any previous 
+        upload finishes before initiating a new one.</para>
     </listitem>
-    
+
     <listitem>
-      <para><remark>ELCCR-1134</remark>In order to avoid an incorrect boot 
-        order after a failed upgrade, the user should remove the upgrade 
-        image before attempting again.</para>
+      <para><remark>LXCR-10922</remark>A very rare error on some Atom C3000
+      boards makes X553 SFP+ Ethernet ports unusable until a target cold reset
+      is performed. When the error occurs in Enea Edge Runtime 2.5.0, there
+      will be a warning printed into the console by the
+      <literal>ixgbe</literal> driver:</para>
+
+      <programlisting>[11.361580] ixgbe 0000:0a:00.0: Warning firmware error detected FWSM: 0x8010801A</programlisting>
+
+      <para>The only currently known workaround for this issue is a cold
+      reset.</para>
     </listitem>
+  </itemizedlist>
 
+  <para><emphasis role="bold">Limitations detected in previous releases, 
+    that still affect this release:</emphasis></para>
+
+  <itemizedlist>
     <listitem>
       <para><remark>ELCCR-474</remark>Deleting VNF instances with flows
       configured on the OVS bridges can be done only after removing the
@@ -43,12 +64,24 @@
     </listitem>
 
     <listitem>
+      <para><remark>ELCCR-527</remark>Canceling a file upload in the Enea Edge
+      Management application will require the user to close and reopen the
+      upload window for the next upload to work.</para>
+    </listitem>
+
+    <listitem>
       <para><remark>ELCCR-572</remark>Sometimes when selecting and deleting
       more than one VNF instance simultaneously, an error message might be
       triggered, even if the delete operation succeeds.</para>
     </listitem>
 
     <listitem>
+      <para><remark>ELCCR-577</remark>If the Enea Edge Management application
+      is restored from a backup made on a release version older than Enea NFV
+      Access 2.2.3, VNFs cannot be instantiated from the GUI.</para>
+    </listitem>
+
+    <listitem>
       <para><remark>ELCCR-847</remark>The Juniper vSRX VNF cannot be
       instantiated on the Xeon-D architectures due to missing CPU features in
       the VNF's domain XML. This impacts all example use cases where the
@@ -56,10 +89,53 @@
     </listitem>
 
     <listitem>
-      <para><remark>USERDOCAP-648</remark>The <literal>storage size</literal>
-      parameter on the VNF onboarding page is ignored. The default storage
-      size specified when creating the VM image is used when instantiating the
-      VM and when presenting VM information.</para>
+      <para><remark>ELCCR-912</remark>When the Enea Edge Management
+      application is installed on CentOS 7, prior to C7.1804 (kernel version
+      3.10.0-862), adding an upgrade image fails. As a workaround, please
+      update <literal>glib2</literal> to version 2.54.2 or later, using
+      <literal>#yum update glib2</literal>.</para>
+    </listitem>
+
+    <listitem>
+      <para><remark>ELCCR-1468</remark>When using the Enea Edge Management
+      application in HTTPS mode, upgrading a device from NFV Access 2.3.0 is
+      not possible. Either switch to HTTP mode (for more details see <olink
+      targetdoc="book_enea_edge_getting_started"
+      targetptr="device_up_process">The uCPE device Upgrade Process in the
+      <xi:include href="../../s_docbuild/olinkdb/pardoc-names.xml"
+      xmlns:xi="http://www.w3.org/2001/XInclude"
+      xpointer="element(book_enea_edge_getting_started/1)" /></olink> Manual)
+      or install it manually.</para>
+    </listitem>
+
+    <listitem>
+      <para><remark>ELCCR-1497</remark>If the Enea Edge Management application
+      has an incorrect database configuration, when performing an
+      uninstallation, the Tomcat instance and Watchdog service will not be
+      stopped automatically. Instead, they must be killed explicitly.</para>
+    </listitem>
+
+    <listitem>
+      <para><remark>ELCCR-1565</remark>Before starting an Enea Edge Management
+      upgrade, any owned Tomcat certificates should be manually copied into
+      the
+      <literal>/opt/ems/ucpemanager/application/config/certificates</literal>
+      folder.</para>
+    </listitem>
+
+    <listitem condition="hidden">
+      <para><remark>LXCR-3283</remark><emphasis role="bold">PDF
+      navigation</emphasis>: When using links to open other PDFs, or jump to
+      another place in the same PDF, jumping back sometimes fails. This has
+      been observed when opening a PDF in Adobe Reader, inside a browser with
+      PDF add-on, as well as when the browser is configured to open PDF files
+      in an external PDF reader. As a workaround, open the HTML version of the
+      document.</para>
+    </listitem>
+
+    <listitem>
+      <para><remark>LXCR-9799</remark>Proper boot order is not ensured if a
+      uCPE device has more than one HDD attached.</para>
     </listitem>
 
     <listitem>
@@ -67,11 +143,10 @@
       to be connected to a network with at least a router/gateway installed
       for next-hop communication.</para>
     </listitem>
-    
+
     <listitem>
-      <para><remark>ELCCR-1504</remark>To change the type of an interface 
-        from DPDK to SR-IOV, first delete the existing interface, then 
-        recreate it with the desired type.</para>
+      <para><remark>LXCR-9904</remark>Enea Edge Runtime cannot be installed on
+      USB storage devices.</para>
     </listitem>
 
     <listitem>
@@ -85,29 +160,9 @@
     </listitem>
 
     <listitem>
-      <para><remark>STCR-6224</remark>The Enea Edge Automation and the Enea
-      Edge Automation Framework and Test Harness do not support multiple
-      custom scripts uploaded to a uCPE device at the same time.</para>
-    </listitem>
-
-    <listitem>
-      <para><remark>STCR-6292</remark>Management of WAN Interfaces is not
-      implemented in the Enea Edge Automation Framework and Test
-      Harness.</para>
-    </listitem>
-
-    <listitem>
-      <para><remark>USERDOCAP-628</remark>Enea Edge Automation Framework and
-      Test Harness does not have support for product features implemented in
-      Enea Edge 2.4.0 or newer.</para>
-    </listitem>
-
-    <listitem>
-      <para><remark>ELCCR-912</remark>When the Enea Edge Management
-      application is installed on CentOS 7, prior to C7.1804 (kernel version
-      3.10.0-862), adding an upgrade image fails. As a workaround, please
-      update <literal>glib2</literal> to version 2.54.2 or later, using
-      <literal>#yum update glib2</literal>.</para>
+      <para><remark>LXCR-10750</remark>In order to avoid an incorrect boot
+      order after a failed upgrade, the user should remove the upgrade image
+      before attempting again.</para>
     </listitem>
 
     <listitem>
@@ -117,58 +172,42 @@
     </listitem>
 
     <listitem>
+      <para><remark>USERDOCAP-648</remark>The <literal>storage size</literal>
+      parameter on the VNF onboarding page is ignored. The default storage
+      size specified when creating the VM image is used when instantiating the
+      VM and when presenting VM information.</para>
+    </listitem>
+
+    <listitem>
       <para><remark>USERDOCAP-651</remark>Wireless AP configuration is
       optimized for wireless modules that use the <literal>ath10k</literal>
       driver. Using other wireless modules may result in undefined
       behavior.</para>
     </listitem>
+  </itemizedlist>
 
-    <listitem>
-      <para><remark>ELCCR-1518</remark>The Wireless AP's wpa2psk password
-      should not contain white space characters.</para>
-    </listitem>
+  <para><emphasis role="bold">The following limitations affect deprecated
+  components and their documentation:</emphasis></para>
 
+  <itemizedlist>
     <listitem>
-      <para><remark>ELCCR-1561</remark>Before starting an Enea Edge Management
-      upgrade, any owned Tomcat certificates should be manually copied into the 
-        <literal>/opt/ems/ucpemanager/application/3rdParty/apache-tomcat/conf/config/certificates</literal>
-      folder.</para>
+      <para><remark>STCR-6224</remark>The Enea Edge Automation Framework and
+      Test Harness do not support multiple custom scripts uploaded to a uCPE
+      device at the same time. This limitation does not apply to Enea Edge
+      Automation.</para>
     </listitem>
 
     <listitem>
-      <para><remark>ELCCR-1378</remark>Modifying the type of the external
-      interfaces can lead to errors. Instead of modifying, it is recommended
-      to delete the old interfaces and recreate them with the desired
-      type.</para>
-    </listitem>
-    
-    <listitem>
-      <para><remark>ELCCR-1497</remark>If the Enea Edge Management application 
-        has an incorrect database configuration, when performing an uninstallation, 
-        the Tomcat instance and Watchdog service will not be stopped automatically. 
-        Instead, they must be killed explicitly.</para>
-    </listitem>
-    
-    <listitem>
-      <para><remark>ELCCR-1468</remark>When using the Enea Edge Management
-      application in HTTPS mode, upgrading a device from NFV Access 2.3.0 is
-      not possible. Either switch to HTTP mode (for more details see <olink
-      targetdoc="book_enea_edge_getting_started"
-      targetptr="device_up_process">The uCPE device Upgrade Process in the
-      <xi:include href="../../s_docbuild/olinkdb/pardoc-names.xml"
-      xmlns:xi="http://www.w3.org/2001/XInclude"
-      xpointer="element(book_enea_edge_getting_started/1)" /></olink> Manual)
-      or install it manually.</para>
+      <para><remark>STCR-6292</remark>Management of WAN Interfaces is not
+      implemented in the Enea Edge Automation Framework and Test
+      Harness. This limitation does not apply to the Enea Edge Automation.</para>
     </listitem>
 
-    <listitem condition="hidden">
-      <para><remark>LXCR-3283</remark><emphasis role="bold">PDF
-      navigation</emphasis>: When using links to open other PDFs, or jump to
-      another place in the same PDF, jumping back sometimes fails. This has
-      been observed when opening a PDF in Adobe Reader, inside a browser with
-      PDF add-on, as well as when the browser is configured to open PDF files
-      in an external PDF reader. As a workaround, open the HTML version of the
-      document.</para>
+    <listitem>
+      <para><remark>USERDOCAP-628</remark>The Enea Edge Automation Framework
+      and Test Harness do not have support for product features implemented in
+      Enea Edge 2.4.0 or newer. Please use the new Enea Edge Automation 
+        component if you want support for newer features.</para>
     </listitem>
   </itemizedlist>
 
@@ -176,4 +215,4 @@
 
   <!-- <xi:include href="jiraissues_generated.xml"
               xmlns:xi="http://www.w3.org/2001/XInclude" /> -->
-</chapter>
+</chapter>
\ No newline at end of file
diff --git a/doc/book-enea-edge-release-info/doc/main_changes.xml b/doc/book-enea-edge-release-info/doc/main_changes.xml
index 8824aa3..629a892 100644
--- a/doc/book-enea-edge-release-info/doc/main_changes.xml
+++ b/doc/book-enea-edge-release-info/doc/main_changes.xml
@@ -15,10 +15,10 @@
 
     <itemizedlist>
       <listitem>
-        <para><remark>CPDX-3496</remark>Embedded WiFi support for all-in-one
-        store/home office deployment. For more details please see the <olink
-        targetdoc="book_enea_edge_getting_started"
-        targetptr="wap_interface_type">Wap Interface Type in the <xi:include
+        <para>Support for Fully Qualified Domain Names (FQDN) for the Enea
+        Edge Management application address. For more details please see
+        <olink targetdoc="book_enea_edge_getting_started"
+        targetptr="prep_deploy">Preparing the Deployment in the <xi:include
         href="../../s_docbuild/olinkdb/pardoc-names.xml"
         xmlns:xi="http://www.w3.org/2001/XInclude"
         xpointer="element(book_enea_edge_getting_started/1)" /></olink>
@@ -26,10 +26,11 @@
       </listitem>
 
       <listitem>
-        <para><remark>CPDX-3499</remark>Expanded hardware, OS and network
-        monitoring capability with Grafana integration. For more details
-        please see <olink targetdoc="book_enea_edge_getting_started"
-        targetptr="grafana">Using Grafana and InfluxDB in the <xi:include
+        <para>Support for a DNS servers list for WAN interfaces with a static
+        IP configuration. For more details please see <olink
+        targetdoc="book_enea_edge_getting_started"
+        targetptr="install_ena_device">Installing Enea Edge - uCPE Device
+        Installation in the <xi:include
         href="../../s_docbuild/olinkdb/pardoc-names.xml"
         xmlns:xi="http://www.w3.org/2001/XInclude"
         xpointer="element(book_enea_edge_getting_started/1)" /></olink>
@@ -37,38 +38,25 @@
       </listitem>
 
       <listitem>
-        <para><remark>CPDX-3407</remark>HTTPS based downloads of VNFs for
-        simplified deployment of the Enea Edge Management application in cloud
-        environments. For more details please see <olink
-        targetdoc="book_enea_edge_getting_started"
-        targetptr="fresh_ucpemg_install">Fresh Installation of the Enea Edge
-        Management application in the <xi:include
-        href="../../s_docbuild/olinkdb/pardoc-names.xml"
+        <para>Support for NFV Infrastructure backup and restore to allow for
+        recovery to a previously known state. For more details please see
+        <olink targetdoc="book_enea_edge_getting_started"
+        targetptr="nfvi_backup">NFV Infrastructure Backup Operations in the
+        <xi:include href="../../s_docbuild/olinkdb/pardoc-names.xml"
         xmlns:xi="http://www.w3.org/2001/XInclude"
         xpointer="element(book_enea_edge_getting_started/1)" /></olink>
         Manual.</para>
       </listitem>
 
       <listitem>
-        <para><remark>CPDX-3500</remark>Enea Edge Automation, a tool for
-        automatic system configuration based on Python scripting that will
-        replace the existing Enea Edge Automation Framework and Test Harness
-        in the next major release. For more details please see the <ns:include
-        href="../../s_docbuild/olinkdb/pardoc-common.xml"
-        xmlns:ns="http://www.w3.org/2001/XInclude"
-        xpointer="element(book_enea_edge_automation_user_guide/1)" />.</para>
-
-        <note>
-          <para>The Enea Edge Automation Framework and Test Harness, and its
-          related documentation the <ns:include
-          href="../../s_docbuild/olinkdb/pardoc-common.xml"
-          xmlns:ns="http://www.w3.org/2001/XInclude"
-          xpointer="element(book_enea_edge_auto_fw_th_user_guide/1)" /> and
-          the <ns:include href="../../s_docbuild/olinkdb/pardoc-common.xml"
-          xmlns:ns="http://www.w3.org/2001/XInclude"
-          xpointer="element(book_enea_edge_system_test_specification/1)" />
-          are deprecated starting with Enea Edge 2.4.0.</para>
-        </note>
+        <para>Support for VNF snapshotting to allow for storing, managing and
+        restoring snapshots of VNFs deployed on Enea Edge Runtime. For more
+        details please see <olink targetdoc="book_enea_edge_getting_started"
+        targetptr="vnf_snapshots">VNF Snapshots in the <xi:include
+        href="../../s_docbuild/olinkdb/pardoc-names.xml"
+        xmlns:xi="http://www.w3.org/2001/XInclude"
+        xpointer="element(book_enea_edge_getting_started/1)" /></olink>
+        Manual.</para>
       </listitem>
     </itemizedlist>
 
@@ -76,20 +64,81 @@
 
     <itemizedlist>
       <listitem>
-        <para>A new <emphasis role="bold">Requirements</emphasis> page has
-        been added to the Web-installer, displaying device characteristics and
-        checking minimal hardware requirements.</para>
+        <para>Documented and hardened support for Factory Reset allowing 
+          reverting of the Enea Edge Runtime to its initial state. 
+          For more details please see <olink
+        targetdoc="book_enea_edge_getting_started"
+        targetptr="basic_oper_device">Basic operations for uCPE device
+        Management in the <ns:include
+        href="../../s_docbuild/olinkdb/pardoc-names.xml"
+        xpointer="element(book_enea_edge_getting_started/1)"
+        xmlns:ns="http://www.w3.org/2001/XInclude" /></olink> Manual.</para>
+      </listitem>
+
+      <listitem>
+        <para>Added support for uploading multiple custom scripts on a uCPE
+        Device in the Enea Edge Automation framework.</para>
+      </listitem>
+
+      <listitem>
+        <para>Python APIs from the Enea Edge Automation framework can now be
+        run with a limited set of optional parameters.</para>
+      </listitem>
+
+      <listitem>
+        <para>Configuration files from the Enea Edge Automation framework can
+        now be generated in a non-interactive way with a limited set of
+        optional parameters.</para>
+      </listitem>
+
+      <listitem>
+        <para>Improved support for large deployments of Enea Edge.</para>
       </listitem>
 
       <listitem>
-        <para>A Web-installer's log is displayed on the last page in case the
-        installation process has failed.</para>
+        <para>Improved the upgrade and uninstall processes of the Enea Edge
+        Management component: the database information is no longer requested
+        during an upgrade or an uninstall.</para>
       </listitem>
 
       <listitem>
-        <para>Extended Web-installer support for NVME disks.</para>
+        <para>Enea Edge Runtime key component upgrades include:</para>
+
+        <itemizedlist spacing="compact">
+          <listitem>
+            <para>Linux kernel 5.10</para>
+          </listitem>
+
+          <listitem>
+            <para>Open vSwitch 2.15</para>
+          </listitem>
+
+          <listitem>
+            <para>QEMU 5.2.0</para>
+          </listitem>
+
+          <listitem>
+            <para>libvirt 6.3.0</para>
+          </listitem>
+
+          <listitem>
+            <para>DPDK 20.11.1</para>
+          </listitem>
+
+          <listitem>
+            <para>Python 3.9.4</para>
+          </listitem>
+        </itemizedlist>
+
+        <para>Further information about what open source versions are used in
+        Enea Edge Runtime, can be found in the Enea Edge Runtime Open Source
+        Report.</para>
       </listitem>
     </itemizedlist>
+    
+    <para></para>
+    <para></para>
+    <para></para>
 
     <para><emphasis role="bold">Early Access Features:</emphasis></para>
 
@@ -100,7 +149,8 @@
       <listitem>
         <para><remark>CPDX-3498</remark>High Availability support with
         redundant Enea Edge Management applications in active standby
-        configuration.</para>
+        configuration. This EA feature has remained unchanged since the 
+          Enea Edge 2.4.0 release.</para>
 
         <para>In order to increase resiliency on the uCPE management side, the
         Enea Edge Management application can be installed in High-Availability
@@ -109,27 +159,6 @@
         Centers and geographical locations, and with multiple MariaDB servers
         for each location.</para>
       </listitem>
-
-      <listitem>
-        <para>Platform and VNF Snapshots (made originally available starting
-        with Enea NFV Access 2.3.0).</para>
-
-        <para>Platform Snapshots allow users to store, manage and restore
-        snapshots of the Enea Edge Runtime configuration, with the purpose of
-        recovering after a failed reconfiguration. This feature is disabled by
-        default.</para>
-
-        <para>VNF Snapshots allow users to store, manage and restore snapshots
-        of VNFs deployed on the Enea Edge Runtime, with the purpose of
-        restoring the VNF after a persistent VNF failure. This feature is
-        disabled by default.</para>
-
-        <note>
-          <para>Users that would like to try out the Early Access features
-          should contact Enea Support for additional documentation and
-          assistance.</para>
-        </note>
-      </listitem>
     </itemizedlist>
 
     <para>Early Access features are provided for evaluation and early
@@ -183,7 +212,10 @@
   <section id="relinfo-backward-compat">
     <title>Compatibility</title>
 
-    <para>This release does not contain any change impacting
-    compatibility.</para>
+    <para>This release does not contain any public API changes impacting
+    backwards compatibility. However, Python 2 support in Enea Edge Runtime 
+      has been discontinued starting with the current version of Enea Edge. 
+      This could affect existing custom scripts using Python 2 syntax. Please 
+      update these scripts accordingly in order to run in a Python 3 environment.</para>
   </section>
 </chapter>
\ No newline at end of file
diff --git a/doc/book-enea-edge-release-info/doc/system_requirements_prerequisites.xml b/doc/book-enea-edge-release-info/doc/system_requirements_prerequisites.xml
deleted file mode 100644
index b0317b3..0000000
--- a/doc/book-enea-edge-release-info/doc/system_requirements_prerequisites.xml
+++ /dev/null
@@ -1,62 +0,0 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
-"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
-<chapter id="sys-req-prerequisites">
-  <title>Host Requirements</title>
-
-  <para>Using Enea NFV Access or compiling applications requires certain
-  packages to be installed on your build host. The requirements listed below
-  are extensive to allow getting Enea NFV Access to be booted on target
-  machines and for building applications.</para>
-
-  <informaltable>
-    <tgroup cols="2">
-      <colspec align="left" colname="1" colwidth="1*" />
-
-      <colspec align="left" colname="2" colwidth="3*" />
-
-      <spanspec nameend="2" namest="1" spanname="onetwo" />
-
-      <tbody>
-        <row>
-          <entry spanname="onetwo"><emphasis role="bold"> Build Host
-          Requirements<indexterm>
-              <primary>host requirements</primary>
-            </indexterm></emphasis></entry>
-        </row>
-
-        <row>
-          <entry>Linux distribution</entry>
-
-          <entry>The downloaded product can installed on the target machine
-          using a Linux host. For information about supported hosts and
-          targets, see <xref
-          linkend="relinfo-supported-host-environment" />.</entry>
-        </row>
-
-        <row>
-          <entry>Packages</entry>
-
-          <entry>Depending on the Linux distribution and version of the host,
-          certain packages may be required. See details on what packages are
-          needed and how to install them in the following sections.</entry>
-        </row>
-
-        <row>
-          <entry>Disk space</entry>
-
-          <entry>Your build host should have at least 50 GB of free disk space
-          for installing the SDK, eSDK or cross-compiling
-          applications.</entry>
-        </row>
-
-        <row>
-          <entry>Recommended RAM</entry>
-
-          <entry>Your build host must have at least 4 GB available
-          RAM.</entry>
-        </row>
-      </tbody>
-    </tgroup>
-  </informaltable>
-</chapter>
\ No newline at end of file