Index: doc/book/book/appa.xml
===================================================================
--- doc/book/book/appa.xml	(revision 6931)
+++ doc/book/book/appa.xml	(working copy)
@@ -5,7 +5,7 @@
 
     <para>This appendix is a guide for CVS users new to Subversion.
       It's essentially a list of differences between the two systems
-      as <quote>viewed from 10,000 feet.</quote> For each section, we
+      as <quote>viewed from 10,000 feet</quote>. For each section, we
       provide backreferences to relevant chapters when
       possible.</para>
 
@@ -33,14 +33,14 @@
       filesystem.  Each commit results in an entirely new filesystem
       tree; in essence, the repository is an array of trees.  Each of
       these trees is labeled with a single revision number.  When
-      someone talks about <quote>revision 54,</quote> they're talking
+      someone talks about <quote>revision 54</quote>, they're talking
       about a particular tree (and indirectly, the way the filesystem
       looked after the 54th commit).</para>
 
     <para>Technically, it's not valid to talk about <quote>revision 5
       of <filename>foo.c</filename></quote>.  Instead, one would say
       <quote><filename>foo.c</filename> as it appears in revision
-      5.</quote> Also, be careful when making assumptions about the
+      5</quote>. Also, be careful when making assumptions about the
       evolution of a file.  In CVS, revisions 5 and 6 of
       <filename>foo.c</filename> are always different.  In Subversion,
       it's most likely that <filename>foo.c</filename> did
@@ -151,7 +151,7 @@
       <varlistentry>
         <term><command>svn status</command></term>
         <listitem>
-          <para>Shows you any local changes you've made. (see <xref
+          <para>Shows you any local changes you've made (see <xref
               linkend="svn-ch-3-sect-4.3.1"/>)</para>
         </listitem>
       </varlistentry>
@@ -159,7 +159,7 @@
       <varlistentry>
         <term><command>svn diff</command></term>
         <listitem>
-          <para>Shows you the details of your changes. (see <xref
+          <para>Shows you the details of your changes (see <xref
               linkend="svn-ch-3-sect-4.3.2"/>)</para>
         </listitem>
       </varlistentry>
@@ -167,7 +167,7 @@
       <varlistentry>
         <term><command>svn revert</command></term>
         <listitem>
-          <para>Removes your local changes. (see <xref
+          <para>Removes your local changes (see <xref
               linkend="svn-ch-3-sect-4.3.3"/>)</para>
         </listitem>
       </varlistentry>
@@ -398,7 +398,7 @@
       performs any kind of keyword or line-ending translation unless
       you explicitly ask it do so (see <xref
       linkend="svn-ch-6-sect-2.3.4"/> and <xref
-      linkend="svn-ch-6-sect-2.3.5"/> for more details.)  By default,
+      linkend="svn-ch-6-sect-2.3.5"/> for more details).  By default,
       Subversion treats all file data as literal byte strings, and
       files are always stored in the repository in an untranslated
       state.</para>
Index: doc/book/book/appc.xml
===================================================================
--- doc/book/book/appc.xml	(revision 6931)
+++ doc/book/book/appc.xml	(working copy)
@@ -79,7 +79,7 @@
         <listitem>
           <para>I just built the distribution binary, and when I try
             to check out Subversion, I get an error about an
-            <quote>Unrecognized URL scheme.</quote></para>
+            <quote>Unrecognized URL scheme</quote>.</para>
         </listitem>
 
         <listitem>
@@ -146,7 +146,7 @@
             action, then one or more lockfiles are left behind, along
             with logfiles describing then unfinished
             actions. (<command>svn status</command> will show an
-            <literal>L</literal> next to locked directories).</para>
+            <literal>L</literal> next to locked directories.)</para>
 
           <para>Any other process that attempts to access the working
             copy will fail when it sees the locks. To awaken your
Index: doc/book/book/appd.xml
===================================================================
--- doc/book/book/appd.xml	(revision 6931)
+++ doc/book/book/appd.xml	(working copy)
@@ -87,7 +87,7 @@
               (e.g. a property called <quote>color</quote>), and
               others are wholly created and controlled by the WebDAV
               server (e.g. a property that contains the last
-              modification time of a file.)  The former kind are
+              modification time of a file).  The former kind are
               called <quote>dead</quote> properties, and the latter
               kind are called <quote>live</quote> properties.</para>
           </listitem>
Index: doc/book/book/appe.xml
===================================================================
--- doc/book/book/appe.xml	(revision 6931)
+++ doc/book/book/appe.xml	(working copy)
@@ -13,7 +13,7 @@
         Subversion client.  Fortunately for those interested in
         developing additional Subversion clients, Subversion is
         implemented as a series of libraries.  These libraries are
