Copy editing of governance model PEPs (#762)

* PEP 8000: Fix typo

* PEP 8000: Add missing period

* PEP 8012: Add missing word

* PEP 8011: Add missing space

* PEP 8010-8012: Remove extra space

* PEP 8000/8001/8011: Improve wording/consistency

* PEP 8000: Improve wording/consistency

pep-8000.rst

@@ -10,8 +10,8 @@ Created: 2018-08-24
 Abstract
 ========
 
-This PEP provides an overview of the Python language governance selection
+This PEP provides an overview of the selection process for a new model of
-process in the wake of `Guido's retirement
+Python language governance in the wake of `Guido's retirement
 <https://mail.python.org/pipermail/python-committers/2018-July/005664.html>`_.
 Once the governance model is selected, it will be codified in PEP 13.
 
@@ -23,17 +23,17 @@ governance model.
 
   This PEP describes how the vote for the new governance model will be
   conducted.  It outlines the voting method, timeline, criteria for
-  participation, and explicit list of eligible voters
+  participation, and explicit list of eligible voters.
 
 * PEP 8002 - Open Source Governance Survey
 
-  Surveys will be conducted of similar open source and free software project
+  Surveys will be conducted of governance models for similar open source and
-  governance models, and summaries of these models are outlined in this PEP.
+  free software projects, and summaries of these models will be outlined in
-  These surveys will serve as useful barometers for how such projects can be
+  this PEP.  These surveys will serve as useful barometers for how such
-  successfully governed, and may serve as inspiration for Python's own
+  projects can be successfully governed, and may serve as inspiration for
-  governance model.  Python is unique, so it's expected that we will have our
+  Python's own governance model.  Python is unique, so it's expected that it
-  own spin on governance, rather than directly adopting any of those
+  will have its own spin on governance, rather than directly adopting any of
-  surveyed.
+  those surveyed.
 
 PEPs in the 8010s describe the actual proposals for Python governance.  It is
 expected that these PEPs will cover the broad scope of governance, and that
@@ -54,11 +54,11 @@ PEPs.
 * PEP 8011 - The Council Governance Model
 
   This is a placeholder PEP for a new model of Python governance based on a
-  small Council of Pythonistas (COP)y.  It describes the size and role of the
+  small Council of Pythonistas (COP).  It describes the size and role of the
   council, but it differs from PEP 8010 in that it does not propose a leader
   to whom the council answers.  The governing council makes the final
   decisions for the Python language.  This PEP does *not* name members of the
-  council; for that, see PEP 13.
+  council.  For that, see PEP 13.
 
 * PEP 8012 - The Community Governance Model
 

pep-8001.rst

@@ -10,8 +10,8 @@ Created: 2018-08-24
 Abstract
 ========
 
-This PEP outlines the process for how the new Python language governance model
+This PEP outlines the process for how the new model of Python governance is
-is selected, in the wake of `Guido's retirement
+selected, in the wake of `Guido's retirement
 <https://mail.python.org/pipermail/python-committers/2018-July/005664.html>`_.
 Once the model is chosen by the procedures outlined here, it will be codified
 in PEP 13.

pep-8010.rst

@@ -9,7 +9,7 @@ Created: 2018-08-24
 
 .. note:: This is just a placeholder until the actual governance PEPs are
           written.  It is possible that the title, content, model proposed,
-          and  authorship will change once the PEP is actually written.
+          and authorship will change once the PEP is actually written.
 
 
 Abstract

pep-8011.rst

@@ -9,18 +9,18 @@ Created: 2018-08-24
 
 .. note:: This is just a placeholder until the actual governance PEPs are
           written.  It is possible that the title, content, model proposed,
-          and  authorship will change once the PEP is actually written.
+          and authorship will change once the PEP is actually written.
 
 
 Abstract
 ========
 
-This PEP proposes a new Python language governance model based on a Council of
+This PEP proposes a new model of Python governance based on a Council of
 Pythonistas (COP) tasked with making final decisions for the language.  It
 differs from PEP 8010 by specifically not proposing a central singular leader.
 It describes the size and role of the council, how the initial group of
-council members will be chosen, any term limits of the councilmembers, and how
+council members will be chosen, any term limits of the council members, and
-successors will be elected.
+how successors will be elected.
 
 This PEP does *not* name the council members.  Should this model be adopted,
 it will be codified in PEP 13 along with the names of all officeholders

pep-8012.rst

@@ -9,17 +9,17 @@ Created: 2018-08-24
 
 .. note:: This is just a placeholder until the actual governance PEPs are
           written.  It is possible that the title, content, model proposed,
-          and  authorship will change once the PEP is actually written.
+          and authorship will change once the PEP is actually written.
 
 
 Abstract
 ========
 
 This PEP proposes a new model of Python governance based on consensus and
-voting by the Python community, without the role of a centralized singular or
+voting by the Python community, without the role of a centralized singular
-a governing council.  It describes how, when, and why votes are conducted for
+leader or a governing council.  It describes how, when, and why votes are
-decisions affecting the Python language.  It also describes the criteria for
+conducted for decisions affecting the Python language.  It also describes the
-voting eligibility.
+criteria for voting eligibility.
 
 Should this model be adopted, it will be codified in PEP 13 along with the
 names of all officeholders described in this PEP.