diff --git a/RELEASE.adoc b/RELEASE.adoc
index 708cb733..748803e9 100644
--- a/RELEASE.adoc
+++ b/RELEASE.adoc
@@ -1,7 +1,7 @@
 == 1. Update Dependencies
 
-Dependencies are declared in `gradle/dependency-management.gradle`.
-Update Spring Framework, Spring Security and Spring Data at a minimum.
+Dependencies are declared in `gradle/libs.versions.toml`.
+They are updated by Dependabot, make sure that there is no Dependabot PR open, the versions are correct and that the build passes.
 
 Run all the checks:
 
@@ -10,8 +10,6 @@ Run all the checks:
 $ ./gradlew check
 ----
 
-Create separate issues for each dependency update, aside from test dependencies which can be combined into a single commit.
-
 == 2. Check All Issues are Closed
 
 You can manually check at https://github.com/spring-projects/spring-session/milestones
@@ -45,7 +43,7 @@ git push origin 3.0.0-RC1
 
 == 7. Update to Next Development Version
 
-Update `gradle.properties` version to next `+SNAPSHOT+` version, update antora.yml and then push
+Update `gradle.properties` version to next `+SNAPSHOT+` version.
 
 == 8. Update version on project pages
 
@@ -54,8 +52,7 @@ Update the versions on https://spring.io/projects for Spring Session Core, Sprin
 == 9. Update Release Notes on GitHub
 
 Download
-https://github.com/spring-io/github-changelog-generator/releases/latest[the
-GitHub release notes generator]
+https://github.com/spring-io/github-changelog-generator/releases/latest[the GitHub release notes generator]
 
 * Generate the release notes
 
@@ -77,20 +74,21 @@ cat release-notes | xclip -selection clipboard
 ....
 
 * Create the
-https://github.com/spring-projects/spring-session/releases[release on
-GitHub], associate it with the tag, and paste the generated notes.
+https://github.com/spring-projects/spring-session/releases[release on GitHub], associate it with the tag, and paste the generated notes.
 
 == 10. Close / Create Milestone
 
-* In
-https://github.com/spring-projects/spring-session/milestones[GitHub
-Milestones], create a new milestone for the next release version.
-* Move any open issues from the existing milestone you just released to
-the new milestone.
+* In https://github.com/spring-projects/spring-session/milestones[GitHub Milestones], create a new milestone for the next release version.
+* Move any open issues from the existing milestone you just released to the new milestone.
 * Close the milestone for the release.
 
 Note: Spring Session typically releases only one milestone (M1) and one release candidate (RC1).
 
 == 11. Announce the release
 
-* Announce via Slack on https://pivotal.slack.com/messages/spring-session[#spring-session], and tag any downstream Spring Session projects (e.g Spring Session for Apache Geode).
+* Announce via Slack on `#spring-release`, including the keyword `+spring-session-announcing+` in the message.
+Something like:
+
+....
+spring-session-announcing 3.2.0 is available.
+....