Update SVN references to git, mostly in docs.

docs/contributing/how-to-add-new-sample.md

@@ -5,9 +5,9 @@ To add a new sample "foo" under directory "samples/foo" you need to do
 the following: (note that all this applies also to demos: just replace
 samples/ with demos/ where needed).
 
-1. Create the directory samples/foo locally and "svn add" it.
+1. Create the directory samples/foo.
 
-2. "svn add" the sample sources (usually based on minimal.cpp) as well.
+2. "git add" the sample sources (usually based on minimal.cpp) as well.
 
    Note that unless your sample requires something special you shouldn't
    add foo.rc, foo.ico, ... any more, please just reuse the generic sample.*

docs/contributing/how-to-release.md

@@ -17,16 +17,12 @@ Update the release announcement post in docs/publicity/announce.txt.
 
 Tag the release:
 
-    svn cp https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@123456 \
-        https://svn.wxwidgets.org/svn/wx/wxWidgets/tags/WX_x_y_z -m 'Tag x.y.z release.'
+    git tag WX_x_y_z -m 'Tag x.y.z release.'
 
 
 Creating release files
 ----------------------
 
-The currently used release scripts need to be used from git-svn checkout and
-rely on Git to avoid problems with using non-clean trees and such.
-
 Follow these steps assuming the current working directory is the root of git
 working copy and you want to prepare distribution for the version x.y.z:
 

docs/contributing/translators-guide.md

@@ -28,8 +28,8 @@ First of all, here is what you will need:
       fine, but you'd have to use some kind of "for /s" loop with the
       command.com/cmd.exe.
 
-3. (at least read) access to the subversion is not necessary strictly speaking, but
-   will make things a lot easier for you and others.
+3. Access to the git repository is not necessary strictly speaking, but will
+   make things a lot easier for you and others.
 
 
 Now a brief overview of the process of translations (please refer to GNU