docs: remove links (#112)

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,6 +1,6 @@
 ## Related issues
 
-Link any related Github issues here in the format of `closes #1`. If this change doesn't resolve an existing issue, please discuss it with us before submitting this PR. We're available on our [Discord server](https://discord.gg/gMfXeXR).
+Link any related Github issues here in the format of `closes #1`. If this change doesn't resolve an existing issue, please discuss it with us before submitting this PR.
 
 ## Proposed changes
 

CONTRIBUTING.md

@@ -6,11 +6,11 @@ Thanks for taking the time to contribute. You're the best! Around! Nothing's gon
 
 ## Code of conduct
 
-This project is governed by the [Contributor Covenant Code of Conduct](CODE_OF_CONDUCT.md). We want to cultivate a respectful and constructive environment for everyone involved, and we expect all other contributors to do the same. Please use Github's reporting features if you have any concerns or reach out to us directly via our [Discord server](https://discord.gg/gMfXeXR).
+This project is governed by the [Contributor Covenant Code of Conduct](CODE_OF_CONDUCT.md). We want to cultivate a respectful and constructive environment for everyone involved, and we expect all other contributors to do the same. Please use Github's reporting features if you have any concerns.
 
 ## Asking general questions
 
-Discord is generally the fastest way to get in touch with us if you have general questions. We try to answer questions in a timely manner. If you have a bug report or feature request, feel free to discuss it with us there or just open an issue with as much detail as possible.
+We try to answer questions in a timely manner. If you have a bug report or feature request, feel free to open an issue with as much detail as possible.
 
 ## Ways to contribute
 
@@ -30,15 +30,15 @@ We use the [conventional commit](https://www.conventionalcommits.org/en/v1.0.0/)
 * test (a change that only includes tests)
 * chore (a change to CI, etc)
 
-Lastly, make sure your commit is signed before submitting the pull request. If you're not sure how to do this, Github has helpful [instructions](https://help.github.com/en/github/authenticating-to-github/signing-commits) or you can ask us for help on Discord.
+Lastly, make sure your commit is signed before submitting the pull request. If you're not sure how to do this, Github has helpful [instructions](https://help.github.com/en/github/authenticating-to-github/signing-commits).
 
 ### Fixing bugs
 
 Open a pull request with the patch, and please include a description that clearly describes the problem and solution and references a relevant issue number if applicable. Please also include a test case that covers the previous bug so that the issue won't occur again.
 
 ### Adding new features
 
-If you have an idea for a new feature, please first discuss it with us on Discord or submit a new issue tagged with the `enhancement` label. If we decide to adopt the feature, you're also welcome to submit a pull request if you have the time and inclination for it. Currently, we have no strict requirements around the design of new features. However, we ask that you try to follow the conventions of the current codebase, and feel free to discuss any design issues before submitting.
+If you have an idea for a new feature, please first discuss it with us by submitting a new issue tagged with the `enhancement` label. If we decide to adopt the feature, you're also welcome to submit a pull request if you have the time and inclination for it. Currently, we have no strict requirements around the design of new features. However, we ask that you try to follow the conventions of the current codebase, and feel free to discuss any design issues before submitting.
 
 ### Fixing whitespace, formatting code, or making purely cosmetic patches
 

README.md

@@ -1,6 +1,6 @@
 # eris ![Logo][eris-logo]
 
-[![GoDoc][doc-img]][doc] [![Build][ci-img]][ci] [![GoReport][report-img]][report] [![Coverage Status][cov-img]][cov] [![Discord][chat-img]][chat]
+[![GoDoc][doc-img]][doc] [![Build][ci-img]][ci] [![GoReport][report-img]][report] [![Coverage Status][cov-img]][cov]
 
 Package `eris` provides a better way to handle, trace, and log errors in Go.
 
@@ -310,7 +310,7 @@ Many of your dependencies will likely still use [pkg/errors](https://github.com/
 
 ## Contributing
 
-If you'd like to contribute to `eris`, we'd love your input! Please submit an issue first so we can discuss your proposal. We're also available to discuss potential issues and features on our [Discord channel](https://discord.gg/gMfXeXR).
+If you'd like to contribute to `eris`, we'd love your input! Please submit an issue first so we can discuss your proposal.
 
 -------------------------------------------------------------------------------
 
@@ -326,5 +326,3 @@ Released under the [MIT License].
 [report]: https://goreportcard.com/report/github.com/rotisserie/eris
 [cov-img]: https://codecov.io/gh/rotisserie/eris/branch/master/graph/badge.svg
 [cov]: https://codecov.io/gh/rotisserie/eris
-[chat-img]: https://img.shields.io/discord/659952923073183749?color=738adb&label=discord&logo=discord
-[chat]: https://discord.gg/gMfXeXR