1 files changed, 15 insertions, 14 deletions

diff --git a/doc/book-enea-nfv-access-guide-intel/doc/container_virtualization.xml b/doc/book-enea-nfv-access-guide-intel/doc/container_virtualization.xml
index 2287146..06bfbb4 100644
--- a/doc/book-enea-nfv-access-guide-intel/doc/container_virtualization.xml
+++ b/doc/book-enea-nfv-access-guide-intel/doc/container_virtualization.xml
@@ -44,23 +44,24 @@
     </section>
 
     <section id="run-enfv-guest-image">
-      <title>Run an Enea NFV Access guest image</title>
+      <title>Run a guest image inside Docker</title>
 
-      <para>Enea NFV Access guest images can run inside Docker as any other
-      container can. Before starting an Enea NFV Access guest image, a root
-      filesystem has to be imported in Docker:</para>
+      <para>Guest images can be run inside Docker as in any other container.
+      You can find an example below of how to configure and run a guest image.
+      Before starting a guest image, a root filesystem has to be imported in
+      Docker:</para>
 
-      <programlisting>docker import enea-nfv-access-guest-qemux86-64.tar.gz el7guest</programlisting>
+      <programlisting>docker import guest-qemux86-64.tar.gz guest</programlisting>
 
       <para>To check that the Docker image has been imported successfully,
       run:</para>
 
       <programlisting>docker images</programlisting>
 
-      <para>Finally, start an Enea NFV Access container with
-      <literal>bash</literal> running as the shell, by running:</para>
+      <para>Finally, start a container with <literal>bash</literal> running as
+      the shell, by running:</para>
 
-      <programlisting>docker run -it el7guest /bin/bash</programlisting>
+      <programlisting>docker run -it guest /bin/bash</programlisting>
     </section>
 
     <section id="attach-ext-resources-docker-containers">
@@ -75,7 +76,7 @@
       <literal>roots</literal> home folder to a container, the command line
       for Docker should have the following format:</para>
 
-      <programlisting>docker run -it -v /home/root:/home/host_root/ el7guest /bin/bash</programlisting>
+      <programlisting>docker run -it -v /home/root:/home/host_root/ guest /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
@@ -94,14 +95,14 @@
           <listitem>
             <para>Mapping the folder can be done as exemplified above:</para>
 
-            <programlisting>docker run -it --rm -v /var/run/openvswitch/:/var/run/openvswitch/ el7guest /bin/bash</programlisting>
+            <programlisting>docker run -it --rm -v /var/run/openvswitch/:/var/run/openvswitch/ guest /bin/bash</programlisting>
           </listitem>
 
           <listitem>
             <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>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 guest /bin/bash</programlisting>
           </listitem>
         </itemizedlist>
       </section>
@@ -116,7 +117,7 @@
         <literal>/mnt/huge</literal> location, a container can also access
         hugepages by being launched with:</para>
 
-        <programlisting>docker run -it -v /mnt/huge el7guest /bin/bash</programlisting>
+        <programlisting>docker run -it -v /mnt/huge guest /bin/bash</programlisting>
       </section>
 
       <section id="access-pci-bus">
@@ -129,8 +130,8 @@
         container if the <literal>--privileged</literal> flag is passed to the
         command line:</para>
 
-        <programlisting>docker run --privileged -it el7guest /bin/bash</programlisting>
+        <programlisting>docker run --privileged -it guest /bin/bash</programlisting>
       </section>
     </section>
   </section>
-</chapter>
\ No newline at end of file
+</chapter>