[svnbook] r3799 committed - Minor tweaks.

svnbook at googlecode.com svnbook at googlecode.com
Thu Oct 14 19:57:23 CDT 2010


Revision: 3799
Author: cmpilato at gmail.com
Date: Thu Oct 14 17:56:49 2010
Log: Minor tweaks.
http://code.google.com/p/svnbook/source/detail?r=3799

Modified:
  /trunk/src/en/book/ch01-fundamental-concepts.xml

=======================================
--- /trunk/src/en/book/ch01-fundamental-concepts.xml	Thu Oct 14 14:58:06  
2010
+++ /trunk/src/en/book/ch01-fundamental-concepts.xml	Thu Oct 14 17:56:49  
2010
@@ -382,13 +382,13 @@
      <title>Version Control the Subversion Way</title>

      <para>We've mentioned already that Subversion is a modern,
-      network-aware version control system.  As we described in the
-      high-level version control overview of
-      <xref linkend="svn.basic.version-control-basics"/>, a repository
-      serves as the core storage mechanism for Subversion's versioned
-      data, and its via working copies that users and their software
-      programs interact with that data.  In this section, we'll begin
-      to introduce the specific ways in which Subversion implements
+      network-aware version control system.  As we described in
+      <xref linkend="svn.basic.version-control-basics"/> (our
+      high-level version control overview), a repository serves as the
+      core storage mechanism for Subversion's versioned data, and its
+      via working copies that users and their software programs
+      interact with that data.  In this section, we'll begin to
+      introduce the specific ways in which Subversion implements
        version control.</para>

      <!-- ===============================================================  
-->
@@ -418,21 +418,21 @@
          <secondary>defined</secondary>
        </indexterm>

-      <para>A Subversion client commits (that is, communicates changes
-        to) any number of files and directories as a single atomic
-        transaction.  By atomic transaction, we mean simply this:
-        either all of the changes are accepted into the repository, or
-        none of them is.  Subversion tries to retain this atomicity in
-        the face of program crashes, system crashes, network problems,
-        and other users' actions.</para>
+      <para>A Subversion client commits (that is, communicates the
+        changes made to) any number of files and directories as a
+        single atomic transaction.  By atomic transaction, we mean
+        simply this: either all of the changes are accepted into the
+        repository, or none of them is.  Subversion tries to retain
+        this atomicity in the face of program crashes, system crashes,
+        network problems, and other users' actions.</para>

        <para>Each time the repository accepts a commit, this creates a
          new state of the filesystem tree, called a
          <firstterm>revision</firstterm>.  Each revision is assigned a
-        unique natural number, one greater than the number of the
-        previous revision.  The initial revision of a freshly created
-        repository is numbered 0 and consists of nothing but an
-        empty root directory.</para>
+        unique natural number, one greater than the number assigned to
+        the previous revision.  The initial revision of a freshly
+        created repository is numbered 0 and consists of nothing but
+        an empty root directory.</para>

        <para><xref linkend="svn.basic.in-action.revs.dia-1"/>
          illustrates a nice way to visualize the repository.  Imagine
@@ -629,7 +629,7 @@
          the <filename>/tags/bigsandwich</filename> directory in the
          root of the repository.  Note that this URL syntax works only
          when your current working directory is a working
-        copy—the commandline client knows the repository's root
+        copy—the command-line client knows the repository's root
          URL by looking at the working copy's metadata.</para>

      </sect2>




More information about the svnbook-dev mailing list