Merge pull request #4725 from reardonj/code-of-conduct-docs

Author: danicheg

CONTRIBUTING.md

@@ -1,4 +1,4 @@
-# Contributor guide
+# Contributor Guide
 
 ## About this document
 
@@ -251,7 +251,7 @@ feature, or have a question about the code. Pull requests are also
 gladly accepted.
 
 People are expected to follow the
-[Scala Code of Conduct](https://www.scala-lang.org/conduct/) when
+[Typelevel Code of Conduct](https://typelevel.org/code-of-conduct.html) when
 discussing Cats on GitHub, Discord, or other venues.
 
 We hope that our community will be respectful, helpful, and kind. If

README.md

@@ -131,7 +131,7 @@ The [Typelevel Discord](https://discord.gg/XF3CXcMzqD) has \#cats and \#cats-dev
 channels, as well as community channels such as \#beginners.  Please join us!
 
 People are expected to follow the
-[Scala Code of Conduct](https://www.scala-lang.org/conduct/) when
+[Typelevel Code of Conduct](https://typelevel.org/code-of-conduct.html) when
 discussing Cats on GitHub, Discord, or other venues.
 
 We hope that our community will be respectful, helpful, and kind. If

docs/faq.md

@@ -27,7 +27,7 @@ Please refer to the [jump start guide](jump_start_guide.md).
 
 Cats and [Scalaz](https://github.com/scalaz/scalaz) have the same goal: to facilitate pure functional programming in Scala applications. However the underlying core strategy is different; Scalaz took the approach of trying to provide a single batteries-included *standard library* for FP that powers the Scala applications. Cats, on the other hand, aims to help build an [ecosystem](typelevelEcosystem.md) of pure FP libraries by providing a solid and stable foundation; these libraries can have their own styles and personalities, competing with each other, while at the same time playing nice. It is through this ecosystem of FP libraries (cats included) that Scala applications can be powered with "FP awesome-ness" and beyond by picking whatever best fit their needs.
 
-Based on this core strategy, Cats takes a [modular](motivations.md#modularity) approach and focuses on providing core, [binary compatible](index.md#binary-compatibility-and-versioning), [approachable](motivations.md#approachability) and [efficient](motivations.md#efficiency) abstractions. It provides a welcoming and supportive environment for the [user community](https://discord.gg/XF3CXcMzqD) governed by the [Scala Code of Conduct](https://www.scala-lang.org/conduct/). It also takes great effort in supplying a comprehensive and beginner-friendly [documentation](motivations.md#documentation).
+Based on this core strategy, Cats takes a [modular](motivations.md#modularity) approach and focuses on providing core, [binary compatible](index.md#binary-compatibility-and-versioning), [approachable](motivations.md#approachability) and [efficient](motivations.md#efficiency) abstractions. It provides a welcoming and supportive environment for the [user community](https://discord.gg/XF3CXcMzqD) governed by the [Typelevel Code of Conduct](https://typelevel.org/code-of-conduct.html). It also takes great effort in supplying a comprehensive and beginner-friendly [documentation](motivations.md#documentation).
 
 ## Where is right-biased Either?
 Up through Cats 0.7.x we had `cats.data.Xor`, which was effectively `scala.util.Either`, but right-biased by default and with

docs/index.md

@@ -117,7 +117,7 @@ The [Typelevel Discord](https://discord.gg/XF3CXcMzqD) has \#cats and \#cats-dev
 channels, as well as community channels such as \#beginners.  Please join us!
 
 People are expected to follow the
-[Scala Code of Conduct](https://www.scala-lang.org/conduct/) when
+[Typelevel Code of Conduct](https://typelevel.org/code-of-conduct.html) when
 discussing Cats on GitHub, Discord, or other venues.
 
 We hope that our community will be respectful, helpful, and kind. If