diff --git a/build.sbt b/build.sbt
index 8af8b3700..3b5694bc7 100644
--- a/build.sbt
+++ b/build.sbt
@@ -10,7 +10,7 @@ import com.eed3si9n.jarjarabrams.ModuleCoordinate
 // ThisBuild settings take lower precedence,
 // but can be shared across the multi projects.
 ThisBuild / version := {
-  val v = "2.0.0-RC8-bin-SNAPSHOT"
+  val v = "2.0.0-RC9-bin-SNAPSHOT"
   nightlyVersion.getOrElse(v)
 }
 ThisBuild / Utils.version2_13 := "2.0.0-SNAPSHOT"
diff --git a/contributing-docs/06_manual_tests.md b/contributing-docs/06_manual_tests.md
index 0df7223d4..8ed1ae347 100644
--- a/contributing-docs/06_manual_tests.md
+++ b/contributing-docs/06_manual_tests.md
@@ -22,7 +22,7 @@ $ sbt --server
 
 ### Clearing out boot and local cache
 
-sbt consists of lots of JAR files. When running sbt locally, these JAR artifacts are cached in the `boot` directory under `$HOME/.sbt/boot/scala-3.8.1/org.scala-sbt/sbt/2.0.0-RC8-bin-SNAPSHOT` directory (The Scala version and sbt version part changes).
+sbt consists of lots of JAR files. When running sbt locally, these JAR artifacts are cached in the `boot` directory under `$HOME/.sbt/boot/scala-3.8.1/org.scala-sbt/sbt/2.0.0-RC9-bin-SNAPSHOT` directory (The Scala version and sbt version part changes).
 
 In order to see a change you've made to sbt's source code, this cache MUST be cleared. To clear this out, from the sbt shell in your application run:
 
@@ -30,6 +30,12 @@ In order to see a change you've made to sbt's source code, this cache MUST be cl
 > reboot dev
 ```
 
+Alternatively from Bash:
+
+```bash
+$ rm -rf $HOME/.sbt/boot/scala-3.*
+```
+
 By default sbt uses a snapshot version (this is a scala convention for quick local changes- it tells users that this version could change).
 One drawback of `-SNAPSHOT` version is that it's slow to resolve as it tries to hit all the resolvers.
 This is important when testing performance, so that the slowness of the resolution does not impact sbt.