[FE training-materials-updates] android-new-board: a few improvements

[Alexandre Belloni]

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

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

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

commit efcf524f3367ca2ba23edb31b82667455eb80138
Author: Alexandre Belloni <alexandre.belloni at free-electrons.com>
Date:   Thu Apr 17 15:21:37 2014 +0200

    android-new-board: a few improvements
    
    Signed-off-by: Alexandre Belloni <alexandre.belloni at free-electrons.com>


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

efcf524f3367ca2ba23edb31b82667455eb80138
 labs/android-new-board/android-new-board.tex |    8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/labs/android-new-board/android-new-board.tex b/labs/android-new-board/android-new-board.tex
index 74d852a..d0b04a3 100644
--- a/labs/android-new-board/android-new-board.tex
+++ b/labs/android-new-board/android-new-board.tex
@@ -20,7 +20,7 @@ will be needed.
 
 \code{repo} allows to manage your Android source tree in a smart way,
 downloading only the differences between the new manifest we would
-give him and the current code we have. In order to integrate these
+give it and the current code we have. In order to integrate these
 additions nicely, the first thing we need is to add rowboat's
 configuration repo to the manifest.
 
@@ -41,7 +41,7 @@ then configuring the build system to use that binary.
 So, the first step is to download the kernel. Once again, we can use
 repo for that. Make it fetch the kernel from
 \code{git://gitorious.org/rowboat/kernel.git}, at revision
-\code{rowboat-am335x-kernel-3.2}, in the \code{kernel} directory.
+\sloppy{\mbox{\code{rowboat-am335x-kernel-3.2}}}, in the \code{kernel} directory.
 
 Once done, make \code{repo} download it, and we can start building our
 kernel. This time, you'll need to use the \code{am335x_evm_android}
@@ -214,8 +214,8 @@ because we haven't installed the GPU drivers yet.
 
 \section{Adding the GPU drivers}
 
-GPU drivers are most of the time implemented in userspace, with a
-bunch of libraries and kernel modules implemented provided by the GPU
+GPU drivers are most of the time implemented using a bunch of
+userspace libraries and kernel modules implemented provided by the GPU
 vendor.
 
 This is often a real pain to integrate, since it's tied to a