<h2 id="contributor">Becoming a contributor</h2>
-<h3>Overview</h3>
+<h3 id="contrib_overview">Overview</h3>
<p>
The first step is registering as a Go contributor and configuring your environment.
an <a href="https://golang.org/issues">existing one</a>.
</p>
-<h3>Check the issue tracker</h3>
+<h3 id="check_tracker">Check the issue tracker</h3>
<p>
Whether you already know what contribution to make, or you are searching for
the flow.
</p>
-<h3>Overview</h3>
+<h3 id="gerrit_overview">Overview</h3>
<p>
This is an overview of the overall process:
Fixes #159
</pre>
-<h3>First line</h3>
+<h3 id="first_line">First line</h3>
<p>
The first line of the change description is conventionally a short one-line
Follow the first line by a blank line.
</p>
-<h3>Main content</h3>
+<h3 id="main_content">Main content</h3>
<p>
The rest of the description elaborates and should provide context for the
benchmark data for change descriptions.
</p>
-<h3>Referencing issues</h3>
+<h3 id="ref_issues">Referencing issues</h3>
<p>
The special notation "Fixes #12345" associates the change with issue 12345 in the