aboutsummaryrefslogtreecommitdiffstats
path: root/chapter06/introduction.xml
diff options
context:
space:
mode:
Diffstat (limited to 'chapter06/introduction.xml')
-rw-r--r--chapter06/introduction.xml6
1 files changed, 3 insertions, 3 deletions
diff --git a/chapter06/introduction.xml b/chapter06/introduction.xml
index dfe834c24..68456fc4e 100644
--- a/chapter06/introduction.xml
+++ b/chapter06/introduction.xml
@@ -3,7 +3,7 @@
<?dbhtml filename="introduction.html" dir="chapter06"?>
<para>In this chapter we enter the building site, and start
-constructing our LFS system in earnest. That is, we chroot into
+constructing our LFS system in earnest. That is, we chroot into
our temporary mini Linux system, create some auxiliary things,
and then start installing all the packages, one by one.</para>
@@ -21,13 +21,13 @@ take a look at the optimization hint at
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>
+optimization and see if the problem goes away.</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
to <filename class="directory">/static</filename> hard-wired into it.
For the same reason, <emphasis>do not </emphasis> compile packages
-in parallel. Compiling in parallel may save you some time (especially on
+in parallel. Compiling in parallel may save you some time (especially on
dual-CPU machines), but it could result in a program containing a
hard-wired path to <filename class="directory">/static</filename>,
which will cause the program to stop working when the static directory