[svnbook commit] r3241 - trunk/src/en/book

fitz noreply at red-bean.com
Mon Aug 4 23:50:25 CDT 2008


Author: fitz
Date: Mon Aug  4 23:50:25 2008
New Revision: 3241

Log:
Second round of copyedits for chapter 9, part 2 of 3.

I didn't reflow any of the paragraphs that I edited.  Still.

* src/en/book/ch09-reference.xml: Copyedit.


Modified:
   trunk/src/en/book/ch09-reference.xml

Modified: trunk/src/en/book/ch09-reference.xml
==============================================================================
--- trunk/src/en/book/ch09-reference.xml	(original)
+++ trunk/src/en/book/ch09-reference.xml	Mon Aug  4 23:50:25 2008
@@ -3004,10 +3004,10 @@
 …
 </screen>
 
-          <para>There are just a handful of action codes used by
-            <command>svn log</command>, and they are similar to the
-            ones used by the <command>svn update</command>
-            command:</para>
+          <para><command>svn log</command> uses just a handful of action codes,
+            and they are similar to the
+            ones the <command>svn update</command>
+            command uses:</para>
 
           <variablelist>
             <varlistentry>
@@ -3032,7 +3032,7 @@
 
           <para>In addition to the action codes which precede the
             changed paths, <command>svn log</command> with the <option>--verbose</option> option will
-            note that a path was added or replaced as the result of a copy
+            note whether a path was added or replaced as the result of a copy
             operation.  It does so by printing <literal>(from
             <replaceable>COPY-FROM-PATH</replaceable>:<replaceable>COPY-FROM-REV</replaceable>)</literal>
             after such paths.</para>
@@ -3115,14 +3115,14 @@
           <tip>
             <para>If you run <command>svn log</command> on a specific
               path and provide a specific revision and get no output
-              at all as in the following:</para>
+              at all, as in the following:</para>
 
             <screen>
 $ svn log -r 20 http://svn.red-bean.com/untouched.txt
 ------------------------------------------------------------------------
 </screen>
 
-            <para>That just means that the path was not modified in
+            <para>that just means the path was not modified in
               that revision.  If you log from the top of the
               repository or know the file that changed in that
               revision, you can specify it explicitly:</para>
@@ -3163,7 +3163,7 @@
           <title>Description</title>
 
           <para>In the first form, the source URLs are specified at
-            revisions <literal>N</literal> and <literal>M</literal>.
+            revisions <replaceable>N</replaceable> and <replaceable>M</replaceable>.
             These are the two sources to be compared.  The revisions
             default to <literal>HEAD</literal> if omitted.</para>
 
@@ -3203,10 +3203,10 @@
             this case, the differences will be applied to that
             file.</para>
 
-          <para>Subversion will only internally track metadata about
-            the merge operation if the two sources are ancestrally
+          <para>Subversion will internally track metadata about
+            the merge operation only if the two sources are ancestrally
             related—if the first source is an ancestor of the
-            second or vice-versa.  This is guaranteed to be the case
+            second or vice versa.  This is guaranteed to be the case
             when using the third form.  Unlike <command>svn
             diff</command>, the merge command takes the ancestry of a
             file into consideration when performing a merge operation.
@@ -3253,7 +3253,7 @@
           <title>Examples</title>
 
           <para>Merge a branch back into the trunk (assuming that
-            you have an up-to-date working copy of the trunk).</para>
+            you have an up-to-date working copy of the trunk):</para>
 
           <screen>
 $ svn merge --reintegrate \
@@ -3343,11 +3343,11 @@
         </refsect1>
 
         <refsect1>
-          <title>Example</title>
+          <title>Examples</title>
 
           <para>Find out which changesets your trunk directory has
             already received as well as what changesets it's still
-            eligible to receive.</para>
+            eligible to receive:</para>
 
           <screen>
 $ svn mergeinfo branches/test
@@ -3382,7 +3382,7 @@
           <title>Description</title>
 
           <para>Create a directory with a name given by the final
-            component of the <replaceable>PATH</replaceable> or URL.
+            component of the <replaceable>PATH</replaceable> or <replaceable>URL</replaceable>.
             A directory specified by a working copy
             <replaceable>PATH</replaceable> is scheduled for addition
             in the working copy.  A directory specified by a URL is
