Index: appa.xml
===================================================================
--- appa.xml	(revision 1501)
+++ appa.xml	(working copy)
@@ -316,7 +316,7 @@
   </sect1>
 
   <!-- ================================================================= -->
-  <!-- ======================== SECTION 5 ============================= -->
+  <!-- ======================== SECTION 5 ============================== -->
   <!-- ================================================================= -->
   <sect1 id="svn.forcvs.branches-and-tags">
     <title>Branches and Tags</title>
Index: appb.xml
===================================================================
--- appb.xml	(revision 1501)
+++ appb.xml	(working copy)
@@ -37,9 +37,9 @@
       
       <para>The tragedy, though, is that the RFC 2518 WebDAV
         specification does not provide any sort of model for version
-        control, despite the "V" in DAV.  Basic WebDAV clients and
-        servers assume only one version of each file or directory
-        exists, and can be repeatedly overwritten.</para>
+        control, despite the <quote>V</quote> in DAV.  Basic WebDAV
+        clients and servers assume only one version of each file or
+        directory exists, and can be repeatedly overwritten.</para>
 
       <para>Here are the concepts and terms introduced in basic
         WebDAV:</para>
@@ -293,7 +293,7 @@
       can ever learn to get everything it needs from a general DeltaV
       server.  On the other hand, mod_dav_svn *could* be further
       developed to implement all of DeltaV, but it's hard to find
-      motivation to do so &mdash; here are almost no DeltaV clients to
+      motivation to do so&mdash;here are almost no DeltaV clients to
       interoperate with.</para>
 
   </sect1>
@@ -640,10 +640,10 @@
 
       <para>Apple's OS X operating system has an integrated
         filesystem-level WebDAV client. From the Finder, select the
-        "Connect to Server" item from the Go menu.  Enter a WebDAV
-        URL, and it appears as a disk on the desktop, just like any
-        other mounted volume.<footnote><para>From the Darwin terminal,
-        one can also run <literal>mount -t webdav URL
+        <quote>Connect to Server</quote> item from the Go menu.  Enter
+        a WebDAV URL, and it appears as a disk on the desktop, just
+        like any other mounted volume.<footnote><para>From the Darwin
+        terminal, one can also run <literal>mount -t webdav URL
         /mountpoint</literal></para></footnote>.</para>
 
       <para>Note that if your mod_dav_svn is older than version 1.2,
@@ -713,10 +713,9 @@
 
       <para>Cadaver is a bare-bones Unix commandline program for
         browsing and changing WebDAV shares.  Like the Subversion
-        client, it uses the neon HTTP library &mdash; not
-        surprisingly, both neon and cadaver are written by the same
-        author.  Cadaver is free sofware (GPL license) and is
-        available at <ulink
+        client, it uses the neon HTTP library&mdash;not surprisingly,
+        both neon and cadaver are written by the same author.  Cadaver
+        is free sofware (GPL license) and is available at <ulink
         url="http://www.webdav.org/cadaver/"/>.</para>
 
       <para>Using cadaver is similar to using a commandline FTP
@@ -727,20 +726,20 @@
       
       <screen>
 $ cadaver http://host/repos
-dav:/repos/> ls
+dav:/repos/&gt; ls
 Listing collection `/repos/': succeeded.
-Coll: > foobar                                 0  May 10 16:19
-      > playwright.el                       2864  May  4 16:18
-      > proofbypoem.txt                     1461  May  5 15:09
-      > westcoast.jpg                      66737  May  5 15:09
+Coll: &gt; foobar                                 0  May 10 16:19
+      &gt; playwright.el                       2864  May  4 16:18
+      &gt; proofbypoem.txt                     1461  May  5 15:09
+      &gt; westcoast.jpg                      66737  May  5 15:09
 
-dav:/repos/> put README
+dav:/repos/&gt; put README
 Uploading README to `/repos/README':
-Progress: [=============================>] 100.0% of 357 bytes succeeded.
+Progress: [=============================&gt;] 100.0% of 357 bytes succeeded.
 
