[svnbook] r3816 committed - Fix some typos....
svnbook at googlecode.com
svnbook at googlecode.com
Thu Dec 2 16:32:35 CST 2010
Revision: 3816
Author: cmpilato at gmail.com
Date: Thu Dec 2 14:31:50 2010
Log: Fix some typos.
Reported by: Steve Eppley <SEppley at alumni.caltech.edu>
http://code.google.com/p/svnbook/source/detail?r=3816
Modified:
/trunk/src/en/book/ch01-fundamental-concepts.xml
=======================================
--- /trunk/src/en/book/ch01-fundamental-concepts.xml Thu Oct 21 14:13:47
2010
+++ /trunk/src/en/book/ch01-fundamental-concepts.xml Thu Dec 2 14:31:50
2010
@@ -71,7 +71,7 @@
definition of a typical file server. And indeed, the
repository <emphasis>is</emphasis> a kind of file server, but
it's not your usual breed. What makes the repository special
- is that these as the files in the repository are changed, the
+ is that as the files in the repository are changed, the
repository remembers each version of those files.</para>
<para>When a client reads data from the repository, it normally
@@ -96,7 +96,7 @@
<secondary>defined</secondary>
</indexterm>
- <para>A version control system's value comes in the fact that it
+ <para>A version control system's value comes from the fact that it
tracks versions of files and directories, but the rest of the
software universe doesn't operate on <quote>versions of files
and directories</quote>. Most software programs understand
@@ -387,7 +387,7 @@
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
+ core storage mechanism for Subversion's versioned data, and it's
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
More information about the svnbook-dev
mailing list