@@ -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
index 09532edec..897c97b1a 100644
--- 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
index 925e83248..2fdf75fc7 100644
--- a/contribute/index.md
+++ b/contribute/index.md
@@ -56,7 +56,7 @@ Coordination of contribution efforts takes place on the
Enhance the Scala tools with features for build tools, IDE plug-ins and other related projects.