Update according to review comments

Change-Id: Ied9626223001932486f0725afed0f7d36c27b5f7
Signed-off-by: Adrian Mangeac <Adrian.Mangeac@enea.com>

2 files changed, 55 insertions, 62 deletions

diff --git a/doc/book-enea-linux-user-guide/doc/using_eclipse.xml b/doc/book-enea-linux-user-guide/doc/using_eclipse.xml
index 077935a..a8b2934 100644
--- a/doc/book-enea-linux-user-guide/doc/using_eclipse.xml
+++ b/doc/book-enea-linux-user-guide/doc/using_eclipse.xml
@@ -5,35 +5,34 @@
   <section id="install_eclipse">
     <title>Installing Oxygen Eclipse IDE</title>
 
-    <para>
-        <note>
-            Yocto Eclipse Plugins are discontinued and the last Yocto version that provides them
-            is Yocto 2.5.
-        </note>
-    </para>
+    <note>
+      <para>Yocto Eclipse Plugins are discontinued, with the last Yocto version that provides them
+        being Yocto 2.5.</para>
+    </note>
 
-    <para>Installation and configuration of the Eclipse Oxygen IDE should be done following the
-        <ulink url="http://www.yoctoproject.org/docs/2.5/sdk-manual/sdk-manual.html#adt-eclipse">Yocto
+    <para>Configuration of the Eclipse Oxygen IDE should be done following the
+      <ulink url="http://www.yoctoproject.org/docs/2.5/sdk-manual/sdk-manual.html#adt-eclipse">Yocto
         Project Application Development and the Extensible Software Development Kit
-        (eSDK)</ulink> documentation, Chapter 5.
-    Instructions provided in Chapter 5.2.1.1 are no longer valid, so, please follow the 
-    steps below in order to install Eclipse Oxygen:
+        (eSDK)</ulink> documentation.</para>
+
+    <para>The installation instructions provided in Chapter 5.2.1.1 are no longer valid, please follow the 
+      steps below in order to install Eclipse Oxygen:
     </para>
 
     <orderedlist>
       <listitem>
-        <para>Download Eclipse Oxygen archive from this link, by selecting the correct architecture:<ulink
+        <para>Download the <ulink
         url="https://www.eclipse.org/downloads/packages/release/oxygen/2/eclipse-ide-cc-developers">
-        https://www.eclipse.org/downloads/packages/release/oxygen/2/eclipse-ide-cc-developers</ulink>
-        (i.e. <filename>eclipse-cpp-oxygen-2-linux-gtk-x86_64.tar.gz</filename>).
+       Eclipse Oxygen archive</ulink>. Make sure to select the correct architecture in the link provided, 
+       e.g. <filename>eclipse-cpp-oxygen-2-linux-gtk-x86_64.tar.gz</filename>.
         </para>
       </listitem>
 
       <listitem>
-        <para>Decompress the Eclipse archive in your home directory and start the IDE:
+        <para>Unzip the Eclipse archive in your home directory and start the IDE:
             <programlisting>
   $ tar xf ~/Downloads/eclipse-cpp-oxygen-2-linux-gtk-x86_64.tar.gz -C ~/
-  $ ~/eclipse/eclipse 
+  $ ~/eclipse/eclipse
             </programlisting>
         </para>
       </listitem>
@@ -43,21 +42,17 @@
               Oxygen.
           </para>
       </listitem>
-
     </orderedlist>
 
-    <para>
-        <note>
-            For compatibility reasons, only use JDK version 1.8 on your host.
+    <note>
+      <para>For compatibility reasons, only use JDK version 1.8 on your host.</para>
         </note>
-    </para>
   </section>
 
   <section id="install_yocto">
-    <title>Installing Yocto Plug-ins</title>
+    <title>Installing Yocto Plugins</title>
 
-    <para>To install the Yocto Plugins in Eclipse, follow the instructions in
-        <ulink 
+    <para>To install the Yocto Plugins in Eclipse, follow the instructions in the <ulink 
             url="http://www.yoctoproject.org/docs/2.5/sdk-manual/sdk-manual.html#oxygen-setting-up-the-eclipse-ide">
         Yocto Project Application Development and the Extensible Software Development Kit
         (eSDK)</ulink> documentation, Chapter 5.2.1.3.
@@ -217,11 +212,11 @@ root 329 0.0 0.2 1864824 2600 ? Ssl 12:47 0:08 /usr/sbin/tcf-agent -d -L- -l0</p
       </orderedlist>
 
       <tip>
-        <para>More details on how to configure the cross-compiler can be found
+        <para>Details on how to configure the cross-compiler can be found
         in the <ulink
         url="http://www.yoctoproject.org/docs/2.5/sdk-manual/sdk-manual.html">Yocto
-        Project Application Development and the Extensible Software Development Kit
-        (eSDK)</ulink>.
+        Project Application Development and Extensible Software Development Kit
+        (eSDK) Manual</ulink>.
         </para>
 
         <para>There is also a good cheat sheet available in Eclipse, under