-dav:/repos/> get proofbypoem.txt
+dav:/repos/&gt; get proofbypoem.txt
 Downloading `/repos/proofbypoem.txt' to proofbypoem.txt:
-Progress: [=============================>] 100.0% of 1461 bytes succeeded.
+Progress: [=============================&gt;] 100.0% of 1461 bytes succeeded.
 </screen>
 
       <para>DAV Explorer is another standalone WebDAV client, written
@@ -771,7 +770,7 @@
 
       <para>It appears that only the Windows versions of these
         programs support WebDAV.  On Mac OS X, the
-        <quote>File->Open</quote> dialog box doesn't allow one to type
+        <quote>File-&gt;Open</quote> dialog box doesn't allow one to type
         a path or URL at all.  It's likely that the the WebDAV
         features were deliberately left out of Macintosh versions of
         these programs, since OS X already provides such excellent
Index: ch04.xml
===================================================================
--- ch04.xml	(revision 1501)
+++ ch04.xml	(working copy)
@@ -516,14 +516,14 @@
 --- integer.c	(revision 343)
 +++ integer.c	(revision 344)
 @@ -147,7 +147,7 @@
-     case 6:  sprintf(info->operating_system, "HPFS (OS/2 or NT)"); break;
-     case 7:  sprintf(info->operating_system, "Macintosh"); break;
-     case 8:  sprintf(info->operating_system, "Z-System"); break;
--    case 9:  sprintf(info->operating_system, "CPM"); break;
-+    case 9:  sprintf(info->operating_system, "CP/M"); break;
-     case 10:  sprintf(info->operating_system, "TOPS-20"); break;
-     case 11:  sprintf(info->operating_system, "NTFS (Windows NT)"); break;
-     case 12:  sprintf(info->operating_system, "QDOS"); break;
+     case 6:  sprintf(info-&gt;operating_system, "HPFS (OS/2 or NT)"); break;
+     case 7:  sprintf(info-&gt;operating_system, "Macintosh"); break;
+     case 8:  sprintf(info-&gt;operating_system, "Z-System"); break;
+-    case 9:  sprintf(info-&gt;operating_system, "CPM"); break;
++    case 9:  sprintf(info-&gt;operating_system, "CP/M"); break;
+     case 10:  sprintf(info-&gt;operating_system, "TOPS-20"); break;
+     case 11:  sprintf(info-&gt;operating_system, "NTFS (Windows NT)"); break;
+     case 12:  sprintf(info-&gt;operating_system, "QDOS"); break;
 @@ -164,7 +164,7 @@
      low = (unsigned short) read_byte(gzfile);  /* read LSB */
      high = (unsigned short) read_byte(gzfile); /* read MSB */
@@ -531,19 +531,19 @@
 -    total = low + high; /* add them togethe for correct total */
 +    total = low + high; /* add them together for correct total */
  
-     info->extra_header = (unsigned char *) my_malloc(total);
-     fread(info->extra_header, total, 1, gzfile);
+     info-&gt;extra_header = (unsigned char *) my_malloc(total);
+     fread(info-&gt;extra_header, total, 1, gzfile);
 @@ -241,7 +241,7 @@
       Store the offset with ftell() ! */
  
-   if ((info->data_offset = ftell(gzfile))== -1) {
+   if ((info-&gt;data_offset = ftell(gzfile))== -1) {
 -    printf("error: ftell() retturned -1.\n");
 +    printf("error: ftell() returned -1.\n");
      exit(1);
    }
  
 @@ -249,7 +249,7 @@
-   printf("I believe start of compressed data is %u\n", info->data_offset);
+   printf("I believe start of compressed data is %u\n", info-&gt;data_offset);
    #endif
    
 -  /* Set postion eight bytes from the end of the file. */
Index: ch06.xml
===================================================================
--- ch06.xml	(revision 1501)
+++ ch06.xml	(working copy)
@@ -1951,17 +1951,17 @@
 
         <para>The <command>mod_dav_svn</command> module goes through a
           lot of work to make sure that data you've marked
-          "unreadable" doesn't get accidentally leaked.  This means
-          that it needs to closely monitor all of the paths and
-          file-contents returned by commands like <command>svn
+          <quote>unreadable</quote> doesn't get accidentally leaked.
+          This means that it needs to closely monitor all of the paths
+          and file-contents returned by commands like <command>svn
           checkout</command> or <command>svn update</command>
           commands.  If these commands encounter a path that isn't
           readable according to some authorization policy, then the
           path is typically omitted altogether.  In the case of
-          history or rename tracing &mdash; e.g. running a command
-          like <command>svn cat -r OLD foo.c</command> on a file that
-          was renamed long ago &mdash; the rename tracking will simply
-          halt if one of the object's former names is determined to be
+          history or rename tracing&mdash;e.g. running a command like
+          <command>svn cat -r OLD foo.c</command> on a file that was
+          renamed long ago&mdash;the rename tracking will simply halt
+          if one of the object's former names is determined to be
           read-restricted.</para>
 
         <para>All of this path-checking can sometimes be quite
@@ -2004,11 +2004,11 @@
           </programlisting>
         </example>
 
-        <para>The <literal>SVNPathAuthz</literal> directive is "on" by
-          default.  When set "off", all path-based authorization
-          checking is disabled; <command>mod_dav_svn</command> stops
-          invoking authorization checks on every path it
-          discovers.</para>
+        <para>The <literal>SVNPathAuthz</literal> directive is <quote>on</quote> by
+          default.  When set <quote>off</quote>, all path-based
+          authorization checking is disabled;
+          <command>mod_dav_svn</command> stops invoking authorization
+          checks on every path it discovers.</para>
 
       </sect3>
 
Index: ch07.xml
===================================================================
--- ch07.xml	(revision 1501)
+++ ch07.xml	(working copy)
@@ -1495,9 +1495,9 @@
           we didn't ask for it to be.</para>
 
         <para>Note also that we set the <literal>svn:keywords</literal>
-          property to "Date Author" yet the keyword anchor used the
-          alias <literal>$LastChangedDate$</literal> and still
-          expanded correctly.</para>
+          property to <quote>Date Author</quote> yet the keyword
+          anchor used the alias <literal>$LastChangedDate$</literal>
+          and still expanded correctly.</para>
 
         <screen>
 Here is the latest report from the front lines.
@@ -3177,7 +3177,7 @@
         <command>svn</command> interprets your input.  The repository
         stores all paths, filenames, and log messages in Unicode,
         encoded as UTF-8.  In that sense, the repository is
-        <firstterm>internationalized</firstterm>&mdash; that is, the
+        <firstterm>internationalized</firstterm>&mdash;that is, the
         repository is ready to accept input in any human language.
         This means, however, that the Subversion client is responsible
         for sending only UTF-8 filenames and log messages into the
Index: ch08.xml
===================================================================
--- ch08.xml	(revision 1501)
+++ ch08.xml	(working copy)
@@ -406,7 +406,7 @@
       printf ("Directory '%s' was successfully added as new revision "
               "'%ld'.\n", new_directory, youngest_rev);
     }
-  else if (err->apr_err == SVN_ERR_FS_CONFLICT)
+  else if (err-&gt;apr_err == SVN_ERR_FS_CONFLICT)
     {
       /* Uh-oh.  Our commit failed as the result of a conflict
          (someone else seems to have made changes to the same area