Re-apply: doc: Replace "underline" with "## Section name".

Re-applying changes after merge.

diff --git a/doc/HACKING/ReleaseSeriesLifecycle.md b/doc/HACKING/ReleaseSeriesLifecycle.md
index d0ce173336792b4968a830e3436b93de2cca582a..4d223af18eb8909feb322d871b6c77988ffdc985 100644 (file)
--- a/doc/HACKING/ReleaseSeriesLifecycle.md
+++ b/doc/HACKING/ReleaseSeriesLifecycle.md
@@ -1,13 +1,11 @@
-
-
-End of Life on an old release series
-------------------------------------
+## End of Life on an old release series
 
 Here are the steps that the maintainer should take when an old Tor release
 series reaches End of Life.  Note that they are _only_ for an entire series
 that has reached its planned EOL: they do not apply to security-related
 deprecations of individual versions.
 
+
 ### 1. Preliminaries
 
 1. A few months before End of Life:
@@ -18,6 +16,7 @@ deprecations of individual versions.
    Send the announcement to tor-announce, tor-talk, tor-relays, and the
    packagers.
 
+
 ### 2. On the day
 
 1. Open tickets to remove the release from: