Update CONTRIBUTING. (#491)

Author: Johnny Goodnow

CONTRIBUTING.md

@@ -1,11 +1,11 @@
 # How to contribute to a Stellar project
 
-Your contributions to the [Stellar network](https://www.stellar.org/) will help improve the world’s financial
-infrastructure, faster.
+Your contributions to the [Stellar network](https://www.stellar.org/) will help improve the world’s
+financial infrastructure, faster.
 
-We want to make it as easy as possible to contribute changes that
-help the Stellar network grow and thrive. There are a few guidelines that we
-ask contributors to follow so that we can merge your changes quickly.
+We want to make it as easy as possible to contribute changes that help the Stellar network grow and
+thrive. There are a few guidelines that we ask contributors to follow so that we can merge your
+changes quickly.
 
 ## Getting Started
 
@@ -25,12 +25,17 @@ an issue number.
 
 ## Finding things to work on
 
-The first place to start is always looking over the current GitHub issues for the project you are interested in contributing to. Issues marked with [help wanted](https://github.com/issues?q=is%3Aopen+is%3Aissue+user%3Astellar+label%3A%22help+wanted%22) are usually pretty self-contained and a good place to get started.
+The first place to start is always looking over the current GitHub issues for the project you are
+interested in contributing to. Issues marked with [help wanted][help-wanted] are usually pretty
+self-contained and a good place to get started.
 
-Stellar.org also uses these same GitHub issues to keep track of what we are working on. If you see any issues that are assigned to a particular person or have the `in progress` label, that means someone is currently working on that issue. The `orbit` label means we will likely be working on this issue in the next week or two. The `ready` label means that the issue is one we have prioritized and will be working on in our next orbit (the Stellar term for a sprint) or two.
+Stellar.org also uses these same GitHub issues to keep track of what we are working on. If you see
+any issues that are assigned to a particular person or have the `in progress` label, that means
+someone is currently working on that issue this issue in the next week or two.
 
 Of course, feel free to create a new issue if you think something needs to be added or fixed.
 
+
 ## Making Changes
 
 * Create a topic branch from where you want to base your work.
@@ -40,27 +45,37 @@ Of course, feel free to create a new issue if you think something needs to be ad
 
 ## Submitting Changes
 
-* [Sign the Contributor License Agreement](https://docs.google.com/forms/d/1g7EF6PERciwn7zfmfke5Sir2n10yddGGSXyZsq98tVY/viewform?usp=send_form).
-* All content, comments, and pull requests must follow the [Stellar Community Guidelines](https://www.stellar.org/community-guidelines/).
+* [Sign the Contributor License Agreement][cla].
+* All content, comments, and pull requests must follow the [Stellar Community
+  Guidelines][community-guidelines] and [Code of Conduct][coc]
 * Push your changes to a topic branch in your fork of the repository.
-* Submit a pull request to the [docs repository](https://github.com/stellar/docs) in the Stellar organization.
- * Include a descriptive [commit message](https://github.com/erlang/otp/wiki/Writing-good-commit-messages).
- * Changes contributed via pull request should focus on a single issue at a time.
- * Rebase your local changes against the master branch. Resolve any conflicts that arise.
+* Submit a pull request to the [docs repository](https://github.com/stellar/docs) in the Stellar
+  organization.
+  * Include a descriptive [commit message][commit-msg].
+  * Changes contributed via pull request should focus on a single issue at a time.
+  * Rebase your local changes against the master branch. Resolve any conflicts that arise.
+
 
 At this point you're waiting on us. We like to at least comment on pull requests within three
-business days (typically, one business day). We may suggest some changes, improvements or alternatives.
+business days (typically, one business day). We may suggest some changes, improvements or
+alternatives.
 
 # Additional Resources
 
-* [Contributor License Agreement](https://docs.google.com/forms/d/1g7EF6PERciwn7zfmfke5Sir2n10yddGGSXyZsq98tVY/viewform?usp=send_form)
 * [Explore the API](https://www.stellar.org/developers/reference/)
-* #dev channel on [Keybase](https://keybase.io/team/stellar.public)
-* #dev channel on [Slack](http://slack.stellar.org)
-* #stellar-dev IRC channel on freenode.org
+* [Stack Exchange](http://stellar.stackexchange.com/)
+* #dev-discussion channel on [Keybase](https://keybase.io/team/stellar.public)
+* [Contributor License Agreement][cla]
 
 This document is inspired by:
 
 * https://github.com/puppetlabs/puppet/blob/master/CONTRIBUTING.md
 * https://github.com/thoughtbot/factory_girl_rails/blob/master/CONTRIBUTING.md
 * https://github.com/rust-lang/rust/blob/master/CONTRIBUTING.md
+
+[help-wanted]: https://github.com/issues?q=is%3Aopen+is%3Aissue+user%3Astellar+label%3A%22help+wanted%22
+[commit-msg]: https://github.com/erlang/otp/wiki/Writing-good-commit-messages
+[cla]: https://docs.google.com/forms/d/1g7EF6PERciwn7zfmfke5Sir2n10yddGGSXyZsq98tVY/viewform?usp=send_form
+[community-guidelines]: https://www.stellar.org/community-guidelines/
+[coc]: https://github.com/stellar/.github/blob/master/CODE_OF_CONDUCT.md
+