Merge branch 'docs' into patch-1

Author: eFail

.openpublishing.publish.config.json

@@ -65,12 +65,11 @@
   ],
   "notification_subscribers": [],
   "sync_notification_subscribers": [
-    "quradic@microsoft.com"
+    "jkendir@microsoft.com"
   ],
   "branches_to_filter": [],
   "git_repository_url_open_to_public_contributors": "https://github.com/MicrosoftDocs/windows-dev-docs",
   "git_repository_branch_open_to_public_contributors": "docs",
-  "skip_source_output_uploading": false,
   "need_preview_pull_request": true,
   "resolve_user_profile_using_github": true,
   "dependent_repositories": [
@@ -111,6 +110,7 @@
     }
   },
   "docs_build_engine": {},
+  "skip_source_output_uploading": false,
   "contribution_branch_mappings": {},
   "need_generate_pdf_url_template": true,
   "need_generate_pdf": false

.openpublishing.redirection.json

@@ -8869,6 +8869,26 @@
       "source_path": "hub/apps/winui/winui2/release-notes/winui-2.8.md",
       "redirect_url": "/windows/uwp/get-started/winui2/release-notes/winui-2.8",
       "redirect_document_id": false
+    },
+    {
+      "source_path": "hub/sudo/index.md",
+      "redirect_url": "/windows/advanced-settings/sudo/",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "hub/apps/develop/actions/action-json.md",
+      "redirect_url": "/windows/ai/app-actions/actions-json",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "hub/apps/develop/actions/action-provider-manifest.md",
+      "redirect_url": "/windows/ai/app-actions/actions-provider-manifest",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "hub/apps/develop/actions/index.md",
+      "redirect_url": "/windows/ai/app-actions/",
+      "redirect_document_id": false
     }
   ]
 }

SECURITY.md

