Fixed Miruna's comments from pdf file

Ref: LXCR-8412

Signed-off-by: Sona Sarmadi <sona.sarmadi@enea.com>

1 files changed, 58 insertions, 46 deletions

diff --git a/doc/book-enea-nfv-access-guide-intel/doc/using_nfv_access_sdks.xml b/doc/book-enea-nfv-access-guide-intel/doc/using_nfv_access_sdks.xml
index e084502..d81cfdb 100644
--- a/doc/book-enea-nfv-access-guide-intel/doc/using_nfv_access_sdks.xml
+++ b/doc/book-enea-nfv-access-guide-intel/doc/using_nfv_access_sdks.xml
@@ -328,8 +328,11 @@ MODULE_LICENSE("GPL");</programlisting>
     <title>Extensible SDK</title>
 
     <para>The Extensible SDK provides a number of features that help you
-    easily build, test and package software, and optionally deploy it to
-    target device. The Extensible SDK consits of:</para>
+    easily build, test and package software, and optionally deploy it to the
+    target device.</para>
+
+    <para><emphasis role="bold">The Extensible SDK consits
+    of:</emphasis></para>
 
     <itemizedlist>
       <listitem>
@@ -337,7 +340,7 @@ MODULE_LICENSE("GPL");</programlisting>
       </listitem>
 
       <listitem>
-        <para>Libraries, Headers and Symbols for x86 architecture</para>
+        <para>Libraries, Headers and Symbols for the x86 architecture</para>
       </listitem>
 
       <listitem>
@@ -346,9 +349,7 @@ MODULE_LICENSE("GPL");</programlisting>
       </listitem>
 
       <listitem>
-        <para>Devtool (d<emphasis>evtool add </emphasis>to create
-        automatically a recipe for an existing source code, <emphasis>devtool
-        modify</emphasis> to build an existing recipe, etc ..)</para>
+        <para>Devtool</para>
       </listitem>
     </itemizedlist>
 
@@ -378,7 +379,7 @@ MODULE_LICENSE("GPL");</programlisting>
         </listitem>
 
         <listitem>
-          <para>Setup the toolchain environment for your target by sourcing
+          <para>Set up the toolchain environment for your target by sourcing
           the environment-setup script. Example: <programlisting>$ source sdkdir/environment-setup-corei7-64-enea-linux
 SDK environment now set up; additionally you may now run devtool to 
 perform development tasks.
@@ -390,17 +391,19 @@ Run devtool --help for further details.</programlisting></para>
     <section id="add_new_comp_esdk">
       <title>Adding a new component</title>
 
-      <para>The <emphasis>devtool add</emphasis> command is used to create a
-      new recipe and <emphasis>devtool modify</emphasis> command is used to
-      work on an existing recipe. To add a component, you can:</para>
+      <para>The<emphasis> <emphasis><literal><literal>devtool</literal>
+      <literal>add</literal></literal></emphasis> </emphasis>command is used
+      to create a new recipe and
+      <emphasis><emphasis><literal>devtool</literal>
+      <literal>modify</literal></emphasis> </emphasis>command is used to work
+      on an existing recipe. To add a component, you can:</para>
 
       <para><emphasis role="bold">A) Generate a recipe from the existing
       application code and Makefile</emphasis></para>
 
       <orderedlist>
         <listitem>
-          <para>Run <emphasis>devtool add</emphasis> command to generate a
-          recipe:</para>
+          <para>Run devtool add command to generate a recipe:</para>
 
           <programlisting>$ devtool add recipe /path/to/your_application 
 
@@ -409,10 +412,15 @@ $ devtool add bbexample /path/to/bbexample
 or download from upstream git repository
 $ devtool add bbexample https://github.com/whbruce/bbexample.git
 
-NOTE: Recipe &lt;SDK_dir&gt;/workspace/recipes/bbexample/bbexample.bb has been
-automatically created; further editing may be required to make it fully functional
-NOTE: devtool creates a Git repository locally during the extraction under 
-      &lt;SDK_dir&gt;/workspace/source/bbexample</programlisting>
+
+NOTE: devtool creates a Git repository locally during the extraction at: 
+      sdkdir/workspace/source/bbexample</programlisting>
+
+          <note>
+            <para>Recipe
+            <literal>sdkdir/workspace/recipes/bbexample/bbexample.bb has been
+            automatically created.</literal></para>
+          </note>
         </listitem>
       </orderedlist>
 
@@ -421,7 +429,8 @@ NOTE: devtool creates a Git repository locally during the extraction under
 
       <orderedlist>
         <listitem>
-          <para>Use any recipe from &lt;SDK_dir&gt;/layers/poky/meta*</para>
+          <para>Use any recipe from
+          <literal>sdkdir/layers/poky/meta*</literal></para>
 
           <programlisting>$ devtool modify recipe
 
@@ -439,12 +448,12 @@ $ devtool modify curl</programlisting>
           <para>Clone a recipe from the upstream Yocto project, e.g.
           meta-security:</para>
 
-          <programlisting>$ pushd &lt;SDK_dir&gt;/layers/poky
+          <programlisting>$ pushd sdkdir/layers/poky
 $ git clone -b rocko git://git.yoctoproject.org/meta-security</programlisting>
         </listitem>
 
         <listitem>
