CONTRIBUTING.md in standard-rubocop-lts-1.0.1 vs CONTRIBUTING.md in standard-rubocop-lts-1.0.2

@@ -11,15 +11,16 @@
 
 To release a new version:
 
 1. Run `bin/setup && bin/rake` as a tests, coverage, & linting sanity check.
 2. update the version number in `version.rb`
-3. run `bundle exec rake build:checksum`
-4. move the built gem to project root
-5. run `bin/checksum` to create the missing SHA256 checksum
-6. move the built gem back to `pkg/`
-7. commit the changes
-8. run `bundle exec rake release`, which will create a git tag for the version, push git commits and tags, and push the `.gem` file to [rubygems.org][rubygems].
+3. Run `bin/setup && bin/rake` again as a secondary check, and to update `Gemfile.lock`.
+4. run `bundle exec rake build:checksum`
+5. move the built gem to project root
+6. run `bin/checksum` to create the missing SHA256 checksum
+7. move the built gem back to `pkg/`
+8. commit the changes
+9. run `bundle exec rake release`, which will create a git tag for the version, push git commits and tags, and push the `.gem` file to [rubygems.org][rubygems].
 
 NOTE: You will need to have a public key in `certs/`, and list your cert in the
 `gemspec`, in order to sign the new release.
 See: [RubyGems Security Guide][rubygems-security-guide]