[bootlin/training-materials updates] master: debugging: labs: 07: various wording and formatting improvements (59d36299)

[Luca Ceresoli]

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

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

commit 59d36299b741d83a7e4e3897b6a1832e7079c751
Author: Luca Ceresoli <luca.ceresoli at bootlin.com>
Date:   Mon Aug 28 17:52:12 2023 +0200

    debugging: labs: 07: various wording and formatting improvements
    
    Signed-off-by: Luca Ceresoli <luca.ceresoli at bootlin.com>


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

59d36299b741d83a7e4e3897b6a1832e7079c751
 .../debugging-kernel-debugging.tex                           | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/labs/debugging-kernel-debugging/debugging-kernel-debugging.tex b/labs/debugging-kernel-debugging/debugging-kernel-debugging.tex
index 2019981b..bc7ef66d 100644
--- a/labs/debugging-kernel-debugging/debugging-kernel-debugging.tex
+++ b/labs/debugging-kernel-debugging/debugging-kernel-debugging.tex
@@ -127,7 +127,7 @@ this happens. We will disassemble the code for this function to understand
 exactly where the issue happened.
 
 That is where we need a kernel compiled with \kconfig{CONFIG_DEBUG_INFO}
-as we did at the beginning of this lab. This way, the kernel vmlinux file is
+as we did in the initial lab. This way, the kernel vmlinux file is
 compiled with \code{-g} compiler flag, which adds a lot of debugging
 information (matching between source code lines and assembly for instance).
 
@@ -201,8 +201,8 @@ $ gdb-multiarch /home/$USER/debugging-labs/buildroot/output/build/linux-5.13/vml
 {\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 the previous information that were obtain post crash using
-GDB. This will allow you to also display variables values. Starting from that
+First of all, confirm with GDB the information that were previous 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
 attach with KGDB at boot time. To do so, we'll modify the bootargs to specify
@@ -255,7 +255,7 @@ Use it to set the variable with the previous value that was used before getting
 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
+{\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
 KGDB.}
 
@@ -404,8 +404,8 @@ the 192.168.0.100 entry).
 $ ifconfig eth0 192.168.0.101
 \end{bashinput}
 
-{\textbf Note: ethernet setup might timeout due to some init issues after kexec
-boot so this commands needs to be run another time.}
+\textbf{Note:} ethernet setup might timeout due to some init issues after kexec
+boot so this commands needs to be run another time.
 
 \begin{bashinput}
 $ cd /home/$USER/debugging-labs/