Merge pull request #760 from magdmartin/patch-1

fixing typos in code-of-conduct

code-of-conduct/index.md

@@ -20,7 +20,7 @@ The following types of behavior are unacceptable in 2i2c spaces, both online and
 (coc:unwelcoming-behavior)=
 ### Unwelcoming behavior
 
-**Blatant -isms**: saying things that assume negative characteristics in a blanket fashion because of identification with a particular group. This is especially true for -isms around traditionally marginalized groups (e.g., explicitly racist, sexist, homophobic, or transphobic statements) For example, arguing that some people are less intelligent because of their gender, race , religion. [Subtle -isms](social:subtle-isms) and small mistakes made in conversation are not code of conduct violations. However, repeating something after it has been pointed out to you that you broke a social rule, or antagonizing or arguing with someone who has pointed out your subtle -ism is considered unwelcoming behavior, and is not allowed at 2i2c.
+**Blatant -isms**: saying things that assume negative characteristics in a blanket fashion because of identification with a particular group. This is especially true for -isms around traditionally marginalized groups (e.g., explicitly racist, sexist, homophobic, or transphobic statements) For example, arguing that some people are less intelligent because of their gender, race, religion. [Subtle -isms](social:subtle-isms) and small mistakes made in conversation are not code of conduct violations. However, repeating something after it has been pointed out to you that you broke a social rule, or antagonizing or arguing with someone who has pointed out your subtle -ism is considered unwelcoming behavior, and is not allowed at 2i2c.
 
 **Maliciousness towards other community members**: deliberately attempting to make others feel bad, name-calling, singling out others for derision or exclusion. For example, telling someone they’re not a real programmer or that they don’t belong at 2i2c. If somebody makes such a statement without malice, they may still be in violation of the Code of Conduct if their actions are deemed especially/repeatedly unpleasant (see below).
 
@@ -82,7 +82,7 @@ The people serving in these roles will be listed on the 2i2c website’s Steerin
 
 We will keep all reports confidential, except if we've discussed with you and agreed otherwise. When we discuss incidents with people who are reported, we will anonymize details as much as we can to protect reporter privacy.
 
-However, some incidents happen in one-on-one interactions, and even if the details are anonymized, the reported person may be able to guess who made the report. If you have concerns about retaliation or your personal safety, and do not want us to share the details of your report with anyone (including the perpetrator) please let us know explicitly in your report. Unfortunately, in that situation we won't be able to conclude that an individual has violated the CoC based on this report alone..
+However, some incidents happen in one-on-one interactions, and even if the details are anonymized, the reported person may be able to guess who made the report. If you have concerns about retaliation or your personal safety, and do not want us to share the details of your report with anyone (including the perpetrator) please let us know explicitly in your report. Unfortunately, in that situation we won't be able to conclude that an individual has violated the CoC based on this report alone.
 
 In some cases we may decide to share an update about a major incident with 2i2c team members, or with the entire 2i2c community. If that's the case, the identities of all victims and reporters will remain confidential unless those individuals instruct us otherwise.
 
@@ -120,6 +120,6 @@ If you or someone else at 2i2c is struggling and needs help, don’t hesitate to
 
 The 2i2c code of conduct is available under the terms of the [CC0 license](https://creativecommons.org/share-your-work/public-domain/cc0/).
 
-Parts of it are based on the [Recurse Center Code of Conduct](https://www.recurse.com/code-of-conduct), the [Jupyter Code of Conduct](https://jupyter.org/governance/conduct/code_of_conduct.html), the [PyLadies Handbook](http://kit.pyladies.com/en/latest/organizer/difficult/responding.html), and the [example conference anti-harassment policy](http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Policy) on the Geek Feminism Wiki, created by the Ada Initiative and other volunteers. It also takes inspiration from [projectinclude's guidelines for Codes of Conduct](https://projectinclude.org/writing_cocs).
+Parts of it are based on the [Recurse Center Code of Conduct](https://www.recurse.com/code-of-conduct), the [Jupyter Code of Conduct](https://jupyter.org/governance/conduct/code_of_conduct.html), the [PyLadies Handbook](http://kit.pyladies.com/en/latest/organizer/difficult/responding.html), and the [example conference anti-harassment policy](http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Policy) on the Geek Feminism Wiki, created by the Ada Initiative and other volunteers. It also takes inspiration from [project include's guidelines for Codes of Conduct](https://projectinclude.org/writing_cocs).
 
 The Recurse Center Code of Conduct and the Geek Feminism conference anti-harassment policy are available under the terms of the CC0 license. The Project Jupyter Code of Conduct and the PyLadies handbook is available under the terms of the [Creative Commons Attribution 3.0 Unported License](https://creativecommons.org/licenses/by/3.0/).