@@ -672,7 +667,7 @@ root 329 0.0 0.2 1864824 2600 ? Ssl 12:47 0:08 /usr/sbin/tcf-agent -d -L- -l0</p
               role="bold">Browse</emphasis> button and select a location on
               the remote target. You need an active TCF connection to the
               target for the <emphasis role="bold">Browse</emphasis> button to
-              work (see Chapter <emphasis role="bold">Setting up a TCF
+              work (see chapter <emphasis role="bold">Setting up a TCF
               Connection from Eclipse</emphasis>). Note that you need to
               specify the path including the filename.</para>
             </listitem>
diff --git a/doc/book-enea-linux-user-guide/doc/using_enea_linux.xml b/doc/book-enea-linux-user-guide/doc/using_enea_linux.xml
index fbd6d28..44dcf0c 100644
--- a/doc/book-enea-linux-user-guide/doc/using_enea_linux.xml
+++ b/doc/book-enea-linux-user-guide/doc/using_enea_linux.xml
@@ -5,9 +5,8 @@
   <section id="build_enealinux">
     <title>Building Enea Linux</title>
 
-    <para>Enea Linux is made available as sources, this allows for of building
-    various Enea Linux artifacts and is detailed in the following
-    sections:</para>
+    <para>Enea Linux is made available as sources, allowing for the building of
+    various Enea Linux artifacts detailed in the following sections.</para>
 
     <section id="build_images">
       <title>Building the images</title>
@@ -34,11 +33,11 @@ $ repo sync</programlisting>
         <step>
           <para>Source the build environment</para>
 
-          <programlisting>$ cd poky 
+          <programlisting>$ cd poky
 $ TEMPLATECONF=meta-el-standard/conf/template.&lt;machine&gt; \
 . ./oe-init-build-env &lt;build_dir&gt;</programlisting>
 
-          <para>Sourcing the build environment is needed everytime a new shell
+          <para>Sourcing the build environment is needed every time a new shell
           is used. However, sourcing using the <literal>TEMPLATECONF</literal>
           is only needed the first time around. After the first time, it is
           enough to source the build directory created before.</para>
@@ -54,7 +53,7 @@ $ TEMPLATECONF=meta-el-standard/conf/template.&lt;machine&gt; \
         </step>
 
         <step>
-          <para>Build Enea Linux image</para>
+          <para>Build an Enea Linux image</para>
 
           <programlisting># You have already initiated the build environment and are in the &lt;build_dir&gt;
 $ bitbake &lt;enea-image-name&gt; 
@@ -73,8 +72,8 @@ $ cd &lt;build_dir&gt;/tmp/deploy/images/&lt;target&gt;/  # Here are the build b
           booting a physical target, according to how the build environment
           was set up before running bitbake.</para>
 
-          <para>Depending on the number of processors and cores, the amount or
-          RAM, the speed of your Internet connection and other factors, the
+          <para>Depending on the number of processors and cores, the amount of
+          RAM, the speed of your internet connection and other factors, the
           build process can take several hours the first time you run it.
           Subsequent builds run much faster since parts of the build are
           cached.</para>
@@ -95,11 +94,11 @@ $ cd &lt;build_dir&gt;/tmp/deploy/images/&lt;target&gt;/  # Here are the build b
       <title>Building the SDK</title>
 
       <para>If you want to rebuild a cross-compilation toolchain to be used by
-      in application development, use the following steps:</para>
+      in application development, do the following:</para>
 
       <procedure>
         <step>
-          <para>Clone Enea Linux sources using Repo tool. Please refer to
+          <para>Clone Enea Linux sources using the Repo tool. Please refer to
           <xref linkend="getting_sources" /> for more details on how to do
           this.</para>
 
@@ -126,13 +125,13 @@ $ TEMPLATECONF=meta-el-standard/conf/template.&lt;machine&gt; \
             <para>The build directory may reside on an NFS mount, but the
             <literal>TMPDIR</literal>
             (<literal>&lt;build_dir&gt;/tmp</literal>) may not. Either build
-            all on a local disk, or update TMPDIR in conf/local.conf to point
-            to a local disk.</para>
+            all on a local disk, or update <literal>TMPDIR</literal> in 
+            <literal>conf/local.conf</literal> to point to a local disk.</para>
           </note>
         </step>
 
         <step>
-          <para>Build Enea Linux SDK</para>
+          <para>Build an Enea Linux SDK</para>
 
           <programlisting># You have already initiated the build environment and are in the &lt;build_dir&gt;
 $ bitbake &lt;enea-image-name&gt; -c populate_sdk_ext 
@@ -144,13 +143,13 @@ $ cd &lt;build_dir&gt;/tmp/deploy/sdk/  # Here is the SDK installer script</prog
             long, you need to move your build to obtain a shorter path.</para>
           </note>
 
-          <para>Generated SDK installer script is by default saved in
+          <para>The generated SDK installer script is by default saved in
           <literal>&lt;build_dir&gt;/tmp/deploy/sdk</literal>, where
           <literal>&lt;build_dir&gt;</literal> by default is the current
           working directory.</para>
 
-          <para>Depending on the number of processors and cores, the amount or
-          RAM, the speed of your Internet connection and other factors, the
+          <para>Depending on the number of processors and cores, the amount of
+          RAM, the speed of your internet connection and other factors, the
           build process can take several hours the first time you run it.
           Subsequent builds run much faster since parts of the build are
           cached.</para>
@@ -170,13 +169,13 @@ $ cd &lt;build_dir&gt;/tmp/deploy/sdk/  # Here is the SDK installer script</prog
     the artifacts availalbe, you may proceed to booting Enea Linux on
     target.</para>
 
-    <para>Enea Linux supports multiple booting methods so those will be
+    <para>Enea Linux supports multiple booting methods which will be
     described in the following sections.</para>
 
     <section id="enea-linux-x86-pxe">
       <title>Booting via PXE</title>
 
-      <para>Below you find an example of how to boot Enea Linux in a target
+      <para>Below is an example of how to boot Enea Linux on a target
       supporting PXE. The PXE boot is handled by the target BIOS.</para>
 
       <para>This requires the setup of DHCP, TFTP and NFS servers on the host.
@@ -190,31 +189,31 @@ $ cd &lt;build_dir&gt;/tmp/deploy/sdk/  # Here is the SDK installer script</prog
 
       <itemizedlist spacing="compact">
         <listitem>
-          <para>Host name</para>
+          <para>Host name.</para>
         </listitem>
 
         <listitem>
           <para>MAC hardware ethernet address (also available in the TFTP
-          configuration)</para>
+          configuration).</para>
         </listitem>
 
         <listitem>
