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

[Luca Ceresoli]

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

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

commit 07468918ee810d583302688f391655dbafd1ced0
Author: Luca Ceresoli <luca.ceresoli at bootlin.com>
Date:   Thu Feb 23 14:39:58 2023 +0100

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


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

07468918ee810d583302688f391655dbafd1ced0
 .../debugging-system-wide-profiling.tex                               | 4 ++--
 1 file changed, 2 insertions(+), 2 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 91c1e936..353d3290 100644
--- a/labs/debugging-system-wide-profiling/debugging-system-wide-profiling.tex
+++ b/labs/debugging-system-wide-profiling/debugging-system-wide-profiling.tex
@@ -82,10 +82,10 @@ Reanalyze the traces with kernel shark and try to understand what is going on.
 \section{LTTng}
 
 In order to observe our program performance, we want to instrument it with
-tracepoints. We would like to know how much times it takes to compute the
+tracepoints. We would like to know how much time it takes to compute the
 crc32 of a specific buffer.
 
-In order to do so, add tracepoints to your program which will allows to measure
+In order to do so, add tracepoints to your program which will allow to measure
 this. We'll add 2 tracepoints:
 
 \begin{itemize}