X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=blobdiff_plain;f=lib%2FCatalyst%2FManual%2FDevelopmentProcess.pod;h=a0183e6ec9fe7d414e5cded6b5013b8348b3f835;hb=4ad342ef92054fc21765383024f77f08f7f66c9b;hp=797ea38d4c442a3e9206fbf5d015c863693c29e0;hpb=32882a5e0ae790a395aa7ec751e29c120496fea2;p=catagits%2FCatalyst-Manual.git

diff --git a/lib/Catalyst/Manual/DevelopmentProcess.pod b/lib/Catalyst/Manual/DevelopmentProcess.pod
index 797ea38..a0183e6 100644
--- a/lib/Catalyst/Manual/DevelopmentProcess.pod
+++ b/lib/Catalyst/Manual/DevelopmentProcess.pod
@@ -33,17 +33,17 @@ will talk you through how to submit a patch, or get a "commit bit".
 
 =head2 Repositories
 
-The Catalyst subversion repository can be found at:
-
-    svn: http://dev.catalyst.perl.org/repos/Catalyst
-    browser: http://dev.catalyst.perl.org/svnweb/Catalyst
-
-and the git repository can be found at:
+The Catalyst git repository can be found at:
 
     read: git://git.shadowcat.co.uk/catagits/PROJECTNAME
     write: catagits@git.shadowcat.co.uk:PROJECTNAME
     browser: https://git.shadowcat.co.uk/gitweb/gitweb.cgi
 
+The Catalyst subversion repository can be found at:
+
+    svn: http://dev.catalyst.perl.org/repos/Catalyst
+    browser: http://dev.catalyst.perl.org/svnweb/Catalyst
+
 =head2 Schedule
 
 There is no dated release cycle for Catalyst. New releases will be made
@@ -57,7 +57,7 @@ L<http://git.shadowcat.co.uk/gitweb/gitweb.cgi?p=catagits/Catalyst-Runtime.git;a
 
 =head2 Bug list
 
-The TODO list with known bugs / deficiences is kept at
+The TODO list with known bugs / deficiencies is kept at
 L<http://git.shadowcat.co.uk/gitweb/gitweb.cgi?p=catagits/Catalyst-Runtime.git;a=blob_plain;f=TODO;hb=master>
 
 =head1 The Catalyst Core Team
@@ -121,9 +121,9 @@ current members.
 Any change to the Catalyst core which can not be conceived as a
 correction of an error in the current feature set will need to be
 accepted by at least 3 members of the Core Team before it can be
-committed to the trunk (which is the basis for CPAN releases). Anyone
+committed to master (which is the basis for CPAN releases). Anyone
 with access is at any time free to make a branch to develop a proof of
-concept for a feature to be committed to trunk.
+concept for a feature to be committed to master.
 
 =head2 Organizational and Philosophical Decisions.