[FE training-materials-updates] Minor "appdev" lab improvements

[Michael Opdenacker]

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

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

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

commit 9a008a403a0141f3fd541eefedda632522a4c1c9
Author: Michael Opdenacker <michael.opdenacker at free-electrons.com>
Date:   Wed Dec 10 06:34:53 2014 +0100

    Minor "appdev" lab improvements
    
    Signed-off-by: Michael Opdenacker <michael.opdenacker at free-electrons.com>


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

9a008a403a0141f3fd541eefedda632522a4c1c9
 .../sysdev-application-development.tex                   | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/labs/sysdev-application-development/sysdev-application-development.tex b/labs/sysdev-application-development/sysdev-application-development.tex
index 94ccea6..ae6be40 100644
--- a/labs/sysdev-application-development/sysdev-application-development.tex
+++ b/labs/sysdev-application-development/sysdev-application-development.tex
@@ -11,17 +11,17 @@ We will re-use the system built during the {\em Buildroot lab} and add
 to it our own application.
 
 In the lab directory the file \code{app.c} contains a very simple
-ncurses application. It is a simple game where you need to reach a
-target using the arrow keys of your keyboard.  We will compile and
+{\em ncurses} application. It is a simple game where you need to reach
+a target using the arrow keys of your keyboard.  We will compile and
 integrate this simple application to our Linux system.
 
 Buildroot has generated toolchain wrappers in
 \code{output/host/usr/bin}, which make it easier to use the toolchain,
 since these wrappers pass some mandatory flags (especially the
-\code{--sysroot} gcc flag, which tells gcc where to look for the
-headers and libraries).
+\code{--sysroot} {\em gcc} flag, which tells {\em gcc} where to look
+for the headers and libraries).
 
-Let's add this directory to our PATH:
+Let's add this directory to our \code{PATH}:
 
 \footnotesize
 \begin{verbatim}
@@ -40,10 +40,10 @@ normal, since we didn't tell the compiler to link with the necessary
 libraries. So let's use \code{pkg-config} to query the {\em
 pkg-config} database about the location of the header files and the
 list of libraries needed to build an application against
-ncurses:\footnote{Again, \code{output/host/usr/bin} has a special
+{\em ncurses}:\footnote{Again, \code{output/host/usr/bin} has a special
 \code{pkg-config} that automatically knows where to look, so it
 already knows the right paths to find \code{.pc} files and their
-sysroot.q}
+sysroot.}
 
 \begin{verbatim}
 arm-linux-gcc -o app app.c $(pkg-config --libs --cflags ncurses)
@@ -51,7 +51,7 @@ arm-linux-gcc -o app app.c $(pkg-config --libs --cflags ncurses)
 
 You can see that \code{ncurses} doesn't need anything in particular for the
 \code{CFLAGS} but you can have a look at what is needed for
-\code{libvorbis} to get a feel of what it can look like:
+{\em libvorbis} to get a feel of what it can look like:
 
 \begin{verbatim}
 pkg-config --libs --cflags vorbis