docs: develop-input (#6523)

* docs: develop-input

Modernize documentation by updating legacy references.
Batch: develop-input
Files changed: 4
Proposals applied: 11

* docs: develop-performance

Modernize documentation by updating legacy references.
Batch: develop-performance
Files changed: 1
Proposals applied: 1

* docs: develop-platform-xaml

Modernize documentation by updating legacy references.
Batch: develop-platform-xaml
Files changed: 4
Proposals applied: 6

* docs: develop-security

Modernize documentation by updating legacy references.
Batch: develop-security
Files changed: 4
Proposals applied: 4

* docs: develop-ui

Modernize documentation by updating legacy references.
Batch: develop-ui
Files changed: 1
Proposals applied: 1

* docs: develop-ui-controls

Modernize documentation by updating legacy references.
Batch: develop-ui-controls
Files changed: 6
Proposals applied: 12

* docs: develop-ui-controls-dialogs-and-flyouts

Modernize documentation by updating legacy references.
Batch: develop-ui-controls-dialogs-and-flyouts
Files changed: 1
Proposals applied: 3

* docs: develop-ui-navigation

Modernize documentation by updating legacy references.
Batch: develop-ui-navigation
Files changed: 1
Proposals applied: 1

* docs: develop-win2d

Modernize documentation by updating legacy references.
Batch: develop-win2d
Files changed: 1
Proposals applied: 3

* docs: develop-windows-integration

Modernize documentation by updating legacy references.
Batch: develop-windows-integration
Files changed: 8
Proposals applied: 10

* docs: get-started

Modernize documentation by updating legacy references.
Batch: get-started
Files changed: 1
Proposals applied: 1

* docs: publish-faq

Modernize documentation by updating legacy references.
Batch: publish-faq
Files changed: 1
Proposals applied: 1

* docs: publish-msstore-dev-cli

Modernize documentation by updating legacy references.
Batch: publish-msstore-dev-cli
Files changed: 1
Proposals applied: 3

* docs: winui-winui3

Modernize documentation by updating legacy references.
Batch: winui-winui3
Files changed: 1
Proposals applied: 1

* fix: remove blank line in nextstepaction block in split-view.md

Co-authored-by: niels9001 <[email protected]>
Agent-Logs-Url: https://github.com/MicrosoftDocs/windows-dev-docs-pr/sessions/01c50673-e462-43e6-88cc-4bd2092cbc2f

* fix: correct include path for winui-3-gallery in split-view.md

Co-authored-by: niels9001 <[email protected]>
Agent-Logs-Url: https://github.com/MicrosoftDocs/windows-dev-docs-pr/sessions/1e61ef2b-4164-4ba0-9eab-91927422679e

* Revert UWP app reference in packaging instructions

It's the actual title of the linked article.

* Revert to UWP in packaging article link text

It's the actual title of the linked article.

* Restore original link text for packaging article

It's the actual title of the linked article.

---------

Co-authored-by: John Kennedy <[email protected]>
Co-authored-by: copilot-swe-agent[bot] <[email protected]>
Co-authored-by: niels9001 <[email protected]>
Co-authored-by: Jim Walker <[email protected]>

Author: 4 people

hub/apps/develop/performance/index.md

@@ -12,7 +12,7 @@ ms.localizationpriority: medium
 
 Improving the performance and fundamentals of your application gives it a feeling of polish and craftsmanship, while saving your customers time, money, battery life, and development effort. Your app will consume less power, improving battery life and reducing carbon emissions. Apps run more smoothly on less expensive hardware. Your customers' productivity increases.
 
-This page provides an overview of the technologies and development tools for measuring, understanding, and refining the performance of your Windows application. If you are writing a UWP application, be sure to also consult the [UWP Performance](/windows/uwp/debug-test-perf/performance-and-xaml-ui) documentation.
+This page provides an overview of the technologies and development tools for measuring, understanding, and refining the performance of your Windows application.
 
 ## What is application performance and why is it important?
 

hub/apps/develop/platform/xaml/dependency-properties-overview.md

@@ -191,7 +191,7 @@ You can deliberately set a property to the default value even after you have alr
 All [**DependencyObject**](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.dependencyobject) instances must be created on the UI thread which is associated with the current [**Window**](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.Window) that is shown by a WinUI app. Although each **DependencyObject** must be created on the main UI thread, the objects can be accessed using a dispatcher reference from other threads, by accessing the [**DispatcherQueue**](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.dependencyobject.dispatcherqueue) property. Then you can call methods such as [**TryEnqueue**](/windows/windows-app-sdk/api/winrt/microsoft.ui.dispatching.dispatcherqueue.tryenqueue) and execute your code within the rules of thread restrictions on the UI thread.
 
 > [!NOTE]
-> For UWP apps, access the [**Dispatcher**](/uwp/api/windows.ui.xaml.dependencyobject.dispatcher) property. Then you can call methods such as [**RunAsync**](/uwp/api/windows.ui.core.coredispatcher.runasync) on the [**CoreDispatcher**](/uwp/api/Windows.UI.Core.CoreDispatcher) object, and execute your code within the rules of thread restrictions on the UI thread. For more info about differences between UWP and WinUI 3 for the Windows App SDK, see [Threading functionality migration](../../../windows-app-sdk/migrate-to-windows-app-sdk/guides/threading.md).
+> For more info about differences between UWP and WinUI 3 for the Windows App SDK, see [Threading functionality migration](../../../windows-app-sdk/migrate-to-windows-app-sdk/guides/threading.md).
 
 The threading aspects of [**DependencyObject**](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.dependencyobject) are relevant because it generally means that only code that runs on the UI thread can change or even read the value of a dependency property. Threading issues can usually be avoided in typical UI code that makes correct use of **async** patterns and background worker threads. You typically only run into **DependencyObject**-related threading issues if you are defining your own **DependencyObject** types and you attempt to use them for data sources or other scenarios where a **DependencyObject** isn't necessarily appropriate.
 

hub/apps/develop/platform/xaml/index.md

@@ -1,6 +1,6 @@
 ---
 ms.assetid: b632a6cc-3503-4ab8-bfd1-dde731bd89ab
-description: This section includes topics that explain the XAML framework for Universal Windows Platform (UWP) apps.
+description: This section includes topics that explain the XAML framework for WinUI apps.
 title: XAML platform
 ms.date: 09/08/2025
 ms.topic: article
@@ -9,7 +9,7 @@ ms.localizationpriority: medium
 ---
 # XAML platform
 
-This section includes topics that explain programming concepts that are generally applicable to any app that you write using the Windows Runtime and XAML for your UI definition. This section applies to both WinUI 3 and UWP.
+This section includes topics that explain programming concepts that are generally applicable to any app that you write using the Windows Runtime and XAML for your UI definition.
 
 | Topic | Description |
 |-------|-------------|

hub/apps/develop/platform/xaml/x-name-attribute.md

@@ -42,7 +42,7 @@ CombiningCharacter::= none
 
 ## Remarks
 
-The specified **x:Name** becomes the name of a field that is created in the underlying code when XAML is processed, and that field holds a reference to the object. The process of creating this field is performed by the MSBuild target steps, which also are responsible for joining the partial classes for a XAML file and its code-behind. This behavior is not necessarily XAML-language specified; it is the particular implementation that Universal Windows Platform (UWP) programming for XAML applies to use **x:Name** in its programming and application models.
+The specified **x:Name** becomes the name of a field that is created in the underlying code when XAML is processed, and that field holds a reference to the object. The process of creating this field is performed by the MSBuild target steps, which also are responsible for joining the partial classes for a XAML file and its code-behind. This behavior is not necessarily XAML-language specified; it is the particular implementation that WinUI programming applies to use **x:Name** in its programming and application models.
 
 Each defined **x:Name** must be unique within a XAML namescope. Generally, a XAML namescope is defined at the root element level of a loaded page and contains all elements under that element in a single XAML page. Additional XAML namescopes are defined by any control template or data template that is defined on that page. At run time, another XAML namescope is created for the root of the object tree that is created from an applied control template, and also by object trees created from a call to [**XamlReader.Load**](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.markup.xamlreader.load). For more info, see [XAML namescopes](xaml-namescopes.md).
 

hub/apps/develop/platform/xaml/x-uid-directive.md

@@ -1,15 +1,15 @@
 ---
-description: Provides a unique identifier for markup elements. For Universal Windows Platform (UWP) XAML, this unique identifier is used by XAML localization processes and tools, such as using resources from a .resw resource file.
+description: Provides a unique identifier for markup elements. For WinUI XAML, this unique identifier is used by XAML localization processes and tools, such as using resources from a .resw resource file.
 title: xUid directive
 ms.assetid: 9FD6B62E-D345-44C6-B739-17ED1A187D69
 ms.date: 09/09/2025
 ms.topic: article
-keywords: windows 10, uwp
+keywords: windows 10, winui
 ms.localizationpriority: medium
 ---
 # x:Uid directive
 
-Provides a unique identifier for markup elements. For Universal Windows Platform (UWP) XAML, this unique identifier is used by XAML localization processes and tools, such as using resources from a .resw resource file.
+Provides a unique identifier for markup elements. For WinUI XAML, this unique identifier is used by XAML localization processes and tools, such as using resources from a .resw resource file.
 
 ## XAML attribute usage
 

hub/apps/develop/security/credential-locker.md

@@ -10,7 +10,7 @@ ms.topic: how-to
 
 This article describes how Windows apps can use the Credential Locker to securely store and retrieve user credentials, and roam them between devices with the user's Microsoft account.
 
-The Windows Runtime (WinRT) APIs for Credential Locker access are part of the [Windows Software Development Kit (SDK)](https://developer.microsoft.com/windows/downloads/windows-sdk/). These APIs were created for use in Universal Windows Platform (UWP) apps, but they can also be used in WinUI apps or in packaged desktop apps, including WPF and Windows Forms. For more information about using WinRT APIs in your Windows desktop app, see [Call Windows Runtime APIs in desktop apps](/windows/apps/desktop/modernize/desktop-to-uwp-enhance).
+The Windows Runtime (WinRT) APIs for Credential Locker access are part of the [Windows Software Development Kit (SDK)](https://developer.microsoft.com/windows/downloads/windows-sdk/). These APIs can be used in WinUI as well as other desktop apps, such as WPF and WinForms. For more information about using WinRT APIs in your Windows desktop app, see [Call Windows Runtime APIs in desktop apps](/windows/apps/desktop/modernize/desktop-to-uwp-enhance).
 
 ## Overview of the sample scenario
 

hub/apps/develop/security/fingerprint-biometrics.md

@@ -10,7 +10,7 @@ ms.topic: how-to
 
 This article explains how to add fingerprint biometrics to your Windows app, including a request for fingerprint authentication when the user must consent to a particular action increases the security of your app. For example, you could require fingerprint authentication before authorizing an in-app purchase, or access to restricted resources. Fingerprint authentication is managed using the [UserConsentVerifier](/uwp/api/Windows.Security.Credentials.UI.UserConsentVerifier) class in the [Windows.Security.Credentials.UI](/uwp/api/Windows.Security.Credentials.UI) namespace.
 
-The Windows Runtime (WinRT) APIs for fingerprint biometrics are part of the [Windows Software Development Kit (SDK)](https://developer.microsoft.com/windows/downloads/windows-sdk/). These APIs were created for use in Universal Windows Platform (UWP) apps, but they can also be used in WinUI apps or in packaged desktop apps, including WPF and Windows Forms. For more information about using WinRT APIs in your Windows desktop app, see [Call Windows Runtime APIs in desktop apps](/windows/apps/desktop/modernize/desktop-to-uwp-enhance).
+The Windows Runtime (WinRT) APIs for fingerprint biometrics are part of the [Windows Software Development Kit (SDK)](https://developer.microsoft.com/windows/downloads/windows-sdk/). These APIs can be used in WinUI as well as other desktop apps, such as WPF and WinForms. For more information about using WinRT APIs in your Windows desktop app, see [Call Windows Runtime APIs in desktop apps](/windows/apps/desktop/modernize/desktop-to-uwp-enhance).
 
 ## Check the device for a fingerprint reader
 

hub/apps/develop/security/oauth2.md

@@ -11,10 +11,6 @@ keywords: windows, winui, winrt, dotnet, security
 
 The [OAuth2Manager](/windows/windows-app-sdk/api/winrt/microsoft.security.authentication.oauth.oauth2manager) in Windows App SDK enables desktop applications such as WinUI 3 to seamlessly perform OAuth 2.0 authorization on Windows. The **OAuth2Manager** API doesn't provide APIs for the implicit request and resource owner password credential because of the security concerns that entails. Use the authorization code grant type with Proof Key for Code Exchange (PKCE). For more information, see the [PKCE RFC](https://tools.ietf.org/html/rfc7636).
 
-## OAuth 2.0 background for Windows apps
-
-The Windows Runtime (WinRT) [WebAuthenticationBroker](/uwp/api/windows.security.authentication.web.webauthenticationbroker), primarily designed for UWP apps, presents several challenges when used in desktop apps. Key issues include the dependency on [ApplicationView](/uwp/api/windows.ui.viewmanagement.applicationview), which isn't compatible with desktop app frameworks. As a result, developers must resort to workarounds involving interop interfaces and additional code to implement OAuth 2.0 functionality into WinUI and other desktop apps.
-
 ## OAuth2Manager API in Windows App SDK
 
 The **OAuth2Manager** API for Windows App SDK provides a streamlined solution that meets the expectations of developers. It offers seamless OAuth 2.0 capabilities with full feature parity across all Windows platforms supported by Windows App SDK. The new API eliminates the need for cumbersome workarounds and simplifies the process of incorporating OAuth 2.0 functionality into desktop apps.

hub/apps/develop/security/smart-cards.md

@@ -13,7 +13,7 @@ ms.localizationpriority: medium
 
 This topic explains how Windows apps can use smart cards to connect users to secure network services, including how to access physical smart card readers, create virtual smart cards, communicate with smart cards, authenticate users, reset user PINs, and remove or disconnect smart cards.
 
-The Windows Runtime (WinRT) APIs for smart cards are part of the [Windows Software Development Kit (SDK)](https://developer.microsoft.com/windows/downloads/windows-sdk/). These APIs were created for use in Universal Windows Platform (UWP) apps, but they can also be used in WinUI apps or in packaged desktop apps, including WPF and Windows Forms. For more information about using WinRT APIs in your Windows desktop app, see [Call Windows Runtime APIs in desktop apps](/windows/apps/desktop/modernize/desktop-to-uwp-enhance).
+The Windows Runtime (WinRT) APIs for smart cards are part of the [Windows Software Development Kit (SDK)](https://developer.microsoft.com/windows/downloads/windows-sdk/). These APIs can be used in WinUI as well as other desktop apps, such as WPF and WinForms. For more information about using WinRT APIs in your Windows desktop app, see [Call Windows Runtime APIs in desktop apps](/windows/apps/desktop/modernize/desktop-to-uwp-enhance).
 
 ## Configure the app manifest