[bootlin/training-materials updates] master: slides/sysdev-build-systems: style improvements (11ff3bdc)

[Michael Opdenacker]

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

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

commit 11ff3bdc3c7090b2e53cdd6aeaedbca4ec2f5d8a
Author: Michael Opdenacker <michael.opdenacker at bootlin.com>
Date:   Fri Jan 20 18:33:46 2023 +0100

    slides/sysdev-build-systems: style improvements
    
    Signed-off-by: Michael Opdenacker <michael.opdenacker at bootlin.com>


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

11ff3bdc3c7090b2e53cdd6aeaedbca4ec2f5d8a
 slides/sysdev-build-systems/sysdev-build-systems.tex | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/slides/sysdev-build-systems/sysdev-build-systems.tex b/slides/sysdev-build-systems/sysdev-build-systems.tex
index e698d1b8..1b7ec4d6 100644
--- a/slides/sysdev-build-systems/sysdev-build-systems.tex
+++ b/slides/sysdev-build-systems/sysdev-build-systems.tex
@@ -627,9 +627,9 @@ BBCLASSEXTEND = "native"
     your system image, and how reproducible this process is
   \item We have seen projects use the following (bad) procedure:
     \begin{itemize}
-    \item Install manually a binary distribution on their target hardware
-    \item Install by hand all necessary packages
-    \item Compile on the target the final applications
+    \item Install a binary distribution manually on their target hardware
+    \item Install all necessary packages by hand
+    \item Compile the final applications on the target
     \item Tweak configuration files directly on the target
     \item Then duplicate the resulting SD card for all other boards
     \end{itemize}