diff --git a/chapter04/chapter04.xml b/chapter04/chapter04.xml
index 2ba008db2..c4092747f 100644
--- a/chapter04/chapter04.xml
+++ b/chapter04/chapter04.xml
@@ -27,19 +27,21 @@ published, please try to google for the package. Should you remain
 unsuccessful with this, you can consult the book's errata page at
 <ulink url="http://linuxfromscratch.org/lfs/print/"/> or try
 the alternative means of downloading given at 
-<ulink url="http://linuxfromscratch.org/lfs/packages.html"/></para>
+<ulink url="http://linuxfromscratch.org/lfs/packages.html"/>.</para>
 
 <para>You'll need to store all the downloaded packages and patches somewhere
 that is conveniently available throughout the entire build. You'll also need a
 working directory in which to unpack the sources and build them. A scheme that
-works well is to use <filename>$LFS/tools/src/packages</filename> for all the
-downloaded files and <filename>$LFS/tools/src</filename> for the working
-directory. In this way, everything will be on the LFS partition and always
-available.</para>
- 
-<para>Ater each package installation you should normally delete the source and
-build directories (for cleanness sake and to save space),
-<emphasis>unless</emphasis> instructed to do otherwise.</para>
+works well is to use <filename>$LFS/usr/src/packages</filename> for all the
+downloaded files and <filename>$LFS/usr/src</filename> as the working
+directory. In this way, everything will be on the LFS partition and available
+during all stages of the building process.</para>
+
+<!--
+<para>So you may want to execute the following command:</para>
+
+<para><screen><userinput>mkdir -p $LFS/usr/src/packages</userinput></screen></para>
+-->
 
 <!--
 <para>For your convenience the top of the list contains a link to a file
diff --git a/chapter05/introduction.xml b/chapter05/introduction.xml
index faf94c045..37866e207 100644
--- a/chapter05/introduction.xml
+++ b/chapter05/introduction.xml
@@ -36,6 +36,10 @@ warnings -- mostly about deprecated, but not invalid, use of the C or C++
 syntax. It's just that C standards have changed rather often and some
 packages still use the older standard, which is not really a problem.</para>
 
+<para><emphasis>Unless</emphasis> told not to, you should normally delete the
+source and build directories after installing each package -- for cleanness
+sake and to save space.</para>
+
 <para>Before continuing, make sure the LFS environment variable is set up
 properly by executing the following:</para>