[bootlin/training-materials updates] master: Embedded Linux: fix font referring to "core" file (ffa305fd)

[Michael Opdenacker]

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

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

commit ffa305fd312aca64dc7b19fbb648bb31e2c82be8
Author: Michael Opdenacker <michael.opdenacker at bootlin.com>
Date:   Thu Apr 14 11:01:58 2022 +0200

    Embedded Linux: fix font referring to "core" file
    
    Signed-off-by: Michael Opdenacker <michael.opdenacker at bootlin.com>


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

ffa305fd312aca64dc7b19fbb648bb31e2c82be8
 .../sysdev-application-development.tex                            | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/slides/sysdev-application-development/sysdev-application-development.tex b/slides/sysdev-application-development/sysdev-application-development.tex
index 6f4d42c3..1e0fdb23 100644
--- a/slides/sysdev-application-development/sysdev-application-development.tex
+++ b/slides/sysdev-application-development/sysdev-application-development.tex
@@ -251,19 +251,19 @@
   \item When an application crashes due to a {\em segmentation fault}
     and the application was not under control of a debugger, we get no
     information about the crash
-  \item Fortunately, Linux can generate a {\em core} file that
+  \item Fortunately, Linux can generate a \code{core} file that
     contains the image of the application memory at the moment of the
-    crash, and gdb can use this {\em core} file to let us analyze the
+    crash, and gdb can use this \code{core} file to let us analyze the
     state of the crashed application
   \item On the target
     \begin{itemize}
     \item Use \code{ulimit -c unlimited} in the shell starting the
-    application, to enable the generation of a {\em core} file
+    application, to enable the generation of a \code{core} file
     when a crash occurs
     \end{itemize}
   \item On the host
     \begin{itemize}
-    \item After the crash, transfer the {\em core} file from the target to
+    \item After the crash, transfer the \code{core} file from the target to
       the host, and run
       \code{ARCH-linux-gdb -c core-file application-binary}
     \end{itemize}