spelling: github

CHANGELOG.md

@@ -1957,7 +1957,7 @@ The following notable changes have been made since the 2.0 Preview announcement.
 
 - update CHANGELOG for 1.0.6 ([commit](https://github.com/Polymer/polymer/commit/c46ec11))
 
-\* *This Change Log was automatically generated by [github_changelog_generator](https://github.com/skywinder/Github-Changelog-Generator) below*
+\* *This Change Log was automatically generated by [github_changelog_generator](https://github.com/skywinder/GitHub-Changelog-Generator) below*
 ## [v1.0.6](https://github.com/Polymer/polymer/tree/v1.0.6) (2015-07-09)
 
 **Fixed issues:**
@@ -3932,7 +3932,7 @@ The following notable changes have been made since the 2.0 Preview announcement.
 
 - Input examples do not work in iPad iOS 7.1.1 [\#558](https://github.com/Polymer/polymer/issues/558)
 
-- Demo & Edit on Github links not working on component page [\#557](https://github.com/Polymer/polymer/issues/557)
+- Demo & Edit on GitHub links not working on component page [\#557](https://github.com/Polymer/polymer/issues/557)
 
 - Download link for checkboxes is broken [\#556](https://github.com/Polymer/polymer/issues/556)
 
@@ -3958,7 +3958,7 @@ The following notable changes have been made since the 2.0 Preview announcement.
 
 - Sidebar menu elements are overlaid [\#541](https://github.com/Polymer/polymer/issues/541)
 
-- Edit on Github Link returning 404 error [\#540](https://github.com/Polymer/polymer/issues/540)
+- Edit on GitHub Link returning 404 error [\#540](https://github.com/Polymer/polymer/issues/540)
 
 - rendering problems with new website in FF on osx [\#539](https://github.com/Polymer/polymer/issues/539)
 

CONTRIBUTING.md

@@ -6,7 +6,7 @@ There are many ways to contribute to the Polymer project! We welcome and truly a
 
 ### Communicating with the Polymer team
 
-Beyond Github, we try to have a variety of different lines of communication open:
+Beyond GitHub, we try to have a variety of different lines of communication open:
 
 * [Blog](https://blog.polymer-project.org/)
 * [Twitter](https://twitter.com/polymer)
@@ -36,7 +36,7 @@ If you've already signed a CLA but are still getting bothered by the awfully ins
 
 ### Filing bugs
 
-The Polymer team heavily uses (and loves!) Github for all of our software management. We use Github issues to track all bugs and features.
+The Polymer team heavily uses (and loves!) GitHub for all of our software management. We use GitHub issues to track all bugs and features.
 
 If you find an issue, please do file it on the repository. The [Polymer/polymer issues](https://github.com/polymer/polymer/issues) should be used only for issues on the Polymer library itself - bugs somewhere in the core codebase.
 
@@ -52,7 +52,7 @@ PR's are even better than issues. We gladly accept community pull requests. In g
 
 - Open an issue describing the problem that you are looking to solve in your PR (if one is not already open), and your approach to solving it. This makes it easier to have a conversation around the best general approach for solving your problem, outside of the code itself.
 - Sign the [CLA](https://cla.developers.google.com/clas), as described above.
-- Fork the repo you're making the fix on to your own Github account.
+- Fork the repo you're making the fix on to your own GitHub account.
 - Code!
 - Ideally, squash your commits into a single commit with a clear message of what the PR does. If it absolutely makes sense to keep multiple commits, that's OK - or perhaps consider making two separate PR's.
 - **Include tests that test the range of behavior that changes with your PR.** If you PR fixes a bug, make sure your tests capture that bug. If your PR adds new behavior, make sure that behavior is fully tested. Every PR *must* include associated tests. (See [Unit tests](#unit-tests) for more.)

README.md

@@ -224,7 +224,7 @@ The Polymer team loves contributions from the community! Take a look at our [con
 
 ## Communicating with the Polymer team
 
-Beyond Github, we try to have a variety of different lines of communication available:
+Beyond GitHub, we try to have a variety of different lines of communication available:
 
 * [Blog](https://blog.polymer-project.org/)
 * [Twitter](https://twitter.com/polymer)