[bootlin/training-materials updates] master: debugging: slides: debugging-system-wide-profiling: Reword some sentences (affebcd2)

[Herve Codina]

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

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

commit affebcd2699822279500714987f3c88643823cf8
Author: Herve Codina <herve.codina at bootlin.com>
Date:   Tue Nov 15 23:15:00 2022 +0100

    debugging: slides: debugging-system-wide-profiling: Reword some sentences
    
    Signed-off-by: Herve Codina <herve.codina at bootlin.com>


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

affebcd2699822279500714987f3c88643823cf8
 .../debugging-system-wide-profiling.tex                        | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

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 1da61c73..98ad967a 100644
--- a/slides/debugging-system-wide-profiling/debugging-system-wide-profiling.tex
+++ b/slides/debugging-system-wide-profiling/debugging-system-wide-profiling.tex
@@ -95,8 +95,8 @@ register_kretprobe(&probe);
   \frametitle{{\em perf}}
   \begin{itemize}
     \item Perf allows to do a wide range of tracing and recording operations.
-    \item The kernel already contains events and tracepoints that can used and
-          listed using \code{perf list}.
+    \item The kernel already contains events and tracepoints that can be used.
+          The list is given using \code{perf list}.
     \item Syscall tracepoints should be enabled in kernel configuration using
           \kconfig{CONFIG_FTRACE_SYSCALLS}.
     \item New tracepoint can be created dynamically on all symbols and registers
@@ -545,7 +545,7 @@ void read_hw()
   \begin{itemize}
     \item {\em trace-cmd} is a tool written by Steven Rostedt which allow
           interacting with kernel ftrace support (\manpage{trace-cmd}{1}).
-    \item The tracer supported by {\em trace-cmd} are the one exposed by ftrace.
+    \item The tracer supported by {\em trace-cmd} are those exposed by ftrace.
     \item {\em trace-cmd} offers multiple commands:
     \begin{itemize}
       \item {\em list}: list available plugins/events that can be recorded
@@ -558,8 +558,8 @@ void read_hw()
 \begin{frame}
   \frametitle{Remote tracing with {\em trace-cmd}}
   \begin{itemize}
-    \item {\em trace-cmd} output can be quite big and thus difficult on embedded
-          platform with much storage space.
+    \item {\em trace-cmd} output can be quite big and thus difficult to be
+          stored on an embedded platform with not much storage space.
     \item For that purpose, a listen command is available and allows sending
           the traces over network.
     \begin{itemize}