Small fixups across the board.

git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@2883 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

1 files changed, 11 insertions, 7 deletions

diff --git a/chapter06/introduction.xml b/chapter06/introduction.xml
index f8063525f..d04afa665 100644
--- a/chapter06/introduction.xml
+++ b/chapter06/introduction.xml
@@ -15,13 +15,17 @@ Although we agree with that, we nevertheless choose to give the
 full instructions for each and every package, simply to minimize
 the possibilities for mistakes.</para>
 
-<para>If you plan to use compiler optimizations in this chapter,
-take a look at the optimization hint at
-<ulink url="&hints-root;optimization.txt"/>.
-Compiler optimizations can make a program run faster, but they
-may also cause compilation difficulties. If a package refuses
-to compile when using optimization, try to compile it without
-optimization and see if the problem goes away.</para>
+<para>If you plan to use compiler optimizations in this chapter, take a look at
+the optimization hint at <ulink url="&hints-root;optimization.txt"/>. Compiler
+optimizations can make a program run a touch faster, but they may also cause
+compilation difficulties and even problems when running the program. If a
+package refuses to compile when using optimization, try to compile it without
+optimization and see if the problem goes away. Even if the package does compile
+when using optimization, there is the risk it may have been compiled
+incorrectly due to compiler bugs or whatever. In short, the small gains achieved
+in using compiler optimization are generally outweighed by the risk. First time
+builders of LFS are encouraged not to bother. Your system will still be plenty
+fast enough and very stable at the same time.</para>
 
 <para>The order in which packages are installed in this chapter has
 to be strictly followed, to ensure that no program gets a path referring