diff --git a/openmetadata-docs/content/partials/v1.4/deployment/upgrade/upgrade-prerequisites.md b/openmetadata-docs/content/partials/v1.4/deployment/upgrade/upgrade-prerequisites.md
index 8fb75c82b662..e28863b9de34 100644
--- a/openmetadata-docs/content/partials/v1.4/deployment/upgrade/upgrade-prerequisites.md
+++ b/openmetadata-docs/content/partials/v1.4/deployment/upgrade/upgrade-prerequisites.md
@@ -88,24 +88,21 @@ After the migration is finished, you can revert this changes.
 
 ### Tooling
 
+- **Metadata Backup & Restore**: The Metadata Backup/Recovery has been deprecated, and no further support will be provided. Users are advised to use database-native tools to back up data and store it in their object store for recovery.
+  You can check the [docs](/deployment/backup-restore-metadata) for more information.
 - **Metadata Docker CLI**: For the past releases, we have been updating the documentation to point users to directly run the docker quickstart
   with the docker compose files in the release page ([docs](quick-start/local-docker-deployment)). In this release, we're completely removing the support for `metadata docker`.
-- **Metadata Backup & Restore**: On the `metadata` CLI, we are deprecating the `backup` and `restore` commands, since users can now completely
-  rely on native database tools both for MySQL and PostgreSQL. Check the [docs](/deployment/backup-restore-metadata)
-  for more information
-- **bootstrap_storage.sh**: `bootstrap/bootstrap_storage.sh` now deprecated in favor of `bootstrap/openmetadata-ops.sh`, please refer to help docs of the new tool for any changes.
+- **bootstrap_storage.sh**: We have deprecated `bootstrap/bootstrap_storage.sh` and replaced it with `bootstrap/openmetadata-ops.sh`. The documentation has been updated accordingly.
+
 
 ### UI
 
-- **Activity Feed**: Activity is Improved, new Update specific cards will be showing critical information such as data quality test case updates, description, tag update or removal
-- **Lineage**: The `Expand All` button is removed. Instead, the new `Layers` button has been introduced to the bottom left corner. 
-  Please use Layers to add Column Level Lineage or Data Observability details to your Lineage view.
+- **Activity Feed**: The Activity Feed has been improved with new, updated cards that display critical information such as data quality test case updates, descriptions, tag updates, or asset removal.
+- **Lineage**: The Expand All button has been removed. A new Layers button is introduced in the bottom left corner. With the Layers button, you can add Column Level Lineage or Data Observability details to your Lineage view.
 - **View Definition**: View Definition is now renamed to Schema Definition
-- **Glossary**: Adding a Glossary Term view has improved. Now, we show glossary terms hierarchically,
-  enabling a better understanding how the terms are set up while adding it to a table or dashboard.
-- **Classifications**: Users can set a classification to be mutually exclusive **only** at the creation time. 
-  Once created, you cannot change it back to non-mutually exclusive or vice-versa. 
-  This is to prevent conflicts of adding multiple tags that belong to same classification and later turning the mutually exclusive flag back to true.
+- **Glossary**: Adding Glossary Term view has been improved. Now, we show glossary terms hierarchically, enabling a better understanding of how the terms are set up while labeling a table or dashboard.
+- **Classifications**: users can set it to be mutually exclusive **only** at the time of creation. Once created, you cannot change it back to mutually non-exclusive or vice versa. 
+    This is to prevent conflicts between adding multiple tags that belong to the same classification and later turning the mutually exclusive flag back to true.
 
 ### API