Merged main into live

Author: QuinnRadich

hub/apps/get-started/index.md

@@ -2,7 +2,7 @@
 description: An overview of Windows app development frameworks
 title: Overview of framework options
 ms.topic: article
-ms.date: 09/06/2024
+ms.date: 09/10/2024
 keywords: windows, desktop development
 ms.localizationpriority: medium
 ---
@@ -86,7 +86,7 @@ If you have a [Windows Forms .NET](/dotnet/desktop/winforms/overview/) app, you
 The Universal Windows Platform (UWP) provides a common type system, APIs, and application model for all devices in the Universal Windows Platform. Not only can you use UWP to create desktop applications for Windows PCs, but UWP is also the only supported platform to write a single native universal app that runs across Xbox, HoloLens, and Surface Hub. UWP apps can be native or managed.
 
 > [!NOTE]
-> Your existing UWP app will continue to function as expected. However, to take advantage of modern features in [WinUI 3](/windows/apps/winui/winui3) and the [Windows SDK](https://developer.microsoft.com/windows/downloads/windows-sdk/) we recommend migrating your app.
+> Your existing UWP app will continue to function as expected. However, to take advantage of modern features in [WinUI 3](../winui/winui3/index.md) and the [Windows App SDK](/windows/apps/windows-app-sdk) we recommend migrating your app.
 
 > [!div class="button"]
 > [Get started with UWP](/windows/uwp/get-started/)

hub/apps/windows-app-sdk/migrate-to-windows-app-sdk/migrate-to-windows-app-sdk-ovw.md

@@ -1,7 +1,7 @@
 ---
 title: Migrate from UWP to the Windows App SDK
 description: A collection of topics describing and demonstrating how to migrate your Universal Windows Platform (UWP) application to the Windows App SDK.
-ms.date: 06/21/2024
+ms.date: 09/10/2024
 ms.topic: article
 keywords: Windows, App, SDK, migrate, migrating, migration, port, porting, overview, hybrid crt, hybrid, crt
 ms.localizationpriority: medium
@@ -12,7 +12,7 @@ ms.localizationpriority: medium
 To migrate your app from the [Universal Windows Platform](/windows/uwp/) (UWP) to the Windows App SDK, your UI code likely needs just a few namespace changes, while much of your platform code can stay the same. You'll need to adjust some code due to differences between UWP apps and desktop apps. But we expect that for most apps (depending on codebase size, of course), migration will take on the order of days rather than weeks.
 
 > [!NOTE]
-> Your existing UWP app will continue to function as expected. However, to take advantage of modern features in [WinUI 3](../../winui/winui3/index.md) and the [Windows SDK](https://developer.microsoft.com/windows/downloads/windows-sdk/) we recommend migrating your app.
+> Your existing UWP app will continue to function as expected. However, to take advantage of modern features in [WinUI 3](../../winui/winui3/index.md) and the [Windows App SDK](/windows/apps/windows-app-sdk) we recommend migrating your app.
 
 Below are the steps, at a high level, for migrating manually. But see the following section for info about using the [.NET Upgrade Assistant tool](#migrating-by-using-the-net-upgrade-assistant-tool)).