Round 2 of several minor wording changes in chapter 6 (matt).

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

1 files changed, 17 insertions, 17 deletions

diff --git a/chapter06/vim.xml b/chapter06/vim.xml
index 073d0a5a4..2accc832d 100644
--- a/chapter06/vim.xml
+++ b/chapter06/vim.xml
@@ -69,11 +69,10 @@ Core that use UTF-8 as a default character set.</para>
 
 <screen><userinput>make</userinput></screen>
 
-<para>To test the results, issue:
-<userinput>make test</userinput>. However, this test suite outputs a
-lot of chaotic characters to the screen, which can cause issues with
-the settings of the current terminal. Therefore, running the test
-suite here is optional.</para>
+<para>To test the results, issue: <userinput>make test</userinput>. However,
+this test suite outputs a lot of binary data to the screen, which can cause
+issues with the settings of the current terminal. This can be resolved by
+redirecting the output to a log file.</para>
 
 <para>Install the package:</para>
 
@@ -99,13 +98,13 @@ url="&blfs-root;view/svn/postlfs/editors.html#postlfs-editors-vim"/>.</para>
 <sect2 id="conf-vim" role="configuration"><title>Configuring Vim</title>
 <indexterm zone="conf-vim"><primary sortas="e-/etc/vim">/etc/vim</primary></indexterm>
 
-<para>By default, <command>vim</command> runs in vi-incompatible mode.
-This may be new to users who have used other editors in the past. The
-<quote>nocompatible</quote> setting is included below to highlight the
-fact that a new behavior is being used. It also reminds those who
-would change to <quote>compatible</quote> mode that it should appear
-first.  This is necessary because it changes other settings, and
-overrides must come after this setting.  Create a default <command>vim</command>
+<para>By default, <command>vim</command> runs in vi-incompatible mode. This may
+be new to users who have used other editors in the past. The
+<quote>nocompatible</quote> setting is included below to highlight the fact that
+a new behavior is being used. It also reminds those who would change to
+<quote>compatible</quote> mode that it should be the first setting in the
+configuration file. This is necessary because it changes other settings, and
+overrides must come after this setting. Create a default <command>vim</command>
 configuration file by running the following:</para>
 
 <screen><userinput>cat &gt; /etc/vimrc &lt;&lt; "EOF"
@@ -233,7 +232,7 @@ commands can be started and <command>vim</command> cannot be suspended</para>
 <varlistentry id="shtags.pl">
 <term><command>shtags.pl</command></term>
 <listitem>
-<para>Generates a tag file for Perl scripts</para>
+<para>Generates a tags file for Perl scripts</para>
 <indexterm zone="ch-system-vim shtags.pl"><primary sortas="b-shtags.pl">shtags.pl</primary></indexterm>
 </listitem>
 </varlistentry>
@@ -241,7 +240,7 @@ commands can be started and <command>vim</command> cannot be suspended</para>
 <varlistentry id="tcltags">
 <term><command>tcltags</command></term>
 <listitem>
-<para>Generates a tag file for TCL code</para>
+<para>Generates a tags file for TCL code</para>
 <indexterm zone="ch-system-vim tcltags"><primary sortas="b-tcltags">tcltags</primary></indexterm>
 </listitem>
 </varlistentry>
@@ -305,9 +304,10 @@ commands can be started and <command>vim</command> cannot be suspended</para>
 <varlistentry id="vimspell.sh">
 <term><command>vimspell.sh</command></term>
 <listitem>
-<para>Spells a file and generates the syntax statements necessary 
-to highlight in <command>vim</command>. This script requires the old Unix <command>spell</command>
-command, which is provided neither in LFS nor in BLFS</para>
+<para>Spell checks a file and generates the syntax statements necessary to
+highlight in <command>vim</command>. This script requires the old Unix
+<command>spell</command> command, which is provided neither in LFS nor in
+BLFS</para>
 <indexterm zone="ch-system-vim vimspell.sh"><primary sortas="b-vimspell.sh">vimspell.sh</primary></indexterm>
 </listitem>
 </varlistentry>