-          <para>Use the <emphasis>bitbake-layers</emphasis> script to add the
+          <para>Use the <literal>bitbake-layers</literal> script to add the
           meta-security to BBLAYERS:</para>
 
           <programlisting>$ layers/poky/bitbake/bin/bitbake-layers add-layer layers/poky/meta-security
@@ -456,32 +465,42 @@ not enabled in your configuration
 clone meta-perl from openembedded and run add-layers again: 
 $ layers/poky/bitbake/bin/bitbake-layers add-layer layers/poky/meta-security
 
-NOTE: Now &lt;SDK_dir&gt;/layers/poky/meta-security is created and the layer has been 
-added to: &lt;SDK_dir&gt;/conf/bblayers.conf
+NOTE: Now sdkdir/layers/poky/meta-security is created and the layer has been 
+added to: sdkdir/conf/bblayers.conf
   ...
   ${SDKBASEMETAPATH}/layers/poky/meta-security \</programlisting>
+
+          <note>
+            <para>The image build result can be seen at:
+            <literal>sdkdir/tmp/deploy/images/qemux86-64</literal></para>
+          </note>
         </listitem>
 
         <listitem>
-          <para>Use <emphasis>devtool modify</emphasis> command to work an an
-          existing recipe inside meta-security layer:</para>
+          <para>Use <literal>devtool modify</literal> to operate an existing
+          recipe inside meta-security layer:</para>
 
           <programlisting>$ devtool modify recipe
 
 EX:
 $ devtool modify isic
 
-NOTE: following directories and files are created:
-&lt;SDK_dir&gt;/workspace/appends/isic_0.07.bbappend 
-&lt;SDK_dir&gt;/workspace/sources/isic</programlisting>
+NOTE: </programlisting>
+
+          <note>
+            <para>following directories and files are created:
+            sdkdir/workspace/appends/isic_0.07.bbappend
+            sdkdir/workspace/sources/isic</para>
+          </note>
         </listitem>
       </orderedlist>
     </section>
 
     <section id="devtool_build">
-      <title>Build your application/recipe</title>
+      <title>Build your application</title>
 
-      <para>Use devtool build command to build the recipe:</para>
+      <para>Use <literal>devtool</literal> <literal>build</literal> to build
+      the recipe:</para>
 
       <orderedlist>
         <listitem>
@@ -491,8 +510,8 @@ EX:
 $ devtool build bbexample
 or
 $ devtool build isic</programlisting><note>
-              <para>The image build result can be seen here:
-              <literal>&lt;SDK_dir&gt;/tmp/deploy/images/qemux86-64</literal></para>
+              <para>The image build result can be seen at:
+              <literal>sdkdir/tmp/deploy/images/qemux86-64</literal></para>
             </note></para>
         </listitem>
       </orderedlist>
@@ -502,9 +521,9 @@ $ devtool build isic</programlisting><note>
   <section id="deploy">
     <title>Deploy your Application to target</title>
 
-    <para>Deploy your application to target by using <emphasis>devtool
-    deploy-target</emphasis> command or build an docker image and dploy the
-    docker image.</para>
+    <para>Deploy your application to the target by using <literal>devtool
+    deploy-target</literal> or by building a <literal>docker
+    image</literal>.</para>
 
     <section id="deploy-artifacts-esdk">
       <title>Using <emphasis>devtool deploy-target</emphasis> command</title>
@@ -529,8 +548,9 @@ $ devtool deploy-target isic root@&lt;target_ip_address&gt;
 isic: error while loading shared libraries: libnet.so.9: cannot open shared 
 object file: No such file or directory
 
-NOTE: If you get dependency error, you need to build that recipe as well and 
-deploy to target:
+NOTE: It is mandatory to add required dependecies. E.g. isic is dependent on libnet, 
+you need to build and deploy libnet separately to the target:
+
 $ devtool modify libnet
 $ devtool build libnet
 $ devtool deploy-target libnet root@&lt;target_ip_address&gt;
@@ -542,8 +562,7 @@ usage: isic [-v] [-D] -s &lt;source ip&gt; -d &lt;destination ip&gt; [-r &lt;ran
         </listitem>
 
         <listitem>
-          <para>Remove/uninstall the application from target if you don't need
-          it:</para>
+          <para>Remove/uninstall the application from target as needed:</para>
 
           <programlisting>$ devtool undeploy-target isic root@&lt;target_ip_address&gt;</programlisting>
         </listitem>
@@ -571,20 +590,13 @@ inherit core-image</programlisting>
         </listitem>
 
         <listitem>
-          <para>Add the following line in
-          <literal>local.conf</literal>:</para>
-
-          <programlisting>IMAGE_CONTAINER_NO_DUMMY = "1"</programlisting>
-        </listitem>
-
-        <listitem>
           <para>Build the container image:</para>
 
           <programlisting>$ devtool build-image cont-image </programlisting>
 
           <note>
-            <para>The image build result can be seen here:
-            <literal>&lt;SDK_dir&gt;/tmp/deploy/images/qemux86-64</literal></para>
+            <para>The image build result can be seen at:
+            <literal>sdkdir/tmp/deploy/images/qemux86-64</literal></para>
           </note>
         </listitem>