diff --git a/waspc/README.md b/waspc/README.md
index a6d2925187..20540386d8 100644
--- a/waspc/README.md
+++ b/waspc/README.md
@@ -405,8 +405,8 @@ Do the non-bold steps when necessary (decide for each step depending on the chan
   - Context: they are used by used by `wasp new`, you can find reference to them in `Wasp.Cli. ... .StarterTemplates`.
   - In `StarterTemplates.hs` file, update git tag to new version of Wasp we are about to release (e.g. `wasp-v0.13.1-template`).
   - Ensure that all starter templates are working with this new version of Wasp.
-    Update Wasp version in their main.wasp files. Finally, in their repos (for those templates that are on Github),
-    create new git tag that is the same as the new one in `StarterTemplates.hs` (e.g. `wasp-v0.13.1-template`).
+    Update Wasp version in their main.wasp files, and update their code as neccessary. Finally, in their repos (for those templates that are on Github), create new git tag that is the same as the new one in `StarterTemplates.hs` (e.g. `wasp-v0.13.1-template`). Now, once new wasp release is out, it will immediately be able to pull the correct and working version of the starter templates, which is why all this needs to happen before we release new wasp version.
+  - Open-saas also falls under this!
 - Make sure apps in [examples](/examples) are up to date and using a version compatible with the newest version of Wasp.
 - Make sure that Wasp AI (which is part of `waspc` and you can run it with e.g. `wasp new:ai`) is correctly producing apps that work with and use this newest version of Wasp.
   This usually means checking that templates and prompts (e.g. examples of Wasp code) are up to date. If there were no breaking changes, there is likely nothing to be done here.