[bootlin/training-materials updates] master: debugging: labs: application-profiling: fix typos and improve sentences (152723d3)

[Luca Ceresoli]

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

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

commit 152723d35b853f7875d58acb187fbcf7e3ca394c
Author: Luca Ceresoli <luca.ceresoli at bootlin.com>
Date:   Thu Mar 23 11:49:22 2023 +0100

    debugging: labs: application-profiling: fix typos and improve sentences
    
    Signed-off-by: Luca Ceresoli <luca.ceresoli at bootlin.com>


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

152723d35b853f7875d58acb187fbcf7e3ca394c
 .../debugging-application-profiling.tex                   | 15 ++++++++-------
 1 file changed, 8 insertions(+), 7 deletions(-)

diff --git a/labs/debugging-application-profiling/debugging-application-profiling.tex b/labs/debugging-application-profiling/debugging-application-profiling.tex
index ccf963ab..9170a64f 100644
--- a/labs/debugging-application-profiling/debugging-application-profiling.tex
+++ b/labs/debugging-application-profiling/debugging-application-profiling.tex
@@ -47,26 +47,27 @@ the results with \code{heaptrack_gui}.
 
 Cachegrind and Callgrind allows to profile a userspace application by
 simulating the processor that will run it. In order to analyze our application
-and understand were the time is spent, we are going to profile it with both
+and understand where time is spent, we are going to profile it with both
 tools.
 
-In order to profile the application using the \code{callgrind} tool. Our program
-takes two parameters, an input png and an output one. We provided a
-\code{tux_small.png} which can be used as an input file. First let's compile it using
-the following commands:
+Let's profile the application using the \code{callgrind} tool. Our program
+takes two file names as parameters: an input PNG image and an output
+one. We provided a sample image in \code{tux_small.png} which can be used
+as an input file. First let's compile it using the following commands:
 
 \begin{bashinput}
 $ cd /home/$USER/debugging-labs/nfsroot/root/app_profiling
 $ make
 \end{bashinput}
 
-We are going to profile cache usage using Cachegrind with the following command:
+We are going to profile cache usage using Cachegrind with the following
+command on the target:
 
 \begin{bashinput}
 $ valgrind --tool=cachegrind ./png_convert tux_small.png out.png
 \end{bashinput}
 
-The execution will take some times and a \code{cachegrind.out.<pid>} will be
+The execution will take some time and a \code{cachegrind.out.<pid>} will be
 generated. Once finished, on the host, fix the permissions on the
 \code{callgrind.out.*} file to be able to open it with \code{Kcachegrind}: