[FE training-materials-updates] yocto: labs: remove i2c-tools as it is not in Poky

[Antoine Ténart]

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

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

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

commit a31dad0c97248f12f23e58ca2088da9697bd1a6b
Author: Antoine Tenart <antoine.tenart at free-electrons.com>
Date:   Fri Nov 7 14:44:49 2014 +0100

    yocto: labs: remove i2c-tools as it is not in Poky
    
    Signed-off-by: Antoine Tenart <antoine.tenart at free-electrons.com>


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

a31dad0c97248f12f23e58ca2088da9697bd1a6b
 labs/yocto-custom-image/yocto-custom-image.tex | 9 ++++-----
 1 file changed, 4 insertions(+), 5 deletions(-)

diff --git a/labs/yocto-custom-image/yocto-custom-image.tex b/labs/yocto-custom-image/yocto-custom-image.tex
index 3fe1a80..417a671 100644
--- a/labs/yocto-custom-image/yocto-custom-image.tex
+++ b/labs/yocto-custom-image/yocto-custom-image.tex
@@ -52,7 +52,7 @@ itself. We will here create a custom package for game related recipes.
 
 With the above documentation, create a \code{packagegroup-felabs-games} group
 which inherits from the \code{packagegroup} class. Add the nInvaders program
-into its dependencies.
+into its runtime dependencies.
 
 Now update the image recipe to include the package group instead of the
 nInvaders program directly.
@@ -66,9 +66,8 @@ possible differences. In our example only the built package list will change.
 
 Create a debug version of the previous image recipe, and name it
 \code{felabs-image-minimal-dev}. Try to avoid duplicating code! Then add the
-\code{dev-pkgs} to the built packages list as well as the \code{i2c-tools}. It
-is also recommended to update the recipe's description.
+\code{dev-pkgs} to the built packages list. It is also recommended to
+update the recipe's description.
 
 Build the new debug image with BitBake and check the previously
-included packages are present in the newly generated rootfs. You can
-look for the \code{i2c-tools} binaries.
+included packages are present in the newly generated rootfs.