[bootlin/training-materials updates] master: Minor fixes (c53be2f9)

[Michael Opdenacker]

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

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

commit c53be2f911423d87d4bf0b8bcaf8a091efc6608a
Author: Michael Opdenacker <michael.opdenacker at bootlin.com>
Date:   Thu Aug 20 15:02:29 2020 +0200

    Minor fixes
    
    Signed-off-by: Michael Opdenacker <michael.opdenacker at bootlin.com>


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

c53be2f911423d87d4bf0b8bcaf8a091efc6608a
 labs/boot-time-bootloader/boot-time-bootloader.tex           | 2 +-
 slides/sysdev-flash-filesystems/sysdev-flash-filesystems.tex | 6 +++---
 2 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/labs/boot-time-bootloader/boot-time-bootloader.tex b/labs/boot-time-bootloader/boot-time-bootloader.tex
index 95e34cef..91503af8 100644
--- a/labs/boot-time-bootloader/boot-time-bootloader.tex
+++ b/labs/boot-time-bootloader/boot-time-bootloader.tex
@@ -149,7 +149,7 @@ setenv bootargs console=ttyO0,115200n8 rdinit=/playvideo
 spl export fdt ${loadaddr} - ${fdtaddr}
 \end{verbatim}
 
-You can then that \code{spl export} prepared everything to boot the
+You can then see that \code{spl export} prepared everything to boot the
 Linux kernel with the provided DTB, but didn't do it. At the end, it
 tells you where the exported data were stored in RAM:
 
diff --git a/slides/sysdev-flash-filesystems/sysdev-flash-filesystems.tex b/slides/sysdev-flash-filesystems/sysdev-flash-filesystems.tex
index 370f0ed2..365cee11 100644
--- a/slides/sysdev-flash-filesystems/sysdev-flash-filesystems.tex
+++ b/slides/sysdev-flash-filesystems/sysdev-flash-filesystems.tex
@@ -301,7 +301,7 @@ setenv mtdparts mtdparts=omap2-nand.0:512k(XLoader)ro,1536k(UBoot)ro,512k(Env),4
   \item The {\bf mtdchar} driver creates a character device for each
     MTD device/partition of the system
     \begin{itemize}
-    \item Usually named \code{/dev/mtdX} or \code{/dev/mtdXro}
+    \item Named \code{/dev/mtdX} and \code{/dev/mtdXro}
     \item Provide \code{ioctl()} to erase and manage the flash
     \item Used by the {\em mtd-utils} utilities
     \end{itemize}
@@ -405,7 +405,7 @@ setenv mtdparts mtdparts=omap2-nand.0:512k(XLoader)ro,1536k(UBoot)ro,512k(Env),4
     \item Wear leveling, power failure resistant
     \item Fast boot time
     \item Not part of the official Linux kernel: code only available
-      separately (Dual GPL / Proprietary license for non Linux
+      separately (Dual GPLv2 / Commercial license for non GPL
       operating systems)
     \item \url{https://yaffs.net/}
     \end{itemize}
@@ -488,7 +488,7 @@ setenv mtdparts mtdparts=omap2-nand.0:512k(XLoader)ro,1536k(UBoot)ro,512k(Env),4
 \begin{frame}
   \frametitle{UBI: good practice}
   \begin{itemize}
-  \item UBI is responsible for distributing writes all over the flash
+  \item UBI is responsible for distributing erases all over the flash
     device: the more space you assign to a partition attached to the
     UBI layer the more efficient the wear leveling will be
   \item If you need partitioning, use UBI volumes not MTD partitions