aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorGreg Schafer <greg@linuxfromscratch.org>2003-10-25 01:31:56 +0000
committerGreg Schafer <greg@linuxfromscratch.org>2003-10-25 01:31:56 +0000
commitb4f6bac08c9d1ee3bf4baa8a7445596e245a0075 (patch)
treed27428155fcba730c69de8cbfa076d863561b65c
parent323ef7403afab7a1bcb989023ac70d22e97c808f (diff)
Typo fix.
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@3039 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
-rw-r--r--chapter05/toolchaintechnotes.xml2
1 files changed, 1 insertions, 1 deletions
diff --git a/chapter05/toolchaintechnotes.xml b/chapter05/toolchaintechnotes.xml
index 20f5ddc5c..5cca86e2b 100644
--- a/chapter05/toolchaintechnotes.xml
+++ b/chapter05/toolchaintechnotes.xml
@@ -185,7 +185,7 @@ recompile this one library, instead of having to recompile all the programs that
make use of the improved function.</para>
<para>If dynamic linking has several advantages, why then do we statically link
-the first two packages in this chapter? The reasonsare threefold: historical,
+the first two packages in this chapter? The reasons are threefold: historical,
educational, and technical. Historical, because earlier versions of LFS
statically linked every program in this chapter. Educational, because knowing
the difference is useful. Technical, because we gain an element of independence