[bootlin/training-materials updates] master: debugging: labs: debugging-kernel-debugging: Fix typos (30754d56)

[Herve Codina]

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

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

commit 30754d56a0f8d7af05005e3beb7a7a408ccf62a9
Author: Herve Codina <herve.codina at bootlin.com>
Date:   Thu Nov 17 15:38:23 2022 +0100

    debugging: labs: debugging-kernel-debugging: Fix typos
    
    Signed-off-by: Herve Codina <herve.codina at bootlin.com>


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

30754d56a0f8d7af05005e3beb7a7a408ccf62a9
 labs/debugging-kernel-debugging/debugging-kernel-debugging.tex | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/labs/debugging-kernel-debugging/debugging-kernel-debugging.tex b/labs/debugging-kernel-debugging/debugging-kernel-debugging.tex
index e9e4d94d..2703df07 100644
--- a/labs/debugging-kernel-debugging/debugging-kernel-debugging.tex
+++ b/labs/debugging-kernel-debugging/debugging-kernel-debugging.tex
@@ -100,7 +100,7 @@ First of all, confirm the previous information that were obtain post crash using
 GDB. This will allow you to also display variables values. Starting from that
 point, we will add a breakpoint on the \code{watchdog_set_drvdata()} function.
 However, this function is called early in boot so we will need to actually
-attach with KGDB at boot time. To do so, we'l modify the bootargs to specify
+attach with KGDB at boot time. To do so, we'll modify the bootargs to specify
 that. In U-Boot, add the following arguments to bootargs using \code{env edit}:
 
 \begin{bashinput}
@@ -141,7 +141,7 @@ clobbered with NULL. Once done, continue the execution and verify that you fixed
 the problem using the \code{watchdog} command.
 
 {\em Note: In theory, we could have add a watchpoint to watch the address that
-was modified but the arm32 platforms does not provide watchpoints support with
+was modified but the arm32 platforms do not provide watchpoints support with
 KGDB.}
 
 \section{Locking problems}
@@ -190,8 +190,8 @@ perfect copy of the crashed kernel (memory, registers, etc) which can be then
 debugged using gdb or crash. 
 
 \subsection{Configuring kexec}
-First of all we need to setup a kexec sutiable memory zone for our crash kernel
-image. THis is achieved via the linux command line. Reboot, interrupt U-Boot and
+First of all we need to setup a kexec suitable memory zone for our crash kernel
+image. This is achieved via the linux command line. Reboot, interrupt U-Boot and
 add the \code{crashkernel=80M} parameter. This will tell the kernel to reserve
 80M of memory to load a "rescue" kernel that will be booted on panic. We will
 also add an option which will panic the kernel on oops to allow executing the