Kbridge/main/wasdk terminology scrub (#5926)

* WASDK-terminology-scrub

* WASDK-terminology-scrub

Author: Karl-Bridge-Microsoft

hub/apps/design/input/drag-and-drop.md

@@ -102,7 +102,7 @@ See [**ListViewBase.CanReorderItems**](/uwp/api/windows.ui.xaml.controls.listvie
 
 The [UIElement](/uwp/api/windows.ui.xaml.uielement) class does most of the work of implementing drag-and-drop for you. But if you want, you can implement your own version by using the APIs below.
 
-| Functionality | WinAppSDK API </br> Microsoft.UI.Input.DragDrop namespace | UWP API <br/> Windows.Applicationmodel.DataTransfer.DragDrop.Core namespace |
+| Functionality | Windows App SDK</br> Microsoft.UI.Input.DragDrop namespace | UWP<br/> Windows.Applicationmodel.DataTransfer.DragDrop.Core namespace |
 | --- | --- | --- |
 | DragPrimitive | [DragOperation](/windows/windows-app-sdk/api/winrt/microsoft.ui.input.dragdrop.dragoperation) | [CoreDragOperation](/uwp/api/windows.applicationmodel.datatransfer.dragdrop.core.coredragoperation)  |
 | Create a data package | [DataPackage](/uwp/api/windows.applicationmodel.datatransfer.datapackage)  | same |

hub/apps/develop/win2d/custom-effects.md

@@ -1,7 +1,7 @@
 ---
 title: Implementing custom effects
 description: An in-depth guide on implementing custom D2D effects with Win2D.
-ms.date: 05/26/2023
+ms.date: 10/28/2025
 ms.topic: concept-article
 keywords: windows 10, windows 11, uwp, xaml, windows app sdk, winui, windows ui, graphics, games, effect win2d d2d d2d1 direct2d interop cpp csharp
 ms.localizationpriority: medium
@@ -267,11 +267,11 @@ Let's go over how they can be used:
 As we mentioned, if you're using C# and want to implement a custom effect, the recommended approach is to use the [ComputeSharp](https://github.com/Sergio0694/ComputeSharp) library. It enables you to both implement custom D2D1 pixel shaders entirely in C#, as well as to easily define custom effects graphs that are compatible with Win2D. The same library is also used in the Microsoft Store to power several graphics components in the application.
 
 You can add a reference to ComputeSharp in your project through NuGet:
-  * On UWP, select the [**ComputeSharp.D2D1.Uwp**](https://www.nuget.org/packages/ComputeSharp.D2D1.Uwp/) package.
-  * On WinAppSDK, select the [**ComputeSharp.D2D1.WinUI**](https://www.nuget.org/packages/ComputeSharp.D2D1.WinUI/) package.
+  * For UWP, select the [**ComputeSharp.D2D1.Uwp**](https://www.nuget.org/packages/ComputeSharp.D2D1.Uwp/) package.
+  * For WinUI, select the [**ComputeSharp.D2D1.WinUI**](https://www.nuget.org/packages/ComputeSharp.D2D1.WinUI/) package.
 
 > [!NOTE]
-> Many APIs in ComputeSharp.D2D1.\* are identical across the UWP and WinAppSDK targets, the only difference being the namespace (ending in either `.Uwp` or `.WinUI`). However, the UWP target is in sustained maintenance and not receiving new features. As such, some code changes might be needed compared to the samples shown here for WinUI. The snippets in this document reflect the API surface as of ComputeSharp.D2D1.WinUI 3.0.0 (the last release for the UWP target is instead 2.1.0).
+> Many APIs in ComputeSharp.D2D1.\* are identical across the UWP and WinUI targets, the only difference being the namespace (ending in either `.Uwp` or `.WinUI`). However, the UWP target is in sustained maintenance and not receiving new features. As such, some code changes might be needed compared to the samples shown here for WinUI. The snippets in this document reflect the API surface as of ComputeSharp.D2D1.WinUI 3.0.0 (the last release for the UWP target is 2.1.0).
 
 There are two main components in ComputeSharp to interop with Win2D:
 - `PixelShaderEffect<T>`: a Win2D effect that is powered by a D2D1 pixel shader. The shader itself is written in C# using the APIs provided by ComputeSharp. This class also provides properties to set effect sources, constant values, and more.
@@ -443,7 +443,7 @@ You can see there are four sections in this class:
 > The `PremultiplyEffect` node after the noise effect is very important: this is because Win2D effects assume that the output is premultiplied, whereas pixel shaders generally work with unpremultiplied pixels. As such, remember to manually insert premultiply/unpremultiply nodes before and after custom shaders, to ensure colors are correctly preserved.
 
 > [!NOTE]
-> This sample effect is using WinUI 3 namespaces, but the same code can be used on UWP as well. In that case, the namespace for ComputeSharp will be `ComputeSharp.Uwp`, matching the package name.
+> This sample effect is using WinUI namespaces, but the same code can be used on UWP as well. In that case, the namespace for ComputeSharp will be `ComputeSharp.Uwp`, matching the package name.
 
 ### Ready to draw!
 

hub/apps/develop/win2d/hellowin2dworld.md

@@ -1,7 +1,7 @@
 ---
 title: Win2D "Hello, World!" quickstart
 description: "This topic shows you how to create a very simple \"Hello, World!\" project for Win2D."
-ms.date: 10/25/2023
+ms.date: 10/28/2025
 ms.topic: quickstart
 keywords: windows 11, windows 10, uwp, xaml, windows app sdk, winui, windows ui, graphics, games, win2d
 ms.localizationpriority: medium
@@ -13,7 +13,7 @@ In this topic you'll create a very simple "Hello, World!" project for Win2D.
 
 In Visual Studio, create a new project from one of the following project templates:
 
-* **WinUI 3 (Windows App SDK)**. To create a new WinUI 3 project, use the **Blank App, Packaged (WinUI 3 in Desktop)** project template. You can find that project template by choosing language: either *C#* or *C++*; platform: *Windows*; project type: *Desktop*.
+* **WinUI (Windows App SDK)**. To create a new WinUI project, use the **WinUI Blank App (Packaged)** project template. You can find that project template by choosing language: either *C#* or *C++*; platform: *Windows*; project type: *Desktop*.
 * **Universal Windows Platform (UWP)**. To create a new UWP project, use the **Blank App (Universal Windows)** or **Blank App (C++/WinRT)** or **Blank App (Universal Windows - C++/CX)** project template. For language, choose: either *C#* or *C++*; platform: *Windows*; project type: *UWP*.
 
 > [!IMPORTANT]
@@ -37,7 +37,7 @@ And then add a **CanvasControl**, prefixed with that xml namespace. For example,
 
 The project won't build at the moment, due to the referenced-but-not-implemented **Draw** event handler. So we'll remedy that next, while we add some drawing code to interact with the **CanvasControl**.
 
-## For a WinUI 3 (Windows App SDK) project
+## For a WinUI (Windows App SDK) project
 
 For a C# project, add the following event handler to `MainWindow.xaml.cs`:
 
@@ -87,7 +87,7 @@ You can now build and run the project. You'll see some Win2D content—a bla
 
 ## For a UWP project
 
-For a C# project, you can use the same C# code as for a WinUI 3 project (see the [For a WinUI 3 project](#for-a-winui-3-windows-app-sdk-project) section above). The only differences are that you'll be editing `MainPage.xaml.cs` instead of `MainWindow.xaml.cs`. And you'll need to change `Microsoft.UI.Colors` to `Windows.UI.Colors`.
+For a C# project, you can use the same C# code as for a WinUI project (see the [For a WinUI project](#for-a-winui-windows-app-sdk-project) section above). The only differences are that you'll be editing `MainPage.xaml.cs` instead of `MainWindow.xaml.cs`. And you'll need to change `Microsoft.UI.Colors` to `Windows.UI.Colors`.
 
 For a C++/WinRT project, add the following code to `pch.h`, `MainPage.h`, and `MainPage.cpp`:
 
@@ -124,8 +124,8 @@ For a C++/CX project, add the following event handler to `MainPage.xaml.h` and `
 // MainPage.xaml.h
 ...
 void CanvasControl_Draw(
-	Microsoft::Graphics::Canvas::UI::Xaml::CanvasControl^ sender,
-	Microsoft::Graphics::Canvas::UI::Xaml::CanvasDrawEventArgs^ args);
+    Microsoft::Graphics::Canvas::UI::Xaml::CanvasControl^ sender,
+    Microsoft::Graphics::Canvas::UI::Xaml::CanvasDrawEventArgs^ args);
 ...
 
 // MainWindow.xaml.cpp

hub/apps/develop/win2d/index.md

@@ -1,7 +1,7 @@
 ---
 title: Overview of Win2D
 description: Win2D is an easy-to-use Windows Runtime API for immediate-mode 2D graphics rendering with GPU acceleration.
-ms.date: 10/23/2023
+ms.date: 10/28/2025
 ms.topic: concept-article
 keywords: windows 10, windows 11, uwp, xaml, windows app sdk, winui, windows ui, graphics, games
 ms.localizationpriority: medium
@@ -11,20 +11,20 @@ ms.localizationpriority: medium
 
 Win2D is an easy-to-use Windows Runtime (WinRT) API for immediate-mode 2D graphics rendering with GPU acceleration. It's ideal for creating simple games, displays such as charts, and other simple 2D graphics.
 
-You can use Win2D in your WinUI 3 (Windows App SDK) apps or Universal Windows Platform (UWP) apps, using either C#, C++, or VB. Win2D utilizes the power of Direct2D, and it integrates seamlessly with XAML on both WinUI 3 (Windows App SDK) and UWP.
+You can use Win2D in your WinUI (Windows App SDK) apps or Universal Windows Platform (UWP) apps, using either C#, C++, or VB. Win2D utilizes the power of Direct2D, and it integrates seamlessly with XAML on both WinUI (Windows App SDK) and UWP.
 
 > [!IMPORTANT]
-> Win2D for WinUI 3 (Windows App SDK) is a work-in-progress, and some features aren't supported. This documentation refers to both the WinUI 3 and UWP versions, which mostly share the same API surface and functionality. Whenever there's any relevant differences between the two, we'll call it out in the documentation. But otherwise, the info being presented applies to both platforms in the same way.
+> Win2D for WinUI (Windows App SDK) is a work-in-progress, and some features aren't supported. This documentation refers to both the WinUI and UWP versions, which mostly share the same API surface and functionality. Whenever there's any relevant differences between the two, we'll call it out in the documentation. But otherwise, the info being presented applies to both platforms in the same way.
 
 ## Get started
 
 Win2D is available as a NuGet package, or as source code (for the source code, see the [Win2D](https://github.com/microsoft/Win2D) repo on GitHub).
 
 ### Reference the Win2D NuGet package
 
-In a WinUI 3 or UWP project in Visual Studio, click **Tools** > **NuGet Package Manager** > **Manage NuGet Packages for Solution...** > **Browse**. Make sure that **Include prerelease** is unchecked, and type or paste into the search box:
+In a WinUI or UWP project in Visual Studio, click **Tools** > **NuGet Package Manager** > **Manage NuGet Packages for Solution...** > **Browse**. Make sure that **Include prerelease** is unchecked, and type or paste into the search box:
 
-* For a WinUI 3 project, [*Microsoft.Graphics.Win2D*](https://www.nuget.org/packages/Microsoft.Graphics.Win2D/).
+* For a WinUI project, [*Microsoft.Graphics.Win2D*](https://www.nuget.org/packages/Microsoft.Graphics.Win2D/).
 * For a UWP project, [*Win2D.uwp*](https://www.nuget.org/packages/Win2D.uwp/).
 
 Select the correct item in search results, check your project, and click **Install** to install the package into that project. Accept the license agreement.

hub/apps/develop/win2d/quick-start.md

@@ -1,7 +1,7 @@
 ---
 title: Build a simple Win2D app
 description: This tutorial introduces some of the basic drawing capabilities of Win2D.
-ms.date: 10/25/2023
+ms.date: 10/28/2025
 ms.topic: how-to
 keywords: windows 11, windows 10, uwp, xaml, windows app sdk, winui, windows ui, graphics, games
 ms.localizationpriority: medium
@@ -26,7 +26,7 @@ Make sure to set up your machine with all the necessary tools:
 
 ## Create a new Win2D project
 
-Follow the steps in the [Win2D "Hello, World!" quickstart](./hellowin2dworld.md) to create a new project using Win2D, and to add a reference to the Win2D NuGet package. You can use either WinUI 3 (Windows App SDK) or the Universal Windows Platform (UWP).
+Follow the steps in the [Win2D "Hello, World!" quickstart](./hellowin2dworld.md) to create a new project using Win2D, and to add a reference to the Win2D NuGet package. You can use either WinUI (Windows App SDK) or the Universal Windows Platform (UWP).
 
 ## Add a Win2D CanvasControl to your app's XAML
 

hub/apps/develop/win2d/using-win2d-without-built-in-controls.md

@@ -1,7 +1,7 @@
 ---
 title: Using Win2D without built-in controls
 description: A guide on how to use the lower level APIs of Win2D, without any of its built-in XAML controls.
-ms.date: 05/28/2023
+ms.date: 10/28/2025
 ms.topic: concept-article
 keywords: windows 10, windows 11, uwp, xaml, windows app sdk, winui, windows ui, graphics, games, effect win2d d2d d2d1 direct2d interop cpp csharp
 ms.localizationpriority: medium
@@ -66,7 +66,7 @@ swapChain.Present();
 The size of the swap chain should match the size of the `CoreWindow`. If the size of the window changes, call [`ResizeBuffers(Size)`](https://microsoft.github.io/Win2D/WinUI2/html/M_Microsoft_Graphics_Canvas_CanvasSwapChain_ResizeBuffers_3.htm) on the swap chain with the new size. For more information, see the `CoreWindow` Win2D sample.
 
 > [!NOTE]
-> `CoreWindow` is only supported on UWP. For WinAppSDK apps, use either composition or HWND swapchains.
+> `CoreWindow` is only supported on UWP. For Windows App SDK, use either composition or HWND swapchains.
 
 ## CanvasSwapChainPanel
 

hub/apps/develop/windows-integration/integrate-sharesheet-overview.md

@@ -2,7 +2,7 @@
 description: Learn how to integrate apps with the Windows Share Sheet, a system-provided UI that enables users to share content from your app with other Windows apps.
 title: Integrate Share options in your Windows app - A comprehensive guide
 ms.topic: concept-article
-ms.date: 11/01/2024
+ms.date: 10/28/2025
 ms.localizationpriority: medium
 keywords: windows, windows share, share sheet, share charm, file sharing, sharesheet, share button, share option, pwa, packaged apps, windows 11, c++
 #customer intent: As a Windows developer, I want to learn how to integrate share options in my Windows app so that users can share content with other Windows apps.
@@ -33,5 +33,5 @@ In this comprehensive guide, you'll learn how to add the share feature to your p
 - [Migrate from UWP to the Windows App SDK](/windows/apps/windows-app-sdk/migrate-to-windows-app-sdk/migrate-to-windows-app-sdk-ovw)
 - [Advantages and Disadvantages of packaging an application - Deployment overview](/windows/apps/package-and-deploy/#advantages-and-disadvantages-of-packaging-your-app)
 - [Identity, Registration and Activation of Non-packaged Win32 Apps](https://blogs.windows.com/windowsdeveloper/2019/10/29/identity-registration-and-activation-of-non-packaged-win32-apps/)
-- [Share Contract Implementation for WinAppSDK App](https://github.com/kmahone/WindowsAppSDK-Samples/tree/user/kmahone/shareapp/Samples/AppLifecycle/ShareTarget/WinUI-CS-ShareTargetSampleApp)
+- [Share Contract Implementation for Windows App SDK](https://github.com/kmahone/WindowsAppSDK-Samples/tree/user/kmahone/shareapp/Samples/AppLifecycle/ShareTarget/WinUI-CS-ShareTargetSampleApp)
 - [Share Contract Implementation for Apps Packaged with External Location](https://github.com/microsoft/AppModelSamples/blob/master/Samples/PackageWithExternalLocation/cs/PhotoStoreDemo/StartUp.cs)

hub/apps/develop/windows-integration/integrate-sharesheet-packaged.md

@@ -2,7 +2,7 @@
 description: Discover how to integrate packaged apps with the Windows Share.
 title: Integrate packaged apps with Windows Share
 ms.topic: how-to
-ms.date: 04/16/2024
+ms.date: 10/28/2025
 ms.localizationpriority: medium
 ---
 
@@ -127,7 +127,7 @@ static async void HandleShareAsync(ShareTargetActivatedEventArgs args)
 - [Migrate from UWP to the Windows App SDK](/windows/apps/windows-app-sdk/migrate-to-windows-app-sdk/migrate-to-windows-app-sdk-ovw)
 - [Advantages and Disadvantages of packaging an application - Deployment overview](/windows/apps/package-and-deploy/#advantages-and-disadvantages-of-packaging-your-app)
 - [Identity, Registration and Activation of Non-packaged Win32 Apps](https://blogs.windows.com/windowsdeveloper/2019/10/29/identity-registration-and-activation-of-non-packaged-win32-apps/)
-- [Share Contract Implementation for WinAppSDK App](https://github.com/kmahone/WindowsAppSDK-Samples/tree/user/kmahone/shareapp/Samples/AppLifecycle/ShareTarget/WinUI-CS-ShareTargetSampleApp)
+- [Share Contract Implementation for Windows App SDK](https://github.com/kmahone/WindowsAppSDK-Samples/tree/user/kmahone/shareapp/Samples/AppLifecycle/ShareTarget/WinUI-CS-ShareTargetSampleApp)
 - [Share Contract Implementation for Apps Packaged with External Location](https://github.com/microsoft/AppModelSamples/blob/master/Samples/PackageWithExternalLocation/cs/PhotoStoreDemo/StartUp.cs)
 - [Get activation info for packaged apps](/windows/apps/desktop/modernize/get-activation-info-for-packaged-apps)
 - [ShareTarget schema reference](/uwp/schemas/appxpackage/uapmanifestschema/element-uap-sharetarget)

hub/apps/develop/windows-integration/integrate-sharesheet-unpackaged.md

@@ -2,7 +2,7 @@
 description: Discover how to integrate unpackaged apps with the Windows Share feature.
 title: Integrate unpackaged apps with Windows Share
 ms.topic: concept-article
-ms.date: 05/27/2025
+ms.date: 10/28/2025
 ms.localizationpriority: medium
 # Customer intent: As a Windows developer, I want to learn how to integrate unpackaged apps with the Windows Share feature.
 ---
@@ -263,5 +263,5 @@ The following video demonstrates how an unpackaged app can be a share target aft
 - [Migrate from UWP to the Windows App SDK](/windows/apps/windows-app-sdk/migrate-to-windows-app-sdk/migrate-to-windows-app-sdk-ovw)
 - [Advantages and Disadvantages of packaging an application - Deployment overview](/windows/apps/package-and-deploy/#advantages-and-disadvantages-of-packaging-your-app)
 - [Identity, Registration and Activation of Non-packaged Win32 Apps](https://blogs.windows.com/windowsdeveloper/2019/10/29/identity-registration-and-activation-of-non-packaged-win32-apps/)
-- [Share Contract Implementation for WinAppSDK App](https://github.com/kmahone/WindowsAppSDK-Samples/tree/user/kmahone/shareapp/Samples/AppLifecycle/ShareTarget/WinUI-CS-ShareTargetSampleApp)
+- [Share Contract Implementation for Windows App SDK](https://github.com/kmahone/WindowsAppSDK-Samples/tree/user/kmahone/shareapp/Samples/AppLifecycle/ShareTarget/WinUI-CS-ShareTargetSampleApp)
 - [Share Contract Implementation for Apps Packaged with External Location](https://github.com/microsoft/AppModelSamples/tree/master/Samples/PackageWithExternalLocation/cppwinrt/PackageWithExternalLocationCppApp)

hub/apps/get-started/windows-developer-glossary.md

@@ -2,7 +2,7 @@
 title: Windows developer glossary
 description:  A glossary of terms related to Windows application development.
 ms.topic: glossary
-ms.date: 9/24/2025
+ms.date: 10/28/2025
 ms.localizationpriority: medium
 ms.collection: windows11
 audience: new-desktop-app-developers
@@ -166,7 +166,7 @@ Windows AI Foundry offers AI-backed features and APIs on Windows 11 PCs. These f
 
 #### Windows API
 
-Refers to the entire set of Windows APIs including Win32 APIs, COM APIs, UWP WinRT APIs, and the WinRT/Win32 APIs that are part of WinAppSDK and WinUI 3.
+Refers to the entire set of Windows APIs including Win32 APIs, COM APIs, UWP WinRT APIs, and the WinRT/Win32 APIs that are part of the Windows App SDK and WinUI.
 
 #### Windows App SDK