aboutsummaryrefslogtreecommitdiffstats
path: root/chapter06
diff options
context:
space:
mode:
authorMark Hymers <markh@linuxfromscratch.org>2002-02-14 14:58:00 +0000
committerMark Hymers <markh@linuxfromscratch.org>2002-02-14 14:58:00 +0000
commit8f9069b37b44c1417787705f15071edf3d48b612 (patch)
treebeff9e6a009b73e7331455b7a7fededfaaeee1ef /chapter06
parentb1623f661df283264ec30aa60f173bddb4a4b17d (diff)
spelling corrections
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@1572 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
Diffstat (limited to 'chapter06')
-rw-r--r--chapter06/config-shadowpwd.xml2
-rw-r--r--chapter06/glibc-exp.xml4
2 files changed, 3 insertions, 3 deletions
diff --git a/chapter06/config-shadowpwd.xml b/chapter06/config-shadowpwd.xml
index e3b0237c9..6c9c3d876 100644
--- a/chapter06/config-shadowpwd.xml
+++ b/chapter06/config-shadowpwd.xml
@@ -6,7 +6,7 @@ what 'password shadowing' means. All about that can be read in the doc/HOWTO
file within the unpacked shadow password suite's source tree. There's one
thing you should keep in mind, if you decide to use shadow support, that
programs that need to verify passwords (examples are xdm, ftp daemons,
-pop3 daemons, etc) need to be 'shadow-compliant', eg. they need to
+pop3 daemons, etc) need to be 'shadow-compliant', e.g. they need to
be able to work with shadow'ed passwords.</para>
<para>To enable shadow'ed passwords, run the following command:</para>
diff --git a/chapter06/glibc-exp.xml b/chapter06/glibc-exp.xml
index bf66d0a5f..db8657eff 100644
--- a/chapter06/glibc-exp.xml
+++ b/chapter06/glibc-exp.xml
@@ -21,7 +21,7 @@ configuration. This is done because Glibc can't autodetect perl since
it hasn't been installed yet.</para>
<para><userinput>sed 's/root/0' login/Makefile.backup &gt;
-login/Makefile:</userinput> This sed command replaces all occurences of
+login/Makefile:</userinput> This sed command replaces all occurrences of
<filename>root</filename> in <filename>login/Makefile.backup</filename>
with 0. This is because we don't have glibc on the LFS system yet, so
usernames can't be resolved to their user id's. Therefore, we replace
@@ -38,7 +38,7 @@ We do this because we are only building for our own system. Cross-compiling
is used, for instance, to build a package for an Apple Power PC on an
Intel system. The reason Glibc thinks we're cross-compiling is that it
can't compile a test program to determine this, so it automatically defaults
-to a cross-compiler. Compiling the test program failes because Glibc hasn't
+to a cross-compiler. Compiling the test program fails because Glibc hasn't
been installed yet.</para>
<para><userinput>exec /bin/bash:</userinput>This command will