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

Michael Opdenacker michael.opdenacker at free-electrons.com
Tue Dec 3 06:28:15 CET 2013

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

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


commit 5543bfe6d6c96b15600325ac4fda7a6b1e53ad65
Author: Michael Opdenacker <michael.opdenacker at free-electrons.com>
Date:   Tue Dec 3 06:27:24 2013 +0100

    Misc typo and grammar corrections
    Signed-off-by: Michael Opdenacker <michael.opdenacker at free-electrons.com>


 agenda/kernel-agenda.tex                           |    2 +-
 slides/kernel-device-model/kernel-device-model.tex |    6 +++---
 .../kernel-porting-content.tex                     |    2 +-
 3 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/agenda/kernel-agenda.tex b/agenda/kernel-agenda.tex
index c357f9e..bc45a58 100644
--- a/agenda/kernel-agenda.tex
+++ b/agenda/kernel-agenda.tex
@@ -137,7 +137,7 @@ Embedded Linux kernel and driver development training\\
   While our explanations will be focused on specifically the Linux
   subsystems needed to implement those drivers, they will always be
   generic enough to convey the general design philosophy of the Linux
-  kernel. The informations learnt will therefore apply beyond just
+  kernel. The information learnt will therefore apply beyond just
   I2C, input or memory-mapped devices.
diff --git a/slides/kernel-device-model/kernel-device-model.tex b/slides/kernel-device-model/kernel-device-model.tex
index 2d965b4..5defb08 100644
--- a/slides/kernel-device-model/kernel-device-model.tex
+++ b/slides/kernel-device-model/kernel-device-model.tex
@@ -558,7 +558,7 @@ static int serial_imx_probe(struct platform_device *pdev)
   \frametitle{Device Tree}
-  \item On many embedded architectures, manual instantation of
+  \item On many embedded architectures, manual instantiation of
     platform devices was considered to be too verbose and not easily
   \item Such architectures are moving, or have moved, to use the {\em
@@ -656,12 +656,12 @@ static struct platform_driver serial_omap_driver = {
   \frametitle{Device Tree Resources}
   \item The drivers will use the same mechanism that we saw previously
-    to retrieve the basic informations: interrupts numbers, physical
+    to retrieve basic information: 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
     unnecessary lookups to the DT when loading your driver.
-  \item Any additional informations will be specific to a driver or
+  \item Any additional information will be specific to a driver or
     the class it belongs to, defining the {\em bindings}
diff --git a/slides/kernel-porting-content/kernel-porting-content.tex b/slides/kernel-porting-content/kernel-porting-content.tex
index 0591f4a..acf370e 100644
--- a/slides/kernel-porting-content/kernel-porting-content.tex
+++ b/slides/kernel-porting-content/kernel-porting-content.tex
@@ -63,7 +63,7 @@
     and one could freely register an additional one.
   \item The Linux kernel was defining a {\em machine structure} for
     each board, which associates the {\em machine ID} with a set of
-    informations and callbacks.
+    information and callbacks.
   \item The bootloader had to pass the {\em machine ID} to the kernel
     in a specific ARM register.

More information about the training-materials-updates mailing list