[bootlin/training-materials updates] master: debugging: labs: debugging-application-profiling: Fix typos (d81c0a91)

[Herve Codina]

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

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

commit d81c0a91371b60497db7ae626628e0750c412e7c
Author: Herve Codina <herve.codina at bootlin.com>
Date:   Thu Nov 17 14:30:28 2022 +0100

    debugging: labs: debugging-application-profiling: Fix typos
    
    Signed-off-by: Herve Codina <herve.codina at bootlin.com>


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

d81c0a91371b60497db7ae626628e0750c412e7c
 .../debugging-application-profiling.tex                             | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/labs/debugging-application-profiling/debugging-application-profiling.tex b/labs/debugging-application-profiling/debugging-application-profiling.tex
index 4db1ce7e..5aaea70c 100644
--- a/labs/debugging-application-profiling/debugging-application-profiling.tex
+++ b/labs/debugging-application-profiling/debugging-application-profiling.tex
@@ -100,9 +100,9 @@ $ perf record ./png_convert tux.png out.png
 \end{bashinput}
 
 Once recorded, a \code{perf.data} file will be generated. This file will
-contains the traces that have been recorded. These traces can be analyzed using
-\code{perf report}. YOu will quickly notice that the output is not the same as
-valgrind because it display a time spent per function (excluding function
+contain the traces that have been recorded. These traces can be analyzed using
+\code{perf report}. You will quickly notice that the output is not the same as
+valgrind because it displays a time spent per function (excluding function
 calls inside them). This allows to find which function takes most of the
 execution time. In order to compare this output to the valgrind one, we can
 run perf and also record the callgraph using the \code{--call-graph} option.