[FE training-materials-updates] Fix: no kpath macro in labs yet

[Michael Opdenacker]

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

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

commit 5bb1127df13083849ba05a1ce1e4b39598b02f8e
Author: Michael Opdenacker <michael.opdenacker at free-electrons.com>
Date:   Thu Oct 29 05:39:58 2015 +0100

    Fix: no kpath macro in labs yet
    
    Signed-off-by: Michael Opdenacker <michael.opdenacker at free-electrons.com>


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

5bb1127df13083849ba05a1ce1e4b39598b02f8e
 labs/android-new-board/android-new-board.tex               | 2 +-
 labs/kernel-i2c-communication/kernel-i2c-communication.tex | 4 ++--
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/labs/android-new-board/android-new-board.tex b/labs/android-new-board/android-new-board.tex
index 029f7fe..b10a5fd 100644
--- a/labs/android-new-board/android-new-board.tex
+++ b/labs/android-new-board/android-new-board.tex
@@ -314,7 +314,7 @@ the values that are working.
 
 To make these changes permanently, you will have to edit the kernel
 code. The used PWM is defined is the \code{am335xevm} board file, in
-the \kpath{arch/arm/mach-omap2} folder. The PWM work by switching on
+the \code{arch/arm/mach-omap2} folder. The PWM work by switching on
 and off at a fast pace the power supply to be able to adjust the
 average voltage delivered between 0 and the actual voltage of the
 line. Increase the period by a factor of 100.
diff --git a/labs/kernel-i2c-communication/kernel-i2c-communication.tex b/labs/kernel-i2c-communication/kernel-i2c-communication.tex
index 005cdf6..ba0deca 100644
--- a/labs/kernel-i2c-communication/kernel-i2c-communication.tex
+++ b/labs/kernel-i2c-communication/kernel-i2c-communication.tex
@@ -71,7 +71,7 @@ signals.
 Now that we know the register offsets, let's try to understand
 how they are used in existing code. For example, open the
 the Device Tree for the AM335x EVM board
-(\kpath{arch/arm/boot/dts/am335x-evm.dts}), which is using
+(\code{arch/arm/boot/dts/am335x-evm.dts}), which is using
 \code{i2c1} too. Look for \code{i2c1_pins}, and you will see how
 offsets are declared and what values they are given:
 
@@ -90,7 +90,7 @@ and \code{0x15c} instead of \code{0x95c}! In both cases, there is a
 
 However, this makes sense if you look at the way the base address of the
 Control Module Registers is defined. Look for \code{pinctrl-single} in
-\kpath{arch/arm/boot/dts/am33xx.dtsi}:
+\code{arch/arm/boot/dts/am33xx.dtsi}:
 
 \begin{verbatim}
 am33xx_pinmux: pinmux at 800 {