Parcourir la source

Fix a couple of typos

git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@6963 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
Matthew Burgess il y a 20 ans
Parent
commit
6bff916735
3 fichiers modifiés avec 4 ajouts et 4 suppressions
  1. 1 1
      chapter05/adjusting.xml
  2. 1 1
      chapter05/gcc-pass2.xml
  3. 2 2
      general.ent

+ 1 - 1
chapter05/adjusting.xml

@@ -66,7 +66,7 @@ necessary.</para></important>
 need to be fixed (they might contain syntax errors, for example), and installs
 the fixed versions in a private include directory.  There is a possibility that,
 as a result of this process, some header files from the host system have found
-their way into GCC's private include dir. As the rest of this chapter only
+their way into GCC's private include directory. As the rest of this chapter only
 requires the headers from GCC and Glibc, which have both been installed at this
 point, any &quot;fixed&quot; headers can safely be removed.  This helps to avoid
 any host headers polluting the build environment.  Run the following commands to

+ 1 - 1
chapter05/gcc-pass2.xml

@@ -62,7 +62,7 @@ working.</para>
 normal circumstances the GCC <command>fixincludes</command> script is run in
 order to fix potentially broken header files.  As GCC-&gcc-version; and
 Glibc-&glibc-version; have already been installed at this point, and their
-respective header files are known not to require fixing, the
+respective header files are known to not require fixing, the
 <command>fixincludes</command> script is not required.  As mentioned previously,
 the script may in fact pollute the build environment by installing fixed headers
 from the host system into GCC's private include directory.  The running of the

+ 2 - 2
general.ent

@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="ISO-8859-1"?>
-<!ENTITY version "SVN-20051004">
-<!ENTITY releasedate "October 4, 2005">
+<!ENTITY version "SVN-20051005">
+<!ENTITY releasedate "October 5, 2005">
 <!ENTITY milestone "6.2">
 <!ENTITY generic-version "development"> <!-- Use "development", "testing", or "x.y[-pre{x}]" -->