diff --git a/13/umbraco-engage/upgrading/version-specific-upgrade-notes.md b/13/umbraco-engage/upgrading/version-specific-upgrade-notes.md
index f4454d074e8..21238ef914a 100644
--- a/13/umbraco-engage/upgrading/version-specific-upgrade-notes.md
+++ b/13/umbraco-engage/upgrading/version-specific-upgrade-notes.md
@@ -11,20 +11,24 @@ When upgrading to a new minor or patch version, learn about the changes in the [
 {% endhint %}
 
 ## Breaking changes
-#### v13.2.0
+#### v13.2.0 (Umbraco Engage) & v13.1.0 (Umbraco Engage Forms)
 Introduced Razor Class Library support to serve static files for Engage, removing physical backoffice, views, and assets files from development projects.
 
 While this is not considered a breaking change, it is recommended that such folders be removed from the project to avoid conflicts in the future.
 
-The following folders should be manually removed from your project upon updating:
+The following folders should be manually removed from your project upon updating Umbraco Engage:
 
   * `App_Plugins\Umbraco.Engage`
   * `Assets\Umbraco.Engage`
   * `Views\Partials\Umbraco.Engage`
 
-Health checks have been added to verify whether these folders are present in your project. If they are, you will receive a warning in the Health Check dashboard.
+The same changes apply to the Forms add-on `Umbraco.Engage.Forms`.
+
+The following folder should be manually removed from your project upon updating Umbraco Engage Forms:
 
-The above only applies to the `Umbraco.Engage` package. Any addons like `Umbraco.Engage.Forms` will still have physical files in your project in this version.
+  * `App_Plugins\Umbraco.Engage.Forms`
+
+Health checks have been added to verify whether these folders are present in your project. If they are, you will receive a warning in the Health Check dashboard.
 
 #### v13.0.0 (Umbraco Engage Launch)