Changeset a22f6e7

Timestamp:

09/11/2002 10:22:24 PM (22 years ago)

Author:

Timothy Bauscher <timothy@…>

Branches:

10.0, 10.0-rc1, 10.1, 10.1-rc1, 11.0, 11.0-rc1, 11.0-rc2, 11.0-rc3, 11.1, 11.1-rc1, 11.2, 11.2-rc1, 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, 6.0, 6.1, 6.1.1, 6.3, 6.4, 6.5, 6.6, 6.7, 6.8, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.5-systemd, 7.6, 7.6-systemd, 7.7, 7.7-systemd, 7.8, 7.8-systemd, 7.9, 7.9-systemd, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, arm, bdubbs/gcc13, ml-11.0, multilib, renodr/libudev-from-systemd, s6-init, trunk, v4_0, v4_1, v5_0, v5_1, v5_1_1, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc

Children:

c77ff37

Parents:

e9d69fa6

Message:

Grammatic changes to the preface.

git-svn-id: ​http://svn.linuxfromscratch.org/LFS/trunk/BOOK@2084 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

Files:

• chapter01/changelog.xml (modified) (1 diff)
• preface/organization.xml (modified) (1 diff)
• preface/organpart1.xml (modified) (1 diff)
• preface/organpart2.xml (modified) (1 diff)
• preface/whonotread.xml (modified) (2 diffs)
• preface/whoread.xml (modified) (5 diffs)

chapter01/changelog.xml

@@ -53 +53 @@
 </itemizedlist>
 </para></listitem>
+
+<listitem><para>September 11th, 2002 [timothy]: Preface: Grammatic
+changes.</para></listitem>
 
 <listitem><para>September 8th, 2002 [timothy]: Chapter 06: Applied Alex's

preface/organization.xml

@@ -3 +3 @@
 <?dbhtml filename="organization.html" dir="preface"?>
 
-<para>This book is divided into the following parts. Although most of
-the appendices are copied into part II (which enlarges the book somewhat), 
-we believe it's the easiest way to read it like this. It simply saves
-you from having to click to an Appendix, then back to where you were in
-part II. That's a real chore especially if you're reading the TXT
-version of this book.</para>
+<para>Much of the appendices is integrated into Part II (which enlarges the
+book somewhat). We believe this makes for easier reading. This way, you
+don't have to keep referencing an Appendix while you read Part II. That's
+a real chore, especially if you're reading the TXT version of this book.
+This book is divided into the following parts.</para>
 
 &pf-oz-organpart1;

preface/organpart1.xml

@@ -4 +4 @@
 <para>Part I gives general information about the contents of the book
 (revisions, where to get it, changelog, mailing lists, and other contact
-information). It also contains suggested reading that discusses a few
-important considerations to think about before beginning your LFS
+information). It also contains suggested readings which discuss a few
+important considerations to consider before beginning your LFS
 system.</para>
 

preface/organpart2.xml

@@ -3 +3 @@
 
 <para>Part II guides you through the building and installation of an LFS
-system. The finished LFS system will be the core foundation that the rest
-of your Linux system will be built on. What you choose to do with your brand
-new LFS system will be built and supported by this foundation that we build
-in Part II.</para>
+system. The resulting LFS system will be the core foundation with which
+the rest of your Linux system is built upon. Whatever your system becomes,
+it will be built and supported by the foundation that we build in Part
+II.</para>
 
 </sect2>

preface/whonotread.xml

@@ -4 +4 @@
 
 <para>If you do not wish to build your own Linux system from scratch, then
-you probably do not want to read this book. Our goal is to build a complete
+you probably don't want to read this book. Our goal is to build a complete
 and useable foundation system. If you only want to know what happens while
-your computer boots, then, we recommend the
-<quote>From-PowerUp-To-Bash-Prompt-HOWTO</quote>. The HOWTO builds a bare
+your computer boots, then we recommend the
+<quote>From Power Up To Bash Prompt</quote> HOWTO. The HOWTO builds a bare
 system which is similar to that of this book, but it focuses strictly on
 creating a system capable of booting to a BASH prompt.</para>
@@ -13 +13 @@
 <para>While you decide which to read, consider your objective. If you wish
 to build a Linux system while learning a bit along the way, then this book
-is probably your best choice. If your objective is strictly educational, and
+is probably your best choice. If your objective is strictly educational and
 you do not have any plans for your finished system, then the
-From-PowerUp-To-Bash-Prompt-HOWTO is probably a better choice.</para>
+<quote>From Power Up To Bash Prompt</quote> HOWTO is probably a better choice.</para>
 
-<para>The <quote>From-PowerUp-To-Bash-Prompt-HOWTO</quote> is located at
+<para>The <quote>From Power Up To Bash Prompt</quote> HOWTO is located at
 <ulink url="http://www.netspace.net.au/~gok/power2bash/"/>.</para>
 

preface/whoread.xml

@@ -9 +9 @@
 is a good question.</para>
 
-<para>One important reason for LFS's existence is helping people 
+<para>One important reason for LFS' existence is to help people
 learn how a Linux system works from the inside out. Building an LFS system
 helps demonstrate what makes Linux tick, and how things work together and
@@ -22 +22 @@
 
 <para>Another benefit of LFS is the ability to create a very compact Linux
-system. When installing a regular distribution, you end up with a lot of
-programs you likely will never use. They're just sitting there wasting
-(precious) disk space. It isn't difficult to build LFS systems of under
+system. When installing a regular distribution, you end up with several
+programs which you are likely to never use. They're just sitting there wasting
+(precious) disk space. It isn't difficult to build an LFS system less than
 100 MB. Does that still sound like a lot? A few of us have been working on
 creating a very small embedded LFS system. We successfully built a system
@@ -34 +34 @@
 fast-food restaurant, you have no idea what you are eating. LFS on the
 other hand, doesn't give you a hamburger, but the recipe to make a hamburger. 
-This allows you to review it, omit unwanted ingredients, and allows you to
-add your own ingredients that enhance the flavor of your burger. When you
+This allows you to review it, to omit unwanted ingredients, and to
+add your own ingredients which enhance the flavor of your burger. When you
 are satisfied with the recipe, you go on to preparing it. You make it just
 the way you like it: broil it, bake it, deep-fry it, barbeque it, or eat it
@@ -42 +42 @@
 <para>Another analogy that we can use is that of comparing LFS with a 
 finished house. LFS will give you the skeletal plan of a house, but it's up 
-to you to build it, giving you the freedom to adjust your plans as you go.</para>
+to you to build it. You have the freedom to adjust your plans as you
+go.</para>
 
 <para>Another advantage of a custom built Linux system is security.
@@ -48 +49 @@
 everything and apply all the security patches you feel are needed. You don't 
 have to wait for somebody else to compile binary packages that fix a security
-hole. Examine the new patch and build it yourself. You have no guarantee 
-that the new package was built correctly and actually fixes the problem
-(adequately). You never truly know whether a security hole is fixed or
-not unless you do it yourself.</para>
+hole. Unless you examine the patch and build it yourself you have no
+guarantee that the new package was built correctly and actually fixes the
+problem (adequately). You never truly know whether a security hole is fixed
+or not unless you do it yourself.</para>
 
 </sect1>