[FE training-materials-updates] Misc typo and grammar corrections

[Michael Opdenacker]

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

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

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

commit 68bb0ebfcf7c06477676ef64c825ea250d764143
Author: Radek Dostal <rd at radekdostal.com>
Date:   Mon Jan 27 21:05:01 2014 +0100

    Misc typo and grammar corrections
    
    Signed-off-by: Radek Dostal <rd at radekdostal.com>


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

68bb0ebfcf7c06477676ef64c825ea250d764143
 labs/android-application/android-application.tex   |    2 +-
 labs/boottime-application/boottime-application.tex |    4 ++--
 .../android-source-compilation.tex                 |    2 +-
 .../boottime-application/boottime-application.tex  |    2 +-
 4 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/labs/android-application/android-application.tex b/labs/android-application/android-application.tex
index e11e993..a2440b8 100644
--- a/labs/android-application/android-application.tex
+++ b/labs/android-application/android-application.tex
@@ -26,7 +26,7 @@ is a perfectly standard Android application, relying on Java $\rightarrow$ C
 bindings integrated in the Android framework, which in turn relies on libusb
 that we included in the system libraries.
 
-We can't have a real USB missile launcher for participant,
+We can't have a real USB missile launcher for participants,
 so the \code{DummyBackend} class is provided to test that your application and the
 changes to the framework are functional.
 
diff --git a/labs/boottime-application/boottime-application.tex b/labs/boottime-application/boottime-application.tex
index c8ac792..52cc0a3 100644
--- a/labs/boottime-application/boottime-application.tex
+++ b/labs/boottime-application/boottime-application.tex
@@ -32,7 +32,7 @@ Run Buildroot and reflash your device as usual.
 \subsection{Tracing and profiling with strace}
 
 With \code{strace}'s help, you can already have a pretty good understanding
-of what how your application spends it time. You can see all the system
+of how your application spends it time. You can see all the system
 calls that it makes and knowing the application, you can guess in which 
 part of the code it is at a given time.
 
@@ -83,7 +83,7 @@ have.
 
 In our particular case, modifying \code{gst-launch} would be very
 difficult. It could make sense with your own application though, for
-which to code is familiar to you.
+which the code is familiar to you.
 
 \section{Optimizing necessary functionality}
 
diff --git a/slides/android-source-compilation/android-source-compilation.tex b/slides/android-source-compilation/android-source-compilation.tex
index e5ecc52..9c06cbc 100644
--- a/slides/android-source-compilation/android-source-compilation.tex
+++ b/slides/android-source-compilation/android-source-compilation.tex
@@ -20,7 +20,7 @@
   \frametitle{Prepare the process}
   \begin{itemize}
   \item Now, we can get a list of all the products available and
-    select them with to the \code{lunch} command
+    select them with the \code{lunch} command
   \item \code{lunch} will also ask for a build variant, to choose
     between \code{eng}, \code{user} and \code{userdebug}, which
     corresponds to which kind of build we want, and which packages it
diff --git a/slides/boottime-application/boottime-application.tex b/slides/boottime-application/boottime-application.tex
index 5e6f9ff..0c89c4f 100644
--- a/slides/boottime-application/boottime-application.tex
+++ b/slides/boottime-application/boottime-application.tex
@@ -273,7 +273,7 @@ Details:
       save less than this upper limit.
 \item You can then decide whether this could be worth the effort.
       Such optimizations are costly, as the way you compile your
-      applications has be be modified. 
+      applications has to be modified.
 \end{itemize}
 \end{frame}