@@ -, +, @@ 
---
 .../embedded/handbook/cross-compiling-kernel.xml   |   15 +++++++++++----
 1 files changed, 11 insertions(+), 4 deletions(-)
--- a/xml/htdocs/proj/en/base/embedded/handbook/cross-compiling-kernel.xml	
+++ a/xml/htdocs/proj/en/base/embedded/handbook/cross-compiling-kernel.xml	
@@ -25,10 +25,10 @@ compiling is all the same.
 
 <p>
 You should install the kernel into the sysroot so that if you want to
-cross-compile packages which include kernel modules, the process should be
-transparent.  If you don't need such packages, then of course the actual place
-where you build the kernel does not matter.  Some people build all their
-kernels in <path>/usr/src/</path> for example.
+cross-compile packages which include kernel modules, the process will be
+transparent.  Otherwise, the actual place where you build the kernel does
+not matter.  Some people build all their kernels in <path>/usr/src/</path>
+for example.
 </p>
 
 </body>
@@ -64,6 +64,13 @@ chop off that trailing <c>gcc</c> and that's what you use:
 </p>
 
 <p>
+There is an additional variable, <c>INSTALL_MOD_PATH</c>, which defines where
+the <path>/lib</path> directory will be created, and all the modules stored.
+While you don't have to transfer the kernel sources to your target device,
+if you build any modules, you'll want this directory.
+</p>
+
+<p>
 There are really two ways you can setup the system.  You can modify the
 toplevel Makefile or you can override the relevant variables on the command
 line.  How you do it is largely a matter of taste, so we'll cover both.  Pick
--