[bootlin/training-materials updates] master: yocto: reword a few sentences (f0d94f30)

[Alexandre Belloni]

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

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

commit f0d94f305ccc66e1acf07d0ade4ef763d0d5df22
Author: Alexandre Belloni <alexandre.belloni at bootlin.com>
Date:   Thu Jun 22 00:23:29 2023 +0200

    yocto: reword a few sentences
    
    Signed-off-by: Alexandre Belloni <alexandre.belloni at bootlin.com>


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

f0d94f305ccc66e1acf07d0ade4ef763d0d5df22
 slides/yocto-advanced/yocto-advanced.tex               |  4 ++--
 slides/yocto-layer/yocto-layer.tex                     |  2 +-
 slides/yocto-recipe-advanced/yocto-recipe-advanced.tex | 16 ++++++++--------
 3 files changed, 11 insertions(+), 11 deletions(-)

diff --git a/slides/yocto-advanced/yocto-advanced.tex b/slides/yocto-advanced/yocto-advanced.tex
index 1187d72d..c7c10fbb 100644
--- a/slides/yocto-advanced/yocto-advanced.tex
+++ b/slides/yocto-advanced/yocto-advanced.tex
@@ -17,8 +17,8 @@
       install a software component (application, library, \dots).
     \item These tasks can be run independently (if their dependencies
       are met).
-    \item All available packages in Poky are not selected by default
-      in the images.
+    \item All the available packages in the project layer are not
+      selected by default to be built and included in the images.
     \item Some packages may provide the same functionality, e.g.
       OpenSSH and Dropbear.
   \end{itemize}
diff --git a/slides/yocto-layer/yocto-layer.tex b/slides/yocto-layer/yocto-layer.tex
index 225037da..80aaaa75 100644
--- a/slides/yocto-layer/yocto-layer.tex
+++ b/slides/yocto-layer/yocto-layer.tex
@@ -36,7 +36,7 @@
     \item Poky is not a final set of layers. It is the common base.
     \item Layers are added when needed.
     \item When making modifications to the existing recipes or when
-      adding new ones, it is a good practice not to modify Poky.
+      adding new ones, it is a good practice to avoid modifying Poky.
       Instead you can create your own layers!
   \end{itemize}
 \end{frame}
diff --git a/slides/yocto-recipe-advanced/yocto-recipe-advanced.tex b/slides/yocto-recipe-advanced/yocto-recipe-advanced.tex
index 3196a1a4..b814725f 100644
--- a/slides/yocto-recipe-advanced/yocto-recipe-advanced.tex
+++ b/slides/yocto-recipe-advanced/yocto-recipe-advanced.tex
@@ -5,10 +5,10 @@
 \begin{frame}
   \frametitle{Introduction to recipe extensions}
   \begin{itemize}
-    \item It is a good practice {\bf not} to modify recipes available
-          in Poky.
-    \item But it is sometimes useful to modify an existing recipe, to
-          apply a custom patch for example.
+    \item It is a good practice to avoid modifying recipes available
+          in third party layers so it is easy to update.
+    \item But it is sometimes useful to apply a custom patch or add a
+      configuration file for example.
     \item The BitBake \emph{build engine} allows to modify a recipe by
           extending it.
     \item Multiple extensions can be applied to a recipe.
@@ -44,9 +44,9 @@
         to \code{example_0.1.bb} and \code{example_0.2.bb} but not
         \code{example_1.0.bb}
     \end{itemize}
-    \item Append files are {\bf version specific}. If the recipe is
-          updated to a newer version, the append files must also be
-          updated.
+    \item Append files should be {\bf version specific}. If the recipe
+      is updated to a newer version, the append files must also be
+      updated.
     \item If adding new files, the path to their directory must
           be prepended to the \code{FILESEXTRAPATHS} variable.
     \begin{itemize}
@@ -150,7 +150,7 @@ do_install:append() {
         \item Utility tasks such as: \code{clean}, \code{listtasks}
       \end{itemize}
     \item Automatically applies patch files listed in \code{SRC_URI}
-    \item Defines mirrors: \code{SOURCEFORGE_MIRROR}
+    \item Defines mirrors: \code{SOURCEFORGE_MIRROR},
       \code{DEBIAN_MIRROR}, \code{GNU_MIRROR}, \code{KERNELORG_MIRROR}\dots
     \item Defines \code{oe_runmake}, using \code{EXTRA_OEMAKE} to use
       custom arguments.