PATCH: more 'revison control' -> 'version control' doc fixes

Hi,

OK, so I'm not including the path of each file in the log message, because
I made the same change to each file. Correct?

Log Message:
Fixed some out-of-book occurrences of 'revision control' to be 'version
control'. Patch from Zack Brown <zbrown@tumblerings.org>

Index: www/variance-adjusted-patching.html
===================================================================
--- www/variance-adjusted-patching.html
+++ www/.svn/tmp/variance-adjusted-patching.html.62772.00001.tmp 2002-10-31 08:44:13.000000000 -0800
@@ -17,7 +17,7 @@
 
 <p>
 
-Revision control systems that use traditional context diff / unidiff
+Version control systems that use traditional context diff / unidiff
 format for branch merging tend to fail spuriously in high variance
 situations. A "high variance" situation is one where the branch text
 differs from the source text by more than roughly 5-10%, counting
@@ -54,7 +54,7 @@
 This is possible because for any given line that a patch hunk expects
 to see in the target text (e.g., in a context diff, these would be the
 context lines, plus the "before" version of affected lines), the
-revision control system can know that line's history in both source
+version control system can know that line's history in both source
 and target, if there is a common ancestor to examine. The process is
 very similar to the calculations done by "<tt>cvs&nbsp;annotate</tt>".
 Informally speaking, one of the following is true for each such line,
@@ -110,7 +110,7 @@
       Either way, the line needs to be changed to the "corresponding"
       line in the target text -- that is, the line that, in target,
       now occupies the place of the obsolete expected line. The
- revision control system has enough information to determine
+ version control system has enough information to determine
       which of the two cases above applies, and can use that to
       decide which of the lines currently in target is the best
       candidate to substitute for the missing line.
@@ -127,7 +127,7 @@
 <p>
 
 Although the patch program can adjust for floating at application
-time, the revision control system can also adjust the line numbers in
+time, the version control system can also adjust the line numbers in
 hunks to compensate for any insertions or deletions that have
 happened, in either source or target, outside the areas covered by the
 hunks. This can result in a patch that applies perfectly, without any
@@ -140,7 +140,7 @@
 
 The above rules are an informal explanation of how variance adjustment
 works. Below, the algorithm is described somewhat more formally, to
-show how the revision control system would do variance adjustment in
+show how the version control system would do variance adjustment in
 any situation. Note that the algorithm is actually <i>too</i>
 powerful -- if taken to its logical limits, it can generate patches
 that apply cleanly even when the user would almost certainly prefer a
Index: www/project_faq.html
===================================================================
--- www/project_faq.html
+++ www/project_faq.html 2002-10-31 08:41:26.000000000 -0800
@@ -87,7 +87,7 @@
 <h3><a name="why">Why does this project exist?</a></h3>
 
 <p>To take over the CVS user base. Specifically, we're writing a new
-revision control system that is very similar to CVS, but fixes many
+version control system that is very similar to CVS, but fixes many
 things that are broken. See our front page.</p>
 
 <![CDATA[-----------------------------------------------------------]]>
Index: doc/translations/french/svn-handbook-french.texi
===================================================================
--- doc/translations/french/svn-handbook-french.texi
+++ doc/translations/french/.svn/tmp/svn-handbook-french.texi.62580.00001.tmp 2002-10-31 08:44:18.000000000 -0800
@@ -58,7 +58,7 @@
 @c
 @c * voici certaine correspondance anglais-français.
 @c - handbook => manuel
-@c - revision control system => système de contrôle de version
+@c - version control system => système de contrôle de version
 @c - commit => requête de prise en compte de changement.
 @c - commit => requête de changement.
 @c - commit => souvent considéré comme "check in"
Index: doc/user/lj_article.txt
===================================================================
--- doc/user/lj_article.txt
+++ doc/user/lj_article.txt 2002-10-31 08:43:07.000000000 -0800
@@ -236,7 +236,7 @@
 disk, the client can do this too; no network is required. The
 "Repository Access" layer (RA) is an abstract API implemented by both
 the DAV and local-access RA libraries. This is a specific benefit of
-writing a "librarized" revision control system; its a big win over
+writing a "librarized" version control system; its a big win over
 CVS, which has two very different, difficult-to-maintain codepaths for
 local vs. network repository-access. Feel like writing a new network
 protocol for Subversion? Just write a new library that implements the
@@ -266,7 +266,7 @@
 job is to mingle the functionality of the working-copy library with
 that of the repository-access library, and then to provide a
 highest-level API to any application that wishes to perform general
-revision control actions.
+version control actions.
 
 For example: the C routine `svn_client_checkout()' takes a URL as an
 argument. It passes this URL to the repository-access library and

-- 
Zack Brown
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org