RELEASE.md in standard-1.17.0

- old
+ new
@@ -20,23 +20,23 @@
 [Rubygems.org](https://rubygems.org/gems/standard).
 
 ## Release steps
 
 1. Make sure git is up to date and `bundle exec rake` exits cleanly
-2. If you upgraded a Rubocop dependency, be sure to lock it down in
+1. If you upgraded a Rubocop dependency, be sure to lock it down in
    `standard.gemspec`. To avoid being broken transitively, we stick to exact
    release dependencies (e.g. "0.91.0" instead of "~> 0.91")
-3. Bump the appropriate version segment in `lib/standard/version.rb` (basic
+1. Update `CHANGELOG.md` as exhaustively as you are able and set the top header
+   to "Unreleased"
+1. Bump the appropriate version segment in `lib/standard/version.rb` (basic
    semantic versioning rules apply; if the release updates Rubocop, follow its
    version bump at a minimum—if rubocop saw minor bump, we'll also bump the
    minor version)
-4. Run `bundle` so that Bundler writes this version to `Gemfile.lock`
-5. Update `CHANGELOG.md` as exhaustively as you are able and set the top header
-   to that of the new version
-6. Commit `lib/standard/version.rb`, `Gemfile.lock`, and `CHANGELOG.md` together
+1. Run `bundle` so that Bundler writes this version to `Gemfile.lock`
+1. Commit `lib/standard/version.rb`, `Gemfile.lock`, and `CHANGELOG.md` together
    with the message equal to the new version (e.g. "0.42.1")
-7. Finally, run `bundle exec rake release`, which will hopefully succeed
-8. Provide your multi-factor-auth token when prompted to finish publishing the
+1. Finally, run `bundle exec rake release`, which will hopefully succeed
+1. Provide your multi-factor-auth token when prompted to finish publishing the
    gem
-9. [Tweet](https://twitter.com) about your awesome new release! (Shameless
+1. [Tweet](https://twitter.com) about your awesome new release! (Shameless
    self-promotion is the most important part of open source software)
 