CommitMessage: use h2 headings

The page title is h1, and the content needs to be nested
lower for the table of content to recognize its sections.

Change-Id: I4d6c48289fcebdbfb119e81adcdb34b7fa26327f
Auto-Submit: Dmitri Shuralyov <>
Reviewed-by: Dmitri Shuralyov <>
diff --git a/ b/
index 7cbaf1a..efef649 100644
--- a/
+++ b/
@@ -45,7 +45,7 @@
 It is common in other Git projects to use `Updates` instead of `For`, and that is acceptable too, even though it makes little sense (the commit does not update the issue). More precise phrasings are fine too. Don't be too pedantic in code reviews: it's not worth asking people to change from `Updates` or something else to `For`, or vice versa.
-# Reverts
+## Reverts
 You can roll back a change using the Gerrit `Revert` button.
 Gerrit will generate a description for you.
@@ -54,7 +54,7 @@
 Do not use the Gerrit UI to create a revert of a revert, as that notifies people right away.
 Instead, mail it as a new change, and in the description explain that it is a roll forward of CL NNNNNN which was rolled back by CL NNNNNN.
-# Other repos
+## Other repos
 For non-"go" repos ("crypto", "tools", "net", etc), the subject is still the name of the package, but you need to fully-qualify the issue number with the GitHub org/repo syntax:
@@ -66,12 +66,12 @@
 Notably, the first line subject should **not** contain the `x/crypto/` prefix. We only do that for the issue tracker.
-# Non-normative references
+## Non-normative references
 - [Please heed my plea and write good CL descriptions for Go—and for any other project you work on.](
 - [The CL description is a public document that explains to the future what has been done and why.](
-# GitHub Pull Requests
+## GitHub Pull Requests
 If you're using GitHub Pull Requests, your commit message is constructed by GerritBot based on your
 PR's title & description. See
@@ -79,4 +79,3 @@
 If somebody asks you to modify your commit message, you'll need to modify your PR.