[FE training-materials-updates] Explain better what raw flash storage is

[Michael Opdenacker]

Repository : git://git.free-electrons.com/training-materials.git

On branch  : master
Link       : http://git.free-electrons.com/training-materials/commit/?id=fc89ed633a159d59c9335a747d9fe1eef46251df

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

commit fc89ed633a159d59c9335a747d9fe1eef46251df
Author: Michael Opdenacker <michael.opdenacker at free-electrons.com>
Date:   Wed Dec 10 14:06:59 2014 +0100

    Explain better what raw flash storage is
    
    Signed-off-by: Michael Opdenacker <michael.opdenacker at free-electrons.com>


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

fc89ed633a159d59c9335a747d9fe1eef46251df
 slides/sysdev-block-filesystems/sysdev-block-filesystems.tex | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/slides/sysdev-block-filesystems/sysdev-block-filesystems.tex b/slides/sysdev-block-filesystems/sysdev-block-filesystems.tex
index 80922ae..199e72f 100644
--- a/slides/sysdev-block-filesystems/sysdev-block-filesystems.tex
+++ b/slides/sysdev-block-filesystems/sysdev-block-filesystems.tex
@@ -17,8 +17,9 @@
       flash storage, but have an integrated controller that emulates a block
       device, managing and erasing flash sectors in a transparent way.
     \end{itemize}
-  \item {\bf Flash devices} can be read, but writing requires erasing,
-    and often occurs on a larger size than the “block” size.
+  \item {\bf Raw flash devices} than are driven by a controller on the
+      SoC. They can be read, but writing requires erasing, and often occurs
+      on a larger size than the “block” size.
     \begin{itemize}
     \item NOR flash, NAND flash
     \end{itemize}