[FE training-materials-updates] "informations" -> "information"

[Michael Opdenacker]

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

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

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

commit 0d0a01584fdba90da727c5c31dea48c5c4630e60
Author: Michael Opdenacker <michael.opdenacker at free-electrons.com>
Date:   Thu Oct 4 15:44:25 2012 +0200

    "informations" -> "information"


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

0d0a01584fdba90da727c5c31dea48c5c4630e60
 labs/kernel-serial-driver/kernel-serial-driver.tex |    6 +++---
 labs/sysdev-thirdparty/sysdev-thirdparty.tex       |    2 +-
 2 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/labs/kernel-serial-driver/kernel-serial-driver.tex b/labs/kernel-serial-driver/kernel-serial-driver.tex
index e12ecbd..2576fc1 100644
--- a/labs/kernel-serial-driver/kernel-serial-driver.tex
+++ b/labs/kernel-serial-driver/kernel-serial-driver.tex
@@ -63,7 +63,7 @@ Instantiate an \code{uart_driver} structure with the following values:
 \item \code{dev_name}, \code{ttyS}
 \item \code{major}, \code{TTY_MAJOR} (this is the usual major for TTY devices)
 \item \code{minor}, \code{64} (this is the usual minor for TTY serial
-  devices, see Documentation/devices.txt in the kernel source tree)
+  devices, see \code{Documentation/devices.txt} in the kernel source tree)
 \item \code{nr}, \code{1} (we will support only one port)
 \end{itemize}
 
@@ -135,7 +135,7 @@ functions. Before that, we need a few definitions:
 
 \begin{itemize}
 \item Declare a global \code{uart_port} structure, that will be used
-  to contain the informations about the single port we will manage;
+  to contain information about the single port we will manage;
 \item Declare an empty \code{uart_ops} structure.
 \end{itemize}
 
@@ -379,7 +379,7 @@ and then a shell:
 /sbin/getty -L ttyS0 115200 vt100
 \end{verbatim}
 
-Go back to your Picocom, you should be able to login normally, but
+Go back to \code{picocom}, you should be able to login normally, but
 using your own serial driver!
 
 \section{Improvements}
diff --git a/labs/sysdev-thirdparty/sysdev-thirdparty.tex b/labs/sysdev-thirdparty/sysdev-thirdparty.tex
index c07b5d2..45a038e 100644
--- a/labs/sysdev-thirdparty/sysdev-thirdparty.tex
+++ b/labs/sysdev-thirdparty/sysdev-thirdparty.tex
@@ -559,7 +559,7 @@ So, we have:
 
 \item The \code{/usr/bin/libpng14-config} tool and its symbolic link
   \code{/usr/bin/libpng-config}. This tool is a small shell script
-  that gives configuration informations about the libraries, needed to
+  that gives configuration information about the libraries, needed to
   know how to compile applications/libraries against libpng. This
   mechanism based on shell scripts is now being superseded by {\em
     pkg-config}, but as old applications or libraries may rely on it,