diff --git a/docs/testing-deployment-publishing/branching-collaboration/branching.md b/docs/testing-deployment-publishing/branching-collaboration/branching.md
index 2cbedcce..cdd0881c 100644
--- a/docs/testing-deployment-publishing/branching-collaboration/branching.md
+++ b/docs/testing-deployment-publishing/branching-collaboration/branching.md
@@ -14,7 +14,7 @@ Branching creates a separate copy of your work, so you can add new features with
 Suppose you have an eCommerce app and you want to add a new feature, such as a product recommendation system. Instead of incorporating it directly into your `main` branch and potentially causing problems, you can create a branch to work on this new feature in isolation. Once it's complete, you can integrate it back into the `main` branch.
 
 :::info
-This feature is only available for Pro, Teams and Enterprise users.
+While all users can access the branching menu and create commits, only **Pro**, **Teams**, and **Enterprise** plans support creating new branches.
 :::
 
 
diff --git a/docs/testing-deployment-publishing/branching-collaboration/saving-versioning.md b/docs/testing-deployment-publishing/branching-collaboration/saving-versioning.md
index c8b619cc..7d8dc1fc 100644
--- a/docs/testing-deployment-publishing/branching-collaboration/saving-versioning.md
+++ b/docs/testing-deployment-publishing/branching-collaboration/saving-versioning.md
@@ -1,8 +1,8 @@
 ---
 slug: /collaboration/saving-versioning
 title: Saving and Versioning
-description: Learn about the crucial concepts of saving and versioning in your FlutterFlow project.
-tags: [Saving, Versioning, Collaboration]
+description: Learn about versioning in your FlutterFlow.
+tags: [Versioning]
 sidebar_position: 2
 keywords: [Saving, Versioning, Collaboration, FlutterFlow, Concepts]
 ---
@@ -13,40 +13,10 @@ In this section, we discuss the important concepts of saving and versioning in y
 
 ## Versions
 
-Versions enable you to save specific named states of your project. This function is particularly useful for recovery purposes. If you accidentally delete a page or component or change settings, you can easily revert to a saved version.
-
-### Saving a version
-
-Saving the latest changes will store the current state of your app in the version control. In the future, if anything goes wrong, you can restore your app to the currently saved state.
-
-Ideally, you should save the version whenever you accomplish something important, for example, after finishing a page, adding configuration, etc.
-
-<div style={{
-    position: 'relative',
-    paddingBottom: 'calc(56.67989417989418% + 41px)', // Keeps the aspect ratio and additional padding
-    height: 0,
-    width: '100%'
-}}>
-    <iframe 
-        src="https://demo.arcade.software/nxgOUj0g3jwszbXnCSXE?embed&show_copy_link=true"
-        title="Sharing a Project with a User"
-        style={{
-            position: 'absolute',
-            top: 0,
-            left: 0,
-            width: '100%',
-            height: '100%',
-            colorScheme: 'light'
-        }}
-        frameborder="0"
-        loading="lazy"
-        webkitAllowFullScreen
-        mozAllowFullScreen
-        allowFullScreen
-        allow="clipboard-write">
-    </iframe>
-</div>
-<p></p>
+:::warning[Project Versions are now deprecated]
+You can no longer create new versions in FlutterFlow. However, any previously created versions will remain accessible. Moving forward, we recommend using [**Commits**](#commits), which provides a more robust way to track changes and manage your project history.
+:::
+
 
 ### Restoring a version