cvsup will be going to a special place soon

Approved by:	bcr

en_US.ISO8859-1/htdocs/gnome/docs/bugging.xml

@@ -19,7 +19,7 @@
 		    <li><b><i>After</i></b> running any build failure
 		      output through <a
 		      href="/gnome/gnomelogalyzer.sh">gnomelogalyzer.sh</a>.</li>
-		    <li><b><i>After</i></b> running <tt>cvsup</tt> to obtain the most
+		    <li><b><i>After</i></b> running <tt>portsnap</tt> to obtain the most
 		      recent ports tree.</li>
 		    <li><b><i>After</i></b> running <tt>portupgrade&nbsp;-a</tt> or
 		      <tt>portmaster&nbsp;-a</tt> to ensure that all applications are
@@ -59,7 +59,7 @@
 		  it has been more than a day, or if you have not run
 		  <tt>portupgrade&nbsp;-a</tt> or <tt>portmaster&nbsp;-a</tt>,
 		  do not bother sending a bug report until you have run
-		  <tt>cvsup</tt> and <tt>portupgrade/portmaster</tt>.</p></li>
+		  <tt>portsnap</tt> and <tt>portupgrade/portmaster</tt>.</p></li>
 	    <li><p>Information specific for each type of breakage:</p>
 		  <ul>
 		    <li>If a port will not build, provide a full log of the

en_US.ISO8859-1/htdocs/gnome/docs/faq2.xml

@@ -114,8 +114,7 @@ Note: links for existing questions should NEVER be changed.
 
 	    <p>To build GNOME &gnomever;, you must first obtain the
 	      latest ports tree skeleton.  This is most easily
-	      accomplished with <tt>portsnap(8)</tt> or <a
-	      href="&base;/doc/en_US.ISO8859-1/books/handbook/cvsup.html">cvsup</a>.
+	      accomplished with <tt>portsnap(8)</tt>
 	      Then:</p>
 
 	    <pre>
@@ -398,7 +397,7 @@ libtool: link: `/usr/X11R6/lib/libglade-2.0.la' is not a valid libtool archive
 		  <tt>portmaster</tt>.</u></p>
 
 		<p>Once you have updated your ports tree (presumably with
-		  <tt>cvsup</tt>), the following two simple commands will update
+		  <tt>portsnap</tt>), the following two simple commands will update
 		  what needs to be updated, and will prevent inconsistencies:</p>
 
 		<pre>