Attached is a few cleanups to grammar and fixes for inconsistent use of
terminology throughout the book.
diff -urN LFS/trunk/BOOK/chapter02/creatingpartition.xml LFS.edited/trunk/BOOK/chapter02/creatingpartition.xml
--- LFS/trunk/BOOK/chapter02/creatingpartition.xml 2012-08-23 03:28:25.000000000 +0200
+++ LFS.edited/trunk/BOOK/chapter02/creatingpartition.xml 2012-08-23 03:39:41.000000000 +0200
@@ -34,7 +34,7 @@
This is enough to store all the source tarballs and compile the packages.
However, if the LFS system is intended to be the primary Linux system,
additional software will probably be installed which will require additional
- space. A 10GB partition is a reasonable size to provide for growth. The LFS
+ space. A 10 gigabyte partition is a reasonable size to provide for growth. The LFS
system itself will not take up this much room. A large portion of this
requirement is to provide sufficient free temporary storage. Compiling
packages can require a lot of disk space which will be reclaimed after the
@@ -104,7 +104,7 @@
<para>Swapping is never good. Generally you can tell if a system is
swapping by just listening to disk activity and observing how the system
reacts to commands. The first reaction to swapping should be to check for
- an unreasonable command such as trying to edit a five gigabyte file. If
+ an unreasonable command such as trying to edit a 5 gigabyte file. If
swapping becomes a normal occurance, the best solution is to purchase more
RAM for your system.</para> </sect3>
@@ -130,13 +130,13 @@
<listitem><para>/usr – A separate /usr partition is generally used
if providing a server for a thin client or diskless workstation. It is
- normally not needed for LFS. A size of five gigabytes will handle most
+ normally not needed for LFS. A size of 5 gigabytes will handle most
installations.</para></listitem>
<listitem><para>/opt – This directory is most useful for
BLFS where multiple installations of large packages like Gnome or KDE can
be installed without embedding the files in the /usr hierarchy. If
- used, five to ten gigabytes is generally adequate.</para>
+ used, 5-10 gigabytes is generally adequate.</para>
</listitem>
<listitem><para>/tmp – A separate /tmp directory is rare, but
diff -urN LFS/trunk/BOOK/prologue/typography.xml LFS.edited/trunk/BOOK/prologue/typography.xml
--- LFS/trunk/BOOK/prologue/typography.xml 2012-08-23 03:28:25.000000000 +0200
+++ LFS.edited/trunk/BOOK/prologue/typography.xml 2012-08-23 03:33:55.000000000 +0200
@@ -17,7 +17,7 @@
<screen role="nodump"><userinput>./configure --prefix=/usr</userinput></screen>
- <para>This form of text is designed to be typed exactly as seen unless
+ <para>This form of text is designed to be typed exactly as seen, unless
otherwise noted in the surrounding text. It is also used in the explanation
sections to identify which of the commands is being referenced.</para>
diff -urN LFS/trunk/BOOK/prologue/why.xml LFS.edited/trunk/BOOK/prologue/why.xml
--- LFS/trunk/BOOK/prologue/why.xml 2012-08-23 03:28:25.000000000 +0200
+++ LFS.edited/trunk/BOOK/prologue/why.xml 2012-08-23 03:32:37.000000000 +0200
@@ -15,7 +15,7 @@
itself while providing a relatively minimal base from which to customize
a more complete system based on the choices of the user. This does not
mean that LFS is the smallest system possible. Several important packages
- are included that are not strictly required. The lists below document the
+ are included that are not strictly required. The lists below documents the
rationale for each package in the book.</para>
<itemizedlist>
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
