SEC-1381: Update source repo information in docs to point to git rather than subversion.

docs/manual/src/docbook/introduction.xml

@@ -278,16 +278,16 @@
         <section xml:id="get-source">
             <title>Checking out the Source</title>
             <para> Since Spring Security is an Open Source project, we'd strongly encourage you to
-                check out the source code using subversion. This will give you full access to all
-                the sample applications and you can build the most up to date version of the project
+                check out the source code using git. This will give you full access to all the
+                sample applications and you can build the most up to date version of the project
                 easily. Having the source for a project is also a huge help in debugging. Exception
                 stack traces are no longer obscure black-box issues but you can get straight to the
                 line that's causing the problem and work out what's happening. The source is the
                 ultimate documentation for a project and often the simplest place to find out how
                 something actually works. </para>
-            <para> To obtain the source for the project trunk, use the following subversion command:
+            <para>To obtain the source for the project trunk, use the following git command:
                 <programlisting>
-        svn checkout https://src.springframework.org/svn/spring-security/trunk/
+  git clone git://git.springsource.org/spring-security/spring-security.git
     </programlisting>
                 You can checkout specific versions from
                     <literal>https://src.springframework.org/svn/spring-security/tags/</literal>.

docs/manual/src/docbook/samples.xml

@@ -10,18 +10,17 @@
         the source as described in <link xlink:href="#get-source">the introduction</link> and it's
         easy to build the project using Maven. There is more information on the project web site at
             <link xlink:href="http://www.springsource.org/security/">
-            http://www.springsource.org/security/ </link> if you need it. All paths
-        referred to in this chapter are relative to the source directory, once you have checked it
-        out from subversion. </para>
+            http://www.springsource.org/security/ </link> if you need it. All paths referred to in
+        this chapter are relative to the project source directory. </para>
     <section xml:id="tutorial-sample">
         <title>Tutorial Sample</title>
         <para> The tutorial sample is a nice basic example to get you started. It uses simple
             namespace configuration throughout. The compiled application is included in the
             distribution zip file, ready to be deployed into your web container
                 (<filename>spring-security-samples-tutorial-3.0.x.war</filename>). The <link
-                    xlink:href="#ns-form-and-basic">form-based</link> authentication mechanism is used in combination
-            with the commonly-used <link xlink:href="#remember-me">remember-me</link> authentication
-            provider to automatically remember the login using cookies.</para>
+                xlink:href="#ns-form-and-basic">form-based</link> authentication mechanism is used
+            in combination with the commonly-used <link xlink:href="#remember-me">remember-me</link>
+            authentication provider to automatically remember the login using cookies.</para>
         <para>We recommend you start with the tutorial sample, as the XML is minimal and easy to
             follow. Most importantly, you can easily add this one XML file (and its corresponding
                 <literal>web.xml</literal> entries) to your existing application. Only when this