Merge pull request #9 from BOINC/knr_supporters

Proposed changes to the governance document from the working committee.  Approved by 8-0 vote of the PMC here: https://groups.google.com/forum/#!topic/boinc_admin/YusqmC8HNcU

Definition_of_Done_for_Feature_Branches.md

@@ -1,10 +1,10 @@
 # Definition of Done for Feature Branches
-The definition of done is an agile document that clarifies what it means for a set of development work to be completed.  It is both a check list and a set of guidelines that should be followed.
+The definition of done is an agile document that clarifies what it means for a set of development tasks to be completed.  It is both a check list and a set of guidelines that should be followed.
 
 ## Development Practices
 - Code has followed the style guide for BOINC (http://boinc.berkeley.edu/trac/wiki/CodingStyle)
-- Does not contain unrelated code changes
-- Uses atomic commits (https://www.freshconsulting.com/atomic-commits/)
+- Commit does not contain unrelated code changes
+- Code uses atomic commits (https://www.freshconsulting.com/atomic-commits/)
 
 ## Testing
 - The code compiles on relevant major platforms (this should be available via automation)

Development_Workflow.md

@@ -1,5 +1,5 @@
 # Development Workflow
-The purpose of a development workflow is to make sure that the BOINC platform produces high quality code that solves the problems of its users. As such, the development workflow needs to have checkpoints to allow for the review and discussion of the following questions:
+The purpose of a development workflow is to make sure that the BOINC is a high-quality platform that solves the problems of its users. As such, the development workflow needs to have checkpoints to allow for the review and discussion of the following questions:
 
 - Should this item be implemented?
 - How should this item be implemented?