[develop] Fix: UWP→WinAppSDK migration — UI, layout & platform

hub/apps/desktop/modernize/ui/apply-mica-win32.md

@@ -33,7 +33,7 @@ The MicaController reacts to the system Light and Dark themes by default. To ove
 > [!TIP]
 > The code in this section is taken from the [Windows App SDK Win32 Mica sample on GitHub](https://github.com/microsoft/WindowsAppSDK-Samples/tree/main/Samples/Mica/cpp-win32). See the GitHub repo for the full code. These examples use [C++/WinRT](/windows/uwp/cpp-and-winrt-apis/).
 
-To enable Mica, you need a reference to the Windows App SDK, a [Compositor](/uwp/api/windows.ui.composition.compositor), and a [DispatcherQueue](/uwp/api/windows.system.dispatcherqueue).
+To enable Mica, you need a reference to the Windows App SDK, a [Compositor](/windows/windows-app-sdk/api/winrt/microsoft.ui.composition.compositor), and a [DispatcherQueue](/uwp/api/windows.system.dispatcherqueue).
 
 This example shows how to do the following to set up an unpackaged app:
 

hub/apps/develop/launch/handle-file-activation.md

@@ -127,6 +127,6 @@ The files that you receive could come from an untrusted source. We recommend tha
 
 ## Related content
 
-- [Association launching sample](https://github.com/microsoft/Windows-universal-samples/tree/master/Samples/AssociationLaunching)
+- [Windows App SDK activation sample](https://github.com/microsoft/WindowsAppSDK-Samples/tree/main/Samples/AppLifecycle/Activation/cs2/cs-winui-packaged/CsWinUiDesktopActivation)
 - [Launch the default app for a file](launch-the-default-app-for-a-file.md)
 - [Handle URI activation](handle-uri-activation.md)

hub/apps/develop/launch/handle-uri-activation.md

@@ -24,7 +24,7 @@ These steps show how to register for a custom URI scheme name, `alsdk://`, and h
 The following APIs are used in this topic:
 
 - [Windows.ApplicationModel.Activation.ProtocolActivatedEventArgs](/uwp/api/Windows.ApplicationModel.Activation.ProtocolActivatedEventArgs)
-- [Windows.UI.Xaml.Application.OnActivated](/uwp/api/windows.ui.xaml.application.onactivated)
+- [Windows.UI.Xaml.Application.OnActivated](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.application.onactivated)
 - [AppInstance.GetCurrent().GetActivatedEventArgs](/windows/windows-app-sdk/api/winrt/microsoft.windows.applifecycle.appinstance.getactivatedeventargs)
 
 > [!NOTE]
@@ -83,7 +83,7 @@ Apps that become the default for a URI scheme name have their icons displayed in
 > [!NOTE]
 > In a WinUI app, in App.OnLaunched (or in fact at any time) you can call [AppInstance.GetCurrent().GetActivatedEventArgs](/windows/windows-app-sdk/api/winrt/microsoft.windows.applifecycle.appinstance.getactivatedeventargs) to retrieve the activated event args, and check them to determine how the app was activated. See [Application lifecycle functionality migration](/windows/apps/windows-app-sdk/migrate-to-windows-app-sdk/guides/applifecycle) for more information about lifecycle differences between UWP and WinUI apps.
 
-In UWP apps, the [OnActivated](/uwp/api/windows.ui.xaml.application.onactivated) event handler receives all activation events. The **Kind** property indicates the type of activation event. This example is set up to handle [Protocol](/uwp/api/Windows.ApplicationModel.Activation.ActivationKind) activation events.
+In UWP apps, the [OnActivated](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.application.onactivated) event handler receives all activation events. The **Kind** property indicates the type of activation event. This example is set up to handle [Protocol](/uwp/api/Windows.ApplicationModel.Activation.ActivationKind) activation events.
 
 ```csharp
 public partial class App
@@ -139,7 +139,7 @@ The following code programmatically launches the app via its URI:
 
 For more details about how to launch an app via a URI, see [Launch the default app for a URI](launch-default-app.md).
 
-It is recommended that apps create a new XAML [Frame](/uwp/api/Windows.UI.Xaml.Controls.Frame) for each activation event that opens a new page. This way, the navigation backstack for the new XAML **Frame** will not contain any previous content that the app might have on the current window when suspended. Apps that decide to use a single XAML **Frame** for Launch and File Contracts should clear the pages on the **Frame** navigation journal before navigating to a new page.
+It is recommended that apps create a new XAML [Frame](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.Controls.Frame) for each activation event that opens a new page. This way, the navigation backstack for the new XAML **Frame** will not contain any previous content that the app might have on the current window when suspended. Apps that decide to use a single XAML **Frame** for Launch and File Contracts should clear the pages on the **Frame** navigation journal before navigating to a new page.
 
 When launched via Protocol activation, apps should consider including UI that allows the user to go back to the top page of the app.
 
@@ -159,9 +159,9 @@ Any app or website can invoke your URI scheme with arbitrary payloads, including
 > [!NOTE]
 > When a UWP app is launched via Protocol Contract, make sure that Back button takes the user back to the screen that launched the app and not to the app's previous content.
 
-We recommend that apps create a new XAML [**Frame**](/uwp/api/Windows.UI.Xaml.Controls.Frame) for each activation event that opens a new Uri target. This way, the navigation backstack for the new XAML **Frame** will not contain any previous content that the app might have on the current window when suspended.
+We recommend that apps create a new XAML [**Frame**](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.Controls.Frame) for each activation event that opens a new Uri target. This way, the navigation backstack for the new XAML **Frame** will not contain any previous content that the app might have on the current window when suspended.
 
-If you decide that you want your apps to use a single XAML [**Frame**](/uwp/api/Windows.UI.Xaml.Controls.Frame) for Launch and Protocol Contracts, clear the pages on the **Frame** navigation journal before navigating to a new page. When launched via Protocol Contract, consider including UI into your apps that allows the user to go back to the top of the app.
+If you decide that you want your apps to use a single XAML [**Frame**](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.Controls.Frame) for Launch and Protocol Contracts, clear the pages on the **Frame** navigation journal before navigating to a new page. When launched via Protocol Contract, consider including UI into your apps that allows the user to go back to the top of the app.
 
 ## Related content