Merge pull request #6339 from MicrosoftDocs/fix/winui-3-first-reference

Use 'WinUI 3' for first reference in WinUI 3 topics

Author: GrantMeStrength

hub/apps/api-reference/cs-interop-apis/index.md

@@ -7,7 +7,7 @@ keywords: windows 10, windows 11, Windows App SDK, desktop development, winui, a
 ms.localizationpriority: low
 ---
 
-# Interop C# APIs for WinUI
+# Interop C# APIs for WinUI 3
 
 As a C# desktop application developer, in .NET you can make use of C# interop classes whose methods wrap and represent several interoperability functions. These include methods of C# classes representing the [GetWindowIdFromWindow](/windows/windows-app-sdk/api/win32/microsoft.ui.interop/nf-microsoft-ui-interop-getwindowidfromwindow) function, for example.
 

hub/apps/design/layout/attached-layouts.md

@@ -52,7 +52,7 @@ For this reason, a Panel in XAML has often been synonymous with layout, but tech
 The [ItemsRepeater](../controls/items-repeater.md) also behaves like Panel, but, unlike Panel, it does not expose a Children property that would allow programmatically adding or removing UIElement children.  Instead, the lifetime of its children are automatically managed by the framework to correspond to a collection of data items.  Although it is not derived from Panel, it behaves and is treated by the framework like a Panel.
 
 > [!NOTE]
-> The [LayoutPanel](/uwp/api/microsoft.ui.xaml.controls.layoutpanel) is a container, derived from Panel, that delegates its logic to the attached [Layout](/uwp/api/microsoft.ui.xaml.controls.layoutpanel.layout) object.  LayoutPanel is in *Preview* and is currently available only in the *Prerelease* drops of the WinUI package.
+> The [LayoutPanel](/uwp/api/microsoft.ui.xaml.controls.layoutpanel) is a container, derived from Panel, that delegates its logic to the attached [Layout](/uwp/api/microsoft.ui.xaml.controls.layoutpanel.layout) object.  LayoutPanel is in *Preview* and is currently available only in the *Prerelease* drops of the WinUI 3 package.
 
 #### Containers
 

hub/apps/design/motion/timing-and-easing.md

@@ -22,7 +22,7 @@ While motion is based in the real world, we are also a digital medium, which com
 
 ## Standard animation duration values
 
-WinUI provides a set of standard animation durations that are used throughout the platform controls. You can use these named resources when building custom Storyboard animations as well.
+WinUI 3 provides a set of standard animation durations that are used throughout the platform controls. You can use these named resources when building custom Storyboard animations as well.
 
 |ThemeResource Name  |Value  |
 |---------|---------|

hub/apps/design/shell/tiles-and-notifications/secondary-tiles-desktop-pinning.md

@@ -11,7 +11,7 @@ ms.localizationpriority: medium
 
 # Pin secondary tiles from desktop apps
 
-A desktop app such as a WinUI app (using the Windows App SDK), or a Windows Presentation Foundation (WPF) or Windows Forms (WinForms) app, can pin a secondary tile by using a packaged app (see [Building an MSIX package from your code](/windows/msix/desktop/source-code-overview)). This was formerly known as Desktop Bridge.
+A desktop app such as a WinUI 3 app (using the Windows App SDK), or a Windows Presentation Foundation (WPF) or Windows Forms (WinForms) app, can pin a secondary tile by using a packaged app (see [Building an MSIX package from your code](/windows/msix/desktop/source-code-overview)). This was formerly known as Desktop Bridge.
 
 ![Screenshot of secondary tiles](images/secondarytiles.png)
 

hub/apps/design/signature-experiences/motion.md

@@ -63,7 +63,7 @@ _Click the image to see it animated._
 
 ### Resourceful: Utilizes existing controls to bring consistency where possible
 
-Avoid custom animations where possible. Use animation resources like [WinUI](../../winui/index.md) controls for page transitions, in-page focus, and micro interactions. If you can't use WinUI controls, mimic existing OS behaviors based on where the app entry point lives.
+Avoid custom animations where possible. Use animation resources like [WinUI 3](../../winui/index.md) controls for page transitions, in-page focus, and micro interactions. If you can't use WinUI controls, mimic existing OS behaviors based on where the app entry point lives.
 
 _Example:_ [Page transitions](../motion/page-transitions.md), [connected animations](../motion/connected-animation.md), and [animated icons](../controls/animated-icon.md) are the recommended WinUI controls that add delightful and necessary motion to apps.
 

hub/apps/design/style/mica.md

@@ -66,7 +66,7 @@ Card pattern content layer<br/>
 
 Mica is ideal as a foundation layer in your app's hierarchy due to its inactive and active states and subtle personalization. To follow the two-layer [Layering and Elevation](../signature-experiences/layering.md) system, we encourage you to apply Mica as the base layer of your app and add an additional content layer that sits on top of the base layer. The content layer should pick up the material behind it, Mica, using the `LayerFillColorDefaultBrush`, a low-opacity solid color, as its background. Our recommended content layer patterns are:
 
