Some more You-Fixes

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

14 files changed, 36 insertions, 36 deletions

diff --git a/appendixa/gettext-desc.xml b/appendixa/gettext-desc.xml
index bc8102d97..a83b3f202 100644
--- a/appendixa/gettext-desc.xml
+++ b/appendixa/gettext-desc.xml
@@ -16,7 +16,7 @@ msgfmt, msgmerge, msgunfmt and xgettext programs.
 The gettext package is used for internationalization (also known as
 i18n) and for localization (also known as l10n). Programs can be
 compiled with Native Language Support (NLS) which enable them to output
-messages in your native language rather than in the default English
+messages in the users native language rather than in the default English
 language.
 </para>
 
diff --git a/appendixa/glibc-desc.xml b/appendixa/glibc-desc.xml
index b7d3a7ed3..553c683e7 100644
--- a/appendixa/glibc-desc.xml
+++ b/appendixa/glibc-desc.xml
@@ -12,7 +12,7 @@ The Glibc package contains the GNU C Library.
 <para>
 The C Library is a collection of commonly used functions in programs.
 This way a programmer doens't need to create his own functions for every
-single task. The most common things like writing a string to your screen
+single task. The most common things like writing a string to the screen
 are already present and at the disposal of the programmer.
 </para>
 
@@ -23,10 +23,9 @@ library, the code from the C library will be copied into the executable
 file. When a program uses a dynamic library, that executable will not
 contain the code from the C library, but  instead a routine that loads
 the functions from the library at the time the program is run. This
-means a significant decrease in the file size of a program. If you don't
-understand this concept, you better read the documentation that comes
-with the C Library as it is too complicated to explain here in one or
-two lines.
+means a significant decrease in the file size of a program. The 
+documentation that comes with the C Library describes this a little deeper,
+as it is too complicated to explain here in one or two lines.
 </para>
 
 </sect2>
diff --git a/appendixa/gzip-desc.xml b/appendixa/gzip-desc.xml
index 98398fd63..79f52cf52 100644
--- a/appendixa/gzip-desc.xml
+++ b/appendixa/gzip-desc.xml
@@ -21,8 +21,8 @@ gunzip decompresses files that are compressed with gzip.
 <sect3><title>gzexe</title>
 
 <para>
