Update links, emails and other info (#7)

Signed-off-by: Tim Beiko <t.beiko23@gmail.com>

Author: timbeiko

CLA.md

@@ -1,6 +1,6 @@
 # Sign the CLA
 
-This page is the step-by-step guide to signing the Consensys AG
+This page is the step-by-step guide to signing the Consensys Software Inc. 
 Individual Contributor License Agreement.
 
 1. First and foremost, read [the current version of the CLA].
@@ -11,8 +11,7 @@ Individual Contributor License Agreement.
 3. After creating your first pull request, you will see a merge
    pre-requisite requiring to you read and sign the CLA.
 
-If you have any questions, you can reach us at [support@pegasys.tech].
+If you have any questions, you can reach us [here](https://codefi.consensys.net/orchestrate-get-in-touch).
 
 [github]: https://github.com/
-[the current version of the cla]: https://gist.github.com/rojotek/978b48a5e8b68836856a8961d6887992
-[support@pegasys.tech]: mailto:support@pegasys.tech
+[the current version of the cla]: https://gist.github.com/rojotek/978b48a5e8b68836856a8961d6887992

CODE-OF-CONDUCT.md

@@ -55,7 +55,7 @@ further defined and clarified by project maintainers.
 ## Enforcement
 
 Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported by contacting the project team at [private@pegasys.tech]. All
+reported by contacting the project team at [private-quorum@consensys.net]. All
 complaints will be reviewed and investigated and will result in a response that
 is deemed necessary and appropriate to the circumstances. The project team is
 obligated to maintain confidentiality with regard to the reporter of an incident.
@@ -71,4 +71,4 @@ This Code of Conduct is adapted from the [Contributor Covenant], version 1.4,
 available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
 
 [contributor covenant]: https://www.contributor-covenant.org
-[private@pegasys.tech]: mailto:private@pegasys.tech
+[private-quorum@consensys.net]: mailto:private-quorum@consensys.net

CONTRIBUTING.md

@@ -21,11 +21,11 @@ Welcome to the Orchestrate repositories! The following is a set of guidelines fo
 
 ## Code of Conduct
 
-This project and everyone participating in it is governed by the [Orchestrate Code of Conduct](CODE-OF-CONDUCT.md). By participating, you are expected to uphold this code. Please report unacceptable behavior to [private@pegasys.tech].
+This project and everyone participating in it is governed by the [Orchestrate Code of Conduct](CODE-OF-CONDUCT.md). By participating, you are expected to uphold this code. Please report unacceptable behavior to [private-quorum@consensys.net].
 
 ## I just have a quick question
 
-Send us an email at [support@pegasys.tech] and that's the fastest way to get an answer.
+Contact us [here](https://codefi.consensys.net/orchestrate-get-in-touch), that's the fastest way to get an answer.
 
 ## How To Contribute
 
@@ -106,5 +106,5 @@ Include details about your configuration and environment:
 - Provide a summary on the first line with more details on additional lines as needed
 - Reference issues and pull requests liberally
 
-[private@pegasys.tech]: mailto:private@pegasys.tech
+[private-quorum@consensys.net]: mailto:private-quorum@consensys.net
 [cla.md]: /CLA.md

GOVERNANCE.md

@@ -1,6 +1,6 @@
 # Overview
 
-This project is led by a benevolent dictator (PegaSys) and managed by the community. That is, the community actively contributes to the day-to-day maintenance of the project, but the general strategic line is drawn by the benevolent dictator. In case of disagreement, they have the last word. It is the benevolent dictator’s job to resolve disputes within the community and to ensure that the project is able to progress in a coordinated way. In turn, it is the community’s job to guide the decisions of the benevolent dictator through active engagement and contribution.
+This project is led by a benevolent dictator (ConsenSys) and managed by the community. That is, the community actively contributes to the day-to-day maintenance of the project, but the general strategic line is drawn by the benevolent dictator. In case of disagreement, they have the last word. It is the benevolent dictator’s job to resolve disputes within the community and to ensure that the project is able to progress in a coordinated way. In turn, it is the community’s job to guide the decisions of the benevolent dictator through active engagement and contribution.
 
 # Principles
 

community-membership.md

@@ -8,9 +8,9 @@ this project.
 | Everyone            | none                                         | anybody with a belly button |
 | Member              | everyone who contributes - code or otherwise | Orchestrate org member      |
 | Approver            | approve accepting contributions              | write permissions on master |
-| Project Sponsor     | contribute developer resources               | PegaSys                     |
-| Project Evangelist  | promote the project                          | PegaSys                     |
-| Benevolent Dictator | decision tie-breaker                         | PegaSys                     |
+| Project Sponsor     | contribute developer resources               | ConsenSys                     |
+| Project Evangelist  | promote the project                          | ConsenSys                     |
+| Benevolent Dictator | decision tie-breaker                         | ConsenSys                     |
 
 ## Everyone
 
@@ -84,7 +84,7 @@ Code approvers are members that have signed an ICLA and have been granted additi
 
 The Project Sponsor role provides a user with the ability to contribute additional developer resources to the project. Project Sponsors must sign the ICLA.
 
-**Defined by:** PegaSys
+**Defined by:** ConsenSys
 
 ### Requirements
 
@@ -99,7 +99,7 @@ The Project Sponsor role provides a user with the ability to contribute addition
 ## Project Evangelist
 
 The Project Evangelist role is for those who wish to promote the project to the outside world, but not actively contribute to it.  
-**Defined by:** PegaSys
+**Defined by:** ConsenSys
 
 ### Requirements