-          <para>IP address, (assuming a fixed IP address is used)</para>
+          <para>IP address (assuming a fixed IP address is used).</para>
         </listitem>
 
         <listitem>
           <para>The TFTP server shall be defined as
-          <literal>next-server</literal></para>
+          <literal>next-server</literal>.</para>
         </listitem>
 
         <listitem>
           <para>The relative path in the TFTP server to the PXE file
-          <filename><literal>pxelinux.0</literal></filename></para>
+          <filename>pxelinux.0</filename>.</para>
         </listitem>
 
         <listitem>
           <para>The NFS server IP address and the path to the rootfs on the
-          NFS server, defined as <literal>option root-path</literal></para>
+          NFS server, defined as <literal>option root-path</literal>.</para>
         </listitem>
       </itemizedlist>
 
@@ -228,8 +227,8 @@ $ cd &lt;build_dir&gt;/tmp/deploy/sdk/  # Here is the SDK installer script</prog
     option root-path  "192.168.2.20:/export/intel-corei7-64_rootfs";
 }</programlisting>
 
-      <para>For the TFTP server, the TFTP path to the target's pxelinux.0 file
-      is given in the DHCP Configuration. Examples of files included in the
+      <para>For the TFTP server, the TFTP path to the target's <filename>pxelinux.0</filename>
+        file is given in the DHCP Configuration. Examples of files included in the
       TFTP subdirectory indicated by the DHCP configuration are:</para>
 
       <programlisting>pxelinux.0
@@ -284,8 +283,7 @@ label device01
 
         <listitem>
           <para>Populate the root file system in the NFS directory by
-          unpacking
-          <filename>enea-image-standard-intel-corei7-64.tar.gz</filename>
+          unpacking <filename>enea-image-standard-intel-corei7-64.tar.gz</filename>
           found at
           <filename>&lt;build_dir&gt;/tmp/deploy/images/&lt;target&gt;/</filename>.</para>
         </listitem>
@@ -379,28 +377,28 @@ U-Boot&gt; booti 0x01000000 0x03000000 0x02000000</programlisting>
             </listitem>
 
             <listitem>
-              <para>Run <filename>Win32DiskImager.exe</filename></para>
+              <para>Run <filename>Win32DiskImager.exe</filename>.</para>
             </listitem>
 
             <listitem>
-              <para>Select the drive of your SD card</para>
+              <para>Select the drive of your SD card.</para>
             </listitem>
 
             <listitem>
               <para>Select the image
-              <filename><filename>enea-image-standard-raspberrypi3-64.rpi-sdimg</filename></filename></para>
+              <filename>enea-image-standard-raspberrypi3-64.rpi-sdimg</filename>.</para>
             </listitem>
 
             <listitem>
-              <para>Click "Write" and wait for the write to complete</para>
+              <para>Click "Write" and wait for the write to complete.</para>
             </listitem>
 
             <listitem>
-              <para>Exit the imager and eject the SD Card</para>
+              <para>Exit the imager and eject the SD Card.</para>
             </listitem>
 
             <listitem>
-              <para>Plug the card into your Raspberry Pi</para>
+              <para>Plug the card into your Raspberry Pi.</para>
             </listitem>
           </orderedlist>