updating terms to align with official names from the product team (#3529)

* updating terms to align with official names from the product team

* fixing pre-existing issues

Author: stevewhims

hub/apps/api-reference/bootstrapper-cpp-api/bootstrapper-cpp-api-constants.md

@@ -82,7 +82,7 @@ Constant | Value | Description |
 | constexpr uint64_t UInt64 | \[release-dependent\] | The version of the Windows App SDK runtime, as a uint64l for example, 0x03E801BE03240000. |
 
 ## Requirements
-**Minimum supported SDK:** Windows App SDK version 1.1 Stable
+**Minimum supported SDK:** Windows App SDK version 1.1
 
 **Namespace:** Microsoft::WindowsAppSDK
 

hub/apps/api-reference/bootstrapper-cpp-api/microsoft.windows.applicationmodel.dynamicdependency.bootstrap/microsoft.windows.applicationmodel.dynamicdependency.bootstrap.initialize.md

@@ -68,7 +68,7 @@ int main()
 ```
 
 ## Requirements
-**Minimum supported SDK:** Windows App SDK version 1.1 Stable
+**Minimum supported SDK:** Windows App SDK version 1.1
 
 **Namespace:** Microsoft::Windows::ApplicationModel::DynamicDependency::Bootstrap
 

hub/apps/api-reference/bootstrapper-cpp-api/microsoft.windows.applicationmodel.dynamicdependency.bootstrap/microsoft.windows.applicationmodel.dynamicdependency.bootstrap.initializefailfast.md

@@ -57,7 +57,7 @@ int main()
 ```
 
 ## Requirements
-**Minimum supported SDK:** Windows App SDK version 1.1 Stable
+**Minimum supported SDK:** Windows App SDK version 1.1
 
 **Namespace:** Microsoft::Windows::ApplicationModel::DynamicDependency::Bootstrap
 

hub/apps/api-reference/bootstrapper-cpp-api/microsoft.windows.applicationmodel.dynamicdependency.bootstrap/microsoft.windows.applicationmodel.dynamicdependency.bootstrap.initializenothrow.md

@@ -65,7 +65,7 @@ int main()
 ```
 
 ## Requirements
-**Minimum supported SDK:** Windows App SDK version 1.1 Stable
+**Minimum supported SDK:** Windows App SDK version 1.1
 
 **Namespace:** Microsoft::Windows::ApplicationModel::DynamicDependency::Bootstrap
 

hub/apps/api-reference/bootstrapper-cpp-api/microsoft.windows.applicationmodel/microsoft.windows.applicationmodel.packageversion.md

@@ -19,7 +19,7 @@ class PackageVersion : public PACKAGE_VERSION;
 ```
 
 ## Requirements
-**Minimum supported SDK:** Windows App SDK version 1.1 Stable
+**Minimum supported SDK:** Windows App SDK version 1.1
 
 **Namespace:** Microsoft::Windows::ApplicationModel
 

hub/apps/api-reference/cs-bootstrapper-apis/microsoft.windows.applicationmodel.dynamicdependency/microsoft.windows.applicationmodel.dynamicdependency.bootstrap.md

@@ -89,7 +89,7 @@ The minimum version of the Windows App SDK framework package to use. Defaults to
 
 | Product | Introduced in |
 |-|-|
-|**Windows App SDK**|Windows App SDK 1.0 Stable|
+|**Windows App SDK**|Windows App SDK 1.0|
 
 ## See also
 

hub/apps/api-reference/cs-bootstrapper-apis/microsoft.windows.applicationmodel.dynamicdependency/microsoft.windows.applicationmodel.dynamicdependency.packageversion.md

@@ -127,7 +127,7 @@ The `major.minor.build.revision` sequence encoded as a (little-endian) **UInt64*
 
 | Product | Introduced in |
 |-|-|
-|**Windows App SDK**|Windows App SDK 1.0 Stable|
+|**Windows App SDK**|Windows App SDK 1.0|
 
 ## See also
 

hub/apps/desktop/modernize/visual-layer-in-desktop-apps.md

@@ -86,7 +86,7 @@ Learn how to use the Visual layer in your applications by experimenting with our
 
 While many Visual Layer features work the same when hosted in a desktop application as they do in a UWP app, some features do have limitations. Here are some of the limitations to be aware of:
 
-- Effect chains rely on [Win2D](http://microsoft.github.io/Win2D/html/Introduction.htm) for the effect descriptions. The [Win2D NuGet package](https://www.nuget.org/packages/Win2D.uwp) is not supported in desktop applications, so you would need to recompile it from the [source code](https://github.com/Microsoft/Win2D).
+- Effect chains rely on [Win2D](https://microsoft.github.io/Win2D/html/Introduction.htm) for the effect descriptions. The [Win2D NuGet package](https://www.nuget.org/packages/Win2D.uwp) is not supported in desktop applications, so you would need to recompile it from the [source code](https://github.com/Microsoft/Win2D).
 - To do hit testing, you need to do bounds calculations by walking the visual tree yourself. This is the same as the Visual Layer in UWP, except in this case there's no XAML element you can easily bind to for hit testing.
 - The Visual Layer does not have a primitive for rendering text.
 - When two different UI technologies are used together, such as WPF and the Visual Layer, they are each responsible for drawing their own pixels on the screen, and they can't share pixels. As a result, Visual Layer content is always rendered on top of other UI content. (This is known as the _airspace_ issue.) You might need to do extra coding and testing to ensure your Visual layer content resizes with the host UI and doesn't occlude other content.

hub/apps/develop/platform/csharp-winrt/create-winrt-component-winui-cswinrt.md

@@ -20,7 +20,7 @@ This walkthrough requires the following tools and components:
 
 - [Visual Studio 2022](/visualstudio/releases/2022/release-notes)
 - [.NET 6.0 SDK](https://dotnet.microsoft.com/download/dotnet/6.0)
-- [Windows App SDK VSIX](../../../windows-app-sdk/downloads.md) (1.1 Stable)
+- [Windows App SDK VSIX](../../../windows-app-sdk/downloads.md) (1.1 from the stable channel)
 
 ## Author your C#/WinRT component using the Windows App SDK
 

hub/apps/package-and-deploy/self-contained-deploy/deploy-self-contained-apps.md

@@ -65,9 +65,9 @@ Consider these options when you're considering using those APIs in a self-contai
 
 ## Opting out of (or into) automatic UndockedRegFreeWinRT support
 
-The project property **WindowsAppSdkUndockedRegFreeWinRTInitialize** was introduced in version 1.2 Stable of the Windows App SDK. If that property is set to *true* then it ensures that the Windows App SDK's implementation of undocked registration-free Windows Runtime (*UndockedRegFreeWinRT*) is enabled automatically at app startup. That support is needed by unpackaged self-contained apps.
+The project property **WindowsAppSdkUndockedRegFreeWinRTInitialize** was introduced in version 1.2 of the Windows App SDK (from the stable channel). If that property is set to *true* then it ensures that the Windows App SDK's implementation of undocked registration-free Windows Runtime (*UndockedRegFreeWinRT*) is enabled automatically at app startup. That support is needed by unpackaged self-contained apps.
 
-**WindowsAppSdkUndockedRegFreeWinRTInitialize** defaults to *true* if **WindowsAppSDKSelfContained** is *true* and **WindowsPackageType** is *None* and (as of version 1.2 Stable of the Windows App SDK) **OutputType** project property is set to *Exe* or *WinExe* (that is, the project produces an executable). That last condition is to prevent adding automatic UndockedRegFreeWinRT support into class library DLLs and other non-executables by default. If you *do* need automatic UndockedRegFreeWinRT support in a non-executable (for example, a test DLL loaded by a host process executable that doesn't initialize UndockedRegFreeWinRT), then you can explicitly enable it in your project with `<WindowsAppSdkUndockedRegFreeWinRTInitialize>true</WindowsAppSdkUndockedRegFreeWinRTInitialize>`.
+**WindowsAppSdkUndockedRegFreeWinRTInitialize** defaults to *true* if **WindowsAppSDKSelfContained** is *true* and **WindowsPackageType** is *None* and (as of version 1.2 of the Windows App SDK) **OutputType** project property is set to *Exe* or *WinExe* (that is, the project produces an executable). That last condition is to prevent adding automatic UndockedRegFreeWinRT support into class library DLLs and other non-executables by default. If you *do* need automatic UndockedRegFreeWinRT support in a non-executable (for example, a test DLL loaded by a host process executable that doesn't initialize UndockedRegFreeWinRT), then you can explicitly enable it in your project with `<WindowsAppSdkUndockedRegFreeWinRTInitialize>true</WindowsAppSdkUndockedRegFreeWinRTInitialize>`.
 
 ## Related topics