[FE training-materials-updates] Make nboot instructions more explicit

[Michael Opdenacker]

Repository : git://git.free-electrons.com/training-materials.git

On branch  : master
Link       : http://git.free-electrons.com/training-materials/commit/?id=592544a131580132a069dd1aee4cb8e0b8eb3513

>---------------------------------------------------------------

commit 592544a131580132a069dd1aee4cb8e0b8eb3513
Author: Michael Opdenacker <michael.opdenacker at free-electrons.com>
Date:   Wed Mar 26 11:33:18 2014 +0100

    Make nboot instructions more explicit
    
    - Suggestions from a participant to the embedded
      Linux course.
    
    Signed-off-by: Michael Opdenacker <michael.opdenacker at free-electrons.com>


>---------------------------------------------------------------

592544a131580132a069dd1aee4cb8e0b8eb3513
 .../sysdev-kernel-cross-compiling.tex              |    3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/labs/sysdev-kernel-cross-compiling/sysdev-kernel-cross-compiling.tex b/labs/sysdev-kernel-cross-compiling/sysdev-kernel-cross-compiling.tex
index 4329fbb..8821035 100644
--- a/labs/sysdev-kernel-cross-compiling/sysdev-kernel-cross-compiling.tex
+++ b/labs/sysdev-kernel-cross-compiling/sysdev-kernel-cross-compiling.tex
@@ -219,7 +219,8 @@ bootm 0x80000000 - 0x81000000
 \end{verbatim}
 
 \code{nboot} copies the kernel to RAM, using the \code{uImage} headers
-to know how many bytes to copy. You could have used \code{nand read
+to know how many bytes to copy. To load the kernel
+to RAM, image, you could have used \code{nand read
 0x80000000 0x300000 0x500000}, but you would have copied more bytes than
 the actual size of your kernel. \footnote{\code{nboot} can save a lot 
 of boot time, as it avoids having to copy a pessimistic number of