@@ -3433,7 +3433,7 @@
 A         newdir
 </screen>
 
-          <para>Create one in the repository (instant commit, so a
+          <para>Create one in the repository (this is an instant commit, so a
             log message is required):</para>
 
           <screen>
@@ -3481,7 +3481,8 @@
             <para>Subversion does not support moving between working
               copies and URLs.  In addition, you can only move files
               within a single repository—Subversion does not
-              support cross-repository moving.</para>
+              support cross-repository moving.  Subversion supports
+              the following types of moves within a single repository:</para>
           </note>
 
           <variablelist>
@@ -3506,7 +3507,7 @@
 
         <refsect1>
           <title>Alternate names</title>
-          <para>mv, rename, ren</para>
+          <para><command>mv</command>, <command>rename</command>, <command>ren</command></para>
         </refsect1>
 
         <refsect1>
@@ -3560,7 +3561,7 @@
 D         qux.c
 </screen>
 
-          <para>Move a file in the repository (an immediate commit,
+          <para>Move a file in the repository (this is an immediate commit,
             so it requires a commit message):</para>
 
           <screen>
@@ -3595,7 +3596,7 @@
 
           <para>This removes properties from files, directories, or
             revisions.  The first form removes versioned properties in
-            your working copy, while the second removes unversioned
+            your working copy, and the second removes unversioned
             remote properties on a repository revision
             (<replaceable>TARGET</replaceable> determines only which
             repository to access).</para>
@@ -3603,7 +3604,7 @@
 
         <refsect1>
           <title>Alternate names</title>
-          <para>pdel, pd</para>
+          <para><command>pdel</command>, <command>pd</command></para>
         </refsect1>
 
         <refsect1>
@@ -3662,7 +3663,7 @@
           <refname>svn propedit</refname>
           <refpurpose>Edit the property of one or more items under
             version control. See <xref
-            linkend="svn.ref.svn.c.propset"/>.</refpurpose>
+            linkend="svn.ref.svn.c.propset"/> later in this chapter.</refpurpose>
         </refnamediv>
         <refsect1>
           <title>Synopsis</title>
@@ -3674,7 +3675,7 @@
 
           <para>Edit one or more properties using your favorite
             editor.  The first form edits versioned properties in
-            your working copy, while the second edits unversioned
+            your working copy, and the second edits unversioned
             remote properties on a repository revision
             (<replaceable>TARGET</replaceable> determines only which
             repository to access).</para>
@@ -3682,7 +3683,7 @@
 
         <refsect1>
           <title>Alternate names</title>
-          <para>pedit, pe</para>
+          <para><command>pedit</command>, <command>pe</command></para>
         </refsect1>
 
         <refsect1>
@@ -3712,7 +3713,7 @@
         </refsect1>
 
         <refsect1>
-          <title>Example</title>
+          <title>Examples</title>
 
           <para><command>svn propedit</command> makes it easy to
             modify properties that have multiple values:</para>
@@ -3752,15 +3753,15 @@
           <para>Print the value of a property on files,
             directories, or revisions.  The first form prints the
             versioned property of an item or items in your working
-            copy, while the second prints unversioned remote
-            property on a repository revision.  See <xref
+            copy, and the second prints unversioned remote
+            properties on a repository revision.  See <xref
             linkend="svn.advanced.props"/> for more information on
             properties.</para>
         </refsect1>
 
         <refsect1>
           <title>Alternate names</title>
-          <para>pget, pg</para>
+          <para><command>pget</command>, <command>pg</command></para>
         </refsect1>
 
         <refsect1>
@@ -3808,7 +3809,7 @@
 </screen>
 
           <para>Lastly, you can get <command>svn propget</command>
-            output in xml format with the <option>--xml</option>
+            output in XML format with the <option>--xml</option>
             option:</para>
 
           <screen>
@@ -3849,7 +3850,7 @@
 
           <para>List all properties on files, directories, or
             revisions.  The first form lists versioned properties in
-            your working copy, while the second lists unversioned remote
+            your working copy, and the second lists unversioned remote
             properties on a repository revision
             (<replaceable>TARGET</replaceable> determines only which
             repository to access).</para>
@@ -3857,7 +3858,7 @@
 
         <refsect1>
           <title>Alternate names</title>
-          <para>plist, pl</para>
+          <para><command>plist</command>, <command>pl</command></para>
         </refsect1>
 
         <refsect1>
@@ -3888,7 +3889,7 @@
         <refsect1>
           <title>Examples</title>
 
-          <para>You can use proplist to see the properties on an
+          <para>You can use <command>proplist</command> to see the properties on an
             item in your working copy:</para>
 
           <screen>
@@ -3899,8 +3900,8 @@
   owner
 </screen>
 
-          <para>But with the <option>--verbose</option> flag, svn
-            proplist is extremely handy as it also shows you the
+          <para>But with the <option>--verbose</option> flag, <command>svn
+            proplist</command> is extremely handy as it also shows you the
             values for the properties:</para>
 
           <screen>
@@ -3940,7 +3941,7 @@
 
         <refnamediv>
           <refname>svn propset</refname>
-          <refpurpose>Set PROPNAME to PROPVAL on files, directories, or revisions.</refpurpose>
+          <refpurpose>Set <replaceable>PROPNAME</replaceable> to <replaceable>PROPVAL</replaceable> on files, directories, or revisions.</refpurpose>
         </refnamediv>
         <refsect1>
           <title>Synopsis</title>
@@ -3963,14 +3964,14 @@
           <tip>
             <para>Subversion has a number of <quote>special</quote>
               properties that affect its behavior.  See <xref
-              linkend="svn.ref.properties"/> for more on these
+              linkend="svn.ref.properties"/> later in this chapter for more on these
               properties.</para>
           </tip>
 
         </refsect1>
         <refsect1>
           <title>Alternate names</title>
-          <para>pset, ps</para>
+          <para><replaceable>pset</replaceable>, <replaceable>ps</replaceable></para>
         </refsect1>
 
         <refsect1>
@@ -4045,7 +4046,7 @@
 property 'svn:log' set on repository revision '25'
 </screen>
 
-          <para>Lastly, you can tell propset to take its input from
+          <para>Lastly, you can tell <command>propset</command> to take its input from
             a file.  You could even use this to set the contents of a
             property to something binary:</para>
 
@@ -4089,7 +4090,7 @@
 
           <para>Resolve <quote>conflicted</quote> state on working
             copy files or directories.  This routine does not
-            semantically resolve conflict markers, however, it
+            semantically resolve conflict markers; however, it
             replaces <replaceable>PATH</replaceable> with the version
             specified by the <option>--accept</option> argument and
             then removes conflict-related artifact files.  This allows
@@ -4103,7 +4104,7 @@
           <variablelist>
 
             <varlistentry>
-              <term>base</term>
+              <term><literal>base</literal></term>
               <listitem>
                 <para>Choose the file that was the
                   <literal>BASE</literal> revision before you updated
@@ -4114,7 +4115,7 @@
             </varlistentry>
 
             <varlistentry>
-              <term>working</term>
+              <term><literal>working</literal></term>
               <listitem>
                 <para>Assuming that you've manually handled the
                 conflict resolution, choose the version of the file as
@@ -4123,7 +4124,7 @@
             </varlistentry>
 
             <varlistentry>
-              <term>mine-full</term>
+              <term><literal>mine-full</literal></term>
               <listitem>
                 <para>Resolve all conflicted files with copies of the
                 files as they stood immediately before you
@@ -4132,7 +4133,7 @@
             </varlistentry>
 
             <varlistentry>
-              <term>theirs-full</term>
+              <term><literal>theirs-full</literal></term>
               <listitem>
                 <para>Resolve all conflicted files with copies of the
                 files that were fetched from the server when you
@@ -4176,12 +4177,12 @@
         </refsect1>
         
         <refsect1>
-          <title>Example</title>
+          <title>Examples</title>
           
           <para>Here's an example where, after a postponed conflict
             resolution during update, <command>svn resolve</command>
             replaces the all conflicts in
-            file <literal>foo.c</literal> with your edits:</para>
+            file <filename>foo.c</filename> with your edits:</para>
 
           <screen>
 $ svn up
@@ -4221,7 +4222,7 @@
 
           <para>This command has been deprecated in favor of
             running <userinput>svn resolve --accept working <replaceable>PATH</replaceable></userinput>.
-            See <xref linkend="svn.ref.svn.c.resolve"/> for
+            See <xref linkend="svn.ref.svn.c.resolve"/> in the preceding section for
             details.</para>
 
           <para>Remove <quote>conflicted</quote> state on working copy
@@ -4261,7 +4262,7 @@
         </refsect1>
         
         <refsect1>
-          <title>Example</title>
+          <title>Examples</title>
           
           <para>If you get a conflict on an update, your working
             copy will sprout three new files:</para>
@@ -4315,10 +4316,10 @@
 
           <para>Reverts any local changes to a file or directory and
             resolves any conflicted states.  <command>svn
-            revert</command> will not only revert the contents of an
+            revert</command> will revert not only the contents of an
             item in your working copy, but also any property
             changes.  Finally, you can use it to undo any scheduling
-            operations that you may have done (e.g., files scheduled
+            operations that you may have performed (e.g., files scheduled
             for addition or deletion can be
             <quote>unscheduled</quote>).</para>
         </refsect1>
@@ -4440,7 +4441,7 @@
             about different aspects of each working copy item.</para>
           
           <para>The first column indicates that an item
-            was added, deleted, or otherwise changed.</para>
+            was added, deleted, or otherwise changed:</para>
 
           <variablelist>
             
@@ -4516,7 +4517,7 @@
             <varlistentry>
               <term><literal>'!'</literal></term>
               <listitem>
-                <para>Item is missing (e.g. you moved or deleted it
+                <para>Item is missing (e.g., you moved or deleted it
                   without using <command>svn</command>).  This also
                   indicates that a directory is incomplete (a checkout
                   or update was interrupted).</para>
@@ -4527,7 +4528,7 @@
               <term><literal>'~'</literal></term>
               <listitem>
                 <para>Item is versioned as one kind of object (file,
-                  directory, link), but has been replaced by different
+                  directory, link), but has been replaced by a different
                   kind of object.</para>
               </listitem>
             </varlistentry>
@@ -4535,7 +4536,7 @@
           </variablelist>
 
           <para>The second column tells the status of a file's or
-            directory's properties.</para>
+            directory's properties:</para>
 
           <variablelist>
             
@@ -4566,8 +4567,8 @@
           </variablelist>
 
           <para>The third column is populated only if the
-            working copy directory is locked. (See
-            <xref linkend="svn.tour.cleanup"/>.)</para>
+            working copy directory is locked (See
+            <xref linkend="svn.tour.cleanup"/>.):</para>
 
           <variablelist>
             
@@ -4588,7 +4589,7 @@
           </variablelist>
 
           <para>The fourth column is populated only if the item is
-            scheduled for addition-with-history.</para>
+            scheduled for addition-with-history:</para>
           
           <variablelist>
             
@@ -4610,7 +4611,7 @@
 
           <para>The fifth column is populated only if the item is
             switched relative to its parent (see <xref
-            linkend="svn.branchmerge.switchwc"/>).</para>
+            linkend="svn.branchmerge.switchwc"/>):</para>
 
           <variablelist>
             
@@ -4630,7 +4631,7 @@
 
           </variablelist>
 
-          <para>The sixth column is populated with lock information.</para>
+          <para>The sixth column is populated with lock information:</para>
           
           <variablelist>
             
@@ -4689,14 +4690,14 @@
 
           <para>The out-of-date information appears in the seventh
             column (only if you pass the
-            <option>--show-updates</option> option).</para>
+            <option>--show-updates</option> option):</para>
 
           <variablelist>
             
             <varlistentry>
               <term><literal>' '</literal></term>
               <listitem>
-                <para>The item in your working copy is up to date.</para>
+                <para>The item in your working copy is up-to-date.</para>
               </listitem>
             </varlistentry>
             
@@ -4713,7 +4714,7 @@
           <para>The remaining fields are variable width and
             delimited by spaces.  The working revision is the next
             field if the <option>--show-updates</option> or
-            <option>--verbose</option> options are passed.</para>
+            <option>--verbose</option> option is passed.</para>
           
           <para>If the <option>--verbose</option> option is passed,
             the last committed revision and last committed author
@@ -4726,7 +4727,7 @@
 
         <refsect1>
           <title>Alternate names</title>
-          <para>stat, st</para>
+          <para><command>stat</command>, <command>st</command></para>
         </refsect1>
 
         <refsect1>
@@ -4787,7 +4788,7 @@
           <note>
             <para><option>--show-updates</option>
               <emphasis>only</emphasis> places an asterisk next to
-              items that are out of date (that is, items that will be
+              items that are out of date (i.e., items that will be
               updated from the repository if you later use <command>svn
               update</command>).  <option>--show-updates</option> does
               <emphasis>not</emphasis> cause the status listing to
@@ -4796,7 +4797,7 @@
               passing the <option>--verbose</option> option).</para>
           </note>
 
-          <para>And finally, the most information you can get out of
+          <para>The most information you can get out of
             the status subcommand is as follows:</para>
 
           <screen>
@@ -4809,7 +4810,7 @@
 </screen>
 
           <para>Lastly, you can get <command>svn status</command>
-            output in xml format with the <option>--xml</option>
+            output in XML format with the <option>--xml</option>
             option:</para>
 
           <screen>
@@ -4900,7 +4901,7 @@
           <para>As with most subcommands, you can limit the scope of
             the switch operation to a particular tree depth using the
             <option>--depth</option> option.  Alternatively, you can
-            use the --set-depth option to set a new
+            use the <option>--set-depth</option> option to set a new
             <quote>sticky</quote> working copy depth on the switch
             target.  Currently, the depth of a working copy directory
             can only be increased (telescoped more deeply); you cannot
@@ -4917,8 +4918,8 @@
         </refsect1>
 
         <refsect1>
-          <title>Alternate name</title>
-          <para>sw</para>
+          <title>Alternate names</title>
+          <para><command>sw</command></para>
         </refsect1>
 
         <refsect1>
@@ -4964,7 +4965,7 @@
 Updated to revision 31.
 </screen>
 
-          <para>And to switch back, just provide the URL to the
+          <para >To switch back, just provide the URL to the
             location in the repository from which you originally
             checked out your working copy:</para>
 
@@ -4978,7 +4979,7 @@
 </screen>
 
           <tip>
-            <para>You can just switch part of your working copy to a
+            <para>You can switch just part of your working copy to a
               branch if you don't want to switch your entire working
               copy.</para>
           </tip>
@@ -5032,12 +5033,12 @@
             <itemizedlist>
               <listitem><para>If the working copy needs to reflect a
                   new directory <emphasis>within</emphasis> the
-                  repository, then use just <command>svn
+                  repository, use just <command>svn
                   switch</command>.</para></listitem>
 
               <listitem><para>If the working copy still reflects the
                   same repository directory, but the location of the
-                  repository itself has changed, then use <command>svn
+                  repository itself has changed, use <command>svn
                   switch</command> with the <option>--relocate</option> option.</para></listitem>
             </itemizedlist>
           </warning>
@@ -5066,7 +5067,7 @@
           <title>Description</title>
 
           <para>Unlock each <replaceable>TARGET</replaceable>.  If any
-            <replaceable>TARGET</replaceable> is either locked by
+            <replaceable>TARGET</replaceable> is locked by
             another user or no valid lock token exists in the working
             copy, print a warning and continue unlocking the rest of
             the <replaceable>TARGET</replaceable>s.  Use
@@ -5082,7 +5083,7 @@
 
         <refsect1>
           <title>Changes</title>
-          <para>Working Copy, Repository</para>
+          <para>Working copy, repository</para>
         </refsect1>
 
         <refsect1>
@@ -5180,7 +5181,7 @@
             <varlistentry>
               <term><literal>B</literal></term>
               <listitem>
-                <para>Broken Lock (third column only)</para>
+                <para>Broken lock (third column only)</para>
               </listitem>
             </varlistentry>
 
@@ -5222,14 +5223,14 @@
           </variablelist>
 
           <para>A character in the first column signifies an update to
-            the actual file, while updates to the file's properties
+            the actual file, whereas updates to the file's properties
             are shown in the second column.  Lock information is
             printed in the third column.</para>
 
           <para>As with most subcommands, you can limit the scope of
             the update operation to a particular tree depth using the
             <option>--depth</option> option.  Alternatively, you can
-            use the --set-depth option to set a new
+            use the <option>--set-depth</option> option to set a new
             <quote>sticky</quote> working copy depth on the update
             target.  Currently, the depth of a working copy directory
             can only be increased (telescoped more deeply); you cannot
@@ -5237,7 +5238,7 @@
         </refsect1>
 
         <refsect1>
-          <title>Alternate name</title>
+          <title>Alternate names</title>
           <para><command>up</command></para>
         </refsect1>
 
@@ -5269,7 +5270,7 @@
         </refsect1>
 
         <refsect1>
-          <title>Example</title>
+          <title>Examples</title>
 
           <para>Pick up repository changes that have happened since
             your last update:</para>
@@ -5315,11 +5316,11 @@
   <!-- ================================================================= -->
   <!-- ================================================================= -->
   <sect1 id="svn.ref.svnadmin">
-    <title><command>svnadmin</command></title>
+    <title>svnadmin</title>
     
     <para><command>svnadmin</command> is the administrative tool for
       monitoring and repairing your Subversion repository.  For
-      detailed information, see the maintenance section for <xref
+      detailed information on repository administration, see the maintenance section for <xref
       linkend="svn.reposadmin.maint.tk.svnadmin"/>.</para>
 
     <para>Since <command>svnadmin</command> works via direct repository access
@@ -5336,7 +5337,7 @@
           <term><option>--bdb-log-keep</option></term>
           <listitem>
             <para>(Berkeley DB-specific.) Disable automatic log removal
-              of database log files.  Having these log files around
+              of database logfiles.  Having these logfiles around
               can be convenient if you need to restore from a
               catastrophic repository failure.</para>
           </listitem>
@@ -5453,8 +5454,8 @@
         <varlistentry>
           <term><option>--use-post-commit-hook</option></term>
           <listitem>
-            <para>When loading a dump file, run the repository's
-              post-commit hook after finalizing each newly loaded
+            <para>When loading a dump file, runs the repository's
+              <literal>post-commit</literal> hook after finalizing each newly loaded
               revision.</para>
           </listitem>
         </varlistentry>
@@ -5462,8 +5463,8 @@
         <varlistentry>
           <term><option>--use-post-revprop-change-hook</option></term>
           <listitem>
-            <para>When changing a revision property, run the
-              repository's post-revprop-change hook after changing the
+            <para>When changing a revision property, runs the
+              repository's <literal>post-revprop-change</literal> hook after changing the
               revision property.</para>
           </listitem>
         </varlistentry>
@@ -5471,20 +5472,20 @@
         <varlistentry>
           <term><option>--use-pre-commit-hook</option></term>
           <listitem>
-            <para>When loading a dump file, run the repository's
-              pre-commit hook before finalizing each newly loaded
-              revision.  If the hook fails, abort the commit and
-              terminate the load process.</para>
+            <para>When loading a dump file, runs the repository's
+              <literal>pre-commit</literal> hook before finalizing each newly loaded
+              revision.  If the hook fails, aborts the commit and
+              terminates the load process.</para>
           </listitem>
         </varlistentry>
 
         <varlistentry>
           <term><option>--use-pre-revprop-change-hook</option></term>
           <listitem>
-            <para>When changing a revision property, run the
-              repository's pre-revprop-change hook before changing the
-              revision property.  If the hook fails, abort the
-              modification and terminate.</para>
+            <para>When changing a revision property, runs the
+              repository's <literal>pre-revprop-change</literal> hook before changing the
+              revision property.  If the hook fails, aborts the
+              modification and terminates.</para>
           </listitem>
         </varlistentry>
 
@@ -5493,7 +5494,11 @@
 
     <!-- =============================================================== -->
     <sect2 id="svn.ref.svnadmin.c">
-      <title><command>svnadmin</command> Subcommands</title>
+      <title>svnadmin Subcommands</title>
+
+      <para>Here are the various subcommands
+        for <command>svnadmin</command>.</para>
+
 
       <refentry id="svn.ref.svnadmin.c.crashtest">
 
@@ -5514,7 +5519,7 @@
         <refsect1>
           <title>Description</title>
 
-            <para>Open the repository at REPOS_PATH, then abort, thus
+            <para>Open the repository at <replaceable>REPOS_PATH</replaceable>, then abort, thus
               simulating a process that crashes while holding an open
               repository handle.  This is used for testing automatic
               repository recovery (a new feature in Berkeley DB 4.4).
@@ -5572,7 +5577,7 @@
               </footnote>
               As of Subversion 1.2, <command>svnadmin</command>
               creates new repositories with the
-              <literal>fsfs</literal> filesystem backend by
+              <literal>FSFS</literal> filesystem backend by
               default.</para>
 
             <para>While <command>svnadmin create</command> will create
@@ -5603,7 +5608,7 @@
         <refsect1>
           <title>Examples</title>
 
-          <para>Creating a new repository is just this easy:</para>
+          <para>Creating a new repository is this easy:</para>
 
           <screen>
 $ svnadmin create /var/svn/repos
@@ -5672,7 +5677,7 @@
 
         <refnamediv>
           <refname>svnadmin dump</refname>
-          <refpurpose>Dump the contents of filesystem to stdout.</refpurpose>
+          <refpurpose>Dump the contents of the filesystem to stdout.</refpurpose>
         </refnamediv>
         <refsect1>
           <title>Synopsis</title>
@@ -5681,9 +5686,9 @@
         <refsect1>
           <title>Description</title>
 
-          <para>Dump the contents of filesystem to stdout in a
+          <para>Dump the contents of the filesystem to <literal>stdout</literal> in a
             <quote>dumpfile</quote> portable format, sending feedback
-            to stderr.  Dump revisions
+            to <literal>stderr</literal>.  Dump revisions
             <replaceable>LOWER</replaceable> rev through
             <replaceable>UPPER</replaceable> rev.  If no revisions are
             given, dump all revision trees.  If only
@@ -5694,16 +5699,16 @@
           <para>By default, the Subversion dumpfile stream contains a
             single revision (the first revision in the requested
             revision range) in which every file and directory in the
-            repository in that revision is presented as if that whole
+            repository in that revision is presented as though that whole
             tree was added at once, followed by other revisions (the
             remainder of the revisions in the requested range), which
             contain only the files and directories that were modified
             in those revisions.  For a modified file, the complete
-            fulltext representation of its contents, as well as all of
+            full-text representation of its contents, as well as all of
             its properties, are presented in the dumpfile; for a
             directory, all of its properties are presented.</para>
 
-          <para>There are two useful options that modify the dumpfile
+          <para>Two useful options modify the dumpfile
             generator's behavior.  The first is the
             <option>--incremental</option> option, which simply causes
             that first revision in the dumpfile stream to contain only
@@ -5717,7 +5722,7 @@
 
           <para>The second useful option is <option>--deltas</option>.
             This option causes <command>svnadmin dump</command> to,
-            instead of emitting fulltext representations of file
+            instead of emitting full-text representations of file
             contents and property lists, emit only deltas of those
             items against their previous versions.  This reduces (in
             some cases, drastically) the size of the dumpfile that
@@ -5784,13 +5789,13 @@
           <title>Description</title>
 
           <para>This subcommand is useful when you're trapped on a
-            desert island with neither a net connection nor a copy of
+            desert island with neither a Net connection nor a copy of
             this book.</para>
         </refsect1>
 
         <refsect1>
           <title>Alternate names</title>
-          <para>?, h</para>
+          <para><command>?</command>, <command>h</command></para>
         </refsect1>
 
       </refentry>
@@ -5819,7 +5824,7 @@
             of your repository, including all hooks, configuration
             files, and, of course, database files.  If you pass the
             <option>--clean-logs</option> option,
-            <command>svnadmin</command> will perform a hotcopy of your
+            <command>svnadmin</command> will perform a hot copy of your
             repository, and then remove unused Berkeley DB logs from
             the original repository.  You can run this command at any
             time and make a safe copy of the repository, regardless of
@@ -5857,7 +5862,7 @@
 
         <refnamediv>
           <refname>svnadmin list-dblogs</refname>
-          <refpurpose>Ask Berkeley DB which log files exist for a
+          <refpurpose>Ask Berkeley DB which logfiles exist for a
             given Subversion repository (applies only to repositories
             using the <literal>bdb</literal> backend).</refpurpose>
         </refnamediv>
@@ -5871,7 +5876,7 @@
           <para>Berkeley DB creates logs of all changes to the
             repository, which allow it to recover in the face of
             catastrophe.  Unless you enable
-            <literal>DB_LOG_AUTOREMOVE</literal>, the log files
+            <literal>DB_LOG_AUTOREMOVE</literal>, the logfiles
             accumulate, although most are no longer used and can be
             deleted to reclaim disk space.  See <xref
             linkend="svn.reposadmin.maint.diskspace"/> for more
@@ -5890,7 +5895,7 @@
 
         <refnamediv>
           <refname>svnadmin list-unused-dblogs</refname>
-          <refpurpose>Ask Berkeley DB which log files can be safely
+          <refpurpose>Ask Berkeley DB which logfiles can be safely
           deleted (applies only to repositories using the
           <literal>bdb</literal> backend).</refpurpose>
         </refnamediv>
@@ -5904,7 +5909,7 @@
           <para>Berkeley DB creates logs of all changes to the
             repository, which allow it to recover in the face of
             catastrophe.  Unless you enable
-            <literal>DB_LOG_AUTOREMOVE</literal>, the log files
+            <literal>DB_LOG_AUTOREMOVE</literal>, the logfiles
             accumulate, although most are no longer used and can be
             deleted to reclaim disk space.  See <xref
             linkend="svn.reposadmin.maint.diskspace"/> for more
@@ -5912,9 +5917,9 @@
         </refsect1>
 
         <refsect1>
-          <title>Example</title>
+          <title>Examples</title>
           
-          <para>Remove all unused log files from the repository:</para>
+          <para>Remove all unused logfiles from the repository:</para>
 
         <screen>
 $ svnadmin list-unused-dblogs /var/svn/repos
@@ -5940,7 +5945,7 @@
         <refnamediv>
           <refname>svnadmin load</refname> <refpurpose>Read a
             <quote>dumpfile</quote>-formatted stream from
-            stdin.</refpurpose>
+            <literal>stdin</literal>.</refpurpose>
         </refnamediv>
         <refsect1>
           <title>Synopsis</title>
@@ -5950,8 +5955,8 @@
           <title>Description</title>
 
           <para>Read a <quote>dumpfile</quote>-formatted stream from
-            stdin, committing new revisions into the repository's
-            filesystem.  Send progress feedback to stdout.</para>
+            <literal>stdin</literal>, committing new revisions into the repository's
+            filesystem.  Send progress feedback to <literal>stdout</literal>.</para>
         </refsect1>
 
         <refsect1>
@@ -6031,7 +6036,7 @@
         </refsect1>
 
         <refsect1>
-          <title>Example</title>
+          <title>Examples</title>
 
 
           <para>This lists the one locked file in the repository at
@@ -6076,10 +6081,10 @@
         </refsect1>
 
         <refsect1>
-          <title>Example</title>
+          <title>Examples</title>
 
           <para>List all outstanding transactions in a
-            repository.</para>
+            repository:</para>
 
           <screen>
 $ svnadmin lstxns /var/svn/repos/ 
@@ -6105,7 +6110,7 @@
           consistent state (applies only to repositories using the
           <literal>bdb</literal> backend).  In addition, if
           <filename>repos/conf/passwd</filename> does not exist, it
-          will create a default password file .</refpurpose>
+          will create a default passwordfile .</refpurpose>
 
         </refnamediv>
         <refsect1>
@@ -6140,7 +6145,7 @@
 
           <para>Recovering the database requires an exclusive lock on
             the repository. (This is a <quote>database lock</quote>;
-            see <xref linkend="svn.advanced.locking.meanings"/>.)
+            see the sidebar <xref linkend="svn.advanced.locking.meanings"/>.)
             If another process is accessing the repository,
             then <command>svnadmin recover</command> will error:</para>
           <screen>
@@ -6192,7 +6197,7 @@
         <refsect1>
           <title>Description</title>
 
-          <para>Remove lock from each <replaceable>LOCKED_PATH</replaceable>.</para>
+          <para>Remove one or more locks from each <replaceable>LOCKED_PATH</replaceable>.</para>
         </refsect1>
 
         <refsect1>
@@ -6202,7 +6207,7 @@
         </refsect1>
 
         <refsect1>
-          <title>Example</title>
+          <title>Examples</title>
 
           <para>This deletes the locks on
             <filename>tree.jpg</filename> and




More information about the svnbook-dev mailing list