aboutsummaryrefslogtreecommitdiffstats
path: root/chapter05/lockingglibc.xml
diff options
context:
space:
mode:
authorGreg Schafer <greg@linuxfromscratch.org>2003-09-14 09:16:58 +0000
committerGreg Schafer <greg@linuxfromscratch.org>2003-09-14 09:16:58 +0000
commitfa2e6935d752ce276379bd57a1e8820cdda7ad9c (patch)
treeef89db523eaa9518f5d41e3079f6b43373fe24f5 /chapter05/lockingglibc.xml
parent0bf1ea9287e37205420476c4c06af9c41a435e65 (diff)
Small grammar adjustments.
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@2812 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
Diffstat (limited to 'chapter05/lockingglibc.xml')
-rw-r--r--chapter05/lockingglibc.xml4
1 files changed, 2 insertions, 2 deletions
diff --git a/chapter05/lockingglibc.xml b/chapter05/lockingglibc.xml
index a8bee36e8..7938df879 100644
--- a/chapter05/lockingglibc.xml
+++ b/chapter05/lockingglibc.xml
@@ -39,8 +39,8 @@ all in. Or you can edit the specs file by hand if you want to: just replace
<para>Lastly, there is a possibility that some include files from the host
system have found their way into gcc's private include dir. This can happen
-because of GCC's "fixincludes" process which part of the GCC build. We'll
-explain more about this further on in this chapter. For now, run the
+because of GCC's "fixincludes" process which runs as part of the GCC build.
+We'll explain more about this further on in this chapter. For now, run the
following commands to eliminate this possibility.</para>
<para><screen><userinput>rm -f /tools/lib/gcc-lib/*/*/include/{pthread.h,bits/sigthread.h}</userinput></screen></para>