-gzexe allows you to compress executables in place and have them 
-automatically uncompress and execute when you run them (at a penalty in 
+gzexe allows to compress executables in place and have them 
+automatically uncompress and execute when they are run (at a penalty in 
 performance).
 </para>
 
diff --git a/appendixa/introduction.xml b/appendixa/introduction.xml
index a8d2d5087..609a8a17b 100644
--- a/appendixa/introduction.xml
+++ b/appendixa/introduction.xml
@@ -27,15 +27,16 @@ chapter 5 (Intel system) or chapter 11 (PPC systems).
 <para>
 Most information about these packages (especially the descriptions of
 it) come from the man pages from those packages. I'm not going to print
-the entire man page, just the core elements to make you understand what
-a program does. If you want to know full details on a program, I suggest
-you start by reading the complete man page in addition to this appendix.
+the entire man page, just the core elements to make it possible to understand
+ what
+a program does. To get knowledge of all details on a program, I suggest
+to start by reading the complete man page in addition to this appendix.
 </para>
 
 <para>
-You will also find that certain packages are documented more in depth
-than others. The reason is that I just happen to know more about certain
-packages than I know about others. If you have anything to add on the
+Certain packages are documented more in depth
+than others, because I just happen to know more about certain
+packages than I know about others. If anything should be added on the
 following descriptions, please don't hesitate to email me. This list is
 going to contain an in depth description of every package installed, but
 I can't do this on my own. I have had help from various people but more
@@ -44,7 +45,7 @@ help is needed.
 
 <para>
 Please note that currently only what a package does is described and not
-why you need to install it. That will be added later.
+why it needs to be installed. That will be added later.
 </para>
 
 </sect1>
diff --git a/appendixa/kernel-desc.xml b/appendixa/kernel-desc.xml
index 48b240640..da3c8d6ec 100644
--- a/appendixa/kernel-desc.xml
+++ b/appendixa/kernel-desc.xml
@@ -10,7 +10,7 @@ The Linux kernel package contains the Linux kernel.
 
 <para>
 The Linux kernel is at the core of every Linux system. It's what makes
-Linux tick. When you turn on your computer and boot a Linux system, the
+Linux tick. When a computer is turned on and boots a Linux system, the
 very first piece of Linux software that gets loaded is the kernel. The
 kernel initializes the system's hardware components such as serial
 ports, parallel ports, sound cards, network cards, IDE controllers, SCSI
diff --git a/appendixa/less-desc.xml b/appendixa/less-desc.xml
index 260e97b28..5ad7702dc 100644
--- a/appendixa/less-desc.xml
+++ b/appendixa/less-desc.xml
@@ -17,7 +17,7 @@ pager called <quote>more</quote>. Less has the ability to scroll
 backwards
 through files as well and it doesn't need to read the entire file when
 it
-starts, which makes it faster when you are reading large files.
+starts, which makes it faster when reading large files.
 </para>
 
 </sect2>
diff --git a/appendixa/libtool-desc.xml b/appendixa/libtool-desc.xml
index 9a9b80589..7618e78fc 100644
--- a/appendixa/libtool-desc.xml
+++ b/appendixa/libtool-desc.xml
@@ -20,7 +20,7 @@ Libtool provides generalized library-building support services.
 <sect3><title>libtoolize</title>
 
 <para>
-libtoolize provides a standard way to add libtool support to your 
+libtoolize provides a standard way to add libtool support to a
 package.
 </para>
 
diff --git a/appendixa/makedev-desc.xml b/appendixa/makedev-desc.xml
index f2c52bc13..68fe6eb2c 100644
--- a/appendixa/makedev-desc.xml
+++ b/appendixa/makedev-desc.xml
@@ -9,7 +9,7 @@ The MAKEDEV package contains the MAKEDEV script.
 <sect2><title>Description</title>
 
 <para>
-MAKEDEV is a script that can aid you in creating the necesarry static
+MAKEDEV is a script that can help in creating the necesarry static
 device files that usually reside in the /dev directory.
 </para>
 
diff --git a/appendixa/ncurses-desc.xml b/appendixa/ncurses-desc.xml
index b1746faf5..a8e2c3b9a 100644
--- a/appendixa/ncurses-desc.xml
+++ b/appendixa/ncurses-desc.xml
@@ -15,7 +15,7 @@ programs.
 
 <para>
 The libraries that make up the Ncurses library are used to display text
-(often in a fancy way) on your screen. An example where ncurses is used
+(often in a fancy way) on the screen. An example where ncurses is used
 is in the kernel's <quote>make menuconfig</quote> process. The libraries
 contain routines to create panels, menu's, form and general text display
 routines.
@@ -29,7 +29,7 @@ routines.
 Tic is the terminfo entry-description compiler. The program translates a
 terminfo file from source format into the binary format for use with the
 ncurses library routines. Terminfo files contain information about the
-capabilities of your terminal.
+capabilities of a terminal.
 </para>
 
 </sect3>
@@ -51,7 +51,7 @@ file (term) in a variety of formats (the opposite of what tic does).
 <sect3><title>clear</title>
 
 <para>
-The clear program clears your screen if this is possible.  It looks in
+The clear program clears the screen if this is possible.  It looks in
 the environment for the terminal type and then in the terminfo database
 to
 figure out how to clear the screen.
diff --git a/appendixa/patch-desc.xml b/appendixa/patch-desc.xml
index 410df67d2..c59f6b836 100644
--- a/appendixa/patch-desc.xml
+++ b/appendixa/patch-desc.xml
@@ -14,12 +14,12 @@ The patch program modifies a file according to a patch file. A patch
 file usually is a list created by the diff program that contains
 instructions on how an original file needs to be modified. Patch is used
 a lot for source code patches since it saves time and space. Imagine
-you have a package that is 1MB in size. The next version of that package
-only has changes in two files of the first version. You can ship an
-entirely new package of 1MB or provide a patch file of 1KB which will
+a package that is 1MB in size. The next version of that package
+only has changes in two files of the first version. It can be shipped as an
+entirely new package of 1MB or just as a patch file of 1KB which will
 update the first version to make it identical to the second version. So
-if you have downloaded the first version already, a patch file can
-save you a second large download.
+if the first version was downloaded already, a patch file avoids
+a second large download.
 </para>
 
 </sect2>
diff --git a/appendixa/shellutils-desc.xml b/appendixa/shellutils-desc.xml
index 7a7b19c76..746196636 100644
--- a/appendixa/shellutils-desc.xml
+++ b/appendixa/shellutils-desc.xml
@@ -285,7 +285,7 @@ who shows who is logged on.
 <sect3><title>whoami</title>
 
 <para>
-whoami prints your effective userid.
+whoami prints the users effective userid.
 </para>
 
 </sect3>
diff --git a/appendixa/sysvinit-desc.xml b/appendixa/sysvinit-desc.xml
index 4f8603ab2..2cd08806f 100644
--- a/appendixa/sysvinit-desc.xml
+++ b/appendixa/sysvinit-desc.xml
@@ -43,8 +43,8 @@ file /var/log/btmp, which contains all the bad login attempts.
 <sect3><title>mesg</title>
 
 <para>
-Mesg controls the access to your terminal by others. It's typically 
-used to allow or disallow other users to write to your terminal.
+Mesg controls the access to the users terminal by others. It's typically 
+used to allow or disallow other users to write to his terminal.
 </para>
 
 </sect3>
diff --git a/appendixa/texinfo-desc.xml b/appendixa/texinfo-desc.xml
index 4cd7c9836..dca6f1b6c 100644
--- a/appendixa/texinfo-desc.xml
+++ b/appendixa/texinfo-desc.xml
@@ -14,7 +14,7 @@ and texindex programs
 <sect3><title>info</title>
 
 <para>
-The info program reads Info documents, usually contained in your
+The info program reads Info documents, usually contained in the 
 /usr/doc/info directory. Info documents are like man(ual) pages, but
 they tend to be more in depth than just explaining the options to a
 program.
@@ -25,12 +25,12 @@ program.
 <sect3><title>install-info</title>
 
 <para>
-The install-info program updates the info entries. When you run the info
-program a list with available topics (ie: available info documents) will
+The install-info program updates the info entries. When the info
+program is run a list with available topics (ie: available info documents) will
 be presented. The install-info program is used to maintain this list of
-available topics. If you decice to remove info files manually, you need
+available topics. If info files are removed manually, it is also necessary
 to delete the topic in the index file as well. This program is used for
-that. It also works the other way around when you add info documents.
+that. It also works the other way around when info documents are added.
 </para>
 
 </sect3>
diff --git a/appendixa/utillinux-desc.xml b/appendixa/utillinux-desc.xml
index 5b546c88a..e9299f52a 100644
--- a/appendixa/utillinux-desc.xml
+++ b/appendixa/utillinux-desc.xml
@@ -86,7 +86,7 @@ agetty opens a tty port, prompts for a login name and invokes the
 <title>blockdev</title>
 
 <para>
-blockdev allows you to call block device ioctls from the command line
+blockdev allows to call block device ioctls from the command line
 </para>
 
 </sect3>