diff --git a/Releasing-Tracks.textile b/Releasing-Tracks.textile
index c8643d1..34756d7 100644
--- a/Releasing-Tracks.textile
+++ b/Releasing-Tracks.textile
@@ -3,19 +3,17 @@ These steps are for maintainers with commit access.
 # _(Major release only)_ Make sure documentation is up to date in master. Don't change the version number yet!
 ** /README.md
 ** everything in /doc
-# _(Major release only)_ Create maintenance branch for release. For example:
-<pre><code>git checkout -b 2.0_branch</code></pre>
-# _(Major release only)_ Update badges in README to point to the new branch (e.g. Travis)
 # _(Major release only)_ Pin all gem versions using pessimistic version constraints matching the current Gemfile.lock
 # Update version numbers and check copyright dates
 ** /README.md
 ** everything in /doc
-** /config/initializers/tracks.rb (comment out the git date)
+** /config/initializers/tracks.rb
 # _(Major release only)_ Push new branch to upstream:
-<pre><code>git push upstream 2.0_branch</code></pre>
+<pre><code>git push upstream 2.0</code></pre>
 # Tag the release:
-<pre><code>git tag v2.0
+<pre><code>git tag -a v2.0
 git push upstream --tags</code></pre>
+# Create release in GitHub, adding a description of the changes.
 # _(Major release only)_ Update the version numbers in master to the next development milestone
 ** /README.md
 ** everything in /doc
@@ -23,5 +21,6 @@ git push upstream --tags</code></pre>
 # Publicize the new release
 ** Post on the Tracks website
 ** Update the IRC topic
+** Update the Gitter topic
 ** Email the mailing list
 ** Post to Twitter
\ No newline at end of file