diff to comm-comm governance

governance.diff

diff --git a/GOVERNANCE.md b/GOVERNANCE.md
index 73917a0..184e724 100644
--- a/GOVERNANCE.md
+++ b/GOVERNANCE.md
@@ -1,4 +1,4 @@
-# Community Committee Governance
+# Community Committee Charter
 
 ## Section 1. Guiding Principle.
 
@@ -16,7 +16,7 @@ The Board will set the overall CC Policy. The policy will describe the overarchi
 
 ## Section 4. Establishment of the Community Committee.
 
-Membership is for 6 months. The group will ask on a regular basis if the expiring members would like to stay on. A member just needs to reply to renew. There is no fixed size of the CC. However, the expected target for Advisers, as defined in Section 10, is between 9 and 12, to ensure adequate coverage of important areas of community expertise, balanced with the ability to make decisions efficiently.
+Membership is for 6 months. The group will ask on a regular basis if the expiring members would like to stay on. A member just needs to reply to renew. There is no fixed size of the CC. However, the expected target for Advisors, as defined in Section 10, is between 9 and 12, to ensure adequate coverage of important areas of community expertise, balanced with the ability to make decisions efficiently.
 
 There is no specific set of requirements or qualifications for CC membership beyond these rules. The CC may add additional members to the CC by a standard CC motion and vote. A CC member may be removed from the CC by voluntary resignation, or by a standard CC motion.
 
@@ -26,13 +26,17 @@ No more than one-fourth of the CC members may be affiliated with the same employ
 
 The CC members shall consist of active members of Community Projects and the two Individual Membership Directors as defined in Section 10.
 
-The CC may, at its discretion, invite any number of non-voting observers to participate in the public portion of CC discussions and meetings.
+The CC may, at its discretion, invite any number of non-voting Guests to participate in the public portion of CC discussions and meetings.
 
 The CC shall meet regularly using tools that enable participation by the community (e.g. weekly on a Google Hangout On Air, or through any other appropriate means selected by the CC). The meeting shall be directed by the Individual Membership Directors. Minutes or an appropriate recording shall be taken and made available to the community through accessible public postings.
 
 CC members are expected to regularly participate in CC activities.
 
-In the case where an individual CC member -- within any three month period -- attends fewer than 25% of the regularly scheduled meetings, does not participate in CC discussions, and does not participate in CC votes, the member shall be automatically removed from the CC. The member may be invited to continue attending CC meetings as an observer.
+In the case where an individual CC member -- within any three month period -- attends
+fewer than 25% of the regularly scheduled meetings, does not participate in CC
+discussions, and does not participate in CC votes, the member shall be automatically
+removed from the CC. The member may be invited to continue attending CC meetings
+as a Guest.
 
 ## Section 5. Responsibilities of the CC.
 
@@ -79,10 +83,36 @@ If an agenda item cannot reach a consensus a CC member can call for either a clo
 
 ## Section 9. Roles
 
-- The Node.js Foundation community git repository will be maintained by the CC and additional Collaborators who are added by the CC on an ongoing basis.
-- Individuals making significant and valuable contributions, “Contributor(s)”, are made Collaborators and given commit-access to the project. These individuals are identified by the CC and their addition as Collaborators is discussed during the weekly CC meeting. Modifications of the contents of the git repository are made on a collaborative basis as defined in the development process.
-- Collaborators may opt to elevate significant or controversial modifications, or modifications that have not found consensus to the CC for discussion by assigning the cc-agenda tag to a pull request or issue. The CC should serve as the final arbiter where required. The CC will maintain and publish a list of current Collaborators by Project, as well as a development process guide for Collaborators and Contributors looking to participate in the effort.
-- Individual Membership Directors of the Node.js Foundation are the Node.js project’s community voice on the board. There are two individual directors that sit on the Node.js Foundation board and they each serve a two-year term. Each Individual Membership Director is responsible for soliciting feedback and data that represents the wishes of other individual members and the community at large. These directors participate and observe CC meetings in order to deliver monthly updates to the Board of the project. They deliver monthly updates to the CC on what the Board is doing. They have been entrusted with the duty to make decisions based on the information they receive to best represent the community, and can gather input for proposals when relevant and granted permission to do so by the Board.
+Node.js Foundation git repositories for Community Committee Initiatives
+are maintained by the CC and additional Collaborators who are added by
+the CC on an ongoing basis.
+
+Individuals making significant and valuable contributions,
+“Contributor(s)”, are made Collaborators and given commit-access to the
+project. These individuals are identified by the CC and their addition
+as Collaborators is discussed during the weekly CC meeting.
+Modifications of the contents of the git repository are made on a
+collaborative basis as defined in the development process.
+
+Collaborators may opt to elevate significant or controversial
+modifications, or modifications that have not found consensus to the CC
+for discussion by assigning the `cc-agenda` tag to a pull request or
+issue. The CC should serve as the final arbiter where required. The CC
+will maintain and publish a list of current Collaborators by Project, as
+well as a development process guide for Collaborators and Contributors
+looking to participate in the development effort.
+
+Individual Membership Directors of the Node.js Foundation are the Node.js
+project’s community voice on the board. There are two individual directors
+that sit on the Node.js Foundation board and they each serve a two-year term.
+Each Individual Membership Director is responsible for soliciting feedback and
+data that represents the wishes of other individual members and the community
+at large. These directors participate and observe CC meetings in order to deliver
+monthly updates to the Board of the project. They deliver monthly updates to the
+CC on what the Board is doing. They have been entrusted with the duty to make
+decisions based on the information they receive to best represent the community,
+and can gather input for proposals when relevant and granted permission to do
+so by the Board.
 
 ## Section 10. Definitions
 
@@ -90,9 +120,9 @@ If an agenda item cannot reach a consensus a CC member can call for either a clo
 - Project: a collaboration effort, e.g. a subsystem, that is organized through the project creation process and approved by the CC.
 - Community Project: projects within the Node.js Foundation or in the ecosystem that contribute to the health of the Node.js project.
 - Adviser: a Collaborator within a Community Project elected to represent the Community Project on the CC.
-- Member: a person who participates in the development of the Community Committee through code or other artifacts.
+- Member: a Collaborator with voting rights who has met the requirements of participation to be considered for acceptance, and subsequently voted in by the CommComm voting process.
 
 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in all Community Committee documents are to be interpreted as described in [RFC 2119](https://www.ietf.org/rfc/rfc2119.txt).
 
 For the current list of CC members, see the project
-[README.md](./README.md#community-committee-collaborators).
+[README.md](./README.md#community-committee-collaborators).