Update references to Contributor Covenant 2.0 for 2.1

Also auto removed trailing white space on save. Ignore white space to diff

Author: Relequestual

FOUNDATION_CODE_OF_CONDUCT_REQUIREMENTS.md

@@ -1,7 +1,7 @@
 # Foundation Code of Conduct Requirements
 
 It is important that there be a Code of Conduct (CoC) which
-is documented and enforced for the OpenJS Foundation, 
+is documented and enforced for the OpenJS Foundation,
 hereinafter referred to as the "Foundation", and the
 projects within it. This document defines the requirements
 for a CoC for the Foundation and the projects which are part
@@ -11,7 +11,7 @@ of the foundation.
 ## Code of Conduct
 
 The Foundation has adopted the
-[Contributor Covenant v2.0](https://www.contributor-covenant.org/version/2/0/code_of_conduct/)
+[Contributor Covenant v2.1](https://www.contributor-covenant.org/version/2/1/code_of_conduct/)
 as its code of conduct and it applies to all foundation activities and spaces. In
 addition, projects joining the foundation are required to adopt this code of conduct
 within 3 months of joining the foundation.
@@ -23,12 +23,12 @@ the Code of Conduct.
 ## Enforcement
 
 For spaces managed by the Foundation, complaints can be forwarded to [email protected] and will
-be investigated by the Cross Project Council (CPC) or its delegates. All complaints will be reviewed, 
+be investigated by the Cross Project Council (CPC) or its delegates. All complaints will be reviewed,
 investigated, and will result in a response that is deemed necessary and appropriate
 to the circumstances. The CPC is obligated to maintain confidentiality with regard
 to the reporter of an incident.
 
-For spaces managed by member projects, the project must provide an email to which complaints 
+For spaces managed by member projects, the project must provide an email to which complaints
 can be forwarded and document that complaints will be investigated and will result in a
 response that is deemed appropriate for the circumstances. Each project is free to
 implement enforcement of the Code of Conduct using processes appropriate for the size
@@ -49,7 +49,7 @@ report can be made to [email protected].
 All escalations will be reviewed and investigated by the Code of Conduct Panel (CoCP)
 and will result in a response that is deemed necessary and appropriate to the circumstances.
 The Code of Conduct panel is obligated to maintain confidentiality with regard
-to the reporter of an escalation. 
+to the reporter of an escalation.
 
 ### Code of Conduct panel
 

HANDLING_CODE_OF_CONDUCT_REPORTS.md

@@ -4,20 +4,20 @@ This document describes the proposed process for handling reports and escalation
 This process covers two types of reports based on the [Foundation's Code of Conduct Requirements](https://github.com/openjs-foundation/cross-project-council/blob/HEAD/FOUNDATION_CODE_OF_CONDUCT_REQUIREMENTS.md):
 
 * Reports for spaces managed by the Cross Project Council (CPC) which come in through `[email protected]`
-* Escalations which come in through `[email protected]`.   
+* Escalations which come in through `[email protected]`.
 
 Generally, reports to coc-escalation should refer to a report that was already submitted to:
 
 * [email protected] or
-* one of the project's reporting emails 
+* one of the project's reporting emails
 * explanation of why the reporter does not feel comfortable using the previous reporting emails for the initial report
 
-If a report to coc-esclation does not include one of those, the reporter will be asked to to provide one of those three as the 
+If a report to coc-esclation does not include one of those, the reporter will be asked to to provide one of those three as the
 reason for reporting to coc-escalation.
 
 ## Code of Conduct
 
-The OpenJS Foundation and its member projects use the Contributor Covenant v2.0 as its Code of Conduct. Refer to the [Code of Conduct](https://github.com/openjs-foundation/cross-project-council/blob/HEAD/CODE_OF_CONDUCT.md) for the full text of the CoC and the reporting and esclation procedures.
+The OpenJS Foundation and its member projects use the Contributor Covenant v2.1 as its Code of Conduct. Refer to the [Code of Conduct](https://github.com/openjs-foundation/cross-project-council/blob/HEAD/CODE_OF_CONDUCT.md) for the full text of the CoC and the reporting and esclation procedures.
 
 ## Confidentiality and record-keeping
 Personal information is confidential. All reports should be recorded, together with the discussion of it. The following private repos will be used to record and discuss reports.
@@ -44,16 +44,16 @@ All members of the CPC are subscribed to the `[email protected]` mailing list.
      1. Information is discussed: The facts are discussed in context of opinions. This can be done in the issue for the report, or in a meeting in which case the key discussion points should then be added to the issue.
      1. An action to be taken is arrived at: The action to be taken is decided by consensus as per the standard CPC
         [Decision Making](https://github.com/openjs-foundation/cross-project-council/blob/HEAD/CPC-CHARTER.md#section-9-decision-making) process.
-     1. Resolution shared: The resolution is shared with the reporter or target by the contact person. If the reporter or target expresses concerns then the contact person will bring these back to the CPC members for further discussion. This cycle can continue until the CPC members reach consensus that the reporter or target's concerns have been adquately addressed. If no feedback is received within 7 days the resolution is considered as accepted. 
+     1. Resolution shared: The resolution is shared with the reporter or target by the contact person. If the reporter or target expresses concerns then the contact person will bring these back to the CPC members for further discussion. This cycle can continue until the CPC members reach consensus that the reporter or target's concerns have been adquately addressed. If no feedback is received within 7 days the resolution is considered as accepted.
      1. Final resolution: the resolution agreed by the CPC members is implemented and the outcome reported to the reporter or target by the main contact.
-        
+
 ## Reports to [email protected]
 
 Note: We understand that the reporter and the target can be separate persons. In this case the CPC will communicate with the reporter unless the target gives permission for the CPC to communicate with them.
 
 All members of the [Code of Conduct Panel (CoCP)](https://github.com/openjs-foundation/cross-project-council/blob/HEAD/FOUNDATION_CODE_OF_CONDUCT_REQUIREMENTS.md#code-of-conduct-panel)
 are subscribed to the [email protected] mailing list. The current list of members is documented in ./CODE_OF_CONDUCT_PANEL_MEMERS.md.
-     
+
 When a report is received the following actions will be taken:
 
   * One of the Code of Conduct Panel (CoCP) members will respond to the reporter or target confirming that the report has been received. When possible the same person who responds initially will act as the point of contact for future conversations.
@@ -67,6 +67,6 @@ When a report is received the following actions will be taken:
         [Decision Making](https://github.com/openjs-foundation/cross-project-council/blob/HEAD/CPC-CHARTER.md#section-9-decision-making) process substituting in CoCP for references to the CPC.
      1. The proposed action is discussed with the leadership for the space to which the report applies (ex CPC or member
         project leadership). If the leadership representatives expresses concerns then the contact person will bring these back to the CoCP members for further discussion.  This cycle can continue until the CoCP members reach consensus that the leadership representatives concerns have been adequately addressed.
-     1. Resolution shared: The resolution is shared with the reporter or target by the contact person. If the reporter or target expresses concerns then the contact person will bring these back to the CPC members for further discussion. This cycle can continue until the CPC members reach consensus that the reporter or target's concerns have been adquately addressed. If no feedback is received within 7 days the resolution is considered as accepted. 
+     1. Resolution shared: The resolution is shared with the reporter or target by the contact person. If the reporter or target expresses concerns then the contact person will bring these back to the CPC members for further discussion. This cycle can continue until the CPC members reach consensus that the reporter or target's concerns have been adquately addressed. If no feedback is received within 7 days the resolution is considered as accepted.
      1. Final resolution: the resolution agreed by the CoCP members is implemented and the outcome reported back to the reporter or target bythe main contact.
-      
+