Updated the ulink present in Getting Enea NFV Access.

Made touchups to Main Changes and Known Issues as well.

Signed-off-by: Miruna Paun <Miruna.Paun@enea.com>

1 files changed, 20 insertions, 24 deletions

diff --git a/doc/book-enea-nfv-access-release-info/doc/known_bugs_and_limitations.xml b/doc/book-enea-nfv-access-release-info/doc/known_bugs_and_limitations.xml
index cccb4df..caa3db5 100644
--- a/doc/book-enea-nfv-access-release-info/doc/known_bugs_and_limitations.xml
+++ b/doc/book-enea-nfv-access-release-info/doc/known_bugs_and_limitations.xml
@@ -4,33 +4,29 @@
 <chapter id="bugs-limitations">
   <title>Known Issues in this Release</title>
 
-  <para>All known issues listed in this chapter will be addressed in
-  maintenance updates following the major release.<remark>INFO: The <emphasis
-  role="bold">Release-Specific Problems</emphasis> section further down is
-  generated from JIRA with gen_known_issues.py, but that script is HARDCODED
-  with affectedversion "EL7_3-virtualization" and needs to be adapted when a
-  release info for another ENFV Access version changes.</remark></para>
+  <para>This chapter lists the known issues that affect the current
+  release.</para>
 
-  <section id="release-specific-limitations">
-    <title>Release-Specific Limitations</title>
+  <para><remark>The section further down is generated from JIRA with
+  gen_known_issues.py, but that script is HARDCODED with affectedversion
+  "EL7_3-virtualization" and needs to be adapted when a release info for
+  another ENFV Access version changes.</remark></para>
 
-    <itemizedlist>
-      <listitem>
-        <para>Kernel modules build using the SDK cannot be removed from the
-        <filename>enea-nfv-access</filename> image.</para>
-      </listitem>
+  <itemizedlist>
+    <listitem>
+      <para>Kernel modules build using the SDK cannot be removed from the
+      <filename>enea-nfv-access</filename> image.</para>
+    </listitem>
 
-      <listitem>
-        <para><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.<remark>LXCR-3283</remark></para>
-      </listitem>
-    </itemizedlist>
-  </section>
+    <listitem>
+      <para><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.<remark>LXCR-3283</remark></para>
+    </listitem>
+  </itemizedlist>
 
   <!-- The file with a section below is autocreated by make init  -->