Changeset c6d5b092

Timestamp:

01/09/2010 07:15:55 AM (14 years ago)

Author:

Bruce Dubbs <bdubbs@…>

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.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, 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:

a55f5b38

Parents:

281a7d3

Message:

Grammar and spelling updates

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

Files:

• chapter01/changelog.xml (modified) (1 diff)
• general.ent (modified) (1 diff)
• prologue/architecture.xml (modified) (2 diffs)
• prologue/standards.xml (modified) (2 diffs)
• prologue/why.xml (modified) (7 diffs)

chapter01/changelog.xml

@@ -37 +37 @@
 
 -->
+
+    <listitem>
+      <para>2009-12-10</para>
+      <itemizedlist>
+        <listitem>
+          <para>[bdubbs] Grammar and spelling updates from 
+          Chris Staub. Fixes
+          <ulink url="&lfs-ticket-root;2548">#2548</ulink>.</para>
+        </listitem>
+      </itemizedlist>
+    </listitem>
+
 
     <listitem>

general.ent

@@ -1 @@
-<!ENTITY version "SVN-20100103">
-<!ENTITY releasedate "January 3, 2010">
+<!ENTITY version "SVN-20100110">
+<!ENTITY releasedate "January 10, 2010">
 <!ENTITY copyrightdate "1999-2010"><!-- jhalfs needs a literal dash, not &ndash; -->
 <!ENTITY milestone "7.0">

prologue/architecture.xml

@@ -11 +11 @@
   <title>LFS Target Architectures</title>
 
-<para>The primary target architecture of LFS is the 32-bit Intel CPU.  If you
+<para>The primary target architecture of LFS is the 32-bit Intel CPU. If you
 have not built an LFS system before, you should probably start with that
-target.  The 32-bit architecture is the most widely supported Linux system and
+target. The 32-bit architecture is the most widely supported Linux system and
 is most compatible with both open source and proprietary software.</para>
 
 <para>On the other hand, the instructions in this book are known to work, with
-some modifications, with both Power PC and 64-bit AMD/Intel CPUs.  To build a
-system that utilizes these CPUs, the main prerequisite in addition to those on
-the next few pages, is an existing system such as an earlier LFS system,
-Ubuntu, Red Hat/Fedora, SuSE, or other distribution that targets the system
-that you have.  Also note that a 32-bit system can be installed and used as a
-host system on a 64-bit AMD/Intel system.</para>
+some modifications, with both Power PC and 64-bit AMD/Intel CPUs. To build a
+system that utilizes one of these CPUs, the main prerequisite, in addition to
+those on the next few pages, is an existing Linux system such as an earlier LFS
+installation, Ubuntu, Red Hat/Fedora, SuSE, or other distribution that targets
+the architecture that you have. Also note that a 32-bit distribution can be
+installed and used as a host system on a 64-bit AMD/Intel computer.</para>
 
-<para>Some other facts about a 64-bit systems need to be added here.  When
+<para>Some other facts about a 64-bit systems need to be added here. When
 compared to a 32-bit system, the sizes of executable programs are slightly
-larger and the execution speeds are only slightly faster.  For example, in a
+larger and the execution speeds are only slightly faster. For example, in a
 test build of LFS-6.5 on a Core2Duo CPU based system, the following statistics
 were measured:</para>
@@ -40 +40 @@
 
 <para>The default 64-bit build that results from LFS is considered a "pure"
-64-bit system.  That is, it supports 64-bit executables only.  Building a
-"multi-lib" system requires building many applications twice, once for a 32-bit
-system and once for a 64-bit system.  Currently this is not directly supported
-in the book, but is under consideration for a future release.  In the meantime,
+64-bit system. That is, it supports 64-bit executables only. Building a
+"multi-lib" system requires compiling many applications twice, once for a 32-bit
+system and once for a 64-bit system. Currently this is not directly supported
+in the book, but is under consideration for a future release. In the meantime,
 you can refer to the <ulink url="http://trac.cross-lfs.org/">Cross Linux From
 Scratch</ulink> project for this advanced topic.</para>
 
-<para>There is one last comment about 64-bit systems.  There are some packages
+<para>There is one last comment about 64-bit systems. There are some packages
 that cannot currently be built in a "pure" 64-bit system or require specialized
-build instructions.  Generally, these packages have some embedded 32-bit
+build instructions. Generally, these packages have some embedded 32-bit
 specific assembly language instructions that fail when building on a 64-bit
 system.  Examples include the  <ulink

prologue/standards.xml

@@ -21 +21 @@
         <para><ulink url="http://www.unix.org/single_unix_specification">The 
         Single UNIX Specification Version 3 (POSIX)</ulink>.  Note: 
-        Free registratration is required.</para>
+        Free registration is required.</para>
       </listitem>
       <listitem>
@@ -50 +50 @@
     certifications tests is possible, but not without many additional packages
     that are beyond the scope of LFS.  Most of these additional packages have
-    intallation instructions in BLFS. </para> 
+    installation instructions in BLFS. </para> 
 
     <variablelist>

prologue/why.xml

@@ -13 +13 @@
     <para>As stated earlier, the goal of LFS is to build a complete and usable 
     foundation-level system.  This includes all packages needed to replicate 
-    itself while providing a relativly minimal base from which to customize
+    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
@@ -51 +51 @@
 
         <para>This package package contains a linker, an assembler, and other 
-        tools for handling object files.  </para>
+        tools for handling object files.</para>
       </listitem>
 
@@ -58 +58 @@
 
         <para>This package contains the GNU version of yacc (Yet Another
-        Compiler Compiler) needed to build several other LFS  programs.
+        Compiler Compiler) needed to build several other LFS programs.
         </para>
       </listitem>
@@ -103 +103 @@
 
         <para>This package contains the utilities for handling the ext2, ext3
-        and ext4 file systems.  These are the most common and thouroughly
+        and ext4 file systems.  These are the most common and thoroughly
         tested file systems that Linux supports.</para>
       </listitem>
@@ -240 +240 @@
 
         <para>This package contains a very nice text file viewer that
-        allows scolling up or down when viewing a file.   
+        allows scrolling up or down when viewing a file.
         </para>
       </listitem>
@@ -330 +330 @@
 
         <para>This package is an interpreter for the runtime language
-        PERL.  </para>
+        PERL.</para>
       </listitem>
 
@@ -437 +437 @@
         <para>Vim</para>
 
-        <para>This package an editor.  It was chosen because its compatibility
-        with the classic vi editor and its huge number of powerful
+        <para>This package contains an editor. It was chosen because of its
+        compatibility with the classic vi editor and its huge number of powerful
         capabilities.  An editor is a very personal choice for
         many users and any other editor could be substituted if desired.