HTCondorWiki: Release Punch List

 1: Upgrading the pool(s) and watching for bugs
 1: Release the binaries to the public and announce the release
 
-{section: Preliminary Work}
+{section: Building the right binaries}
 
 1: Coordinate a development code-freeze. This involves chasing down people who are trying to finish bug fixes, new features (if it's a development release), porting, or any other core development that is slated for a given release.
 
@@ -142,7 +142,7 @@
 *:: =git tag V7_0_3 BUILD-V7_0_3-branch-2008-6-15=
 *:: =git push origin V7_0_3= (This puts the V7_0_3 tag in the central CONDOR_DOC.git repo.)
 
-{section: Release Day}
+{section: Preparing to release to the world}
 
 1: Release binary tarballs to the web.
 Releasing the binaries to the public is a two step process.  First, we put the binaries into AFS at =/p/condor/public/binaries/vX.Y/X.Y.Z=.  Then, we invoke the download system scripts to push these binaries from AFS out to the mirrors (this is a later step in these instructions).
@@ -211,7 +211,7 @@
 {endcode}
 
 
-{subsection: Release Condor}
+{subsection: Release Condor to the world}