typo fix

[catagits/Catalyst-Runtime.git] / lib / Catalyst / Manual / DevelopmentProcess.pod

diff --git a/lib/Catalyst/Manual/DevelopmentProcess.pod b/lib/Catalyst/Manual/DevelopmentProcess.pod
index a62be00..a474904 100644 (file)
--- a/lib/Catalyst/Manual/DevelopmentProcess.pod
+++ b/lib/Catalyst/Manual/DevelopmentProcess.pod
@@ -1,6 +1,6 @@
-=head1 Catalyst Development Process
+=head1 NAME
 
-Below you will find information related to the Catalyst Development Process
+Catalyst::Manual::DevelopmentProcess - Administrative structure of the Catalyst Development Process
 
 =head1 Aims of the Catalyst Core Team
 
@@ -9,18 +9,18 @@ be stability, performance, and a more paced addition of features, with a
 focus on extensibility. Extensive improvements to the documentation are
 also expected in the short term.
 
-The Catalyst Roadmap at http://dev.catalyst.perl.org/roadmap will remain
-as is, and continues to reflect the specific priorities and schedule for
-future releases.
+The Catalyst Roadmap at L<http://dev.catalyst.perl.org/roadmap> will
+remain as is, and continues to reflect the specific priorities and
+schedule for future releases.
 
 =head1 Charter for the Catalyst Core Team
 
 =head2 Intention
 
-The intention of the Catalyst Core Team is to maintain and support the 
+The intention of the Catalyst Core Team is to maintain and support the
 Catalyst framework, in order for it to be a viable and stable framework
 for developing web-based MVC applications. This includes both technical
-decisions about the Catalyst core distribution, and public relations 
+decisions about the Catalyst core distribution, and public relations
 relating to the Catalyst framework as a whole.
 
 The main priority for development is stability for the users of the
@@ -33,8 +33,7 @@ The Catalyst Core Team consists of the developers that have full commit
 privileges to the entire Catalyst source tree. 
 
 In addition, the core team may accept members that have non-technical
-roles such as marketing, legal, or ecconomic responsibilities.
-
+roles such as marketing, legal, or economic responsibilities.
 
 At the time of conception, the Core Team consists of the following people:
 
@@ -80,7 +79,7 @@ majority.
 =head2 CPAN Releases
 
 Planned releases to CPAN should be performed by the release manager, at
-the time of writing Marcus Ramberg, or the backup release manager, at
+the time of writing Marcus Ramberg, or the deputy release manager, at
 the time of writing Andy Grundman. In the case of critical error
 correction, any member of the Core Team can perform a rescue release.