Merged PR 21277: public/private sync

Author: QuinnRadich

windows.security.authorization.appcapabilityaccess/appcapability_displaymessage.md

@@ -17,7 +17,8 @@ The purpose of why the capability is being accessed.
 The stored display message as a string property.
 
 ## -remarks
-The display message, if specified, appears in the system tray and settings app under **Privacy & security > App permissions** pages while the capability is in use. Display messages should be provided before the capability is accessed and should continue to be provided until after the apps terminate access to the capability.
+
+The display message, if specified, appears in the system tray and settings app under **Privacy & security > App permissions** pages while the capability is in use. Display messages should be provided before the capability is accessed and should continue to be provided until the app terminates access to the capability.
 
 ## -see-also
 

windows.ui.core/corewindow_getkeystate_1676715341.md

@@ -20,11 +20,18 @@ The virtual key for which state is returned.
 The flags indicating the current state of the supplied virtual key when the input event fired.
 
 > [!NOTE]
-> All keys support the **Locked** state (not just the standard Caps Lock and Num Lock keys).
+> For WinUI 3 apps, this method returns null. Use [**Microsoft.UI.Input.InputKeyboardSource.GetKeyStateForCurrentThread**](/windows/windows-app-sdk/api/winrt/microsoft.ui.input.inputkeyboardsource.getkeystateforcurrentthread) instead.
+>
+> See [Windows Runtime APIs not supported in desktop apps](/windows/apps/desktop/modernize/desktop-to-uwp-supported-api).
 
 ## -remarks
 
+All keys support the **Locked** state (not just the standard Caps Lock and Num Lock keys).
+
 ## -examples
 
 ## -see-also
-[CoreVirtualKeyStates](corevirtualkeystates.md), [GetAsyncKeyState](corewindow_getasynckeystate_1621551046.md)
+
+* [CoreVirtualKeyStates](corevirtualkeystates.md)
+* [GetAsyncKeyState](corewindow_getasynckeystate_1621551046.md)
+* [InputKeyboardSource.GetKeyStateForCurrentThread](/windows/windows-app-sdk/api/winrt/microsoft.ui.input.inputkeyboardsource.getkeystateforcurrentthread)

windows.ui.xaml.input/focusmanager_getfocusedelement_1183614552.md

@@ -22,6 +22,12 @@ The object that has focus. Typically, this is a [Control](../windows.ui.xaml.con
 
 ## -remarks
 
+> [!WARNING]
+> For WinUI 3 apps, this method always returns `null` as it relies on CoreWindow APIs not supported by WinUI 3.
+>
+> Instead, use the [FocusManager.GetFocusedElement(XamlRoot)](./windows.ui.xaml.input.focusmanager.getfocusedelement#windows-ui-xaml-input-focusmanager-getfocusedelement(windows-ui-xaml-xamlroot))
+> overload, where `XamlRoot` can be retrieved any loaded UIElement through the [XamlRoot](/uwp/api/windows.ui.xaml.uielement.xamlroot) property.
+
 ## -examples
 
 ## -see-also

windows.ui.xaml/images/HighContrastAdjustment_auto.png

@@ -22,7 +22,12 @@ The value of the property is inherited.  When set to **Application** the adjustm
 When set to **Auto**, the framework automatically applies the following adjustments to XAML's text elements while a high contrast theme is enabled:
 * The foreground color on text is ignored.  The text is colored using either the system’s high contrast text color or the disabled color when in a parent [Control](../windows.ui.xaml.controls/control.md) where [IsEnabled](../windows.ui.xaml.controls/control_isenabled.md) = "False".
 * An opaque rectangle is rendered immediately behind the text to enforce a high contrast ratio.
-* Non-zero values for [Opacity](uielement_opacity.md) are ignored.  The element and its children will appear as if they had an opacity of 1.0.   
+* Non-zero values for [Opacity](uielement_opacity.md) are ignored.  The element and its children will appear as if they had an opacity of 1.0.
+
+The following images show the difference between **Auto** (the default **Application** value) and **None**:
+
+:::image type="content" source="images/HighContrastAdjustment_auto.png" alt-text="Example of buttons with HighContrastAdjustment set to auto.":::
+:::image type="content" source="images/HighContrastAdjustment_none.png" alt-text="Example of buttons with HighContrastAdjustment set to none.":::
 
 It is possible to set HighContrastAdjustment = None on a UIElement and then have HighContrastAdjustment = Auto on one of its descendants.  However, the framework does not guarantee that the descendent will be fully opaque if an opacity is applied on any of its ancestors.