[svk-devel] Fwd: [PATCH] Punctuation fixes to svnbook, ch09.xml

[Chia-Liang Kao]

---------- Forwarded message ----------
From: Chung-chieh Shan <ccshan at post.harvard.edu>
Date: 11-Feb-2007 09:35
Subject: [PATCH] Punctuation fixes to svnbook, ch09.xml
To: clkao at clkao.org


Hello,

I couldn't send the following svkbook patch to
svk-dev-request at lists.openfoundry.org because
I couldn't subscribe to svk-dev.

Thanks!

=== ch09.xml
==================================================================
--- ch09.xml    (revision 2961)
+++ ch09.xml    (local)
@@ -36,7 +36,7 @@

     <para>One notable exception to the <command>svk</command>
     subcommand switches rule is the <command>admin</command>
-    subcommand.  This command takes it's own set of subcommands.  It's
+    subcommand.  This command takes its own set of subcommands.  It's
     described below in the <xref linkend="svk.ref.svk.c.admin"/>
     section.</para>

@@ -972,7 +972,7 @@
            checkout</command> with the <option>--relocate</option>.
            Give it both the old and the new path to the working copy.
            Either before or after that you should move the working
-           copy to it's new location so SVK can find it.</para>
+           copy to its new location so SVK can find it.</para>

          <para>Once you are done using a working copy you should tell
            svk this since it keeps track of all checked out working
@@ -2741,7 +2741,7 @@
           <title>Description</title>
          <para>The first form sets up a new mirror of the repository
            at URL in DEPOTPATH.  DEPOTPATH must not yet exist, nor
-           can any of it's parent directories already be a mirror.
+           can any of its parent directories already be a mirror.
            The URL can either be a Subversion repository URL, or
            something that <command>vcp</command> understands if you
            have that installed.  Subversion repository mirrors are
@@ -2754,9 +2754,9 @@
            mirrors if no <replaceable>DEPOTNAME</replaceable> is
            given.</para>

-         <para>The third form detaches the specified path from it's
-           mirrored URL, causing that path and it's children to be
-           treated as regular DEPOTPATHs from now one.  The contents
+         <para>The third form detaches the specified path from its
+           mirrored URL, causing that path and its children to be
+           treated as regular DEPOTPATHs from now on.  The contents
            of DEPOTPATH remain unchanged, so any revisions retrieved
            into the mirror prior to the detaching remain
            available.</para>
@@ -2859,12 +2859,12 @@
            the new location of the mirrored repository.</para>

          <para>For the sake of this example let's assume that the
-           book repository we mirrored, switched from using the
+           book repository we mirrored switched from using the
            <literal>svn</literal>protocol to <literal>http</literal>
            instead, and that the hostname changed from svn to
            svkbook, and that the svkbook virtual host has the repos
-           at it's root. To change our depot to refer to the mirrored
-           repository by it's new URL we would run:</para>
+           at its root. To change our depot to refer to the mirrored
+           repository by its new URL we would run:</para>

           <screen>
 $ svk mirror --relocate //mirror/svkbook http://svkbook.clkao.org/
@@ -3996,7 +3996,7 @@
            copy who's depotpath is a copy of something. Directly in
            the depot to the source from which TARGET was copied.
            Essentially this pushes the changes since the last smerge
-           on the specified branch to it's parent.</para>
+           on the specified branch to its parent.</para>

          <para>The fourth form will merge changes directly in the
            depot to the closest copy anchor in the depot specified by
@@ -4061,7 +4061,7 @@

          <para>Let's say you have worked on a project locally in your
            svk depot until now, and you've decided it's time to
-           publish your project and it's history to a remote
+           publish your project and its history to a remote
            Subversion repository. Furthermore let's assume you have
            already mirrored the repository in question and there are
            empty trunk tags and branches folders in the mirror.

--
Edit this signature at http://www.digitas.harvard.edu/cgi-bin/ken/sig
I think that it is much more likely that the reports of flying saucers
are the result of the known irrational characteristics of terrestrial
intelligence rather than the unknown rational efforts of extraterrestrial
intelligence. -Richard Feynman

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFFznLYzjAc4f+uuBURAmWSAKCgDQpgzUgi+NcHB2xdPeHI4E/ZJgCg7nzT
+9Pdh3jhz9QTtXfCfUG3r/U=
=fqKS
-----END PGP SIGNATURE-----