[bootlin/training-materials updates] master: debugging: labs: fix typos (507ee6e1)

[Luca Ceresoli]

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

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

commit 507ee6e173a131e0491f36575ffa083f17783bb3
Author: Luca Ceresoli <luca.ceresoli at bootlin.com>
Date:   Fri Mar 24 16:11:03 2023 +0100

    debugging: labs: fix typos
    
    Signed-off-by: Luca Ceresoli <luca.ceresoli at bootlin.com>


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

507ee6e173a131e0491f36575ffa083f17783bb3
 .../debugging-system-wide-profiling.tex                             | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/labs/debugging-system-wide-profiling/debugging-system-wide-profiling.tex b/labs/debugging-system-wide-profiling/debugging-system-wide-profiling.tex
index af079717..ef203765 100644
--- a/labs/debugging-system-wide-profiling/debugging-system-wide-profiling.tex
+++ b/labs/debugging-system-wide-profiling/debugging-system-wide-profiling.tex
@@ -47,7 +47,7 @@ $ perf probe --source=./ -x ./crc_random main:35 crc
 \end{bashinput}
 
 We can finally trace the application using \code{trace-cmd} with this event. We will
-use the remote tracing capabilities of \code{trace-cmd} top do that. First, we will
+use the remote tracing capabilities of \code{trace-cmd} to do that. First, we will
 start the \code{trace-cmd} server on the desktop platform:
 
 \begin{bashinput}
@@ -70,7 +70,7 @@ $ sudo apt install kernelshark
 $ kernelshark
 \end{bashinput}
 
-We can see that something is wrong, our process does not seems to compute crc at
+We can see that something is wrong, our process does not seem to compute crc at
 a fixed rate. Let's trace the \code{sched_switch} events to see whats happening:
 
 \begin{bashinput}
@@ -78,7 +78,7 @@ $ trace-cmd record -e sched_switch -e probe_crc_random:main_L35 ./crc_random
 ^C
 \end{bashinput}
 
-Reanalyze the traces with kernel shark and try to understand what is going on.
+Reanalyze the traces with kernelshark and try to understand what is going on.
 
 \section{LTTng}