[FE training-materials-updates] Minor improvements

[Michael Opdenacker]

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

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

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

commit 7b66a66a355f3ea885424ed8c17fa5dc937bafa3
Author: Michael Opdenacker <michael.opdenacker at free-electrons.com>
Date:   Fri Oct 5 13:38:49 2012 +0200

    Minor improvements


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

7b66a66a355f3ea885424ed8c17fa5dc937bafa3
 .../kernel-serial-interrupt.tex                    |    2 +-
 ...kernel-driver-development-character-drivers.tex |   10 +++++-----
 ...el-driver-development-lab-character-drivers.tex |    2 +-
 .../kernel-driver-development-lab-interrupts.tex   |    2 +-
 .../kernel-driver-development-sleeping.tex         |    4 ++--
 5 files changed, 10 insertions(+), 10 deletions(-)

diff --git a/labs/kernel-serial-interrupt/kernel-serial-interrupt.tex b/labs/kernel-serial-interrupt/kernel-serial-interrupt.tex
index b1a0a62..3bfb925 100644
--- a/labs/kernel-serial-interrupt/kernel-serial-interrupt.tex
+++ b/labs/kernel-serial-interrupt/kernel-serial-interrupt.tex
@@ -7,7 +7,7 @@ During this lab, you will:
   Calao board
 \item See how Linux handles shared interrupt lines
 \item Implement the read() operation of the serial port driver to put
-  the process to sleep when no data is available
+  the process to sleep when no data are available
 \item Implement the interrupt handler to wake-up the sleeping process
   waiting for received characters
 \item Handle communication between the interrupt handler and the
diff --git a/slides/kernel-driver-development-character-drivers/kernel-driver-development-character-drivers.tex b/slides/kernel-driver-development-character-drivers/kernel-driver-development-character-drivers.tex
index 0445618..d1e41ac 100644
--- a/slides/kernel-driver-development-character-drivers/kernel-driver-development-character-drivers.tex
+++ b/slides/kernel-driver-development-character-drivers/kernel-driver-development-character-drivers.tex
@@ -460,14 +460,14 @@ Block devices:
 \begin{frame}[fragile]
   \frametitle{Character device registration 1/2}
   \begin{itemize}
-  \item The kernel represents character drivers with a cdev structure
+  \item The kernel represents character drivers with a \code{cdev} structure
   \item Declare this structure globally (within your module):
 \begin{minted}{c}
 #include <linux/cdev.h>
 
 static struct cdev acme_cdev;
 \end{minted}
-  \item In the init function, initialize the structure:
+  \item In the \code{init} function, initialize the structure:
 \begin{minted}{c}
 cdev_init(&acme_cdev, &acme_fops);
 \end{minted}
@@ -609,11 +609,11 @@ module_exit(acme_exit);
 \begin{frame}
 \frametitle{Character Driver Example Summary 4/4}
   \begin{itemize}
-  \item Kernel: Character Device Writer
+  \item Kernel: character device writer
     \begin{itemize}
     \item Define the file operations callbacks for the device file:
-      read, write, ioctl, ...
-    \item In the module init function, reserve major and minor numbers
+      \code{read}, \code{write}, \code{ioctl}, ...
+    \item In the module \code{init} function, reserve major and minor numbers
       with \code{register_chrdev_region()}, init a \code{cdev}
       structure with your file operations and add it to the system
       with \code{cdev_add()}.
diff --git a/slides/kernel-driver-development-lab-character-drivers/kernel-driver-development-lab-character-drivers.tex b/slides/kernel-driver-development-lab-character-drivers/kernel-driver-development-lab-character-drivers.tex
index e923ebb..8dfede3 100644
--- a/slides/kernel-driver-development-lab-character-drivers/kernel-driver-development-lab-character-drivers.tex
+++ b/slides/kernel-driver-development-lab-character-drivers/kernel-driver-development-lab-character-drivers.tex
@@ -4,7 +4,7 @@
   \begin{itemize}
   \item Writing a simple character driver, to write data to the serial
     port.
-  \item On your workstation, checking that transmitted data is
+  \item On your workstation, checking that transmitted data are
     received correctly.
   \item Exchanging data between userspace and kernel space.
   \item Practicing with the character device driver API.
diff --git a/slides/kernel-driver-development-lab-interrupts/kernel-driver-development-lab-interrupts.tex b/slides/kernel-driver-development-lab-interrupts/kernel-driver-development-lab-interrupts.tex
index 769cc15..69c4a20 100644
--- a/slides/kernel-driver-development-lab-interrupts/kernel-driver-development-lab-interrupts.tex
+++ b/slides/kernel-driver-development-lab-interrupts/kernel-driver-development-lab-interrupts.tex
@@ -6,6 +6,6 @@
     earlier.
   \item Register an interrupt handler.
   \item Waiting for data to be available in the read file operation.
-  \item Waking up the code when data is available from the device.
+  \item Waking up the code when data are available from the device.
   \end{itemize}
 }
diff --git a/slides/kernel-driver-development-sleeping/kernel-driver-development-sleeping.tex b/slides/kernel-driver-development-sleeping/kernel-driver-development-sleeping.tex
index 90ee0e1..e2e966b 100644
--- a/slides/kernel-driver-development-sleeping/kernel-driver-development-sleeping.tex
+++ b/slides/kernel-driver-development-sleeping/kernel-driver-development-sleeping.tex
@@ -12,8 +12,8 @@
 \begin{frame}[fragile]
   \frametitle{How to sleep 1/3}
   \begin{itemize}
-  \item Must declare a wait queue A wait queue will be used to store
-  \item the list of threads waiting for an event
+  \item Must declare a wait queue
+  \item A wait queue will be used to store the list of threads waiting for an event
     \begin{itemize}
     \item Static queue declaration
       \begin{itemize}