Maven project-roles.md proposed small patch.

patch-project-roles.md.diff

Index: content/markdown/project-roles.md
===================================================================
--- content/markdown/project-roles.md  (revision 1510429)
+++ content/markdown/project-roles.md	(working copy)
@@ -54,7 +54,7 @@
 we will welcome you with open arms… (and if we don't welcome you
 with open arms, please advise the [Project management committee][3]
 who are responsible for ensuring that the community is a healthy
-one)
+one).
 
 ### Consumers
 
@@ -89,6 +89,7 @@
 ### Users
 
 People who use Maven and have joined the community. This includes people who have:
+
 * Submitted a bug report,
 * Asked a question on the [Maven user list][2],
 * Joined one of the other Maven user communities.
@@ -112,6 +113,7 @@
 
 People who use Maven, have joined the Maven community and contribute 
 back to the community. This includes people who:
+
 * Submit reports of the results of testing proposed releases of
 Maven and Maven plugins,
 * Answer questions on the [Maven user list][2] (or even other Maven user communities),
@@ -235,7 +237,7 @@
 
 #### Forks of the project codebase
 
-All code that gets released by the community should have sufficient opertunity
+All code that gets released by the community should have sufficient opportunity
 for review both:
 
 * By the PMC, to check the legal responsibilities delegated by
@@ -262,7 +264,7 @@
 fork back to Apache Maven source control. 
 
 Similarly, if a fork is being hosted elsewhere in order to get contributions
-from other talented individuals, the PMC members should endevour to bring
+from other talented individuals, the PMC members should endeavour to bring
 those individuals and their talent to the project as committers.
 
 Finally, where a fork is hosted outside of Apache hardware, there is less
@@ -274,8 +276,8 @@
 originating from a long running fork hosted outside of Apache foundation
 source control. Anybody maintaining a long running fork should be aware
 of the risk that review obligations may grow above the time capabilities
-of the PMC and committers such that when they eventually decide to try and
-bring the changes in their fork back to the Apache Maven project their 
+of the PMC and committers, such that when they eventually decide to try and
+bring the changes in their fork back to the Apache Maven project, their 
 contribution may end up being rejected on the basis of the review of a
 large set of changes being too difficult/timeconsuming.
 
@@ -295,8 +297,8 @@
 
 If things break down and there is no consensus and there is no clear
 ability to reach any conclusion *and* it is in the interest of the
-foundation because damage is done and the board expects the chair
-to act as an officier of the foundation and clean things up, then the chair
+foundation, because damage is done and the board expects the chair
+to act as an officer of the foundation and clean things up, then the chair
 can act as an ultimate decision maker, however, by this point the
 board of the foundation must already be well aware of the situation and
 should be actively monitoring the chair.