[FE training-materials-updates] kernel slides: fix some typos

[Alexandre Belloni]

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

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

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

commit f61ca9958112714b09faebb8c7d252864a3283a0
Author: Alexandre Belloni <alexandre.belloni at free-electrons.com>
Date:   Wed Nov 13 17:34:04 2013 +0800

    kernel slides: fix some typos
    
    Signed-off-by: Alexandre Belloni <alexandre.belloni at free-electrons.com>


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

f61ca9958112714b09faebb8c7d252864a3283a0
 slides/kernel-device-model/kernel-device-model.tex |    4 ++--
 .../kernel-driver-development-io-memory.tex        |    2 +-
 .../kernel-linux-intro-sources.tex                 |    2 +-
 3 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/slides/kernel-device-model/kernel-device-model.tex b/slides/kernel-device-model/kernel-device-model.tex
index 5bce5e6..ec28969 100644
--- a/slides/kernel-device-model/kernel-device-model.tex
+++ b/slides/kernel-device-model/kernel-device-model.tex
@@ -655,12 +655,12 @@ static struct platform_driver serial_omap_driver = {
 \begin{frame}
   \frametitle{Device Tree Resources}
   \begin{itemize}
-  \item The drivers will use the same mechanism than we saw previously
+  \item The drivers will use the same mechanism that we saw previously
     to retrieve the basic informations: interrupts numbers, physical
     addresses, etc.
   \item The available resources list will be built up by the kernel at
     boot time from the device tree, so that you don't need to make any
-    unnnecessary lookups to the DT when loading your driver.
+    unnecessary lookups to the DT when loading your driver.
   \item Any additional informations will be specific to a driver or
     the class it belongs to, defining the {\em bindings}
   \end{itemize}
diff --git a/slides/kernel-driver-development-io-memory/kernel-driver-development-io-memory.tex b/slides/kernel-driver-development-io-memory/kernel-driver-development-io-memory.tex
index c8faa65..83aac87 100644
--- a/slides/kernel-driver-development-io-memory/kernel-driver-development-io-memory.tex
+++ b/slides/kernel-driver-development-io-memory/kernel-driver-development-io-memory.tex
@@ -80,7 +80,7 @@ void release_region(
   \begin{itemize}
   \item Functions to read/write bytes (\code{b}), word (\code{w}) and longs (\code{l}) to I/O ports:
     \begin{itemize}
-    \item \mint{c}+unsigned in[bwl](unsigned port)+
+    \item \mint{c}+unsigned in[bwl](unsigned long port)+
     \item \mint{c}+void out[bwl](value, unsigned long port)+
     \end{itemize}
   \item And the strings variants: often more efficient than the
diff --git a/slides/kernel-linux-intro-sources/kernel-linux-intro-sources.tex b/slides/kernel-linux-intro-sources/kernel-linux-intro-sources.tex
index 2ad2f08..2276958 100644
--- a/slides/kernel-linux-intro-sources/kernel-linux-intro-sources.tex
+++ b/slides/kernel-linux-intro-sources/kernel-linux-intro-sources.tex
@@ -33,7 +33,7 @@
     \url{http://kernel.org/pub/linux/kernel} as {\bf full tarballs}
     (complete kernel sources) and {\bf patches} (differences between
     two kernel versions).
-  \item But for kernel development, one generaly uses the Git version
+  \item But for kernel development, one generally uses the Git version
     control system:
     \begin{itemize}
     \item Fetch the entire kernel sources and history\\