1 files changed, 12 insertions, 14 deletions

diff --git a/doc/book-enea-nfv-access-platform-guide/doc/container_virtualization.xml b/doc/book-enea-nfv-access-platform-guide/doc/container_virtualization.xml
index c6ce223..055de7c 100644
--- a/doc/book-enea-nfv-access-platform-guide/doc/container_virtualization.xml
+++ b/doc/book-enea-nfv-access-platform-guide/doc/container_virtualization.xml
@@ -15,7 +15,7 @@
     <para>The software container mechanism uses resource isolation features
     inside the Linux kernel, such as cgroups and kernel namespaces to allow
     multiple containers to run within a single Linux instance, avoiding the
-    overhead of starting and maintaining virtual machines. </para>
+    overhead of starting and maintaining virtual machines.</para>
 
     <para>Containers are lightweight and include everything needed to run
     themselves: code, runtime, system tools, system libraries and settings.
@@ -23,7 +23,7 @@
     software is isolated from its surroundings. For example, differences
     between development and staging environments can be kept separate in order
     to reduce conflicts between teams running different software on the same
-    infrastructure. </para>
+    infrastructure.</para>
 
     <para>For a better understanding of what Docker is and how it works, the
     official documentation provided on the Docker website should be consulted:
@@ -37,12 +37,10 @@
       system is running the daemon correctly. This container can be launched
       by simply running:</para>
 
-      <programlisting>&gt;docker run hello-world
+      <programlisting>docker run hello-world</programlisting>
 
-Hello from Docker!</programlisting>
-
-      <para>This message shows that your installation appears to be working
-      correctly.</para>
+      <para>If your installation is working correctly, the following message
+      should be outputted:<programlisting>Hello from Docker!</programlisting></para>
     </section>
 
     <section id="run-enfv-guest-image">
@@ -52,17 +50,17 @@ Hello from Docker!</programlisting>
       other container can. Before starting an Enea NFV Access Platform guest
       image, a root filesystem has to be imported in Docker:</para>
 
-      <programlisting>&gt;docker import enea-linux-virtualization-guest-x86-64.tar.gz el7guest</programlisting>
+      <programlisting>docker import enea-linux-virtualization-guest-qemux86-64.tar.gz el7guest</programlisting>
 
       <para>To check that the Docker image has been imported successfully,
       run:</para>
 
-      <programlisting>&gt;docker images</programlisting>
+      <programlisting>docker images</programlisting>
 
       <para>Finally, start an Enea NFV Access Platform container with
       <literal>bash</literal> running as the shell, by running:</para>
 
-      <programlisting>&gt;docker run -it el7guest /bin/bash</programlisting>
+      <programlisting>docker run -it el7guest /bin/bash</programlisting>
     </section>
 
     <section id="attach-ext-resources-docker-containers">
@@ -77,7 +75,7 @@ Hello from Docker!</programlisting>
       <literal>roots</literal> home folder to a container, the command line
       for Docker should have the following format:</para>
 
-      <programlisting>&gt;docker run -it -v /home/root:/home/host_root/ el7guest /bin/bash</programlisting>
+      <programlisting>docker run -it -v /home/root:/home/host_root/ el7guest /bin/bash</programlisting>
 
       <para>To check that folders have been properly passed from the host to
       the container, create a file in the source folder on the host root
@@ -103,7 +101,7 @@ Hello from Docker!</programlisting>
             <para>Mapping a file descriptor is done in a similar way, but the
             <literal>-v</literal> flag needs to point directly to it:</para>
 
-            <programlisting>&gt;docker run -it --rm -v /var/run/openvswitch/vhost-user1 el7guest /bin/bash</programlisting>
+            <programlisting>docker run -it --rm -v /var/run/openvswitch/vhost-user1 el7guest /bin/bash</programlisting>
           </listitem>
         </itemizedlist>
       </section>
@@ -118,7 +116,7 @@ Hello from Docker!</programlisting>
         <literal>/mnt/huge</literal> location, a container can also access
         hugepages by being launched with:</para>
 
-        <programlisting>&gt;docker run -it -v /mnt/huge el7guest /bin/bash</programlisting>
+        <programlisting>docker run -it -v /mnt/huge el7guest /bin/bash</programlisting>
       </section>
 
       <section id="access-pci-bus">
@@ -131,7 +129,7 @@ Hello from Docker!</programlisting>
         container if the <literal>--privileged</literal> flag is passed to the
         command line:</para>
 
-        <programlisting>&gt;docker run --privileged -it el7guest /bin/bash</programlisting>
+        <programlisting>docker run --privileged -it el7guest /bin/bash</programlisting>
       </section>
     </section>
   </section>