Fix broken links

Author: Philippus

contribute/codereviews.md

@@ -6,7 +6,7 @@ includeTOC: true
 ---
 ## Code Review Contributions
 
-In addition to [bug fixing](/contribute/guide/), you can help us review
+In addition to [bug fixing](/contribute/guide.html), you can help us review
 [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
@@ -51,4 +51,4 @@ own pull requests.
 </div>
 </div>
 
-Also note that the [Tools contributions](/contribute/tools/) page has more projects that will generate pull requests.
+Also note that the [Tools contributions](/contribute/tools.html) page has more projects that will generate pull requests.

contribute/guide.md

@@ -61,7 +61,7 @@ This is the impatient developer's checklist for the steps to submit a bug-fix pu
 3. [Fork the Scala repository](/contribute/hacker-guide.html#fork) and clone your fork (if you haven't already).
 4. [Create a feature branch](/contribute/hacker-guide.html#branch) to work on: use the branch name `issue/NNNN` where NNNN is the JIRA issue number.
 5. [Fix the bug, or implement the new small feature](/contribute/hacker-guide.html#implement), include new tests (yes, for bug fixes too).
-6. [Test, rinse](/contribute/hacker-guide.html#test) and [test some more](/contribute/partest-guide/) until [all the tests pass](/contribute/hacker-guide.html#verify).
+6. [Test, rinse](/contribute/hacker-guide.html#test) and [test some more](/contribute/partest-guide.html) until [all the tests pass](/contribute/hacker-guide.html#verify).
 7. [Commit your changes](/contribute/hacker-guide.html#commit) to your feature branch in your fork. Please choose your commit message based on the [Git Hygiene](https://github.com/scala/scala#user-content-git-hygiene) section of the Scala project README.
 8. If necessary [re-write git history](http://git-scm.com/book/en/Git-Branching-Rebasing) so that [commits are organized by major steps to the fix/feature](
 https://github.com/scala/scala#git-hygiene). For bug fixes, a single commit is requested, for features several commits may be desirable (but each separate commit must compile and pass all tests)

contribute/scala-standard-library-api-documentation.md

@@ -77,7 +77,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#set-up) - follow the setup steps through
+* [Forking the Repo](./hacker-guide.html#2-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.