diff --git a/doc/articles/guides/xf-migration/intro.md b/doc/articles/guides/xf-migration/intro.md
index 9b7ab2d00cae..beb7903b90db 100644
--- a/doc/articles/guides/xf-migration/intro.md
+++ b/doc/articles/guides/xf-migration/intro.md
@@ -4,11 +4,11 @@ uid: Uno.XamarinFormsMigration.Intro
 
 # Uno Platform for Xamarin.Forms developers
 
-With an imminent end of [support](https://dotnet.microsoft.com/platform/support/policy/xamarin#microsoft-support) date in May 2024, it is important for your team to consider a migration from Xamarin.Forms to another framework. This page expands on the previous [section](xref:Uno.XamarinFormsMigration.Overview) section to offer more context about why your team should consider Uno Platform.
+With an announced [end of support](https://dotnet.microsoft.com/platform/support/policy/xamarin#microsoft-support) for Xamarin.Forms, you should start the process of migrating to the Uno Platform as soon as possible. This page expands on the previous [section](xref:Uno.XamarinFormsMigration.Overview) section to offer more context about the Uno Platform.
 
 ## Understanding our approach
 
-Uno Platform is designed for compatibility with Microsoft's native UI framework [WinUI](https://learn.microsoft.com/windows/apps/winui/winui3/). It achieves this by implementing the same controls, panels, and other constructs. While Xamarin.Forms also supports reuse across platforms, it differs from Uno Platform architecturally as a type of abstraction. 
+Uno Platform is designed for compatibility with Microsoft's native UI framework [WinUI](https://learn.microsoft.com/windows/apps/winui/winui3/). It achieves this by implementing the same controls, panels, and other non-UI APIs across the other supported platforms: iOS, Android, MacCatalyst, Web and Linux. While Xamarin.Forms also supports reuse across platforms, it differs from Uno Platform architecturally as a type of abstraction. 
 
 In the Xamarin.Forms space, it would be difficult to miss the differing behaviors and properties inherited by your app UI depending on the platform. This occasionally requires more boilerplate code, with less-natural methods to customize views for your brand identity. Migrating to Uno Platform is a step forward, as its appreciation for consistency in appearance and behavior across platforms allows your app to embody a precise brand identity.
 
@@ -18,7 +18,7 @@ When platforms, albeit in their infancy, invested in a robust set of first-party
 
 Microsoft significantly evolved the visual layer for Windows devices by launching WinRT XAML in 2012 and has expanded the compatibility of its modern UI framework with the launch of WinUI 3 in 2021. 
 
-The creation of Uno Platform was driven by the aspiration to make pixel-perfect apps possible across platforms. This is achieved by implementing the same controls, panels, and other constructs as WinUI.
+The creation of Uno Platform was driven by the aspiration to make pixel-perfect apps possible across all platforms. This is achieved by implementing the same controls, panels, and other constructs as WinUI.
 
 ## Architectural differences