[bootlin/training-materials updates] master: Kernel debugging: fix compile and syntax issues (976b82b2)

[Michael Opdenacker]

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

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

commit 976b82b27584e8321c88f7cd20b862f1ba243831
Author: Michael Opdenacker <michael.opdenacker at bootlin.com>
Date:   Mon Sep 13 09:02:30 2021 +0200

    Kernel debugging: fix compile and syntax issues
    
    Signed-off-by: Michael Opdenacker <michael.opdenacker at bootlin.com>


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

976b82b27584e8321c88f7cd20b862f1ba243831
 .../kernel-driver-development-debugging.tex                  | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/slides/kernel-driver-development-debugging/kernel-driver-development-debugging.tex b/slides/kernel-driver-development-debugging/kernel-driver-development-debugging.tex
index 0250fc1d..72773849 100644
--- a/slides/kernel-driver-development-debugging/kernel-driver-development-debugging.tex
+++ b/slides/kernel-driver-development-debugging/kernel-driver-development-debugging.tex
@@ -105,13 +105,13 @@ dev_info(&pdev->dev, "in probe\n");
   \begin{itemize}
   \item Messages are visible only once the console driver has been initialized.
   \item The console driver is simpler than a complete serial driver
-    and is initialize earlier than serial driver
-  \item But core subsystem are still initialized before, such as
-    memory, timer or interrupt, if a crash occurred there, then no
-    message are visible
-  \item on arm (32 bits) architecture most of the SoC implement the
+    and is initialized earlier than the serial driver
+  \item But core subsystems are still initialized before, such as
+    memory, timer or interrupt; if a crash occurred there, then no
+    messages are visible
+  \item On the ARM (32 bit) architecture most of the SoCs implement
     \code{early_printk} support
-  \item \Activate it with kconfig{CONFIG_DEBUG_LL} and \kconfig{CONFIG_EARLYPRINTK} and add
+  \item Activate it with \kconfig{CONFIG_DEBUG_LL} and \kconfig{CONFIG_EARLYPRINTK} and add
     \code{earlyprintk} to the kernel command line.
   \end{itemize}
 \end{frame}