-        accessible via C API, as well as other languages (See <xref
+        accessible via C API, as well as other languages (see <xref
         linkend="svn-ch-7-sect-2.3"/>).</para>
 
       <para>This component design means that it's easy (well, at least
Index: doc/book/book/ch03.xml
===================================================================
--- doc/book/book/ch03.xml	(revision 6931)
+++ doc/book/book/ch03.xml	(working copy)
@@ -92,7 +92,7 @@
       </screen>
 
       <para>If at any point in the future you want to refer to that
-        revision (We'll see how and why we might want to do that later
+        revision (we'll see how and why we might want to do that later
         in this chapter), you can refer to it as
         <quote>3</quote>.</para>
 
@@ -148,7 +148,7 @@
           <listitem>
             <para>The revision just <emphasis>before</emphasis> the last
               revision in which an item changed.  (Technically,
-              COMMITTED - 1).</para>
+              COMMITTED - 1.)</para>
           </listitem>
         </varlistentry>
         
@@ -320,8 +320,8 @@
     </screen>
     
     <para>Since Subversion uses a <quote>copy-modify-merge</quote>
-      model instead of <quote>lock-modify-unlock,</quote> (see <xref
-      linkend="svn-ch-2"/>) you're now ready to start making changes
+      model instead of <quote>lock-modify-unlock</quote> (see <xref
+      linkend="svn-ch-2"/>), you're now ready to start making changes
       to the files and directories that you've checked out (known
       collectively as your <firstterm>working
       copy</firstterm>).</para>
@@ -329,7 +329,7 @@
     <para>In other words, your <quote>working copy</quote> is now just
       like any other collection of files and/or directories on your
       system<footnote><para>Well, except for the fact that every
-      directory within your <quote>working copy</quote>also contains a
+      directory within your <quote>working copy</quote> also contains a
       <filename>.svn</filename> subdirectory.  But that's getting a
       little ahead of ourselves.</para></footnote>.  You can edit and
       change them, move them around, you can even delete the entire
@@ -660,7 +660,7 @@
               addition.  When <filename>bar</filename> is added to the
               repository on the next commit, its copy-history is
               recorded (as having originally come from
-              <filename>foo</filename>.)</para>
+              <filename>foo</filename>).</para>
           </listitem>
         </varlistentry>
 
@@ -905,7 +905,7 @@
         </variablelist>
 
         <para>The second column tells the status of a file or
-          directory's properties (See <xref
+          directory's properties (see <xref
           linkend="svn-ch-6-sect-2"></xref> for more information on
           properties).  If an <computeroutput>M</computeroutput>
           appears in the second column, then the properties have been
@@ -1009,7 +1009,7 @@
           useful information&mdash;you'll need to update and get the
           server changes on <filename>README</filename> before you
           commit, or the repository will reject your commit for being
-          out-of-date.  (More on this subject later).</para>
+          out-of-date.  (More on this subject later.)</para>
 
       </sect3>
 
@@ -1237,7 +1237,7 @@
         <listitem>
           <para>Subversion prints a <computeroutput>C</computeroutput> during
             the update, and remembers that the file is
-            <quote>conflicted.</quote></para>
+            <quote>conflicted</quote>.</para>
         </listitem>
 
         <listitem>
@@ -1253,7 +1253,7 @@
           <variablelist>
             
             <varlistentry>
-              <term><filename>filename.*.mine</filename></term>
+              <term><filename>filename.mine</filename></term>
               <listitem>
                 <para> This is your file as it existed in your working
                   copy before you updated your working copy&mdash;that
@@ -1263,7 +1263,7 @@
             </varlistentry>
             
             <varlistentry>
-              <term><filename>filename.*.rOLDREV</filename></term>
+              <term><filename>filename.rOLDREV</filename></term>
               <listitem>
                 <para>This is the file that was the BASE revision
                   before you updated your working copy.  That is, the
@@ -1273,7 +1273,7 @@
             </varlistentry>
 
             <varlistentry>
-              <term><filename>filename.*.rNEWREV</filename></term>
+              <term><filename>filename.rNEWREV</filename></term>
               <listitem>
                 <para>This is the file that your Subversion client
                   just received from the server when you updated your
@@ -1284,12 +1284,10 @@
 
           </variablelist>
           
-          <para>Here <literal>*</literal> represents some random
-            digits that Subversion chooses,
-            <literal>OLDREV</literal> is the revision number of the
-            file in your <filename>.svn</filename> directory, and
-            <literal>NEWREV</literal> is the revision number of the
-            repository HEAD.
+          <para>Here <literal>OLDREV</literal> is the revision number
+            of the file in your <filename>.svn</filename> directory
+            and <literal>NEWREV</literal> is the revision number of
+            the repository HEAD.
           </para>
         </listitem>
         
@@ -1306,11 +1304,10 @@
 C  sandwich.txt
 Updated to revision 2.
 $ ls -1
-sandwich.txt                       
-sandwich.txt.r2        
-sandwich.txt.r1
+sandwich.txt
 sandwich.txt.mine
-$
+sandwich.txt.r1
+sandwich.txt.r2
       </screen>
       <!-- ###TODO What happens if the revnum is gt 99999?-->
       
@@ -1764,7 +1761,7 @@
         <para>At first glance, this seems like an error, but you need
           to remember that while revisions are repository-wide,
           <command>svn log</command> operates on a path in the
