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

[cmpilato]

Author: cmpilato
Date: Tue Mar 14 11:18:54 2006
New Revision: 2066

Modified:
   trunk/src/en/book/ch07.xml

Log:
* src/en/book/ch07.xml
  (Peg and Operative Revisions): Re-work the opening words of this
    section, plus fix a little typo elsewhere in the section.


Modified: trunk/src/en/book/ch07.xml
==============================================================================
--- trunk/src/en/book/ch07.xml	(original)
+++ trunk/src/en/book/ch07.xml	Tue Mar 14 11:18:54 2006
@@ -2346,18 +2346,19 @@
   <sect1 id="svn.advanced.pegrevs">
     <title>Peg and Operative Revisions</title>
 
-    <para>The ability to copy, move, and rename files and directories;
-      to be able to create an object, then delete it and then add a
-      new one at the same path—those are operations which we
-      perform on files and directories on our computers all the time,
-      and operations we tend to take for granted.  And Subversion
-      would like you to think they are granted.  Subversion's file
-      management support is quite liberating, affording almost as much
+    <para>We make use of the ability to copy, move, rename, and
+      completely replace files and directories on our computers all
+      that time.  And your version control system shouldn't get in the
+      way of your doing these things with your version controlled
+      files and directories, either.  Subversion's file management
+      support is quite liberating, affording almost as much
       flexibility for versioned files that you'd expect when
       manipulating your unversioned ones.  But that flexibility means
       that across the lifetime of your repository, a given versioned
       resource might have many paths, and a given path might represent
-      several entirely different versioned resources.</para>
+      several entirely different versioned resources.  And this
+      introduces a certain level of complexity to your interactions
+      with those paths and resources.</para>
 
     <para>Subversion is pretty smart about noticing when an object's
       version history includes such <quote>changes of address</quote>.
@@ -2542,7 +2543,7 @@
 svn: Unable to find repository location for 'concept/IDEA' in revision 1
 </screen>
 
-    <para>And when executed, has the expected results.  Peg revisions
+    <para>And when executed, it has the expected results.  Peg revisions
       generally default to a value of <literal>BASE</literal> (the
       revision currently present in the working copy) when applied to
       working copy paths, and of <literal>HEAD</literal> when applied