[svn:parrot] r37121 - trunk/docs/project

[Util at svn.parrot.org]

Author: Util
Date: Thu Mar  5 05:51:48 2009
New Revision: 37121
URL: https://trac.parrot.org/parrot/changeset/37121

Log:
[docs] Typos in docs/project/*.pod

Modified:
   trunk/docs/project/branching_guide.pod
   trunk/docs/project/roles_responsibilities.pod
   trunk/docs/project/support_policy.pod

Modified: trunk/docs/project/branching_guide.pod
==============================================================================
--- trunk/docs/project/branching_guide.pod	Thu Mar  5 05:46:45 2009	(r37120)
+++ trunk/docs/project/branching_guide.pod	Thu Mar  5 05:51:48 2009	(r37121)
@@ -147,7 +147,7 @@
 
 If there was a specific language, tool, or platform that you wanted tested
 before merging but couldn't get any response from the responsible person, you
-may want to include some warning in the annoucement that you weren't able to
+may want to include some warning in the announcement that you weren't able to
 test that piece fully.
 
 =cut

Modified: trunk/docs/project/roles_responsibilities.pod
==============================================================================
--- trunk/docs/project/roles_responsibilities.pod	Thu Mar  5 05:46:45 2009	(r37120)
+++ trunk/docs/project/roles_responsibilities.pod	Thu Mar  5 05:51:48 2009	(r37121)
@@ -19,7 +19,7 @@
 
 The architect has primary responsibility for setting overall direction of the
 project, and to facilitate team communication and understanding of
-architectual issues. The architect is primarily but not solely responsible
+architectural issues. The architect is primarily but not solely responsible
 for making design decisions and documenting them in Parrot Design Documents;
 responsibility for design and design documentation of project subcomponents
 may be given to other members of the Project Team, or may be held jointly.
@@ -79,7 +79,7 @@
 =head2 Platform Porter
 
 Develops and maintains Parrot for a particular platform, making
-portablility fixes or creating installation packages.
+portability fixes or creating installation packages.
 
 =head2 Patch Monster
 

Modified: trunk/docs/project/support_policy.pod
==============================================================================
--- trunk/docs/project/support_policy.pod	Thu Mar  5 05:46:45 2009	(r37120)
+++ trunk/docs/project/support_policy.pod	Thu Mar  5 05:51:48 2009	(r37121)
@@ -106,7 +106,7 @@
 On the whole, we're happy to support releases as much as a year old. We
 might even go as far as making a bug/security release for a supported
 release up to two years old, depending on the circumstances. As a
-voluteer project we don't have the resources to commit to making
+volunteer project we don't have the resources to commit to making
 bug/security releases farther back than that. Depending on the nature of
 your problem, it's likely you'll be able to get help from individual
 volunteers within the project or commercial support organizations,