Edits for clarity.

Author: kgodey

content/blog/entries/say_hello_to_ct/contents.lr

@@ -12,62 +12,49 @@ pub_date: 2020-08-14
 body:
 
 Creative Commons is committed to open-source software. We have over two dozen
-projects, spanning thrice as many repositories on GitHub, each with its small,
+projects, spanning three times as many repositories on GitHub, each with its small,
 but extremely enthusiastic, subcommunity. With only a few full-time employees
-working on these projects, it is vital that members from the community take
+working on these projects, it is vital that we enable members from the community to take
 increased responsibility in developing and maintaining them, and growing the
-very community of which they are a part.
+community of which they are a part.
 
-With that goal in mind, we've launched our Community Teams initiative. Since the
-team has just crossed a major milestone with a strength of forty members, I feel
-like it would be a good time to talk a little more about this idea.
+With that goal in mind, we've launched our Community Team initiative.
 
-### What are Community Teams?
+### What is the Community Team?
 
-Due to the very nature of open-source, communities that grow organically around
+Communities that grow organically around open source
 projects tend to be a bit disorganised and the frequency of contributions and
 degree of involvement tends to vary from member to member. Our goal is to
 identify contributors who are actively involved within their communities and
-give them increased permissions over the codebase, and access to more
-information channels and tools in an effort to nurture them as future
-maintainers of that particular project.
+give them increased permissions over the codebase and access to more
+information channels and tools in an effort to empower them to participate
+more fully in the project.
 
 This is not restricted to code though. We're also looking for people who work
 with the community on other aspects of the projects, such as design,
-documentation, evangelism and onboarding to name a few.
+documentation, evangelism, and onboarding to name a few.
 
-- First, they establish a framework for formalising the level of involvement,
+- The Community Team establishes a framework for formalising the level of involvement,
   which is a spectrum, into discrete level or 'roles'.
-
-  Community Teams bring a certain order into the community, which is chaotic by
-  its very nature. By introducing this concept, we discretise the community into
-  strata, which gives us an overview of the sustainability of the community.
-
-- Then they map each role to a set of responsibilities that a member holding the
+- Each role is mapped to a set of responsibilities that a member holding the
   role is encouraged to take up.
-
-  Based on how members are familiarising themselves with the code and processes,
-  and then volunteering to take up increased responsibilities for the projects
-  and communities that they're associated with, we can determine how
-  self-sustaining the community can be.
-
 - Each role also entrusts the members holding it to certain privileges, accesses
   and permissions, to help them execute these responsibilities.
 
-  Roles also progressively include members in our roadmaps and planning meetings
-  to ensure that the community is aligned with our long-term goals.
+Roles also progressively include members in our roadmaps and planning meetings
+to ensure that the community is aligned with our long-term goals.
 
 ### What's in it for me?
 
-Community Teams are not just a one-sided deal. Your membership in the Community
+The Community Team is not just a one-sided deal. Your membership in the Community
 Team is just as beneficial for the you as it is for us. While there is a
 [laundry list of benefits][benefits] that you're entitled to, I'll just mention
 some notable ones here.
 
 [benefits]:/community/community-team/#benefits-of-joining-the-community-team
 
 - You gain real-world practical experience of working on open-source projects.
-- You gain both soft-skills and technical-skills by constantly interacting with
+- You gain both soft-skills and technical-skills by interacting with
   other developers from both the community as well as CC staff.
 - Since we've already seen the quality of your work and involvement with the
   community, you get priority in internship applications*.
@@ -92,7 +79,7 @@ Oh and, lest I forget, you'll receive CC swag!
 
 ### What are these 'roles'?
 
-If you've reached this point, I assume you see the potential of Community Teams.
+If you've reached this point, I assume you see the potential of the Community Team.
 Let's see where you'd fit in them.
 
 We have two kinds of roles, code-oriented [Project roles][projectroles], that
@@ -129,21 +116,17 @@ incoming issues or block certain PRs that you've reviewed. You could escalate
 your role to Project Collaborator. Want to me more involved? You can apply to be
 a Project Core Committer, or even a Project Maintainer.
 
-While our goal is to equip as many people as possible with the skills to become
-Project Maintainers, you are no-doubt free to de-escalate if you want to reduce
-your involvement with the community.
-
 #### "No, I can't code..."
 
-*That's cool too!* We realise that open-source communities are never just about
+*That's cool too!* We realise that open source communities are never just about
 the code. If you're passionate about growing the CC community by enabling new
 contributors to get started or by spreading the word, you can apply for one of
 the Community Building roles. Like the Project roles, there are a couple of
 levels to choose from.
 
 Community builders have a whole different set of responsibilities and privileges
 specifically catered to the unique task of cultivating a healthy community
-around our many open-source projects.
+around our many open source projects.
 
 So if you want to be lightly involved with onboarding new contributors to the
 repositories and the workflows, you could start off as a Community Contributor.
@@ -155,11 +138,7 @@ tweets for our Twitter account, or pariticipate in long-term community building
 tasks from Asana. You could escalate your role to Community Collaborator. Want
 to me more involved? You can even apply to be a Community Maintainer.
 
-While our goal is to equip as many people as possible with the skills to become
-Community Maintainers, you are no-doubt free to de-escalate if you want to
-reduce your involvement with the community.
-
-### What's in store?
+### What's next?
 
 <p style="text-align:center;">
   <img
@@ -171,15 +150,15 @@ reduce your involvement with the community.
   </small>
 </p>
 
-Community Teams are a fairly novel idea for us and we're still tweaking things
-along the way. Take our recent merge of two Project roles, namely Project Member
-and Project Collaborator for example. We combined both when we realised they
-weren't so different. As we internalise these roles more and more, we'll find
+The Community Team is a fairly novel idea for us and we're still tweaking things
+along the way. For example, we recently merged of two Project roles, namely Project Member
+and Project Collaborator, when we realised they weren't so different.
+As we internalise these roles more and more, we'll find
 more scope for improvement and we'll continue to refine these roles over time.
 
 We're excited about Community Teams. If you're interested in joining us on this
 ride, it's really easy to [get started][communityteam].
 
 [communityteam]:/community/community-team/
 
-<small>*This is not a guarantee!</small>
+<small>*We do not guarantee that you will be accepted if you apply for an internship!</small>