diff --git a/RELEASING.md b/RELEASING.md
index a169f831..7c71a3f2 100644
--- a/RELEASING.md
+++ b/RELEASING.md
@@ -12,8 +12,7 @@ See the [prerequisites](#prerequisites) if this is your first release.
 
 * [ ] [Check CI][ci] passes against the latest Scala versions.
 * [ ] [Draft a new release][releases/new] for the release, allowing GitHub to generate draft release notes automatically.
-* [ ] Bump the version in the `README.md` and `git commit -am 'Release 1.x.y`.
-* [ ] Run `git tag -a -s 1.x.y -m 'Version 1.x.y`. The name of the tag should NOT have a 'v' prefix.
+* [ ] Run `git tag -a -s 1.x.y -m 'Version 1.x.y'`. The name of the tag should NOT have a `v` prefix.
 * [ ] In sbt run `reload` and `show version` to verify the version.
 * [ ] In sbt run `clean`, particularly if you've recently bumped `scalaVersion`.
 * [ ] In sbt run `publishSigned`. You should start seeing "published mima-.. to https://oss.sonatype.org/service/local/staging/deploy/maven2/..".
@@ -21,23 +20,23 @@ See the [prerequisites](#prerequisites) if this is your first release.
 * [ ] In sbt run `++3.2` `coreJVM/publishSigned` `coreNative/publishSigned`
 * [ ] [Find and close][sonatype/staging-repos] your staging repository.  (See Sonatype's [Releasing the Deployment][sonatype/guide] guide.)
 * [ ] Switch to a branch (e.g. `git checkout -b release-1.x.y`)
-* [ ] In `plugins.sbt` update `sbt-mima-plugins`.
+* [ ] In `project/plugins.sbt` update `sbt-mima-plugin`.
 * [ ] In `project/MimaSettings.scala` update `mimaPreviousVersion` & clear out `mimaBinaryIssueFilters`.
 * [ ] In sbt run `testStaging` **WITHOUT** `reload`ing first (`testStaging` adds the staging resolvers & runs `reload`).
-* [ ] Run `git commit -am 'Update sbt-mima-plugin to 1.x.y` and PR it (`hub pull-request`). The PR won't pass CI until the release is available on Maven Central. You may poll [repo1 directly][repo1/list] (note the trailing slash in the URL).
+* [ ] Run `git commit -am 'Update sbt-mima-plugin to 1.x.y'` and PR it (`gh pr create` or `hub pull-request`). The PR won't pass CI until the release is available on Maven Central. You may poll [repo1 directly][repo1/list] (note the trailing slash in the URL).
 * [ ] [Find and release][sonatype/staging-repos] your staging repository.
 * [ ] Switch back to the main branch and run `git push --follow-tags` to push the tag.
 * [ ] [Find and merge][prs/list] your update PR.
 * [ ] [Find and hit "Publish Release"][releases/list] on the draft GitHub release.
 
-[compare/view]:    https://github.com/lightbend/mima/compare/1.1.1...main
+[compare/view]:    https://github.com/lightbend/mima/compare/1.1.2...main
 [issues/new]:      https://github.com/lightbend/mima/issues/new
 [prs/list]:        https://github.com/lightbend/mima/pulls
 [releases/list]:   https://github.com/lightbend/mima/releases
 [releases/new]:    https://github.com/lightbend/mima/releases/new
 
 [RELEASING.md]: https://raw.githubusercontent.com/lightbend/mima/main/RELEASING.md
-[repo1/list]: https://repo1.maven.org/maven2/com/typesafe/mima-core_2.12/1.1.1/
+[repo1/list]: https://repo1.maven.org/maven2/com/typesafe/mima-core_2.12/1.1.2/
 [sonatype/guide]: https://central.sonatype.org/pages/releasing-the-deployment.html
 [sonatype/staging-repos]: https://oss.sonatype.org/#stagingRepositories
 [ci]: https://github.com/lightbend/mima/actions/workflows/ci.yml