book-enea-nfv-access-guide: unhide docker installer chapter

Signed-off-by: Adrian Calianu <adrian.calianu@enea.com>

1 files changed, 11 insertions, 8 deletions

diff --git a/doc/book-enea-nfv-access-guide/doc/getting_started.xml b/doc/book-enea-nfv-access-guide/doc/getting_started.xml
index 6c3db86..cb1de6d 100644
--- a/doc/book-enea-nfv-access-guide/doc/getting_started.xml
+++ b/doc/book-enea-nfv-access-guide/doc/getting_started.xml
@@ -96,14 +96,14 @@
    /* GRUB EFI file */</programlisting>
   </section>
 
-  <section condition="hidden" id="prebuilt-artifacts">
+  <section condition="" id="prebuilt-artifacts">
     <title>How to use the Prebuilt Artifacts</title>
 
     <section id="sysshell_config">
       <title>Booting NFV Access to RAM</title>
 
       <para>NFV Access can be booted on target using the RAMDISK images.
-      Following is described how to prepare the environment and configure
+      Following is described how to set the environment, configure the
       bootloader(U-Boot), load and boot the NFV Access on target. Please check
       the <link linkend="boot_prereq">Prerequisites</link> subchapter before
       starting boot process.</para>
@@ -127,7 +127,8 @@
 &gt; setenv rootfs_addr 0x60000000
 &gt; tftpboot $rootfs_addr enea-nfv-access-cn8304.ext4.gz.u-boot
 &gt; booti $kernel_addr $rootfs_addr $fdtcontroladdr
-&gt; setenv bootargs root=/dev/ram0 rw ramdisk_size=1000000 console=ttyAMA0,115200n8 earlycon=pl011,0x87e028000000 coherent_pool=16M</programlisting>
+&gt; setenv bootargs root=/dev/ram0 rw ramdisk_size=1000000 console=ttyAMA0,115200n8 \
+  earlycon=pl011,0x87e028000000 coherent_pool=16M</programlisting>
 
       <section id="boot_prereq">
         <title>Prerequisites:</title>
@@ -175,25 +176,27 @@
         servers will be installed and configured in order to facilitate a
         RAMDISK boot process on the target. Following is an example of how to
         build and run Enea provided docker image. In this case host is
-        directly connected to target on eth1. For more details please see
-        README file from docker installater folder.</para>
+        directly connected to target on eth1. For more details about docker
+        installer please see README file from docker installater
+        folder.</para>
 
         <programlisting>&gt; cd nfv-access-tools/nfv-installer/docker-pxe-ramboot/
 &gt; mkdir -p ./images
 &gt; cp &lt;NFVAccessReleasePath&gt;/Image $(pwd)/images/Image
-&gt; cp &lt;NFVAccessReleasePath&gt;/enea-nfv-access-cn8304.ext4.gz.u-boot $(pwd)/images/enea-nfv-access-cn8304.ext4.gz.u-boot</programlisting>
+&gt; cp &lt;NFVAccessReleasePath&gt;/enea-nfv-access-cn8304.ext4.gz.u-boot \
+     $(pwd)/images/enea-nfv-access.ext4.gz.u-boot</programlisting>
 
         <programlisting>&gt; docker build . -t el_installer</programlisting>
 
         <programlisting>&gt; docker run -it --net=host --privileged \
 -v $(pwd)/dhcpd.conf:/etc/dhcp/dhcpd.conf \
 -v $(pwd)/images/Image:/var/lib/tftpboot/Image \
--v $(pwd)/images/enea-nfv-access-cn8304.ext4.gz.u-boot:/var/lib/tftpboot/enea-nfv-access-cn8304.ext4.gz.u-boot \
+-v $(pwd)/images/enea-nfv-access.ext4.gz.u-boot:/var/lib/tftpboot/enea-nfv-access.ext4.gz.u-boot \
 el_installer eth1</programlisting>
 
         <para>Using this setup, on target side, U-Boot need to be configured
         as following before starting to boot Linux. It was considered that the
-        first eth port(vnic0) is connected to host:</para>
+        first eth port(vnic0) is connected to network:</para>
 
         <programlisting>&gt; setenv ethact vnic0
 &gt; setenv gatewayip 192.168.1.1