diff --git a/README b/README
index 4d1fe22..5eb48ce 100644
--- a/README
+++ b/README
@@ -1,5 +1,5 @@
-commit-patch - commit patches to Darcs, Git, CVS, SVN, or Mercurial repositories
---------------------------------------------------------------------------------
+commit-patch - commit patches to Darcs, Git, CVS, Subversion, or Mercurial
+--------------------------------------------------------------------------
 
 PREREQUISITES
        commit-patch relies on several programs to get the job done:
diff --git a/commit-patch b/commit-patch
index a362a2a..e186243 100755
--- a/commit-patch
+++ b/commit-patch
@@ -194,7 +194,7 @@ foreach my $k (keys %clean) { unlink $k }
 
 =head1 NAME
 
-commit-patch - commit patches to I<Darcs>, I<Git>, I<CVS>, I<SVN>, or I<Mercurial> repositories
+commit-patch - commit patches to I<Darcs>, I<Git>, I<CVS>, I<Subversion>, or I<Mercurial> repositories
 
 =head1 SYNOPSIS
 
@@ -219,7 +219,7 @@ B<vi>. Any files you specify will be passed to your version control's
 diff command.
 
 B<commit-patch> currently supports the following version control systems:
-B<I<Darcs>>, B<I<Git>>, B<I<CVS>>, B<I<SVN>>, and B<I<Mercurial>>.
+B<I<Darcs>>, B<I<Git>>, B<I<CVS>>, B<I<Subversion>>, and B<I<Mercurial>>.
 
 =head1 OPTIONS
 
@@ -231,7 +231,7 @@ the same as whatever the underlying version control system would do if
 you didn't specify a message name on the command line. That is,
 B<commit-patch> does not interfere with the patch naming process of
 the underlying version control system; I<Darcs> will still ask you
-interactively; I<CVS> and I<SVN> will still launch your editor.
+interactively; I<CVS> and I<Subversion> will still launch your editor.
 
 B<-F>, B<--message-file>=I<filename> - You can optionally get the
 commit message from a file. This is generally only useful for