--- a/releasechecklist
+++ b/releasechecklist
@@ -26,7 +26,7 @@
 bump OPD_VERSION (in libop/op_config.h) if it hasn't already been done.
   </li>
   <li>
-    Change version to non-cvs and commit
+    Change version to non-git and commit
   </li>
   <ul>
     <li>Change version in configure.in's AM_INIT_AUTOMAKE</li>
@@ -123,22 +123,19 @@
     </li>
   </ul>
   <li>
-    Run the command <pre>'cvs tag RELEASE_&lt;v_r_m&gt;';  e.g, 'cvs tag RELEASE_0_9_4'</pre>
+    Run the command <pre>'git tag RELEASE_&lt;v_r_m&gt;';  e.g, 'git tag RELEASE_0_9_4'</pre>
   </li>
   <ul>
     <li>After committing the change to configure.in's AM_INIT_AUTOMAKE
 for the GA release, cd into the checked-out oprofile directory and run
-the 'cvs tag' command.&nbsp; You should get a password prompt, then
-you'll see a message for every file in the project:&nbsp; "T
-&lt;filename&gt;".&nbsp; You can go to OProfile CVS on SourceForge and
-browse the files to see that the new tag has been applied.<br>
+the 'git tag' command.<br>
     </li>
   </ul>
   <li>
     Update web page release-notes/, news, download, srcdoc/, doc/
   </li>
   <ul>
-    <li>Do a normal cvs checkout of oprofile and
+    <li>Do a 'git clone' of oprofile and
 oprofile-www.</li>
     <li>In oprofile-www, make the following updates:<br>
 	<ul><li>Edit the news/index.php and
@@ -147,36 +144,36 @@
 	a temporary change in the oprofile source code -- change the value of LINE_LEN
 	in utils/ophelp from 99 to 999.  Do a 'make install' to put this change into effect for
 	the actual generation of event doc.  Add new .php files in the doc directory for any
-	new processor type that was added since last regeneration.  Now run 'sh all-events-doc.sh' and do a 'cvs diff'
+	new processor type that was added since last regeneration.  Now run 'sh all-events-doc.sh' and do a 'git diff'
 	to verify the updates to the doc dir.</li>
 	<li>Verify correctness/completeness
 	of the new release-notes.  Any meaningful change seen when diffing docs/ subdir
 	should be reported in the release-notes file.</li>
 	</ul>
-	Do 'cvs commit' of these changes.&nbsp; </li>
+	Do 'git commit' of these changes.&nbsp; </li>
     <li>In oprofile, do ./autogen.sh, ./configure, and then cd into
 doc/ and run 'make chunk'.&nbsp; Tar up the doc/ directory that gets created inside of
 doc/.&nbsp; Then
 cd into doc/srcdoc/ and run 'make'.&nbsp; Tar up the srcdoc/ directory.</li>
   </ul>
   <li>
-    Sync website to oprofile-www CVS
+    Sync website to oprofile-www git
   </li>
   <ul>
     <li>Navigate to SourceForge's Site Support/Site Documentation.  Then go to
 Shell services (https://sourceforge.net/apps/trac/sourceforge/wiki/Shell%20service).
 See instructions there on how to do ssh and scp.  Then ssh into SF with your admin ID
 and cd to oprofile's www directory
-(/home/groups/o/op/oprofile/htdocs/). There's a cvs dir there; 'cvs
-update' that.</li>
+(/home/project-web/oprofile/htdocs/). There's a git dir there; do a 'git
+pull' to update that directory with current data from the shared repo.</li>
     <li>scp the new doc and srcdoc tar balls created in the previous
-step over to SF and untar them into the cvs dir.</li>
+step over to SF and untar them into the git dir.</li>
     <li>Ensure that any new files you create have write access for the
 'oprofile' group (do 'chmod g+w' if necessary).</li>
-    <li>Point your browser at http://oprofile.sourceforge.net/cvs/ and
+    <li>Point your browser at http://oprofile.sourceforge.net/git/ and
 verify the website, documentation, etc. looks OK.</li>
     <li>Make a backup of the parent (htdocs) directory; then copy all
-the stuff from the cvs dir into the parent dir to make it live.&nbsp;
+the stuff from the git dir into the parent dir to make it live.&nbsp;
 Now use your browser to verify that the actual OProfile website looks
 OK.<br>
     </li>
@@ -186,7 +183,7 @@
   </li>
   <li>
     Change AM_INIT_AUTOMAKE in configure.in '&lt;<span
- style="font-style: italic;">v.r.m</span>&gt;cvs' and commit
+ style="font-style: italic;">v.r.m</span>&gt;git' and commit
   </li>
 </ol>
 </body>