[bootlin/training-materials updates] master: debugging: slides: minor wording improvements (e5667ff4)

[Luca Ceresoli]

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

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

commit e5667ff4c0ba5e21e036dff1978f81dae8099f36
Author: Luca Ceresoli <luca.ceresoli at bootlin.com>
Date:   Wed Aug 23 16:38:40 2023 +0200

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


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

e5667ff4c0ba5e21e036dff1978f81dae8099f36
 .../debugging-application-profiling.tex                             | 6 +++---
 .../debugging-application-profiling.tex                             | 4 ++--
 slides/debugging-memory-issues/debugging-memory-issues.tex          | 2 +-
 .../debugging-system-wide-profiling.tex                             | 6 +++---
 4 files changed, 9 insertions(+), 9 deletions(-)

diff --git a/labs/debugging-application-profiling/debugging-application-profiling.tex b/labs/debugging-application-profiling/debugging-application-profiling.tex
index 4f4f6be6..d17da459 100644
--- a/labs/debugging-application-profiling/debugging-application-profiling.tex
+++ b/labs/debugging-application-profiling/debugging-application-profiling.tex
@@ -55,7 +55,7 @@ the results with \code{heaptrack_gui}.
 
 \section{Cachegrind \& Callgrind}
 
-Cachegrind and Callgrind allows to profile a userspace application by
+Cachegrind and Callgrind allow to profile a userspace application by
 simulating the processor that will run it. In order to analyze our application
 and understand where time is spent, we are going to profile it with both
 tools.
@@ -125,8 +125,8 @@ event, use \code{perf list} on the target to find it amongst the cache events:
 $ perf list cache
 \end{bashinput}
 
-Once found, execute the program on the target using perf stat and specified that event
-using -e:
+Once found, execute the program on the target using \code{perf stat} and
+specify that event using \code{-e}:
 
 \begin{bashinput}
 $ perf stat -e L1-dcache-store-misses ./png_convert tux.png out.png
diff --git a/slides/debugging-application-profiling/debugging-application-profiling.tex b/slides/debugging-application-profiling/debugging-application-profiling.tex
index fd35cfb4..cbea345a 100644
--- a/slides/debugging-application-profiling/debugging-application-profiling.tex
+++ b/slides/debugging-application-profiling/debugging-application-profiling.tex
@@ -90,8 +90,8 @@
     \item Allocating/freeing memory too much can lead to the kernel spending a
           considerable amount of time in \code{clear_page()}.
     \begin{itemize}
-      \item Due to the fact the kernel clear pages before giving them to
-            processes to avoid data leakage.
+      \item The kernel clears pages before giving them to processes to
+            avoid data leakage.
     \end{itemize}
     \item Reducing application memory footprint can allow optimizing cache usage
           as well as page miss.
diff --git a/slides/debugging-memory-issues/debugging-memory-issues.tex b/slides/debugging-memory-issues/debugging-memory-issues.tex
index 7ce44606..1c0289a6 100644
--- a/slides/debugging-memory-issues/debugging-memory-issues.tex
+++ b/slides/debugging-memory-issues/debugging-memory-issues.tex
@@ -267,7 +267,7 @@ Segmentation fault (core dumped)
   \begin{itemize}
     \item Upon segfault, a coredump will be generated in the current directory
     \item This coredump can be opened with GDB and will pinpoint the exact
-          location where the error did happened
+          location where the error happened
   \end{itemize}
   \begin{block}{}
     \begin{minted}[fontsize=\small]{console}
diff --git a/slides/debugging-system-wide-profiling/debugging-system-wide-profiling.tex b/slides/debugging-system-wide-profiling/debugging-system-wide-profiling.tex
index ab367dd8..e72008d0 100644
--- a/slides/debugging-system-wide-profiling/debugging-system-wide-profiling.tex
+++ b/slides/debugging-system-wide-profiling/debugging-system-wide-profiling.tex
@@ -312,7 +312,7 @@ kworker/0:2-mm_    44 [000]   208.620653:     133104   cycles:          c0a44c84
 \begin{frame}[fragile]
   \frametitle{Using {\em perf trace} }
   \begin{itemize}
-    \item \code{perf trace} captures and display all tracepoints/events that
+    \item \code{perf trace} captures and displays all tracepoints/events that
           have been triggered when executing a command
   \end{itemize}
 
@@ -370,8 +370,8 @@ Overhead  Shared Object                         Symbol
     \item It offers a wide range of tracing capabilities allowing to observe the
           system behavior.
     \begin{itemize}
-      \item Trace static tracepoints already inserted in the kernel various
-            parts (scheduler, interrupts, etc).
+      \item Trace static tracepoints already inserted at various locations
+            in the kernel (scheduler, interrupts, etc).
       \item Relies on GCC mcount() capability and kernel code patching mechanism
             to call {\em ftrace} tracing handlers.
     \end{itemize}