Update CONTRIBUTING.md
Use markdown reflinks for readability
@@ -12,9 +12,9 @@ We love your input! We want to make contributing to this project as easy and tra
We use PlexTraktSync to host code, to track issues and feature requests, as well as accept pull requests.
-## We Use [Github Flow](https://guides.github.com/introduction/flow/index.html), So All Code Changes Happen Through Pull Requests
+## We Use [GitHub Flow], So All Code Changes Happen Through Pull Requests
-Pull requests are the best way to propose changes to the codebase (we use [Github Flow](https://guides.github.com/introduction/flow/index.html)). We actively welcome your pull requests:
+Pull requests are the best way to propose changes to the codebase (we use [GitHub Flow]). We actively welcome your pull requests:
1. Fork the repo and create your branch from `master`.
2. If you've added code that should be tested, add tests.
@@ -23,14 +23,20 @@ Pull requests are the best way to propose changes to the codebase (we use [Githu
5. Make sure your code lints.
6. Issue that pull request!
+[GitHub Flow]: https://guides.github.com/introduction/flow/index.html
+
## Any contributions you make will be under the MIT Software License
-In short, when you submit code changes, your submissions are understood to be under the same [MIT License](http://choosealicense.com/licenses/mit/) that covers the project. Feel free to contact the maintainers if that's a concern.
+In short, when you submit code changes, your submissions are understood to be under the same [MIT License] that covers the project. Feel free to contact the maintainers if that's a concern.
+
+[MIT License]: http://choosealicense.com/licenses/mit/
-## Report bugs using Github's [issues](https://github.com/briandk/transcriptase-atom/issues)
+## Report bugs using GitHub's [issues]
We use GitHub issues to track public bugs. Report a bug by [opening a new issue](); it's that easy!
+[issues]: https://github.com/Taxel/PlexTraktSync/issues
+
## Write bug reports with detail, background, and sample code
[This is an example](http://stackoverflow.com/q/12488905/180626) of a bug report I wrote, and I think it's not a bad model. Here's [another example from Craig Hockenberry](http://www.openradar.me/11905408), an app developer whom I greatly respect.
@@ -49,15 +55,19 @@ People *love* thorough bug reports. I'm not even kidding.
## Use a Consistent Coding Style
-I'm again borrowing these from [Facebook's Guidelines](https://github.com/facebook/draft-js/blob/a9316a723f9e918afde44dea68b5f9f39b7d9b00/CONTRIBUTING.md)
+I'm again borrowing these from [Facebook's Guidelines]
* 2 spaces for indentation rather than tabs
* You can try running `npm run lint` for style unification
+[Facebook's Guidelines]: https://github.com/facebook/draft-js/blob/a9316a723f9e918afde44dea68b5f9f39b7d9b00/CONTRIBUTING.md
+
## License
By contributing, you agree that your contributions will be licensed under its MIT License.
## References
-This document was adapted from the open-source contribution guidelines for [Facebook's Draft](https://github.com/facebook/draft-js/blob/a9316a723f9e918afde44dea68b5f9f39b7d9b00/CONTRIBUTING.md)
+This document was adapted from the open-source contribution guidelines for [Facebook's Draft]
+
+[Facebook's Draft]: https://github.com/facebook/draft-js/blob/a9316a723f9e918afde44dea68b5f9f39b7d9b00/CONTRIBUTING.md
