[FE training-materials-updates] Show "patch -p<n>" instead of "patch -p <n>"

[Michael Opdenacker]

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

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

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

commit cdba30afb2491030a1e1539258ac93945bad7b7f
Author: Michael Opdenacker <michael.opdenacker at free-electrons.com>
Date:   Mon Oct 8 21:27:26 2012 +0200

    Show "patch -p<n>" instead of "patch -p <n>"
    
    That's more common and consistent with the examples
    that we give afterwards.


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

cdba30afb2491030a1e1539258ac93945bad7b7f
 .../sysdev-linux-intro-sources.tex                 |   10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/slides/sysdev-linux-intro-sources/sysdev-linux-intro-sources.tex b/slides/sysdev-linux-intro-sources/sysdev-linux-intro-sources.tex
index 5d6cff1..73ebbdb 100644
--- a/slides/sysdev-linux-intro-sources/sysdev-linux-intro-sources.tex
+++ b/slides/sysdev-linux-intro-sources/sysdev-linux-intro-sources.tex
@@ -190,11 +190,11 @@ diff -Nru a/Makefile b/Makefile
   \end{itemize}
   \code{patch} usage examples:
   \begin{itemize}
-  \item \code{patch -p <n>   < diff_file}
-  \item \code{cat diff_file | patch -p <n>}
-  \item \code{xzcat diff_file.xz | patch -p <n>}
-  \item \code{bzcat diff_file.bz2 | patch -p <n>}
-  \item \code{zcat diff_file.gz | patch -p <n>}
+  \item \code{patch -p<n> < diff_file}
+  \item \code{cat diff_file | patch -p<n>}
+  \item \code{xzcat diff_file.xz | patch -p<n>}
+  \item \code{bzcat diff_file.bz2 | patch -p<n>}
+  \item \code{zcat diff_file.gz | patch -p<n>}
   \item Notes:
     \begin{itemize}
     \item \code{n}: number of directory levels to skip in the file paths