Merge pull request #6391 from MicrosoftDocs/fix/build-suggestions-group-c

Fix build suggestions: broken links in widgets, click-to-do, winui-perf, and other docs (Group C)

Author: GrantMeStrength

hub/apps/develop/widgets/web-widget-providers.md

@@ -62,7 +62,7 @@ async void IWidgetResourceProvider.OnResourceRequested(WidgetResourceRequestedAr
 }
 ```
 
-If the provider does not set a response on the **WidgetResourceRequestedArgs** object passed into the method, the system will retrieve the resource from the web. In this case, the provider can choose to modify the [Headers](/windows/windows-app-sdk/api/winrt/microsoft.windows.widgets.providers.widgetresourcerequestedargs.headers) property of the [WidgetResourceRequestedArgs.Request](/windows/windows-app-sdk/api/winrt/microsoft.windows.widgets.providers.widgetresourcerequestedargs.request) object, such as to provide user context or tokens, and the system will use the updated headers when retrieving the resource from the web.
+If the provider does not set a response on the **WidgetResourceRequestedArgs** object passed into the method, the system will retrieve the resource from the web. In this case, the provider can choose to modify the [Headers](/windows/windows-app-sdk/api/winrt/microsoft.windows.widgets.providers.widgetresourcerequestedargs) property of the [WidgetResourceRequestedArgs.Request](/windows/windows-app-sdk/api/winrt/microsoft.windows.widgets.providers.widgetresourcerequestedargs.request) object, such as to provide user context or tokens, and the system will use the updated headers when retrieving the resource from the web.
 
 ## Handle messages to and from web content
 
@@ -77,7 +77,7 @@ public void OnMessageReceived(WidgetMessageReceivedArgs args)
 }
 ```
 
