scala · SethTisue · Nov 16, 2016 · Nov 16, 2016
diff --git a/_layouts/downloadpage.html b/_layouts/downloadpage.html
@@ -60,7 +60,7 @@
 </div>
 
 <h3>Release Notes</h3>
-For important changes, please consult the <a href="{{ site.baseurl }}/news/{{ page.release_version }}">release notes</a>.
+For important changes, please consult the <a href="{{ site.baseurl }}/news#announcements--changelog">release notes</a>.
 
 <h3>Software Requirements</h3>
 

diff --git a/_layouts/page.html b/_layouts/page.html
@@ -42,7 +42,7 @@ <h1 id="page-title">{{ page.title }}</h1>
               <div id="toc"></div>
               <br/>
               <div class="alert-info">
-                <a href="/contribute/documentation.html#updating_scalalangorg"><p><strong>Problem with this page?</strong>
+                <a href="/contribute/documentation.html#updating-scala-langorg"><p><strong>Problem with this page?</strong>
                 Please help us fix it!</p></a>
               </div>
             </div>

diff --git a/blog/_posts/2016-03-14-announcing-the-scala-center.md b/blog/_posts/2016-03-14-announcing-the-scala-center.md
@@ -24,7 +24,7 @@ half a million developers are using Scala.
 Scala is the technology of choice for a vibrant open-source ecosystem,
 including popular platforms and frameworks such as
 [Spark](http://spark.apache.org/), [Kafka](http://kafka.apache.org/),
-[Akka](akka.io), [Finagle](https://twitter.github.io/finagle),
+[Akka](http://akka.io), [Finagle](https://twitter.github.io/finagle),
 [Cats](http://typelevel.org/cats/), and
 [Play](https://www.playframework.com/), to name just a few.
 

diff --git a/blog/_posts/2016-05-23-scala-moocs-specialization-launched.md b/blog/_posts/2016-05-23-scala-moocs-specialization-launched.md
@@ -34,6 +34,4 @@ you can visit each course's landing page:
 - **[Parallel Programming](https://www.coursera.org/learn/parprog1/)**
 
 More info about each course can be found on the [Scala Specialization page](https://www.coursera.org/specializations/scala), or on
-the [Scala Center's website](https://scala.epfl.ch/). Questions, or to join the discussion about the Scala Center, visit us in the [Scala Center gitter channel](gitter.im/scala/center)!
-
-
+the [Scala Center's website](https://scala.epfl.ch/). Questions, or to join the discussion about the Scala Center, visit us in the [Scala Center gitter channel](https://gitter.im/scala/center)!
diff --git a/contribute/codereviews.md b/contribute/codereviews.md
@@ -5,7 +5,7 @@ title: Code Review Contributions
 ## Code Review Contributions
 
 In addition to [bug fixing](./guide.html), you can help us review 
-[waiting pull requests](#pull_requests_awaiting_comment). 
+[waiting pull requests](#pull-requests-awaiting-comment). 
 This is also a good (and recommended) way to get to know the feel of
 the bug-fixing and submissions process before jumping in with your
 own pull requests.

diff --git a/contribute/documentation.md b/contribute/documentation.md
@@ -21,7 +21,7 @@ Thanks
 
 The Scala API documentation lives with the scala project source code. There are many ways you can help with improving Scaladoc, including:
 
-* [Log issues for missing scaladoc documentation](./scala-standard-library-api-documentation.html#contribute_api_documentation_bug_reports) - 
+* [Log issues for missing scaladoc documentation](./scala-standard-library-api-documentation.html#contribute-api-documentation-bug-reports) - 
 Please *follow the issue submission process closely* to help prevent duplicate issues being created.
 * [Claim Scaladoc Issues and Provide Documentation](./scala-standard-library-api-documentation.html) - please claim issues prior to working on a specific scaladoc task to prevent duplication of effort. If you sit on an issue for too long without submitting a pull request, it will revert back to unassigned and you will need to re-claim it.
 * You can also just 
@@ -61,4 +61,3 @@ to Scala and related projects) is provided on the main
 
 Please read both the
 [docs.scala-lang.org contribution](http://docs.scala-lang.org/contribute.html) document and the [scala-lang.org github README](https://github.com/scala/scala-lang#scala-langorg) before embarking on any changes to the Scala language site, as it uses the same Jekyll markdown tool and many of the same conventions as the Scala documentation site.
-
diff --git a/contribute/guide.md b/contribute/guide.md
@@ -17,7 +17,7 @@ title: Contributing guide
 
   <div class="row">
     <div class="span4 doc-block">
-      <h3><a href="{{ site.baseurl }}/contribute/#community_tickets">Community issues</a></h3>
+      <h3><a href="{{ site.baseurl }}/contribute/#community-tickets">Community issues</a></h3>
       <p>Get cracking on some easy to approach issues.</p>
     </div>
     <div class="span4 doc-block">
@@ -52,9 +52,9 @@ unencumbered by copyrights or patents.
 
 This is the impatient developer's checklist for the steps to submit a bug-fix pull request to the Scala project. For more information, description and justification for the steps, follow the links in that step. Further specific instructions for the release of Scala you are targeting can be found in the `CONTRIBUTING.md` file for that [github branch](https://github.com/scala/scala)
 
-1. [Select a bug to fix from JIRA](/contribute/index.html#community_tickets), or if you found the bug yourself and want to fix it, [create a JIRA issue](./bug-reporting-guide.html) (but please 
-[make sure it's not a duplicate](./bug-reporting-guide.html#reporting_confirmed_bugs_is_a_sin)).
-2. Optional ([but recommended](./scala-internals.html#why_its_a_good_idea)), announce your intention to work on the bug on [scala-internals](./scala-internals.html). After all, don't you want to work on a team with 
+1. [Select a bug to fix from JIRA](/contribute/index.html#community-tickets), or if you found the bug yourself and want to fix it, [create a JIRA issue](./bug-reporting-guide.html) (but please 
+[make sure it's not a duplicate](./bug-reporting-guide.html#reporting-confirmed-bugs-is-a-sin)).
+2. Optional ([but recommended](./scala-internals.html#why-its-a-good-idea)), announce your intention to work on the bug on [scala-internals](./scala-internals.html). After all, don't you want to work on a team with 
 [these friendly people](./hacker-guide.html#connect) - it's one of the perks of contributing.
 3. [Fork the Scala repository](./hacker-guide.html#fork) and clone your fork (if you haven't already).
 4. [Create a feature branch](./hacker-guide.html#branch) to work on: use the branch name `issue/NNNN` where NNNN is the JIRA issue number.
@@ -77,4 +77,3 @@ on the [scala-internals](http://groups.google.com/group/scala-internals) mailing
 
 Contributions, big or small, simple or complex, controversial or undisputed, need to materialize as patches against
 the Scala project source tree. The [hacker guide](hacker-guide.html) will explain how to materialize your idea into a full-fledged pull request against the Scala code base.
-
diff --git a/contribute/hacker-guide.md b/contribute/hacker-guide.md
@@ -28,7 +28,7 @@ Sometimes it's appealing to hack alone and not to have to interact with others o
 this might not be the very best idea. There are people in the Scala community who have spent years accumulating knowledge about Scala libraries and internals. They might provide
 unique insights and, what's even better, direct assistance in their areas, so it is not only advantageous, but recommended to communicate with the community about your new patch.
 
-Typically bug fixes and new features start out as an idea or an experiment posted on one of [our mailing lists]({{ site.baseurl }}/community/index.html#mailing_lists) to find out how people feel
+Typically bug fixes and new features start out as an idea or an experiment posted on one of [our mailing lists]({{ site.baseurl }}/community/index.html#mailing-lists) to find out how people feel
 about things you want to implement. People proficient in certain areas of Scala usually monitor mailing lists, so you'll often get some help
 by simply posting a message. But the most efficient way to connect is to cc your message to one of the people responsible for maintaining the aspect of Scala which you wish to contribute to.
 

diff --git a/contribute/index.md b/contribute/index.md
@@ -56,7 +56,7 @@ Coordination of contribution efforts takes place on the
 <p>Enhance the Scala tools with features for build tools, IDE plug-ins and other related projects.</p>
 </div>
 <div class="span4 doc-block">
-<h4><a href="./guide.html#larger_changes_new_features">Compiler/Language</a></h4>
+<h4><a href="./guide.html#larger-changes-new-features">Compiler/Language</a></h4>
 <p>Larger language features and compiler enhancements including language specification and SIPs.</p>
 </div>
 </div>

diff --git a/contribute/scala-standard-library-api-documentation.md b/contribute/scala-standard-library-api-documentation.md
@@ -75,7 +75,7 @@ component so that they show up in the correct issue filters.
 Please familiarize yourself with the following before contributing
 new API documentation to save time, effort, mistakes and repetition.
 
-* [Forking the Repo](./hacker-guide.html#2_set_up) - follow the setup steps through
+* [Forking the Repo](./hacker-guide.html#set-up) - follow the setup steps through
   the Branch section. If providing new documentation related to an existing JIRA issue, use `issue/NNNN`
   or `ticket/NNNN` as the guide states. If providing API documentation with no associated
   JIRA issue, use `scaladoc/xxxx` instead.

diff --git a/documentation/getting-started.md b/documentation/getting-started.md
@@ -84,7 +84,7 @@ The `scala` command executes the generated bytecode with the appropriate options
 
     > scala -cp classes HelloWorld
 
-The argument of the `scala` command has to be a top-level object. If that object extends trait [`App`]({{page.docpath}}#scala.App), then all statements contained in that object will be executed; otherwise you have to add a method `main` which will act as the           entry point of your program.
+The argument of the `scala` command has to be a top-level object. If that object extends trait scala.App, then all statements contained in that object will be executed; otherwise you have to add a method `main` which will act as the           entry point of your program.
 
 Here is how the "Hello, world!" example looks like using the `App` trait:
 

diff --git a/gsoc/2014.md b/gsoc/2014.md
@@ -16,7 +16,7 @@ in much more detail, preferably with their own suggestions and
 detailed plans on how they want to proceed. Don't feel constrained by
 the provided list! We welcome any of your own challenging ideas, but
 make sure that the proposed project satisfies the [main
-requirements](#requirements_and_guidelines) mentioned below.
+requirements](#requirements-and-guidelines) mentioned below.
 
 ### How to get involved
 

diff --git a/gsoc/2015.md b/gsoc/2015.md
@@ -16,7 +16,7 @@ in much more detail, preferably with their own suggestions and
 detailed plans on how they want to proceed. Don't feel constrained by
 the provided list! We welcome any of your own challenging ideas, but
 make sure that the proposed project satisfies the [main
-requirements](#requirements_and_guidelines) mentioned below.
+requirements](#requirements-and-guidelines) mentioned below.
 
 ### How to get involved