[bootlin/training-materials updates] master: yocto: slides: SBoM: fix a few typos (0e21bd46)

[Luca Ceresoli]

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

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

commit 0e21bd46cc1e08040b26243a6a1c136a6b80b75c
Author: Luca Ceresoli <luca.ceresoli at bootlin.com>
Date:   Fri May 5 17:04:44 2023 +0200

    yocto: slides: SBoM: fix a few typos
    
    Signed-off-by: Luca Ceresoli <luca.ceresoli at bootlin.com>


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

0e21bd46cc1e08040b26243a6a1c136a6b80b75c
 slides/yocto-licensing/yocto-licensing.tex | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/slides/yocto-licensing/yocto-licensing.tex b/slides/yocto-licensing/yocto-licensing.tex
index 0f847a18..807a7485 100644
--- a/slides/yocto-licensing/yocto-licensing.tex
+++ b/slides/yocto-licensing/yocto-licensing.tex
@@ -129,14 +129,14 @@ ARCHIVER_MODE[src] = "configured"
      \item License compliance assessment
      \item Vulnerability assessment. You can use the SBoM to check
 	   whether your software supply chain is impacted by currently known
-	   vulnerabilities, both in through host or target packages.
+	   vulnerabilities, both in host and target packages.
   \end{itemize}
   The US government is pushing for having such information
   in all software it procures and will probably make it mandatory soon.
 \end{frame}
 
 \begin{frame}[fragile]
-  \frametitle{How to create SPDX with OpenEmbedded}
+  \frametitle{How to create SPDX SBoM with OpenEmbedded}
   \begin{itemize}
      \item Add \code{INHERIT += "create-spdx"} to your configuration file
      \item JSON SPDX files will be generated in \code{tmp/deploy/images/MACHINE/}