Some content updates.

kgodey · kgodey · commit adb1a4ee6ed8 · 2020-04-27T10:23:55.000-04:00
diff --git a/content/community/community-teams/contents.lr b/content/community/community-teams/contents.lr
@@ -22,7 +22,7 @@ Joining the community team involves three steps:
 -   You'll build your resume. 
 -   You'll be given "priority" in internship applications (not an automatic bump, but if the applicant is known for good quality, that's a big advantage)
 -   You'll advance the Creative Commons mission
--   You'll engage with CC's global Free/Libre and Open Source (FLOSS) community!f
+-   You'll engage with CC's global Free/Libre and Open Source (FLOSS) community!
 
 How to Contribute
 -----------------
@@ -54,20 +54,20 @@ Privileges and access will be granted per-repository. For example, if you are ap
 
 | Name                  	| Privileges                                                                                                                                                                                                                                                                                                                                                                                                                         	| Requirements                                                                                                                 	|
 |-----------------------	|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------	|------------------------------------------------------------------------------------------------------------------------------	|
-| Project Contributor   	| <li>Invitation to private community contributors Slack channel.</li><li>Addition to Community Team page on CC Open Source.</li>	| 3 contributions.<br><br>1 merged pull request or “Great Contribution” to the project you’re applying for.                    	|
-| Project Member        	| <li>All Project Contributor privileges.</li><li>Addition to creativecommons GitHub organization with Triage access to the GitHub repo associated with the project.</li><ul><li>This will allow you to update labels on issues, etc.</li></ul>	| 15 contributions with at least 4 pull requests* submitted to the project you’re applying for.<br><br>3 “Great” Contributions 	|
-| Project Collaborator  	| <li>All Project Member privileges.</li><li>Addition to project’s CODEOWNERs file.</li><ul><li>This will allow your PR reviews to block merge.</li><li>This will auto assign you PRs to review.</li></ul><li>Eligibility to mentor interns for programs like GSoC and Outreachy for Creative Commons.</li><li>Invitation to some of CC’s internal meetings and Slack channels.</li><li>Letter of recommendation from Creative Commons available on request.</li> 	| 35 contributions with at least 8 pull requests* submitted to the project you’re applying for.<br><br>5 “Great” Contributions 	|
-| Project Core Commiter 	| <li>All Project Collaborator privileges.</li><li>Write access to the project's GitHub repo.</li><ul><li>This will allow you to merge PRs.</li></ul>	| N/A, Mainters will invite standout contributors.                                                                               	|
+| **Project Contributor**   	| <li>Invitation to private community contributors Slack channel.</li><li>Addition to Community Team page on CC Open Source.</li>	| 3 contributions.<br><br>1 merged pull request or “Great Contribution” to the project you’re applying for.                    	|
+| **Project Member**        	| <li>All <b>Project Contributor</b> privileges.</li><li>Addition to creativecommons GitHub organization with Triage access to the GitHub repo associated with the project.</li><ul><li>This will allow you to update labels on issues, etc.</li></ul>	| 15 contributions with at least 4 pull requests* submitted to the project you’re applying for.<br><br>3 “Great” Contributions 	|
+| **Project Collaborator**  	| <li>All <b>Project Member</b> privileges.</li><li>Addition to project’s CODEOWNERs file.</li><ul><li>This will allow your PR reviews to block merge.</li><li>This will auto assign you PRs to review.</li></ul><li>Eligibility to mentor interns for programs like GSoC and Outreachy for Creative Commons.</li><li>Invitation to some of CC’s internal meetings and Slack channels.</li><li>Letter of recommendation from Creative Commons available on request.</li> 	| 35 contributions with at least 8 pull requests* submitted to the project you’re applying for.<br><br>5 “Great” Contributions 	|
+| **Project Core Committer** 	| <li>All <b>Project Collaborator</b> privileges.</li><li>Write access to the project's GitHub repo.</li><ul><li>This will allow you to merge PRs.</li></ul>	| N/A, Maintainers will invite standout contributors.                                                                               	|
 
 ### Community Roles
 
 These roles are not project based and are for folks interested in helping grow CC's open source community by ensuring all contributors have a good experience and spreading the word about CC's projects.
 
 | Name                   	| Privileges                                                                                                                                                                                                                        	| Requirements                                                                                                                                                                                    	|
 |------------------------	|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------	|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------	|
