fix Github -> GitHub

Author: SethTisue

blog/_posts/2016-05-30-scala-center-advisory-board.md

@@ -91,7 +91,7 @@ I mentioned at the beginning that it's important for the Advisory Board to make
 good on its promise, but it's just as important that we are *seen* to be doing
 so. So the whole Advisory Board process is open, and we will publish the
 proposals and minutes from each meeting. You will be able to see these in the
-Advisory Board's [Github
+Advisory Board's [GitHub
 repository](https://github.com/scalacenter/advisoryboard/) in the next few
 days.
 

contribute/codereviews.md

@@ -43,7 +43,7 @@ own pull requests.
 <p>The Scala language web site.</p>
 </div>
 <div class="span4 doc-block">
-<h4><a href="https://github.com/scala">All Scala Github Projects</a></h4>
+<h4><a href="https://github.com/scala">All Scala GitHub Projects</a></h4>
 <p>For other PRs, follow the scala project from here.</p>
 </div>
 </div>

news/_posts/2013-03-20-gsoc13.md

@@ -39,7 +39,7 @@ The to goal of this project is to extend the desugaring of for-comprehensions in
 
 ### Alternative / social Scala documentation
 
-This project has two  parts. First you will work on generating alternative api documentation  formats for Scaladoc. You will need to hook into the scaladoc part of  the scala compiler, to access and work with Scaladoc's code model. We  have a small prototype you can use as a starting point. You should then  generate documentation in (non-framed, non-js) single/multi-page HTML,  PDF, CHM formats. The result should make sensible use of the scaladoc  @-commands and you should think about a good way to present apis  designed as in cake patterns. HTML-Formats should support external  linking to methods. You can use a documentation generator such as Sphinx  to help generating different formats. The second part of this project  concerns collaboration. You will need to come up with smart and simple  ideas and an implementation how to make Scala api documentation more  social, favorably in a way that can be shared between the different HTML  doc formats. It can be as simple as adding Github Links and Disqus or  more involved. Make sure to also review the work  that has been done on [Colladoc](http://colladoc.github.com/). We are very open for your own new or alternative ideas  regarding any aspect of this project.  Good knowledge of modern, accessible HTML/CSS and possibly JS will be  helpful. We want to work with you in an agile, ticket-based development  style with frequent communication and coordination.
+This project has two  parts. First you will work on generating alternative api documentation  formats for Scaladoc. You will need to hook into the scaladoc part of  the scala compiler, to access and work with Scaladoc's code model. We  have a small prototype you can use as a starting point. You should then  generate documentation in (non-framed, non-js) single/multi-page HTML,  PDF, CHM formats. The result should make sensible use of the scaladoc  @-commands and you should think about a good way to present apis  designed as in cake patterns. HTML-Formats should support external  linking to methods. You can use a documentation generator such as Sphinx  to help generating different formats. The second part of this project  concerns collaboration. You will need to come up with smart and simple  ideas and an implementation how to make Scala api documentation more  social, favorably in a way that can be shared between the different HTML  doc formats. It can be as simple as adding GitHub Links and Disqus or  more involved. Make sure to also review the work  that has been done on [Colladoc](http://colladoc.github.com/). We are very open for your own new or alternative ideas  regarding any aspect of this project.  Good knowledge of modern, accessible HTML/CSS and possibly JS will be  helpful. We want to work with you in an agile, ticket-based development  style with frequent communication and coordination.
 
 * * *