Updated doc to account for limtations in COSNOSCR-540

Signed-off-by: Paul Vaduva <Paul.Vaduva@enea.com>

Conflicts:
	book-enea-nfv-core-release-info/doc/known_bugs_and_limitations.xml

1 files changed, 9 insertions, 10 deletions

diff --git a/book-enea-nfv-core-release-info/doc/known_bugs_and_limitations.xml b/book-enea-nfv-core-release-info/doc/known_bugs_and_limitations.xml
index 9494eae..d87ebe2 100644
--- a/book-enea-nfv-core-release-info/doc/known_bugs_and_limitations.xml
+++ b/book-enea-nfv-core-release-info/doc/known_bugs_and_limitations.xml
@@ -24,15 +24,14 @@
           <listitem>
             <para>Description and Impact:</para>
 
-            <para>For aarch64 architecture qemu describes a CPU in terms of
-            Vendor, Model and Revision number in contrast with x86
-            architecture where CPU supported features (e. g. instruction set
-            supported) are used.</para>
-
-            <para>Due to lack of support in qemu for describing a cpu in terms
-            of features for aarch64 architecture (e. g. instruction set
-            supported) there will be impossible to migrate VMs between hosts
-            with different revision CPUs.</para>
+            <para>For an aarch64 architecture, QEMU describes a CPU in terms
+            of Vendor, Model and Revision number in contrast with the x86
+            architecture, where CPU supported features (e.g. the instruction
+            set supported) are used. </para>
+
+            <para>QEMU lacks support in describing a CPU in terms of features
+            for an aarch64 architecture, causing the migration of VMs between
+            hosts with different CPU revisions to fail.</para>
           </listitem>
 
           <listitem>
@@ -403,4 +402,4 @@
 
   <xi:include href="jiraissues_generated.xml"
               xmlns:xi="http://www.w3.org/2001/XInclude" /> -->
-</chapter>
\ No newline at end of file
+</chapter>