[svnbook] r3899 committed - Follow-up to r3898: Fix a transposed period and closing...

svnbook at googlecode.com svnbook at googlecode.com
Fri Jul 8 12:31:02 CDT 2011


Revision: 3899
Author:   ptburba at gmail.com
Date:     Fri Jul  8 10:27:22 2011
Log:      Follow-up to r3898: Fix a transposed period and closing
parentheses spotted by cmpilato and while I'm at it, fix
similar typos elsewhere.

* src/en/book/appa-quickstart.xml
* src/en/book/ch04-branching-and-merging.xml
* src/en/book/ch06-server-configuration.xml

http://code.google.com/p/svnbook/source/detail?r=3899

Modified:
  /trunk/src/en/book/appa-quickstart.xml
  /trunk/src/en/book/ch04-branching-and-merging.xml
  /trunk/src/en/book/ch06-server-configuration.xml

=======================================
--- /trunk/src/en/book/appa-quickstart.xml	Tue Jul  5 09:25:22 2011
+++ /trunk/src/en/book/appa-quickstart.xml	Fri Jul  8 10:27:22 2011
@@ -133,7 +133,7 @@
          also works at the Windows command-line prompt, assuming you
          make some obvious tweaks.)  We also assume you are using
          Subversion 1.2 or later (run <userinput>svn --version</userinput>
-        to check.)</para>
+        to check).</para>
      </note>

      <para>Subversion stores all versioned data in a central
=======================================
--- /trunk/src/en/book/ch04-branching-and-merging.xml	Fri Jul  8 08:28:10  
2011
+++ /trunk/src/en/book/ch04-branching-and-merging.xml	Fri Jul  8 10:27:22  
2011
@@ -669,7 +669,7 @@
            this command records the changes that have been duplicated
            to your branch so that Subversion is aware of exactly which
            changes exist in each location (see
-          <xref linkend="svn.branchmerge.basicmerging.mergeinfo"/>.)
+          <xref linkend="svn.branchmerge.basicmerging.mergeinfo"/>).
            This is a critical feature that makes branch management
            usable; without it, users would have to manually keep notes
            on which sets of changes have or haven't been merged
@@ -738,7 +738,7 @@
          either doing an <command>svn checkout</command>, dredging up
          an old trunk working copy from somewhere on your disk, or
          using <command>svn switch</command>
-        (see <xref linkend="svn.branchmerge.switchwc"/>.)
+        (see <xref linkend="svn.branchmerge.switchwc"/>).
          Your trunk working copy cannot have any local edits or be at
          mixed-revisions
          (see <xref linkend="svn.basic.in-action.mixedrevs"/>).  While
=======================================
--- /trunk/src/en/book/ch06-server-configuration.xml	Thu Jul  7 13:48:46  
2011
+++ /trunk/src/en/book/ch06-server-configuration.xml	Fri Jul  8 10:27:22  
2011
@@ -1216,7 +1216,7 @@
        <para>You'd think that the story of SSH tunneling would end
          here, but it doesn't.  Subversion allows you to create custom
          tunnel behaviors in your runtime <filename>config</filename>
-        file (see <xref linkend="svn.advanced.confarea"/>.)  For
+        file (see <xref linkend="svn.advanced.confarea"/>).  For
          example, suppose you want to use RSH instead of
          SSH.<footnote><para>We don't actually recommend this, since
          RSH is notably less secure than SSH.</para></footnote>  In
@@ -1356,7 +1356,7 @@
          <para>In this example, <filename>/path/to/svnserve</filename>
            might be a custom wrapper script
            around <command>svnserve</command> which sets the umask (see
-          <xref linkend="svn.serverconfig.multimethod"/>.)  It also
+          <xref linkend="svn.serverconfig.multimethod"/>).  It also
            shows how to anchor <command>svnserve</command> in a virtual
            root directory, just as one often does when
            running <command>svnserve</command> as a daemon process.




More information about the svnbook-dev mailing list