[bootlin/training-materials updates] master: debugging: slides: improve wording (5a4c223a)

[Luca Ceresoli]

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

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

commit 5a4c223a7db5b34da40ec6aac1b7cdc4f0b6ce81
Author: Luca Ceresoli <luca.ceresoli at bootlin.com>
Date:   Mon Aug 28 14:06:44 2023 +0200

    debugging: slides: improve wording
    
    Signed-off-by: Luca Ceresoli <luca.ceresoli at bootlin.com>


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

5a4c223a7db5b34da40ec6aac1b7cdc4f0b6ce81
 .../debugging-kernel-debugging.tex                      | 17 +++++++++--------
 1 file changed, 9 insertions(+), 8 deletions(-)

diff --git a/slides/debugging-kernel-debugging/debugging-kernel-debugging.tex b/slides/debugging-kernel-debugging/debugging-kernel-debugging.tex
index 0d19925c..c2b965c6 100644
--- a/slides/debugging-kernel-debugging/debugging-kernel-debugging.tex
+++ b/slides/debugging-kernel-debugging/debugging-kernel-debugging.tex
@@ -3,8 +3,9 @@
 \begin{frame}
   \frametitle{Linux Kernel Debugging}
   \begin{itemize}
-    \item Kernel features some very useful tools for debugging.
-    \item These tools are builtin the kernel since their activation often select instrumentation code for debugging
+    \item The Linux Kernel features some very useful tools for debugging.
+    \item These tools are builtin the kernel since their activation often
+          selects instrumentation code for debugging
     \begin{itemize}
       \item Erroneous memory accesses debugging tools ({\em KASAN}, {\em Kmemleak}, {\em KFENCE})
       \item Undefined behavior code debugging ({\em UBSAN})
@@ -24,7 +25,7 @@
 \begin{frame}
   \frametitle{Kernel early debug}
   \begin{itemize}
-  \item When booting, the kernel sometimes crashes before even displaying
+  \item When booting, the kernel sometimes crashes even before displaying
     the system messages
   \item On ARM, if your kernel doesn't boot or hangs without any
     message, you can activate early debugging options
@@ -67,7 +68,7 @@
     \begin{itemize}
       \item CPU state when the oops happened
       \item Registers content with potential interpretation
-      \item Backtrace of function calls that lead to the crash
+      \item Backtrace of function calls that led to the crash
       \item Stack content (last X bytes)
     \end{itemize}
     \item Depending on the architecture, the crash location can be identified
@@ -215,12 +216,12 @@
   \begin{itemize}
     \item Finally, on panic, the kernel will reboot into the "dump-capture"
       kernel allowing the user to dump the kernel coredump (\code{/proc/vmcore})
-      onto whatever media  
-    \item Command line additional options depends on the architecture
+      onto whatever media
+    \item Additional command line options depends on the architecture
     \item See \kdochtml{admin-guide/kdump/kdump} for more comprehensive
       explanations on how to setup the kdump kernel with \code{kexec}.
-    \item Additional user-space services and tools allows to automatically
-      collect and dump the vmcore file to remote location.
+    \item Additional user-space services and tools allow to automatically
+      collect and dump the vmcore file to a remote location.
     \begin{itemize}
       \item See kdump systemd service and the \code{makedumpfile} tool which
         can also compress the vmcore file into a smaller file (Only for x86,