[bootlin/training-materials updates] master: debugging: labs: kernel: fix typos and formatting (02bb0ba5)

[Luca Ceresoli]

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

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

commit 02bb0ba5408bd26ddabbe5f2c713bdf490dadfa4
Author: Luca Ceresoli <luca.ceresoli at bootlin.com>
Date:   Thu Sep 21 18:21:02 2023 +0200

    debugging: labs: kernel: fix typos and formatting
    
    Signed-off-by: Luca Ceresoli <luca.ceresoli at bootlin.com>


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

02bb0ba5408bd26ddabbe5f2c713bdf490dadfa4
 labs/debugging-kernel-debugging/debugging-kernel-debugging.tex | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/labs/debugging-kernel-debugging/debugging-kernel-debugging.tex b/labs/debugging-kernel-debugging/debugging-kernel-debugging.tex
index 99c764c2..a8a963e2 100644
--- a/labs/debugging-kernel-debugging/debugging-kernel-debugging.tex
+++ b/labs/debugging-kernel-debugging/debugging-kernel-debugging.tex
@@ -180,7 +180,7 @@ Use <ctrl>C to terminate program
 Note: the slave ports number will depend on the run.
 
 \textbf{Important: before using \code{/dev/pts/7} and \code{/dev/pts/8}, the
-picocom process that did opened \code{/dev/ttyACM0} must be closed!}
+picocom process that did open \code{/dev/ttyACM0} must be closed!}
 
 On the target, setup KGDB by setting the console to be used for that purpose in
 kgdboc module parameters:
@@ -201,7 +201,7 @@ $ ${CROSS_COMPILE}gdb ${HOME}/debugging-labs/buildroot/output/build/linux-5.13/v
 {\em TIP: in order to allow auto-loading of python scripts, you can add
 \code{set auto-load safe-path /} in your .gdbinit file}
 
-First of all, confirm with GDB the information that were previous obtained
+First of all, confirm with GDB the information that were previously obtained
 post-crash. 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
@@ -235,7 +235,7 @@ that case, you can set the architecture using:
 
 Before continuing the execution, add a breakpoint on
 \code{watchdog_set_drvdata()} using the \code{break} GDB command and then
-continue the execution using the continue \code{command}
+continue the execution using the \code{continue} command
 
 \begin{bashinput}
 (gdb) break watchdog_set_drvdata
@@ -257,7 +257,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 added a watchpoint to watch the address that
-was modified but the arm32 platforms do not provide watchpoints support with
+was modified but the arm32 platform does not provide watchpoint support with
 KGDB.}
 
 \subsection{Debugging a module}
@@ -282,7 +282,7 @@ Then on the target, insert the module using insmod:
 \end{bashinput}
 
 We can now enter KGDB mode and attach the external gdb to it. We will do
-that using using the magic SySrq 'g' key. Before that, ensure the tty
+that using the magic SySrq 'g' key. Before that, ensure the tty
 device for gdb already set, or set it now:
 
 \begin{bashinput}