Index: doc/book/book/appb.xml
===================================================================
--- doc/book/book/appb.xml	(revision 11879)
+++ doc/book/book/appb.xml	(working copy)
@@ -234,8 +234,8 @@
 
       <sect3 id="svn-ap-b-sect-1.2.8">
         <title>I just built the distribution binary, and when I try to
-          check out Subversion, I get an error about an "Unrecognized
-          URL scheme."</title>
+          check out Subversion, I get an error about an <quote>Unrecognized
+          URL scheme.</quote></title>
         
         <para>Subversion uses a plugin system to allow access to
           repositories.  Currently there are three of these plugins:
@@ -264,9 +264,10 @@
 
 
       <sect3 id="svn-ap-b-sect-1.2.9">
-        <title>Why does the 'svn revert' command require an explicit
-          target? Why is it not recursive by default? This behavior
-          differs from almost all the other subcommands.</title>
+        <title>Why does the <command>svn revert</command> command
+          require an explicit target? Why is it not recursive by
+          default? This behavior differs from almost all the other
+          subcommands.</title>
 
         <para>The short answer: it's for your own good.</para>
 
@@ -306,8 +307,9 @@
 
 
       <sect3 id="svn-ap-b-sect-1.2.11">
-        <title>I'm getting "Function not implemented" errors on RedHat
-          9, and nothing works. How do I fix this?</title>
+        <title>I'm getting <quote>Function not implemented</quote>
+          errors on RedHat 9, and nothing works. How do I fix
+          this?</title>
 
         <para>This is not really a problem with Subversion, but it often
           affects Subversion users.</para>
@@ -371,8 +373,8 @@
 
 
       <sect3 id="svn-ap-b-sect-1.2.13">
-        <title>I'm getting occasional "Access Denied" errors on
-          Windows.  They seem to happen at random.</title>
+        <title>I'm getting occasional <quote>Access Denied</quote>
+          errors on Windows.  They seem to happen at random.</title>
 
         <para>These appear to be due to the various Windows services
           that monitor the filesystem for changes (anti-virus
@@ -406,9 +408,9 @@
 
 
       <sect3 id="svn-ap-b-sect-1.2.15">
-        <title>I can see my repository in a web browser, but 'svn
-          checkout' gives me an error about "301 Moved
-          Permanently".</title> 
+        <title>I can see my repository in a web browser, but
+          <command>svn checkout</command> gives me an error about
+          <literal>301 Moved Permanently</literal>.</title>
 
         <para>It means your httpd.conf is misconfigured.  Usually this
           error happens when you've defined the Subversion virtual
Index: doc/book/book/ch03.xml
===================================================================
--- doc/book/book/ch03.xml	(revision 11879)
+++ doc/book/book/ch03.xml	(working copy)
@@ -2100,7 +2100,7 @@
         <filename>some/project</filename> in the repository:</para>
 
       <screen>
-$ svn ls file:///usr/local/svn/newrepos/some/project
+$ svn list file:///usr/local/svn/newrepos/some/project
 bar.c
 foo.c
 subdir/
Index: doc/book/book/ch06.xml
===================================================================
--- doc/book/book/ch06.xml	(revision 11879)
+++ doc/book/book/ch06.xml	(working copy)
@@ -252,7 +252,7 @@
 
 # password was not cached, so a second commit still prompts us
 
-$ svn rm newfile
+$ svn delete newfile
 $ svn commit -F new_msg.txt
 Authentication realm: &lt;svn://host.example.com:3690&gt; example realm
 Username:  joe
Index: doc/book/book/ch07.xml
===================================================================
--- doc/book/book/ch07.xml	(revision 11879)
+++ doc/book/book/ch07.xml	(working copy)
@@ -2028,7 +2028,7 @@
         libcomplex&mdash;we run <command>svn add</command> on those to
         get them under version control.  The missing files are files
         that were in 1.0 but not in 1.1, and on those paths we run
-        <command>svn remove</command>.  Finally, once our
+        <command>svn delete</command>.  Finally, once our
         <filename>current</filename> working copy contains only the
         libcomplex 1.1 code, we commit the changes we made to get it
         looking that way.</para>