@@ -0,0 +1,41 @@
+<!-- BEGIN MICROSOFT SECURITY.MD V0.0.8 BLOCK -->
+
+## Security
+
+Microsoft takes the security of our software products and services seriously, which includes all source code repositories managed through our GitHub organizations, which include [Microsoft](https://github.com/microsoft), [Azure](https://github.com/Azure), [DotNet](https://github.com/dotnet), [AspNet](https://github.com/aspnet), [Xamarin](https://github.com/xamarin), and [our GitHub organizations](https://opensource.microsoft.com/).
+
+If you believe you have found a security vulnerability in any Microsoft-owned repository that meets [Microsoft's definition of a security vulnerability](https://aka.ms/opensource/security/definition), please report it to us as described below.
+
+## Reporting Security Issues
+
+**Please do not report security vulnerabilities through public GitHub issues.**
+
+Instead, please report them to the Microsoft Security Response Center (MSRC) at [https://msrc.microsoft.com/create-report](https://aka.ms/opensource/security/create-report).
+
+If you prefer to submit without logging in, send email to [[email protected]](mailto:[email protected]).  If possible, encrypt your message with our PGP key; please download it from the [Microsoft Security Response Center PGP Key page](https://aka.ms/opensource/security/pgpkey).
+
+You should receive a response within 24 hours. If for some reason you do not, please follow up via email to ensure we received your original message. Additional information can be found at [microsoft.com/msrc](https://aka.ms/opensource/security/msrc). 
+
+Please include the requested information listed below (as much as you can provide) to help us better understand the nature and scope of the possible issue:
+
+  * Type of issue (e.g. buffer overflow, SQL injection, cross-site scripting, etc.)
+  * Full paths of source file(s) related to the manifestation of the issue
+  * The location of the affected source code (tag/branch/commit or direct URL)
+  * Any special configuration required to reproduce the issue
+  * Step-by-step instructions to reproduce the issue
+  * Proof-of-concept or exploit code (if possible)
+  * Impact of the issue, including how an attacker might exploit the issue
+
+This information will help us triage your report more quickly.
+
+If you are reporting for a bug bounty, more complete reports can contribute to a higher bounty award. Please visit our [Microsoft Bug Bounty Program](https://aka.ms/opensource/security/bounty) page for more details about our active programs.
+
+## Preferred Languages
+
+We prefer all communications to be in English.
+
+## Policy
+
+Microsoft follows the principle of [Coordinated Vulnerability Disclosure](https://aka.ms/opensource/security/cvd).
+
+<!-- END MICROSOFT SECURITY.MD BLOCK -->

hub/advanced-settings/fe-version-control.md

@@ -0,0 +1,26 @@
+---
+title: File Explorer Version Control Integration (PREVIEW)
+description: Learn how to use File Explorer + version control integration inside Windows Advanced settings.
+ms.reviewer: cinnamon
+ms.topic: article
+ms.date: 04/11/2025
+---
+
+# File Explorer version control integration (PREVIEW)
+
+**File Explorer version control integration** provides version control information directly in File Explorer. This includes information such as the branch name, last commit author, last commit message, and more.
+
+> [!NOTE]
+> As of right now, File Explorer version control integration only supports Git. The Advanced Settings system component is extensible to allow for additional version control types.
+
+![File Explorer version control integration](../images/fe-source.png)
+
+## Prerequisites
+
+File Explorer version control integration is available in the [Windows Beta channel](https://aka.ms/BetaLatest). See [Get started with the Windows Insider Program](/windows-insider/get-started) for more information about joining the program and selecting a channel. After you've joined the Beta channel, you can ([check for Windows updates](ms-settings:windowsupdate)).
+
+## How to identify repositories
+
+Windows has to know which folders are source code repositories so File Explorer can display the version control information. You can select your repository folders in Windows Advanced Settings > File Explorer settings under the File Explorer + version control header.
+
+![File Explorer version control Settings](../images/fe-source-settings.png)

hub/advanced-settings/index.md

@@ -0,0 +1,25 @@
+---
+title: Advanced Windows Settings (PREVIEW)
+description: Learn about the settings provided in the Advanced page of Windows settings.
+ms.reviewer: cinnamon
+ms.topic: article
+ms.date: 04/10/2025
+---
+
+# Advanced Windows Settings (PREVIEW)
+
+**Advanced Windows settings** is a redesign of the original **For Developers** page in Windows settings with additional settings to help you be more productive.
+
+## Prerequisites
+
+Advanced settings is available in the [Windows Beta channel](https://aka.ms/BetaLatest). See [Get started with the Windows Insider Program](/windows-insider/get-started) for more information about joining the program and selecting a channel. After you've joined the Beta channel, you can ([check for Windows updates](ms-settings:windowsupdate)).
+
+## FAQ
+
+### Why was For Developers renamed to Advanced?
+
+Most of the settings available within the For Developers page are useful for other advanced Windows users as well. In order to help all users discover these settings, the page was redesigned and renamed to Advanced.
+
+## Windows Advanced Settings system component open source repository
+
+To provide enhanced functionality to the Advanced settings page, there is an open-source system component that enables features like [File Explorer version control integration](fe-version-control.md). We welcome your contributions and feedback, and the source code for the Windows Advanced Settings system component is available on [GitHub](https://github.com/microsoft/windowsAdvancedSettings).

hub/sudo/index.md hub/advanced-settings/sudo/index.mdhub/sudo/index.md renamed to hub/advanced-settings/sudo/index.md

@@ -24,7 +24,7 @@ The Sudo for Windows command is available in [Windows 11, version 24H2](https://
 
 To enable Sudo for Windows, open `Settings > System > For Developers` and set **Enable sudo** to **On**.
 
-![Enable Sudo](../images/sudo-enable.png)
+![Enable Sudo](../../images/sudo-enable.png)
 
 >[!WARNING]
 > Sudo for Windows can be used as a potential escalation of privilege vector when enabled in certain configurations. You should make sure to be aware of the [security considerations](#security-considerations) when enabling the sudo command on your machine.

hub/apps/design/controls/commanding.md

@@ -1,9 +1,9 @@
 ---
 title: Commanding in Windows apps
 description: How to use the XamlUICommand and StandardUICommand classes (along with the ICommand interface) to share and manage commands across various control types, regardless of the device and input type being used.
-ms.service: #Required; service per approved list.
 ms.topic: overview
-ms.date: 06/24/2021
+ms.date: 05/30/2025
+ms.localizationpriority: medium
 ---
 
 # Commanding in Windows apps using StandardUICommand, XamlUICommand, and ICommand

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/design/input/custom-text-input.md

@@ -5,23 +5,19 @@ ms.assetid: 58F5F7AC-6A4B-45FC-8C2A-942730FD7B74
 label: Custom text input
 template: detail.hbs
 keywords: keyboard, text, core text, custom text, Text Services Framework, input, user interactions
-ms.date: 09/24/2020
+ms.date: 05/30/2025
 ms.topic: article
-
-
 ms.localizationpriority: medium
 ---
-# Custom text input
-
 
+# Custom text input
 
-The core text APIs in the [**Windows.UI.Text.Core**](/uwp/api/Windows.UI.Text.Core) namespace enable a Windows app to receive text input from any text service supported on Windows devices. The APIs are similar to the [Text Services Framework](/windows/desktop/TSF/text-services-framework) APIs in that the app is not required to have detailed knowledge of the text services. This enables the app to receive text in any language and from any input type, like keyboard, speech, or pen.
+The core text APIs in the [**Windows.UI.Text.Core**](/uwp/api/Windows.UI.Text.Core) namespace enable a Windows app to receive text input from any text service supported on Windows devices. The APIs are similar to the [Text Services Framework](/windows/desktop/TSF/text-services-framework) APIs in that the app is not required to have detailed knowledge of the text services. This enables the app to receive text in any language and from any input type (such as keyboard, speech, or pen).
 
 > **Important APIs**: [**Windows.UI.Text.Core**](/uwp/api/Windows.UI.Text.Core), [**CoreTextEditContext**](/uwp/api/Windows.UI.Text.Core.CoreTextEditContext)
 
 ## Why use core text APIs?
 
-
 For many apps, the XAML or HTML text box controls are sufficient for text input and editing. However, if your app handles complex text scenarios, like a word processing app, you might need the flexibility of a custom text edit control. You could use the [**CoreWindow**](/uwp/api/Windows.UI.Core.CoreWindow) keyboard APIs to create your text edit control, but these don't provide a way to receive composition-based text input, which is required to support East Asian languages.
 
 Instead, use the [**Windows.UI.Text.Core**](/uwp/api/Windows.UI.Text.Core) APIs when you need to create a custom text edit control. These APIs are designed to give you a lot of flexibility in processing text input, in any language, and let you provide the text experience best suited to your app. Text input and edit controls built with the core text APIs can receive text input from all existing text input methods on Windows devices, from [Text Services Framework](/windows/desktop/TSF/text-services-framework) based Input Method Editors (IMEs) and handwriting on PCs to the WordFlow keyboard (which provides auto-correction, prediction, and dictation) on mobile devices.

hub/apps/design/shell/tiles-and-notifications/firewall-allowlist-config.md

@@ -43,7 +43,6 @@ Regardless of the method you choose from below, you'll need to allow network tra
     </CloudServiceDNS>
     <ClientDNS>
         <DNS FQDN="*.wns.windows.com"/>
-        <DNS FQDN="*.notify.live.net"/>
     </ClientDNS>
     <CloudServiceIPs>
         <IpRange Subnet=""/>