aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMark Hymers <markh@linuxfromscratch.org>2002-02-05 00:44:06 +0000
committerMark Hymers <markh@linuxfromscratch.org>2002-02-05 00:44:06 +0000
commit76c0b783eeb766c0dec8e66dab2e6c275ba0786d (patch)
tree751e2cc85e0ed2736148a391b6178b79b165feca
parent2d416d6f14ff0a42d1058c7a8b5350204d3ce88b (diff)
spelling / phrasing fixes
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@1547 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
-rw-r--r--appendixa/sysvinit-desc.xml2
-rw-r--r--chapter01/changelog.xml2
-rw-r--r--chapter01/othermodes.xml6
-rw-r--r--chapter05/whystatic.xml8
-rw-r--r--chapter06/kbd-exp.xml2
5 files changed, 10 insertions, 10 deletions
diff --git a/appendixa/sysvinit-desc.xml b/appendixa/sysvinit-desc.xml
index b1e112456..aa52e91fa 100644
--- a/appendixa/sysvinit-desc.xml
+++ b/appendixa/sysvinit-desc.xml
@@ -68,7 +68,7 @@ notified that the system is going down, and login is blocked.</para></sect3>
<para>sulogin is invoked by init when the system goes into single user mode
(this is done through an entry in /etc/inittab). Init also tries to
execute sulogin when it is passed the -b flag from the boot loader
-(eg, LILO).</para></sect3>
+(e.g., LILO).</para></sect3>
<sect3><title>telinit</title>
<para>telinit sends appropriate signals to init, telling it which runlevel to
diff --git a/chapter01/changelog.xml b/chapter01/changelog.xml
index ab294e423..c50478d48 100644
--- a/chapter01/changelog.xml
+++ b/chapter01/changelog.xml
@@ -153,7 +153,7 @@ Sysvinit: Changed the inittab contents to match the new
bootscripts.</para></listitem>
<listitem><para>January 15th, 2002 [marcheerdink]: Chapter 6 - file: changed
-the installation instruction so the sed isn't nessecary anymore.</para></listitem>
+the installation instruction so the sed isn't necessary anymore.</para></listitem>
<listitem><para>January 14th, 2002 [marcheerdink]: Changed the kernel header
files installation in chapter 5 so it's a bit more portable.</para></listitem>
diff --git a/chapter01/othermodes.xml b/chapter01/othermodes.xml
index 41e2b4c77..bef0720ab 100644
--- a/chapter01/othermodes.xml
+++ b/chapter01/othermodes.xml
@@ -10,9 +10,9 @@ the appropriate commands in the subject header of the message.</para>
to write to set a mode. The <emphasis>Unset command</emphasis> tells
what to write to unset a mode.</para>
-<para>The listname in the example subject headers should be replaced with the
-listname to which
-the mode is going to be applied to. If more than one mode is to be set (to
+<para>The word "listname" in the example subject headers below should be
+replaced with the listname to which the mode is going to be applied.
+If more than one mode is to be set (to
the same list or multiple lists) with one email, this can be done by
leaving the subject header blank and writing all the commands in the body of
the message instead.</para>
diff --git a/chapter05/whystatic.xml b/chapter05/whystatic.xml
index 316449d1e..a0d611469 100644
--- a/chapter05/whystatic.xml
+++ b/chapter05/whystatic.xml
@@ -6,7 +6,7 @@
based to one of the LFS mailing lists.</para>
<para>When making (compiling) a program, rather than having to rewrite all the
-functions for dealing with the kernel, hardware, files, etc. everytime you
+functions for dealing with the kernel, hardware, files, etc. every time you
write a new program, all these basic functions are instead kept in libraries.
glibc, which you install later, is one of these major libraries, which contain
code for all the basic functions programs use, like opening files, printing
@@ -16,11 +16,11 @@ program, so that it can use any of the functions that the library
has.</para>
<para>However, these libraries can be very large (for example, libc.a
-from can often be around 2.5MB), so you may not want a seperate copy of
+from can often be around 2.5MB), so you may not want a separate copy of
each library attached to the
program. Just imagine if you had a simple command like ls with an extra 2.5MB
attached to it! Instead of making the library an actual part of the
-program, or Statically Linked, the library is kept a seperate file,
+program, or Statically Linked, the library is kept a separate file,
which is loaded only when the program needs it. This is what we call Dynamically
Linked, as the library is loaded and unloaded dynamically, as the program needs
it.</para>
@@ -50,7 +50,7 @@ them, hence the <userinput>--enable-static-link</userinput>,
through Chapter 5. Once in Chapter 6, the first thing we do is build the
main set of system libraries, glibc. Once this is made we start rebuilding
all the programs we just did in Chapter 5, but this time dynamically linked,
-so that we can take advantage of the space saving opportunites.</para>
+so that we can take advantage of the space saving opportunities.</para>
<para>And there you have it, that's why you need to use those weird
<userinput>-static</userinput> flags. If you try building everything
diff --git a/chapter06/kbd-exp.xml b/chapter06/kbd-exp.xml
index 249307299..f6ca100e2 100644
--- a/chapter06/kbd-exp.xml
+++ b/chapter06/kbd-exp.xml
@@ -3,7 +3,7 @@
<para><userinput>patch -Np1 -i ../kbd-&kbd-patch-version;.patch</userinput>:
This patch fixes two problems. The first one is the <userinput>loadkeys -d</userinput>
-behaviour which is broken in current kbd versions. It is nessecary to fix this,
+behaviour which is broken in current kbd versions. It is necessary to fix this,
because the boot scripts rely on a proper <userinput>loadkeys -d</userinput>.
The second part of the patch changes a Makefile so some utilities (setlogcons,
setvesablank and getunimap) that are not installed by default, are installed as