Apply suggestions from code review

Co-authored-by: Chris de Almeida <[email protected]>
Signed-off-by: Matteo Collina <[email protected]>

PROJECT_PROGRESSION.md

@@ -200,7 +200,7 @@ To be considered for the At Large Stage, the project must meet the following req
 #### Definition
 
 The Impact Stage is for projects that have reached their growth goals and are now on a sustaining cycle of development, maintenance, and long-term support. Impact Stage projects are used commonly in enterprise production environments and have large, well-established project communities.
-Impact projects offer long-term stability guarantees, and therefore the governing body of Impact projects are expected to have representatives from at least three organizations.
+Impact projects offer long-term stability guarantees, and therefore the governing bodies of Impact projects are expected to have representatives from at least three organizations.
 
 #### Examples
 
@@ -218,7 +218,7 @@ Impact Stage projects are expected to participate actively in CPC proceedings, a
 To graduate from At Large stage or for a new project to join as an Impact project, a project must meet the following criteria:
 
  * Demonstrate that it is being used successfully in production by at least two independent end users which, in the CPC’s judgement, are of adequate quality and scope.
- * Have a defined governing body of at least 5 or more members (owners and core maintainers), of which no more than 1/3 is affiliated with the same employer. In the case there are 5 governing members, 2 may be from the same employer. This limitation is to ensure broad representation and to prevent a single organization from having excessive influence on project decision-making.
+ * Have a defined governing body of at least 5 or more members (owners and core maintainers), of which no more than 1/3 is affiliated with the same employer. In the case there are 5 governing members, 2 may be from the same employer. This criterion is to ensure broad representation and to prevent a single organization from having excessive influence on project decision-making.
  * Have a documented and publicly accessible description of the project's governance, decision-making, contribution, and release processes. This is preferably laid out in a GOVERNANCE.md file and references a CONTRIBUTING.md and AUTHORS.md file showing the current and emeritus committers.
  * Demonstrate a substantial ongoing flow of commits and merged contributions.
  * Have a healthy number of committers from at least two organizations. A committer is defined as someone with the commit bit; i.e., someone who can accept contributions to some or all of the project.