[bootlin/training-materials updates] master: debugging: slides: fix and improve sentences (d53df879)

[Luca Ceresoli]

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

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

commit d53df8796f8140de0a7eca795236230ecbd5757f
Author: Luca Ceresoli <luca.ceresoli at bootlin.com>
Date:   Tue Nov 14 11:37:32 2023 +0100

    debugging: slides: fix and improve sentences
    
    Fix grammar/typos and rewrite some sentencences for clarity.
    
    Signed-off-by: Luca Ceresoli <luca.ceresoli at bootlin.com>


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

d53df8796f8140de0a7eca795236230ecbd5757f
 slides/debugging-common-tools/debugging-common-tools.tex           | 2 +-
 .../debugging-linux-application-stack.tex                          | 7 ++++---
 2 files changed, 5 insertions(+), 4 deletions(-)

diff --git a/slides/debugging-common-tools/debugging-common-tools.tex b/slides/debugging-common-tools/debugging-common-tools.tex
index 58c18dbf..620bf4ab 100644
--- a/slides/debugging-common-tools/debugging-common-tools.tex
+++ b/slides/debugging-common-tools/debugging-common-tools.tex
@@ -373,7 +373,7 @@ sdb      104,42     274,55    2126,64       0,00  1280853  9921488        0
   \begin{itemize}
     \item {\em iotop} displays information about IOs much like {\em top} for each
           process.
-    \item Useful to find which application are generating too much IO accesses.
+    \item Useful to find applications generating too much I/O traffic.
     \begin{itemize}
     \item Needs \kconfigval{CONFIG_TASKSTATS}{y},
           \kconfigval{CONFIG_TASK_DELAY_ACCT}{y} and
diff --git a/slides/debugging-linux-application-stack/debugging-linux-application-stack.tex b/slides/debugging-linux-application-stack/debugging-linux-application-stack.tex
index 342fe344..cd67ef84 100644
--- a/slides/debugging-linux-application-stack/debugging-linux-application-stack.tex
+++ b/slides/debugging-linux-application-stack/debugging-linux-application-stack.tex
@@ -139,12 +139,13 @@
   \frametitle{Userspace memory segments}
   \begin{itemize}
     \item When starting a process, the kernel sets up several {\em Virtual
-          Memory Area}s (VMA), backed by \kstruct{vm_area_struct}), with
+          Memory Area}s (VMA), backed by \kstruct{vm_area_struct}, with
           different execution attributes.
     \item VMA are actually memory zones that are mapped with specific
           attributes (R/W/X).
-    \item A segmentation fault happens when a program tries to access a non
-          existent VMA or a correct one but in a way that is not allowed.
+    \item A segmentation fault happens when a program tries to access an
+      unmapped area or a mapped area with an access mode that is not
+      allowed.
     \begin{itemize}
       \item Writing data in a read-only segment
       \item Executing data from a non-executable segment