33.. _release-guide :
44
55=============
6- Release Guide
6+ Release guide
77=============
88
99
@@ -45,8 +45,8 @@ is currently broken::
4545
4646.. _release_ghstats :
4747
48- GitHub Stats
49- ============
48+ GitHub statistics
49+ =================
5050
5151
5252We automatically extract GitHub issue, PRs, and authors from GitHub via the
@@ -85,7 +85,7 @@ most common issue is ``*`` which is interpreted as unclosed markup).
8585
8686.. _release_chkdocs :
8787
88- Update and Validate the Docs
88+ Update and validate the docs
8989============================
9090
9191Merge ``*-doc `` branch
@@ -101,7 +101,7 @@ When making major or minor releases, update the supported versions in the
101101Security Policy in :file: `SECURITY.md `. Commonly, this may be one or two
102102previous minor releases, but is dependent on release managers.
103103
104- Update "What's New " and "API changes"
104+ Update "What's new " and "API changes"
105105-------------------------------------
106106
107107Before tagging major and minor releases, the "what's new" and "API changes"
@@ -216,7 +216,7 @@ On this branch un-comment the globs from :ref:`release_chkdocs`. And then ::
216216
217217.. _release_DOI :
218218
219- Release Management / DOI
219+ Release management / DOI
220220========================
221221
222222Via the `GitHub UI
@@ -308,7 +308,7 @@ Congratulations, you have now done the second scariest part!
308308
309309.. _release_docs :
310310
311- Build and Deploy Documentation
311+ Build and deploy documentation
312312==============================
313313
314314To build the documentation you must have the tagged version installed, but
0 commit comments