[bootlin/training-materials updates] master: debugging: labs: fix typo (f7532da4)

[Luca Ceresoli]

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

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

commit f7532da4a89dc7349ef2b82c3d5dcdfa9f12f7c8
Author: Luca Ceresoli <luca.ceresoli at bootlin.com>
Date:   Wed Mar 22 12:28:25 2023 +0100

    debugging: labs: fix typo
    
    "be able to disable" is funny, but incorrect, unfortunately! :-)
    
    Signed-off-by: Luca Ceresoli <luca.ceresoli at bootlin.com>


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

f7532da4a89dc7349ef2b82c3d5dcdfa9f12f7c8
 labs/debugging-memory-issues/debugging-memory-issues.tex | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/labs/debugging-memory-issues/debugging-memory-issues.tex b/labs/debugging-memory-issues/debugging-memory-issues.tex
index e9ba920d..2abda64e 100644
--- a/labs/debugging-memory-issues/debugging-memory-issues.tex
+++ b/labs/debugging-memory-issues/debugging-memory-issues.tex
@@ -34,7 +34,7 @@ You'll see various errors found by valgrind
   \item Memory leaks
 \end{itemize}
 
-In order to pinpoint exactly each error and be able to disable with gdb, vgdb
+In order to pinpoint exactly each error and be able to debug with gdb, vgdb
 can be used. We will do that remotely on the host using gdb-multiarch. First, we
 need to run valgrind with vgdb enabled on the target: