Update simplified-experience-for-azure-migrate.md

Author: Dhananjayanr98

articles/migrate/simplified-experience-for-azure-migrate.md

@@ -17,28 +17,28 @@ The simplified experience leverages an enhanced agent-based migration stack tail
 - **Modern replication appliance**: It utilizes Windows Server 2019 (WS2019) and Windows Server 2022 (WS2022) for the replication appliance, ensuring robust and up-to-date infrastructure.
 - **Unified OS support matrix**: This provides a consistent and streamlined approach to operating system support across migration workflows, simplifying planning and execution.
 
-Overall, the upgraded stack equips customers with powerful tools to efficiently migrate newer Linux distributions, leverage modern Windows Server platforms for replication, and benefit from a unified OS support framework—enhancing the entire migration journey to Azure. [Learn more](tutorial-migrate-physical-virtual-machines.md#simplified-experience-recommended)
+Overall, the upgraded stack equips customers with powerful tools to efficiently migrate newer Linux distributions, leverage modern Windows Server platforms for replication, and benefit from a unified OS support framework—enhancing the entire migration journey to Azure.
 
-## Key differences
+## Key differences between classic and simplified experience
 
 The key differences between the Classic and Simplified experience:
 
 | **Aspect** | **Classic experience** | **Simplified experience** |
 | --- | --- | --- | 
 | Upgrade and replacement | Old version with traditional interface | Upgraded version offering a more streamlined and user-friendly interface.
-| Enhanced compatibility | Limited support for newer Linux distributions | Supports newer Linux distributions and uses Windows Server 2019 as the replication appliance. |
+| Enhanced compatibility | Limited support for newer Linux distributions | Supports newer Linux distributions and uses Windows Server 2019 and Windows Server 2022 as the replication appliance. |
 | Improved performance and reliability | Standard performance and reliability | Leveraging latest technologies for better performance and reliability in physical and VMware agent-based migrations. |
 |Streamlined migration process| Traditional migration process	 | Provides a more seamless and efficient migration process, addressing multiple customer concerns. |
-| Deprecation of classic experience | Support for ongoing replications will be active until March 2026 and support for initializing new replications ends by October 30, 2025 | NA |
+| Deprecation of classic experience | Support for ongoing replications will remain active until March 2026, while support for initiating new replications will end on October 30, 2025 | NA |
 
 ## Action Required
-- We recommend using the **simplified experience** for initiating replication of any new agent-based VMware or physical servers. Please note that replication initialization via the classic experience will no longer be supported after **October 30, 2025**.
-- Servers currently under replication using the classic experience will continue to be supported until the retirement date of **March 30, 2026**. We encourage you to complete your migrations well before this date.
-- If you have servers discovered through the replication appliance under the classic experience, ensure replication is initiated before **October 30, 2025**, and plan your subsequent migrations accordingly.
-
-[Learn more](../site-recovery/vmware-physical-azure-classic-deprecation.md) about the deprecation of classic experience.
-
-
+- We recommend using the **simplified experience** for initiating replication of any new agent-based VMware or physical servers.
+  >[!NOTE]
+  >Classic experience will not support starting replications on new servers after **October 30, 2025**.
+- Servers currently replicating using the classic experience will be supported until **March 30, 2026**. We recommend completing your migrations before this date.
+- If you have servers discovered through the replication appliance under the classic experience, ensure replication is initiated before **October 30, 2025**, and plan your subsequent migrations before the retirement date **(March 30, 2026)**.
+  
 ## Next steps
 
-- Learn about the [Simplified experience](tutorial-migrate-physical-virtual-machines.md#simplified-experience-recommended).
+- Learn more about the [Simplified experience](tutorial-migrate-physical-virtual-machines.md#simplified-experience-recommended).
+- Learn more about the [deprecation of classic experience](../site-recovery/vmware-physical-azure-classic-deprecation.md).