[bootlin/training-materials updates] master: debugging: labs: remove space before question mark (557df737)

[Luca Ceresoli]

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

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

commit 557df737a7a1c3f9b5954eb11d55024da86e797a
Author: Luca Ceresoli <luca.ceresoli at bootlin.com>
Date:   Tue Mar 21 22:33:37 2023 +0100

    debugging: labs: remove space before question mark
    
    Unlike French, in English there is no space before ending punctuation.
    
    Just replace ' ?' -> '?', no other content change.
    
    Signed-off-by: Luca Ceresoli <luca.ceresoli at bootlin.com>


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

557df737a7a1c3f9b5954eb11d55024da86e797a
 .../debugging-application-profiling.tex            |  6 ++---
 .../debugging-application-tracing.tex              |  8 +++----
 .../debugging-memory-issues.tex                    |  2 +-
 .../debugging-system-status.tex                    | 26 +++++++++++-----------
 4 files changed, 21 insertions(+), 21 deletions(-)

diff --git a/labs/debugging-application-profiling/debugging-application-profiling.tex b/labs/debugging-application-profiling/debugging-application-profiling.tex
index 1874fdce..fb19914f 100644
--- a/labs/debugging-application-profiling/debugging-application-profiling.tex
+++ b/labs/debugging-application-profiling/debugging-application-profiling.tex
@@ -34,9 +34,9 @@ Once done, a \code{massif.out.<pid>} file will be created. This file can be
 displayed with \code{ms_print}. Based on the result, can you answer the
 following questions:
 \begin{itemize}
-  \item What is the peak allocation size of this program ?
-  \item How much memory was allocated during the program lifetime ?
-  \item Do we have memory leaks at the end of execution ?
+  \item What is the peak allocation size of this program?
+  \item How much memory was allocated during the program lifetime?
+  \item Do we have memory leaks at the end of execution?
 \end{itemize}
 
 Note: \code{heaptrack} is not available on buildroot but is available on debian.
diff --git a/labs/debugging-application-tracing/debugging-application-tracing.tex b/labs/debugging-application-tracing/debugging-application-tracing.tex
index 57ba802a..44760a9f 100644
--- a/labs/debugging-application-tracing/debugging-application-tracing.tex
+++ b/labs/debugging-application-tracing/debugging-application-tracing.tex
@@ -70,8 +70,8 @@ $ strace ./strace_me
 Based on the output and running strace with other options, try to answer the
 following questions:
 \begin{itemize}
-  \item What are the files that are opened by this binary ?
-  \item How many time is \code{read()} called ?
-  \item Which \code{openat} system call failed ?
-  \item How many system calls are issued by the program ?
+  \item What are the files that are opened by this binary?
+  \item How many time is \code{read()} called?
+  \item Which \code{openat} system call failed?
+  \item How many system calls are issued by the program?
 \end{itemize}
diff --git a/labs/debugging-memory-issues/debugging-memory-issues.tex b/labs/debugging-memory-issues/debugging-memory-issues.tex
index 2f5f7047..e9ba920d 100644
--- a/labs/debugging-memory-issues/debugging-memory-issues.tex
+++ b/labs/debugging-memory-issues/debugging-memory-issues.tex
@@ -17,7 +17,7 @@ $ cd /home/$USER/debugging-labs/nfsroot/root/valgrind
 $ make
 \end{bashinput}
 
-Then run it on the target. Do you notice any problem ? Does it run correctly ?
+Then run it on the target. Do you notice any problem? Does it run correctly?
 Even though there is no segfault, an application might have some memory leaks
 or even out-of-bounds accesses, uninitialized memory, etc.
 
diff --git a/labs/debugging-system-status/debugging-system-status.tex b/labs/debugging-system-status/debugging-system-status.tex
index 78e00f86..d71bb897 100644
--- a/labs/debugging-system-status/debugging-system-status.tex
+++ b/labs/debugging-system-status/debugging-system-status.tex
@@ -19,19 +19,19 @@ system. Try to answer the following questions using the commands that were
 presented during the course:
 
 \begin{enumerate}
-  \item How many CPU does this processor have ?
-  \item What are the memory maps used by the \code{dropbear} process ?
-  \item How much PSS memory is used by \code{dropbear} ?
-  \item What is the amount of memory available for applications on the system ?
-  \item How much unused memory is left on our system ?
-  \item Is there swapped memory ?
-  \item Is there an application using too much CPU ?
-  \item How much time is spent by CPU0 in system mode (kernel) ?
-  \item Is there some IOs ongoing with storage devices ?
-  \item How many Mbytes/s are transferred from/to the MMC card ?
-  \item What is the process generating transfers to the MMC ?
-  \item Which processor receive most of the interrupts ?
-  \item How many interrupts were received from the MMC controller ?
+  \item How many CPU does this processor have?
+  \item What are the memory maps used by the \code{dropbear} process?
+  \item How much PSS memory is used by \code{dropbear}?
+  \item What is the amount of memory available for applications on the system?
+  \item How much unused memory is left on our system?
+  \item Is there swapped memory?
+  \item Is there an application using too much CPU?
+  \item How much time is spent by CPU0 in system mode (kernel)?
+  \item Is there some IOs ongoing with storage devices?
+  \item How many Mbytes/s are transferred from/to the MMC card?
+  \item What is the process generating transfers to the MMC?
+  \item Which processor receive most of the interrupts?
+  \item How many interrupts were received from the MMC controller?
 \end{enumerate}
 
 Once found, you can remove the files \code{/etc/init.d/S25stress-ng} and