-| Community Contributor  	| <li>Invitation to private community contributors Slack channel.</li><li>Addition to Community Team page on CC Open Source.</li>                                                                                                             	| 3 contributions.<br><br>1 published tweet to the CC Open Source Twitter account based on an idea submitted by you or “Great Contribution” on any project.<br><br>General community interaction. 	|
-| Community Collaborator 	| <li>All Community Contributor privileges</li><li>Comment-only access to the Open Source Community project on Asana, with the option to pick up tasks if desired.</li>                                                                       	| 15 contributions.<br><br>At least five people helped on Slack or the mailing list.                                                                                                              	|
-| Community Maintainer   	| <li>All Community Collaborator privileges</li><li>Manager permission on CC’s developer mailing list</li><li>Access to tweet directly from CC Open Source account</li><li>Letter of recommendation from Creative Commons available on request</li> 	| N/A, Maintainers will watch and select standout contributors                                                                                                                                    	|
+| **Community Contributor**  	| <li>Invitation to private community contributors Slack channel.</li><li>Addition to Community Team page on CC Open Source.</li>                                                                                                             	| 3 contributions.<br><br>1 published tweet to the CC Open Source Twitter account based on an idea submitted by you or “Great Contribution” on any project.<br><br>General community interaction. 	|
+| **Community Collaborator** 	| <li>All **Community Contributor** privileges</li><li>Comment-only access to the Open Source Community project on Asana, with the option to pick up tasks if desired.</li>                                                                       	| 15 contributions.<br><br>At least five people helped on Slack or the mailing list.                                                                                                              	|
+| **Community Maintainer**   	| <li>All **Community Collaborator** privileges</li><li>Manager permission on CC’s developer mailing list</li><li>Access to tweet directly from CC Open Source account</li><li>Letter of recommendation from Creative Commons available on request</li> 	| N/A, Maintainers will watch and select standout contributors                                                                                                                                    	|
 
 How to Apply
 ------------
diff --git a/content/community/contents.lr b/content/community/contents.lr
@@ -6,13 +6,7 @@ title: Join the CC Developer Community
 ---
 body:
 
-<p class="lead">Join our Slack, IRC, or mailing list communities to meet other developers interested in Creative Commons, get feedback on your projects, and talk with CC's full-time engineering staff. You can also keep up with us on the <a href="/blog">CC Open Source Blog</a> or via <a href="https://twitter.com/cc_opensource">Twitter</a>.</p>
-
-To do this, you can:
-<ul>
-  <li>Join the Creative Commons Slack organization and introduce yourself in the #cc-developers channel.</li>
-  <li>Join the CC Developer's mailing list.</li>
-</ul>
+<p class="lead">Join our Slack or mailing list communities to meet other developers interested in Creative Commons, get feedback on your projects, and talk with CC's full-time engineering staff. You can also keep up with us on the <a href="/blog">CC Open Source Blog</a> or via <a href="https://twitter.com/cc_opensource">Twitter</a>.</p>
 
 ## Mailing Lists
 
@@ -23,6 +17,8 @@ To do this, you can:
 ## Slack
 Creative Commons has a large Slack community with sub-communities for tech/developers (of course), the [CC Global Network](https://network.creativecommons.org/), specific countries, open education, GLAM, and more. It is open to the public and you can [sign up here](http://slack-signup.creativecommons.org/). If you're not familiar with Slack, please read ["Getting Started" on Slack's usage guide](https://get.slack.help/hc/en-us/categories/360000049043). Information on joining a specific channel is on ["Join a channel"](https://get.slack.help/hc/en-us/articles/205239967-Join-a-channel).
 
+Once you join, please introduce yourself in the `#cc-developers` channel.
+
 The channels most relevant to CC's developer community are:  
 
 <table class="table table-sm table-striped">
@@ -92,6 +88,6 @@ The channels most relevant to CC's developer community are:
 - If you're looking to talk to someone on CC's full-time engineering staff, you're most likely to find us on Slack between 11:00 and 23:00 UTC on weekdays.
 
 ## IRC
-Please join the `#creativecommons-dev` channel on [Freenode](https://freenode.net/). This channel is mirrored to the `#cc-developers` channel on Slack so that messages posted on Slack show up on IRC and vice-versa.
+We don't use IRC much, but if you'd like, you can join the `#creativecommons-dev` channel on [Freenode](https://freenode.net/). This channel is mirrored to the `#cc-developers` channel on Slack so that messages posted on Slack show up on IRC and vice-versa.
 
 If you're not familiar with IRC, [here's a good guide to getting started](https://www.wikihow.com/Get-Started-with-IRC-%28Internet-Relay-Chat%29). You can also join using the [Freenode webchat](https://webchat.freenode.net/).