-          repository (If you supply no path, Subversion defaults to
+          repository (if you supply no path, Subversion defaults to
           <literal>"."</literal>).  As a result, if you're operating
           in a subdirectory of your working copy and attempt to log a
           revision where nothing beneath your current directory
@@ -2016,9 +2013,9 @@
         information within <filename>.svn</filename>), it tries to do
         so as safely as possible.  Before changing anything, it writes
         its intentions to a logfile, executes the commands in the
-        logfile, then removes the logfile (This is similar in design
+        logfile, then removes the logfile (this is similar in design
         to a journaled filesystem).  If a Subversion operation is
-        interrupted (If you hit Control-C, or if the machine crashes,
+        interrupted (if you hit Control-C, or if the machine crashes,
         for example), the logfiles remain on disk.  By re-executing
         the logfiles, Subversion can complete the previously started
         operation, and your working copy can get itself back into a
Index: doc/book/book/ch05.xml
===================================================================
--- doc/book/book/ch05.xml	(revision 6931)
+++ doc/book/book/ch05.xml	(working copy)
@@ -1830,7 +1830,7 @@
         class="url">http://httpd.apache.org</systemitem>.  For
         example, a general reference for the configuration directives
         is located at <systemitem
-        class="url">http://httpd.apache.org/docs-2.0/mod/directives.html</systemitem>.)</para>
+        class="url">http://httpd.apache.org/docs-2.0/mod/directives.html</systemitem>.</para>
               
       <para>Also, as you make changes to your Apache setup, it is
         likely that somewhere along the way a mistake will be made.
Index: doc/book/book/ch07.xml
===================================================================
--- doc/book/book/ch07.xml	(revision 6931)
+++ doc/book/book/ch07.xml	(working copy)
@@ -116,7 +116,7 @@
       of the diagram (initiated by the user) and flows
       "downward".</para>
 
-    <!-- Fitz's revised graphic here (Heaven help us if he ever makes
+    <!-- Fitz's revised graphic here (heaven help us if he ever makes
          another piece of graphic art ... what *will* we call it?).
          Verify that the layers are accurately represented.  For
          example, It might make more sense to refer to the
Index: doc/book/book/ch08.xml
===================================================================
--- doc/book/book/ch08.xml	(revision 6931)
+++ doc/book/book/ch08.xml	(working copy)
@@ -61,7 +61,7 @@
             you want to use an external diff program, use
             <option>--diff-cmd</option>.  You can pass switches to the
             diff program with the <option>--extensions</option>
-            switch (More on that later in this section).</para>
+            switch (more on that later in this section).</para>
           </listitem>
         </varlistentry>
       
@@ -135,7 +135,7 @@
               you from doing in normal usage, but you can pass the
               force switch to tell Subversion <quote>I know what I'm
               doing as well as the possible repercussions of doing it,
-              so let me at 'em.</quote>. This switch is the
+              so let me at 'em</quote>. This switch is the
               programmatic equivalent of doing your own electrical
               work with the power on&mdash;if you don't know what
               you're doing, you're likely to get a nasty shock.</para>
@@ -948,7 +948,7 @@
           </screen>
 
           <para>Copy an item from the repository to your working
-            copy (Just schedules the copy&mdash;nothing goes into the
+            copy (just schedules the copy&mdash;nothing goes into the
             repository until you commit):</para>
 
           <tip>
@@ -1187,7 +1187,7 @@
         <refsect1>
           <title>Examples</title>
 
-          <para>Compare BASE and your working copy (One of the most
+          <para>Compare BASE and your working copy (one of the most
             popular uses of <command>svn diff</command>):</para>
 
           <screen>
@@ -2912,7 +2912,7 @@
           </variablelist>
 
           <para>The fifth column is populated only if the item is
-            switched relative to its parent (See <xref
+            switched relative to its parent (see <xref
             linkend="svn-ch-4-sect-5"/>).</para>
 
           <variablelist>
@@ -3015,7 +3015,7 @@
 
           <para>If you want to find out what files in your working
             copy are out-of-date, pass the
-            <option>--show-updates</option> switch (This will
+            <option>--show-updates</option> switch (this will
             <emphasis>not</emphasis> make any changes to your
             working copy).  Here you can see that
             <filename>wc/foo.c</filename> has changed in the
@@ -3251,7 +3251,7 @@
 
           <para>You can also update your working copy to an older
             revision (Subversion doesn't have the concept of
-            <quote>sticky</quote> files like CVS does.  See <xref
+            <quote>sticky</quote> files like CVS does; see <xref
             linkend="svn-ap-a"/>):</para>
 
           <screen>
@@ -3609,7 +3609,7 @@
             in which PATH was modified.  Use the COPIES flag to allow
             this operation to cross copy history while searching for
             revisions.  PATH must exist in the HEAD of the
-            repository).</para>
+            repository.</para>
         </refsect1>
 
         <refsect1>
Index: doc/book/book/glossary.xml
===================================================================
--- doc/book/book/glossary.xml	(revision 6931)
+++ doc/book/book/glossary.xml	(working copy)
@@ -9,7 +9,7 @@
         <term>Add</term>
         <listitem>
 
-          <para> A <command>svn</command> command that is used to add a
+          <para> An <command>svn</command> command that is used to add a
             file or directory to a repository.  </para>
 
         </listitem>