[bootlin/training-materials updates] master: Kernel materials: minor improvements (d92da602)

[Michael Opdenacker]

Repository : https://github.com/bootlin/training-materials
On branch  : master
Link       : https://github.com/bootlin/training-materials/commit/d92da60248360b9124ed9b2a28fd55ee661325fa

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

commit d92da60248360b9124ed9b2a28fd55ee661325fa
Author: Michael Opdenacker <michael.opdenacker at bootlin.com>
Date:   Mon Feb 8 10:31:59 2021 +0100

    Kernel materials: minor improvements
    
    Signed-off-by: Michael Opdenacker <michael.opdenacker at bootlin.com>


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

d92da60248360b9124ed9b2a28fd55ee661325fa
 labs/kernel-serial-iomem/kernel-serial-iomem.tex | 2 +-
 slides/kernel-frameworks2/kernel-frameworks2.tex | 4 ++--
 slides/kernel-input/kernel-input.tex             | 2 +-
 3 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/labs/kernel-serial-iomem/kernel-serial-iomem.tex b/labs/kernel-serial-iomem/kernel-serial-iomem.tex
index ae06c71e..0b021770 100644
--- a/labs/kernel-serial-iomem/kernel-serial-iomem.tex
+++ b/labs/kernel-serial-iomem/kernel-serial-iomem.tex
@@ -180,7 +180,7 @@ address for the device plus the offset multiplied by 4.
 
 All the UART register offsets have standardized values, shared between
 several types of serial drivers (see
-\code{include/uapi/linux/serial_reg.h}). This explains why they are not
+\kfile{include/uapi/linux/serial_reg.h}). This explains why they are not
 completely ready to use and we have to multiply them by 4 for OMAP SoCs.
 
 Create a similar \code{reg_write()} routine, writing an unsigned integer
diff --git a/slides/kernel-frameworks2/kernel-frameworks2.tex b/slides/kernel-frameworks2/kernel-frameworks2.tex
index 1431e83a..03695b42 100644
--- a/slides/kernel-frameworks2/kernel-frameworks2.tex
+++ b/slides/kernel-frameworks2/kernel-frameworks2.tex
@@ -251,7 +251,7 @@ int main(void)
     reg.field1 = 42;
     reg.field2 = 67;
 
-    ret = ioctl(fd, PHN_SET_REG, & reg);
+    ret = ioctl(fd, PHN_SET_REG, &reg);
     assert(ret == 0);
 
     return 0;
@@ -539,7 +539,7 @@ struct rtl8150 {
     pointer that the driver must point to the corresponding
     \kstruct{device}
     \begin{itemize}
-    \item It's the relation between the logical device (for example a
+    \item It's the relationship between the logical device (for example a
       network interface) and the physical device (for example the USB
       network adapter)
     \end{itemize}
diff --git a/slides/kernel-input/kernel-input.tex b/slides/kernel-input/kernel-input.tex
index 92b7789c..1ad55f83 100644
--- a/slides/kernel-input/kernel-input.tex
+++ b/slides/kernel-input/kernel-input.tex
@@ -5,7 +5,7 @@
   \item The input subsystem takes care of all the input events coming
     from the human user.
   \item Initially written to support the USB {\em HID} (Human
-    Interface Device) devices, it quickly grew up to handle all kind
+    Interface Device) devices, it quickly grew up to handle all kinds
     of inputs (using USB or not): keyboards, mice, joysticks,
     touchscreens, etc.
   \item The input subsystem is split in two parts: