Merge pull request #5450 from MicrosoftDocs/main638840596934980109sync_temp

For protected branch, push strategy should use PR and merge to target branch method to work around git push error

Author: learn-build-service-prod[bot]

hub/apps/design/devices/designing-for-MR.md

@@ -116,7 +116,7 @@ When creating a UWP app that will potentially be used on a Mixed Reality platfor
 
 * Remember, gaze is not as accurate as mouse pointing. Smaller mouse targets or buttons may cause frustration for your users, so resize controls accordingly. If they are designed for touch, they will work in Mixed Reality, but you may decide to enlarge some buttons at runtime. See [Updating 2D UWP apps for Windows Mixed Reality](/windows/mixed-reality/develop/porting-apps/building-2d-apps).
 
-* The HoloLens defines the color black as the absence of light. It's simply not rendered, allowing the "real world" so show through. Your application should not use black if this is would cause confusion. In a Mixed Reality headset, black is black.
+* Your application should not use black as this could cause confusion. The HoloLens defines the color black as the absence of light and is simply not rendered, allowing the "real world" to show through. In a Mixed Reality headset, black is rendered as black.
 
 * The HoloLens does not support color themes in apps, and defaults to blue to ensure the best experience for users. For more advice about selecting colors, you should consult [this topic](https://developer.microsoft.com/windows/mixed-reality/color_light_and_materials) which discusses the use of color and material in Mixed Reality designs.
 

hub/apps/desktop/modernize/xaml-islands/host-custom-control-with-xaml-islands-cpp.md

@@ -47,7 +47,7 @@ To host a custom WinRT XAML control, you'll create the following projects and co
 5. Add a reference to the Windows Runtime metadata:
    1. In **Solution Explorer**, right-click on your project **References** node and select **Add Reference**.
    2. Click the **Browse** button at the bottom of the page and navigate to the UnionMetadata folder in your SDK install path. By default the SDK will be installed to `C:\Program Files (x86)\Windows Kits\10\UnionMetadata`. 
-   3. Then, select the folder named after the Windows version you are targetting (e.g. 10.0.18362.0) and inside of that folder pick the `Windows.winmd` file.
+   3. Then, select the folder named after the Windows version you are targeting (e.g. 10.0.18362.0) and inside of that folder pick the `Windows.winmd` file.
    4. Click **OK** to close the **Add Reference** dialog.
 
 6. Build the solution and confirm that it builds successfully.
@@ -169,7 +169,7 @@ You're now ready to add code to the **MyUWPApp** project to perform these tasks:
             <TextBlock HorizontalAlignment="Center" TextWrapping="Wrap" 
                            Text="Hello from XAML Islands" FontSize="30" />
             <TextBlock HorizontalAlignment="Center" Margin="15" TextWrapping="Wrap"
-                           Text="😍❤💋🌹🎉😎�🐱‍👤" FontSize="16" />
+                           Text="😍❤💋🌹🎉😎 🐱‍👤" FontSize="16" />
             <Button HorizontalAlignment="Center" 
                     x:Name="Button" Click="ClickHandler">Click Me</Button>
         </StackPanel>
@@ -566,7 +566,7 @@ This section demonstrates how to add a WinRT XAML control from the WinUI 2 libra
         <TextBlock HorizontalAlignment="Center" TextWrapping="Wrap" 
                        Text="Hello from XAML Islands" FontSize="30" />
         <TextBlock HorizontalAlignment="Center" Margin="15" TextWrapping="Wrap"
-                       Text="😍❤💋🌹🎉😎�🐱‍👤" FontSize="16" />
+                       Text="😍❤💋🌹🎉😎 🐱‍👤" FontSize="16" />
         <Button HorizontalAlignment="Center" 
                 x:Name="Button" Click="ClickHandler">Click Me</Button>
         <winui:RatingControl />

hub/apps/develop/camera/process-media-frames-with-mediaframereader.md

@@ -149,7 +149,7 @@ The **FrameRenderer** helper class implements the following methods.
 
 ## Use MultiSourceMediaFrameReader to get time-correlated frames from multiple sources
 
-Starting with Windows 10, version 1607, you can use [**MultiSourceMediaFrameReader**](/uwp/api/windows.media.capture.frames.multisourcemediaframereader) to receive time-corellated frames from multiple sources. This API makes it easier to do processing that requires frames from multiple sources that were taken in close temporal proximity, such as using the [**DepthCorrelatedCoordinateMapper**](/uwp/api/windows.media.devices.core.depthcorrelatedcoordinatemapper) class. One limitation of using this new method is that frame-arrived events are only raised at the rate of the slowest capture source. Extra frames from faster sources will be dropped. Also, because the system expects frames to arrive from different sources at different rates, it does not automatically recognize if a source has stopped generating frames altogether. The example code in this section shows how to use an event to create your own timeout logic that gets invoked if correlated frames don't arrive within an app-defined time limit.
+Starting with Windows 10, version 1607, you can use [**MultiSourceMediaFrameReader**](/uwp/api/windows.media.capture.frames.multisourcemediaframereader) to receive time-correlated frames from multiple sources. This API makes it easier to do processing that requires frames from multiple sources that were taken in close temporal proximity, such as using the [**DepthCorrelatedCoordinateMapper**](/uwp/api/windows.media.devices.core.depthcorrelatedcoordinatemapper) class. One limitation of using this new method is that frame-arrived events are only raised at the rate of the slowest capture source. Extra frames from faster sources will be dropped. Also, because the system expects frames to arrive from different sources at different rates, it does not automatically recognize if a source has stopped generating frames altogether. The example code in this section shows how to use an event to create your own timeout logic that gets invoked if correlated frames don't arrive within an app-defined time limit.
 
 The steps for using [**MultiSourceMediaFrameReader**](/uwp/api/windows.media.capture.frames.multisourcemediaframereader) are similar to the steps for using [**MediaFrameReader**](/uwp/api/Windows.Media.Capture.Frames.MediaFrameReader) described previously in this article. This example will use a color source and a depth source. Declare some string variables to store the media frame source IDs that will be used to select frames from each source. Next, declare a [**ManualResetEventSlim**](/dotnet/api/system.threading.manualreseteventslim), a [**CancellationTokenSource**](/dotnet/api/system.threading.cancellationtokensource), and an [**EventHandler**](/dotnet/api/system.eventhandler) that will be used to implement timeout logic for the example. 
 

hub/apps/develop/dispatcherqueue.md

@@ -168,7 +168,7 @@ void Main()
 
     var appWindow = AppWindow.Create(nullptr, 0, dispatcherQueueController.DispatcherQueue());
 
-    // Since we associated the DispatcherQueue above with the AppWindow, we're able to retreive it 
+    // Since we associated the DispatcherQueue above with the AppWindow, we're able to retrieve it 
     // as a property. If we were to not associate a dispatcher, this property would be null.
     ASSERT(appWindow.DispatcherQueue() == dispatcherQueueController.DispatcherQueue());
 

hub/apps/develop/ui-input/display-ui-objects.md

@@ -18,7 +18,7 @@ Your desktop app can be [WinUI 3](../../winui/winui3/index.md), [Windows Present
 For classes that implement the [**IInitializeWithWindow**](/windows/win32/api/shobjidl_core/nn-shobjidl_core-iinitializewithwindow) interface (or the equivalent [**IDataTransferManagerInterop**](/windows/win32/api/shobjidl_core/nn-shobjidl_core-idatatransfermanagerinterop) interface), you can use that interface to set an owner window on the object before you display it. It's a two-step process.
 
 1. Decide which window will be the owner of the UI object that you want to display, and retrieve that window's HWND. For more details and code examples for this step, see [Retrieve a window handle (HWND)](./retrieve-hwnd.md).
-2. Then call the appropriate interoperatability API (for C# or C++/WinRT) to set an owner window handle (HWND) for the WinRT UI object.
+2. Then call the appropriate interoperability API (for C# or C++/WinRT) to set an owner window handle (HWND) for the WinRT UI object.
 
 ## For classes that implement IInitializeWithWindow
 
@@ -75,7 +75,7 @@ private async void ShowFolderPickerAsync(IntPtr hWnd)
 
 ### WinUI 3 with C++
 
-The C++/WinRT code below expects that you've already used the pattern documented in [Retrieve a window handle (HWND)](./retrieve-hwnd.md). Then, to set the owner window for the UI object that you want to display, the code calls the interoperatability method [**IInitializeWithWindow::Initialize**](/windows/win32/api/shobjidl_core/nf-shobjidl_core-iinitializewithwindow-initialize).
+The C++/WinRT code below expects that you've already used the pattern documented in [Retrieve a window handle (HWND)](./retrieve-hwnd.md). Then, to set the owner window for the UI object that you want to display, the code calls the interoperability method [**IInitializeWithWindow::Initialize**](/windows/win32/api/shobjidl_core/nf-shobjidl_core-iinitializewithwindow-initialize).
 
 ```cppwinrt
 // pch.h

hub/apps/distribute-through-store/how-to-distribute-your-win32-app-through-microsoft-store.md

@@ -35,7 +35,7 @@ Let's explore each of these options in more detail in the following sections.
 
 ### Option 1 - Package your Win32 app as MSIX
 
-Package your application into a MSIX is very simple, you can either use:
+Package your application into an MSIX is very simple, you can either use:
 - Visual Studio by adding the project Windows Application Packaging to your solution. See [Set up your desktop application for MSIX packaging in Visual Studio](/windows/msix/desktop/desktop-to-uwp-packaging-dot-net).
 - Use installer solutions from one of our partners. See [Package a desktop app using third-party installers](/windows/msix/desktop/desktop-to-uwp-third-party-installer).
 - Microsoft MSIX Packaging Tool to create the MSIX from an existing installer. See [Create an MSIX package from any desktop installer (MSI, EXE, ClickOnce, or App-V)](/windows/msix/packaging-tool/create-app-package).

hub/apps/get-started/start-here.md

@@ -105,7 +105,7 @@ To create a new project using the WinUI C# Blank App project template:
 The `MainWindow` class included with the project template includes some sample code that needs to be removed to make room for your content.
 
 1. Double-click `MainWindow.xaml` in **Solution Explorer** to open it. You should see XAML markup for a `StackPanel` control.
-1. Delete the XAML for the `StackPanel`. (You'll add your own content in it's place as you create your app.)
+1. Delete the XAML for the `StackPanel`. (You'll add your own content in its place as you create your app.)
 
     ```xaml
     <!-- ↓ Delete this. ↓ -->

hub/apps/publish/partner-center/remove-azure-ad-tenant-associations.md

@@ -20,4 +20,4 @@ To remove a tenant, find its name on the **Tenants** page (in **Account settings
 :::image type="content" source="../images/partner-center-account-settings-tenants-remove-azure-ad.png" alt-text="Screenshot showing Remove option in Partner Center tenant settings.":::
 
 > [!TIP]
-> You can’t remove a tenant if you are currently signed into Partner Center using an account in the same tenant. To remove a tenant, you must sign in to Partner Center as an **Manager** for another tenant that is associated with the account. If there is only one tenant associated with the account, that tenant can only be removed after signing in with the Microsoft account that opened the account.
+> You can’t remove a tenant if you are currently signed into Partner Center using an account in the same tenant. To remove a tenant, you must sign in to Partner Center as a **Manager** for another tenant that is associated with the account. If there is only one tenant associated with the account, that tenant can only be removed after signing in with the Microsoft account that opened the account.

hub/apps/publish/store-business-verification-reqs.md

@@ -80,7 +80,7 @@ Then, expand and edit the **Contact Info** section. Select **Update**.
 
 ![Additional Information for Verification location in Partner Center](images\account-verify-additional-info.png)
 
-5. Within this tab, you can chose between the two availabe identification options.
+5. Within this tab, you can chose between the two available identification options.
 
 * **DUNS ID**: This is the recommended and faster verification method. Simply enter your DUNS ID.
 

hub/apps/windows-app-sdk/migrate-to-windows-app-sdk/guides/background-task-migration-strategy.md

@@ -18,7 +18,7 @@ Background tasks offered in the UWP app model can either be out-of-proc or in-pr
 
 In the case of out-of-proc background tasks in UWP, background tasks will be written as a Windows Runtime (WinRT) component, and the component is set as the [TaskEntryPoint](/uwp/api/windows.applicationmodel.background.backgroundtaskbuilder.taskentrypoint) on [BackgroundTaskBuilder](/uwp/api/windows.applicationmodel.background.backgroundtaskbuilder) during registration. While migrating to Windows App SDK, developers can keep this as-is and package the WinRT component together with the desktop project. In this case, the broker infrastructure will be launching `backgroundtaskhost` process when the trigger is invoked, and the WinRT component background task would be executed in the process. In this approach, the background task would be running in a Low Integrity Level (IL) process (`backgroundtaskhost.exe`) while the main desktop project would be running in a Medium IL process.
 
-If the application needs to to run a background task in a medium IL process itself, the full trust COM component needs to be used for background tasks. In that scenario, developers must use the Windows App SDK [BackgroundTaskBuilder](/windows/windows-app-sdk/api/winrt/microsoft.windows.applicationmodel.background.backgroundtaskbuilder) to register the full trust COM component. Note that the [BackgroundTaskBuilder](/uwp/api/windows.applicationmodel.background.backgroundtaskbuilder) API from the **Windows.ApplicationModel.Background** namespace will throw exceptions while registering of some of the triggers.
+If the application needs to run a background task in a medium IL process itself, the full trust COM component needs to be used for background tasks. In that scenario, developers must use the Windows App SDK [BackgroundTaskBuilder](/windows/windows-app-sdk/api/winrt/microsoft.windows.applicationmodel.background.backgroundtaskbuilder) to register the full trust COM component. Note that the [BackgroundTaskBuilder](/uwp/api/windows.applicationmodel.background.backgroundtaskbuilder) API from the **Windows.ApplicationModel.Background** namespace will throw exceptions while registering of some of the triggers.
 
 A full WinUI 3 background task registration sample can be found on [GitHub](https://github.com/microsoft/WindowsAppSDK-Samples/tree/release/experimental/Samples/BackgroundTask).