gronod/lfs
1
0
Fork 0
mirror of https://git.linuxfromscratch.org/lfs.git synced 2025-03-06 06:14:47 +00:00
Code Issues Packages Projects Releases Wiki Activity

Grammar fixes.

Browse Source 
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@362 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
This commit is contained in:
Simon Perreault 2001-03-25 08:17:59 +00:00
parent 08463b5b7b
commit 55ffe68cad
3 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
chapter03/introduction.xml
View File

@ -2,9 +2,9 @@
<title>Introduction</title>
<para>
In this chapter the partition that is going to host the LFS system is
In this chapter, the partition that is going to host the LFS system is
going to be prepared. A new partition will be created, a file
system will be created on it and the directory structure will be
system will be created on it, and the directory structure will be
created. When this is done, we can move on to the next chapter and start
building a new Linux system from scratch.
</para>

2
chapter03/mounting.xml
View File

@ -4,7 +4,7 @@
<para>
Now that we have created a file system, it is ready for use. All we have
to do to be able to access it (as in reading data from and writing data to
it) is mounting it. If it is mounted under /mnt/lfs, this partition can
it) is mount it. If it is mounted under /mnt/lfs, this partition can
be accessed by going to the /mnt/lfs directory and then doing whatever
needed to do. This book will assume that the partition was mounted
under /mnt/lfs. It doesn't matter which directory is chosen, the

6
chapter05/bash-exp.xml
View File

@ -44,11 +44,11 @@ possible) as the original Bourne shell.
<para>
The <userinput>&amp;&amp;</userinput>'s at the end of every line cause
the next command only to be executed when the previous command exists
the next command to be executed only if the previous command exists
with a return value of 0 indicating success. In case all of these
commands are copy&amp;pasted
on the shell is is important to be ensured that if
./configure fails, make isn't being executed and likewise if make fails
on the shell, is is important to be ensured that if
./configure fails, make isn't being executed and, likewise, if make fails,
that make install isn't being executed, and so forth.
</para>