-* **Standard pattern**: A contiguous background for large areas that need a distinct hierarchical differentiation from the base layer. The `LayerFillColorDefaultBrush` should be applied to the container backgrounds of your WinUI app surfaces (e.g. Grids, StackPanels, Frames, etc.).
+* **Standard pattern**: A contiguous background for large areas that need a distinct hierarchical differentiation from the base layer. The `LayerFillColorDefaultBrush` should be applied to the container backgrounds of your WinUI 3 app surfaces (e.g. Grids, StackPanels, Frames, etc.).
 * **Card pattern**: Segmented cards for apps that are designed with multiple sectioned and discontinuous UI components. For the definition of the card UI using the `LayerFillColorDefaultBrush`, see [Layering and Elevation](../signature-experiences/layering.md) guidance.
 
 To give your app's window a seamless look, Mica should be visible in the title bar if you choose to apply the material to your app. You can show Mica in the title bar by extending your app into the non-client area and creating a transparent custom title bar. For more info, see [Title bar](../basics/titlebar-design.md).

hub/apps/desktop/modernize/desktop-to-uwp-supported-api.md

@@ -16,7 +16,7 @@ Although you can use most Windows Runtime (WinRT) APIs (see [Windows UWP namespa
 * APIs that have dependencies on user interface (UI) features that were designed for use only in a Universal Windows Platform (UWP) app.
 * APIs that require package identity (see [Features that require package identity](./modernize-packaged-apps.md)). Such APIs are supported only in desktop apps that are packaged using [MSIX](/windows/msix/).
 
-This article provides details about both of those sets of WinRT APIs. Where available, this article suggests alternative APIs to achieve the same functionality as the APIs that are unsupported in desktop apps. Most of the alternative APIs are available in [WinUI](../../winui/index.md) or via WinRT COM interfaces that are available in the Windows SDK.
+This article provides details about both of those sets of WinRT APIs. Where available, this article suggests alternative APIs to achieve the same functionality as the APIs that are unsupported in desktop apps. Most of the alternative APIs are available in [WinUI 3](../../winui/index.md) or via WinRT COM interfaces that are available in the Windows SDK.
 
 > [!NOTE]
 > Apps using .NET can make use of provided class implementations for some of the WinRT COM interfaces listed in this article. Those classes are easier to work with than using the WinRT COM interfaces directly. For more information about the available class implementations, see [Call interop APIs from a .NET app](winrt-com-interop-csharp.md). Note that those classes require the .NET 6 SDK or later.

hub/apps/desktop/modernize/index.md

@@ -24,7 +24,7 @@ The Windows App SDK is a set of new developer components and tools that represen
 
 For more information, see [Windows App SDK](../../windows-app-sdk/index.md).
 
-## WinUI
+## WinUI 3
 
 WinUI is a native user experience framework for both Windows desktop and UWP applications. WinUI started as a toolkit that provided new and updated versions of WinRT XAML controls for UWP apps that target down-level versions of Windows. The latest version, WinUI, has grown in scope and is now the modern native UI platform for Windows desktop apps.
 

hub/apps/desktop/modernize/ui/apply-windows-themes.md

@@ -38,7 +38,7 @@ In practice, this means that in Dark mode, most of the UI will be dark, and in L
 
 ## Enable support for switching color modes
 
-There are many approaches to implementing Dark mode support in an application. Some apps contain two sets of UIs (one with a light color and one with a dark color). Some Windows UI frameworks, such as [WinUI](../../../winui/winui3/index.md), automatically detect a system's theme and adjust the UI to follow the system theme. To fully support Dark mode, the entirety of an app's surface must follow the dark theme.
+There are many approaches to implementing Dark mode support in an application. Some apps contain two sets of UIs (one with a light color and one with a dark color). Some Windows UI frameworks, such as [WinUI 3](../../../winui/winui3/index.md), automatically detect a system's theme and adjust the UI to follow the system theme. To fully support Dark mode, the entirety of an app's surface must follow the dark theme.
 
 There are two main things you can do in your Win32 app to support both Light and Dark themes.
 

hub/apps/desktop/modernize/winrt-com-interop-csharp.md

@@ -16,7 +16,7 @@ This topic lists the available C# interop classes, and shows how to use them. Th
 
 The C# interop classes listed in the next section ([Available C# interop classes](#available-c-interop-classes)) are available in .NET either as part of the [Windows App SDK](../../windows-app-sdk/index.md), or else by using a particular [Target Framework Moniker](desktop-to-uwp-enhance.md#net-6-and-later-use-the-target-framework-moniker-option), as we'll see.
 
-### In a WinUI C# desktop project
+### In a WinUI 3 C# desktop project
 
 When you create a new WinUI project in Visual Studio (see [Create your first WinUI project](../../winui/winui3/create-your-first-winui3-app.md)), your project is already configured, and you can start using all of the C# interop classes right away.