-Widget providers can send a message to the web content of the widget by calling [WidgetManager.SendMessage](/windows/windows-app-sdk/api/winrt/microsoft.windows.widgets.providers.widgetmanager.sendmessage). You must provide the ID of the widget to which the message is sent, which is the value specified in the *Id* attribute of the **Definition** element in the provider's package manifest file. For more information see [Widget provider package manifest XML format](/windows/apps/develop/widgets/widget-provider-manifest). The message string can be simple text or the serialized form of an object interpreted by the web content. For more information, see [PostWebMessageAsString](/dotnet/api/microsoft.web.webview2.core.corewebview2.postwebmessageasstring).
+Widget providers can send a message to the web content of the widget by calling [WidgetManager.SendMessage](/windows/windows-app-sdk/api/winrt/microsoft.windows.widgets.providers.widgetmanager). You must provide the ID of the widget to which the message is sent, which is the value specified in the *Id* attribute of the **Definition** element in the provider's package manifest file. For more information see [Widget provider package manifest XML format](/windows/apps/develop/widgets/widget-provider-manifest). The message string can be simple text or the serialized form of an object interpreted by the web content. For more information, see [PostWebMessageAsString](/dotnet/api/microsoft.web.webview2.core.corewebview2.postwebmessageasstring).
 
 ```csharp
 var message = $"{{ \"current_location\": \"{ location }\" }}";

hub/apps/develop/windows-integration/click-to-do.md

@@ -8,7 +8,7 @@ no-loc: [Click to Do, Windows Copilot Runtime, Phi Silica]
 
 # Click to Do overview
 
-**Click to Do** is an AI-supported feature that utilizes the local Phi Silica model in Copilot+ PCs or [eligible Cloud PCs](https://learn.microsoft.com/windows-365/enterprise/ai-enabled-cloud-pcs) to connect actions to the content (text or images) on the screen.
+**Click to Do** is an AI-supported feature that utilizes the local Phi Silica model in Copilot+ PCs or [eligible Cloud PCs](/windows-365/enterprise/ai-enabled-cloud-pcs) to connect actions to the content (text or images) on the screen.
 
 Click to Do analyzes what's on screen and then you can choose the text or image you want to take action on. Once selected, Click to Do will suggest actions that you can take based on the content. For example, if you select a piece of text, it might suggest summarizing or rewriting it. If you select an image, it might suggest blurring the background, erasing objects in the image, or searching the web for related information.
 

hub/apps/performance/winui-perf.md

@@ -35,7 +35,7 @@ WinUI logs ETW events that track the start and stop of each frame (shown in the
 
 :::image type="content" source="images/wpa-generic-events.png" alt-text="Screenshot of the Windows Performance Analyzer showing the Generic Events table with a series of frame starts and stops.":::
 
-To address this issue, a new "XAML Frame Analysis" table plugin is included with the [Windows Assessment Toolkit (ADK)](https://learn.microsoft.com/windows-hardware/get-started/adk-install) 10.1.26100.1 and later. This table calculates and shows the duration of each frame (along with other time-consuming operations).
+To address this issue, a new "XAML Frame Analysis" table plugin is included with the [Windows Assessment Toolkit (ADK)](/windows-hardware/get-started/adk-install) 10.1.26100.1 and later. This table calculates and shows the duration of each frame (along with other time-consuming operations).
 
 > [!NOTE]
 > The "XAML Frame Analysis" table requires Windows Performance Analyzer (WPA) from Windows ADK 10.1.26100.1 or later. The version of WPR used to take the trace does not matter.

hub/apps/publish/distribute-lob-apps-to-enterprises.md

@@ -17,13 +17,13 @@ You have several options for distributing line of business (LOB) apps to your or
 If your organization uses Microsoft Endpoint Configuration Manager or Microsoft Intune to manage devices, you can deploy LOB apps using these tools. For more information, see these articles:
 
 * [Introduction to application management in Configuration Manager](/configmgr/apps/understand/introduction-to-application-management)
-* [Overview of the app lifecycle in Microsoft Intune](/intune/apps/app-lifecycle)
+* [Overview of the app lifecycle in Microsoft Intune](/mem/intune/apps/app-lifecycle)
 
 ## App Installer
 
 App Installer enables Windows 10 or Windows 11 apps to be installed by double-clicking an MSIX app package directly, or by double-clicking an .appinstaller file that installs the app package from a web server. This means that users don't need to use PowerShell or other developer tools to install LOB apps. App Installer can also install app packages that include optional packages and related sets.
 
-App Installer can be downloaded for offline use in the enterprise from Microsoft Store for Business [web portal](https://businessstore.microsoft.com/store/details/app-installer/9NBLGGH4NNS1). For more information about App Installer, see [Install Windows 10 or Windows 11 apps with App Installer](/windows/msix/app-installer/app-installer-root).
+App Installer can be downloaded for offline use in the enterprise from the [Microsoft Store](https://apps.microsoft.com/detail/9NBLGGH4NNS1). For more information about App Installer, see [Install Windows 10 or Windows 11 apps with App Installer](/windows/msix/app-installer/app-installer-root).
 
 ## Sideloading
 

hub/dev-environment/javascript/react-overview.md

@@ -33,7 +33,7 @@ Windows supports a wide range of scenarios for React developers, including:
 
 - **Single-Page Apps (SPAs)**: These are websites that interact with the user by dynamically rewriting the current web page with new data from a server, rather than the browser default of loading entire new pages. If you want to build a static content-oriented SPA website, we recommend installing [Gatsby on WSL](./gatsby-on-wsl.md). If you want to build a server-rendered SPA website with a Node.js backend, we recommend [installing Next.js on WSL](./nextjs-on-wsl.md). (Though Next.js now also offers [static file serving](https://nextjs.org/docs/app/building-your-application/optimizing/static-assets)).
 
-- **Native desktop apps**: [React Native for Desktop + macOS](https://microsoft.github.io/react-native-windows/) enables you to build native desktop applications with JavaScript that run across various types of desktop PCs, laptops, tablets, Xbox, and Mixed Reality devices. It supports both the [Windows SDK](https://microsoft.github.io/react-native-windows/docs/rnw-dependencies) and [macOS SDK](https://microsoft.github.io/react-native-windows/docs/rnm-dependencies).
+- **Native desktop apps**: [React Native for Desktop + macOS](https://microsoft.github.io/react-native-windows/) enables you to build native desktop applications with JavaScript that run across various types of desktop PCs, laptops, tablets, Xbox, and Mixed Reality devices. It supports both the [Windows SDK](https://microsoft.github.io/react-native-windows/docs/rnw-dependencies) and [macOS SDK](https://microsoft.github.io/react-native-macos/).
 
 - **Native mobile apps**: [React Native](https://reactnative.dev/docs/environment-setup) is a cross-platform way to create Android and iOS apps with JavaScript that render to native platform UI code. There are two main ways to install React Native -- the Expo CLI and the React Native CLI. There's a good [comparison of the two on StackOverflow](https://stackoverflow.com/questions/54862388/what-is-the-difference-between-expo-cli-and-react-native-cli). Expo has a client app for iOS and Android mobile devices for running and testing your apps. For instructions on developing an Android app using Windows, React Native, and the Expo CLI see [React Native for Android development on Windows](./react-native-for-android.md).