svn commit: r1618 - trunk/docs/upgrading-howto.html

Author: cmpilato
Date: 2007-04-18 09:00:37-0700
New Revision: 1618

Modified:
   trunk/docs/upgrading-howto.html

Log:
* docs/upgrading-howto.html
  Don't refer to "ViewCVS 1.0".  It was "ViewVC 1.0".


Modified: trunk/docs/upgrading-howto.html
Url: 
http://viewvc.tigris.org/source/browse/viewvc/trunk/docs/upgrading-howto.html?view=diff&rev=1618&p1=trunk/docs/upgrading-howto.html&p2=trunk/docs/upgrading-howto.html&r1=1617&r2=1618
==============================================================================
--- trunk/docs/upgrading-howto.html     (original)
+++ trunk/docs/upgrading-howto.html     2007-04-18 09:00:37-0700
@@ -56,7 +56,7 @@
    directory and to carefully compare the configuration files.  A
    possible approach is to name the directories
    <code>/usr/local/viewvc-1.0</code>,
-   <code>/usr/local/viewcvs-1.1</code> and so on and than create a
+   <code>/usr/local/viewvc-1.1</code> and so on and than create a
    symbolic link <code>viewvc</code> pointing to the production
    version.  This way you can easily test several versions and switch
    back if your users start to complain.</p>
@@ -67,16 +67,16 @@
 <h2 id="toc">Table of Contents</h2>
 <ul class="toc-list">
   <li><a href="#introduction">Introduction</a></li>
-  <li><a href="#sec-from-1-0">Upgrading From ViewCVS 1.0.0</a></li>
+  <li><a href="#sec-from-1-0">Upgrading From ViewVC 1.0</a></li>
   <li><a href="#sec-from-0-9">Upgrading From ViewCVS 0.9</a></li>
   <li><a href="#sec-from-0-8">Upgrading From ViewCVS 0.8</a></li>
 </ul>
 </div>
 
 <div class="h2">
-<h2 id="sec-from-1-0">Upgrading From ViewCVS 1.0.0</h2>
+<h2 id="sec-from-1-0">Upgrading From ViewVC 1.0</h2>
 
-<p>This section discusses how to upgrade ViewCVS 1.0.x to ViewVC 1.1.x.</p>
+<p>This section discusses how to upgrade ViewVC 1.0.x to ViewVC 1.1.x.</p>
 
 <div class="h3">
 <h3>root_as_url_component Now Enabled by Default</h3>