[BL training-materials-updates] labs/buildroot-*: fix various typos

[Michael Opdenacker]

Repository : git://git.free-electrons.com/training-materials.git
On branch  : master
Link       : http://git.free-electrons.com/training-materials/commit/?id=35fb53fd0939467f6d6241a174ebe4fad65b6b05

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

commit 35fb53fd0939467f6d6241a174ebe4fad65b6b05
Author: Jean-François Têtu <jean-francois.tetu at savoirfairelinux.com>
Date:   Tue Mar 20 16:48:14 2018 -0400

    labs/buildroot-*: fix various typos
    
    When I noticed that the referenced Buildroot version in the "Basic
    Buildroot usage" section was not the same as the `git checkout` command,
    I decided take a look at the rest of document to see if I could catch
    other typos. This is basically a Boy Scout Rule patch:
    
    - advanced-packages: package vs packaging.
    
    - advanced: re-phrasings and add missing patch file in file tree.
    
    - appdev: fix package name for test application.
    
    - basic: fix referenced Buildroot version, device names and minor typos
    
    Signed-off-by: Jean-François Têtu <jean-francois.tetu at savoirfairelinux.com>


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

35fb53fd0939467f6d6241a174ebe4fad65b6b05
 labs/buildroot-advanced-packages/buildroot-advanced-packages.tex | 2 +-
 labs/buildroot-advanced/buildroot-advanced.tex                   | 5 +++--
 labs/buildroot-appdev/buildroot-appdev.tex                       | 2 +-
 labs/buildroot-basic/buildroot-basic.tex                         | 8 ++++----
 4 files changed, 9 insertions(+), 8 deletions(-)

diff --git a/labs/buildroot-advanced-packages/buildroot-advanced-packages.tex b/labs/buildroot-advanced-packages/buildroot-advanced-packages.tex
index 297e105..23c6c89 100644
--- a/labs/buildroot-advanced-packages/buildroot-advanced-packages.tex
+++ b/labs/buildroot-advanced-packages/buildroot-advanced-packages.tex
@@ -209,7 +209,7 @@ verbose = "yes"
 
 And run \code{bar} again, and see what difference it makes.
 
-Congratulations, you've finished package the most useless application
+Congratulations, you've finished packaging the most useless application
 in the world!
 
 \section{Preparing for the next lab}
diff --git a/labs/buildroot-advanced/buildroot-advanced.tex b/labs/buildroot-advanced/buildroot-advanced.tex
index a7bea77..f282021 100644
--- a/labs/buildroot-advanced/buildroot-advanced.tex
+++ b/labs/buildroot-advanced/buildroot-advanced.tex
@@ -15,7 +15,7 @@ When your embedded Linux system grows, its build time will also grow,
 so it is often interesting to understand where the build time is
 spent.
 
-Since we have just do a fresh clean rebuild at the end of the previous
+Since we just did a fresh clean rebuild at the end of the previous
 lab, we can analyze the build time. The raw data has been generated by
 Buildroot in \code{output/build/build-time.log}, which contains for
 each step of each package the start time and end time (in seconds
@@ -124,7 +124,7 @@ more readable.
 
 Such dependencies graphs are very useful to understand why a package
 is being built, and help identifying what you could do to reduce the
-number of packages part of the build.
+number of packages that are part of the build.
 
 \section{Filesystem size graphing}
 
@@ -218,6 +218,7 @@ Your \code{BR2_EXTERNAL} tree should look like this:
 |                       +-- interfaces
 +-- package/
 |   +-- bar
+|       +-- 0001-Fix-missing-libconfig.h-include.patch
 |       +-- bar.mk
 |       +-- Config.in
 |   +-- libfoo
diff --git a/labs/buildroot-appdev/buildroot-appdev.tex b/labs/buildroot-appdev/buildroot-appdev.tex
index 27cb494..9abaae3 100644
--- a/labs/buildroot-appdev/buildroot-appdev.tex
+++ b/labs/buildroot-appdev/buildroot-appdev.tex
@@ -222,7 +222,7 @@ that the \code{myapp} source code gets {\em rsynced} from
 The build should now proceed to the end. Now, make a stupid but
 visible change to the source code in \code{myapp.c}.
 
-Restart the build of \code{bar} using \code{make myapp-rebuild}, you
+Restart the build of \code{myapp} using \code{make myapp-rebuild}, you
 will see that Buildroot automatically {\em rsyncs} again the source
 code. Then scp the file \code{output/target/usr/bin/myapp} to
 \code{192.168.0.2:/usr/bin} and run \code{myapp} again on the target.
diff --git a/labs/buildroot-basic/buildroot-basic.tex b/labs/buildroot-basic/buildroot-basic.tex
index 8c83cfc..9367410 100644
--- a/labs/buildroot-basic/buildroot-basic.tex
+++ b/labs/buildroot-basic/buildroot-basic.tex
@@ -49,7 +49,7 @@ keep track of them.
 
 Go into the newly created \code{buildroot} directory.
 
-We're going to start a branch from the {\em 2016.05} Buildroot
+We're going to start a branch from the {\em 2017.08} Buildroot
 release, with which this training has been tested.
 
 \begin{verbatim}
@@ -336,14 +336,14 @@ find your SD card. In general, if you use the internal SD card reader
 of a laptop, it will be \code{mmcblk0}, while if you use an external
 USB SD card reader, it will be \code{sdX} (i.e\code{sdb}, \code{sdc},
 etc.). {\bf Be careful: \code{/dev/sda} is generally the hard drive of
-  your machine!}.
+  your machine!}
 
 If your SD card is \code{/dev/mmcblk0}, then the partitions inside the
-SD card are named \code{mmcblk0p1}, \code{mmc0blkp2}, etc. If your SD
+SD card are named \code{/dev/mmcblk0p1}, \code{/dev/mmcblk0p2}, etc. If your SD
 card is \code{/dev/sdc}, then the partitions inside are named
 \code{/dev/sdc1}, \code{/dev/sdc2}, etc.
 
-To format our SD card, do the following steps:
+To format your SD card, do the following steps:
 
 \begin{enumerate}