fix Store links

mikehoffms · mikehoffms · commit 4b32c30fe089 · 2025-02-28T13:40:13.000-08:00
diff --git a/microsoft-edge/devtools-guide-chromium/remote-debugging/windows.md b/microsoft-edge/devtools-guide-chromium/remote-debugging/windows.md
@@ -30,7 +30,7 @@ To set up the host (debuggee) machine:
 
 1. Install and configure [Microsoft Edge](https://www.microsoft.com/edge)
 
-1. Install the [Remote Tools for Microsoft Edge (Beta)](https://www.microsoft.com/store/apps/9P6CMFV44ZLT) from the [Microsoft Store](https://www.microsoft.com/store/apps/windows)
+1. Install the [Remote Tools for Microsoft Edge](https://apps.microsoft.com/detail/9p6cmfv44zlt) from the [Microsoft Store](https://apps.microsoft.com).
 
 1. Activate [Developer Mode](/windows/apps/get-started/enable-your-device-for-development) and enable [Device Portal](/windows/uwp/debug-test-perf/device-portal)
 
@@ -50,15 +50,15 @@ To set up the host (debuggee) machine:
 
 
 <!-- ------------------------------ -->
-#### Install the Remote Tools for Microsoft Edge (Beta)
+#### Install the Remote Tools for Microsoft Edge
 
-Install the [Remote Tools for Microsoft Edge (Beta)](https://www.microsoft.com/store/apps/9P6CMFV44ZLT) from the [Microsoft Store](https://www.microsoft.com/store/apps/windows).
+Install the [Remote Tools for Microsoft Edge](https://apps.microsoft.com/detail/9p6cmfv44zlt) from the [Microsoft Store](https://apps.microsoft.com).
 
-The **Get** button for the [Remote Tools for Microsoft Edge (Beta)](https://www.microsoft.com/store/apps/9P6CMFV44ZLT) may be disabled if you are on Windows 10 or later version 1809 or earlier.  To set up the host (debuggee) machine, it must be running Windows 10 version 1903 or later.  Update the host (debuggee) machine to acquire the [Remote Tools for Microsoft Edge (Beta)](https://www.microsoft.com/store/apps/9P6CMFV44ZLT).
+The **Get** button for the [Remote Tools for Microsoft Edge](https://apps.microsoft.com/detail/9p6cmfv44zlt) may be disabled if you are on Windows 10 or later version 1809 or earlier.  To set up the host (debuggee) machine, it must be running Windows 10 version 1903 or later.  Update the host (debuggee) machine to acquire the [Remote Tools for Microsoft Edge](https://apps.microsoft.com/detail/9p6cmfv44zlt).
 
-![The Remote Tools for Microsoft Edge (Beta) in the Microsoft Store](./windows-images/remote-debugging-windows-media-remote-tools-in-store.png)
+![The Remote Tools for Microsoft Edge in the Microsoft Store](./windows-images/remote-debugging-windows-media-remote-tools-in-store.png)
 
-Launch the [Remote Tools for Microsoft Edge (Beta)](https://www.microsoft.com/store/apps/9P6CMFV44ZLT) and, if prompted, accept the permissions dialog in the app.  You can now close the [Remote Tools for Microsoft Edge (Beta)](https://www.microsoft.com/store/apps/9P6CMFV44ZLT) and you don't need to have it open for future remote debugging sessions.
+Launch the [Remote Tools for Microsoft Edge](https://apps.microsoft.com/detail/9p6cmfv44zlt) and, if prompted, accept the permissions dialog in the app.  You can now close the [Remote Tools for Microsoft Edge](https://apps.microsoft.com/detail/9p6cmfv44zlt) and you don't need to have it open for future remote debugging sessions.
 
 
 <!-- ------------------------------ -->
@@ -70,7 +70,7 @@ If your network is listed as **Public**, go to **Settings** > **Network & Intern
 
 Now, open the **Settings** app.  In **Find a setting**, enter `Developer settings` and select it.  Toggle on **Developer Mode**.  You can now turn on the **Device Portal** by setting **Turn on remote diagnostics over local area network connections** to **On**.  You can then optionally turn **Authentication** on so that the client (debugger) device must provide the correct credentials to connect to this device.
 
-If **Turn on remote diagnostics over local area network connections.** was previously turned on, you must turn it off and turn it on again for **Device Portal** to work with the [Remote Tools for Microsoft Edge (Beta)](https://www.microsoft.com/store/apps/9P6CMFV44ZLT).  If  a **For developers** section isn't displayed in **Settings**, **Device Portal** may already be turned on, so try restarting the Windows 10 or later device instead.
+If **Turn on remote diagnostics over local area network connections.** was previously turned on, you must turn it off and turn it on again for **Device Portal** to work with the [Remote Tools for Microsoft Edge](https://apps.microsoft.com/detail/9p6cmfv44zlt).  If  a **For developers** section isn't displayed in **Settings**, **Device Portal** may already be turned on, so try restarting the Windows 10 or later device instead.
 
 ![The Settings app with Developer Mode and Device Portal configured](./windows-images/remote-debugging-windows-media-host-settings.png)
 
diff --git a/microsoft-edge/devtools-guide-chromium/whats-new/2020/03/devtools.md b/microsoft-edge/devtools-guide-chromium/whats-new/2020/03/devtools.md
@@ -35,9 +35,9 @@ These are the latest features in the Stable release of Microsoft Edge DevTools.
 <!-- ------------------------------ -->
 #### Remotely debug Microsoft Edge on Windows 10 or later Devices
 
-The [Remote Tools for Microsoft Edge (Beta)](https://www.microsoft.com/store/apps/9P6CMFV44ZLT) app is now available in the [Microsoft Store](https://www.microsoft.com/store/apps/windows). This app extends the [Windows Device Portal](/windows/uwp/debug-test-perf/device-portal).  You can connect from Microsoft Edge running on your development machine to a remote Windows 10 or later device and display a list of targets.  This list of targets includes all tabs in Microsoft Edge and [PWAs](../../../../progressive-web-apps-chromium/index.md) open on the Windows device.  Use DevTools on your development machine against a target running on the remote Windows device.
+The [Remote Tools for Microsoft Edge](https://apps.microsoft.com/detail/9p6cmfv44zlt) app is now available in the [Microsoft Store](https://apps.microsoft.com). This app extends the [Windows Device Portal](/windows/uwp/debug-test-perf/device-portal).  You can connect from Microsoft Edge running on your development machine to a remote Windows 10 or later device and display a list of targets.  This list of targets includes all tabs in Microsoft Edge and [PWAs](../../../../progressive-web-apps-chromium/index.md) open on the Windows device.  Use DevTools on your development machine against a target running on the remote Windows device.
 
-![The Remote Tools for Microsoft Edge (Beta) app available in the Microsoft Store](./devtools-images/remote-tools.png)
+![The Remote Tools for Microsoft Edge app available in the Microsoft Store](./devtools-images/remote-tools.png)
 
 Read our guide for setting up your Windows 10 device and your development machine for remote debugging: [Remotely debug Windows devices](../../../remote-debugging/windows.md).
 
diff --git a/microsoft-edge/devtools-protocol-chromium/index.md b/microsoft-edge/devtools-protocol-chromium/index.md
@@ -129,13 +129,13 @@ String("Target is closing")
 
 
 <!-- ====================================================================== -->
-## Remote Tools for Microsoft Edge (Beta)
+## Remote Tools for Microsoft Edge
 
-You can install the [Remote Tools for Microsoft Edge (Beta)](https://www.microsoft.com/store/apps/9P6CMFV44ZLT) from the [Microsoft Store](https://www.microsoft.com/store/apps/windows).  This app enables you to remotely debug Microsoft Edge running on a Windows 10 or later device from your development machine.
+You can install the [Remote Tools for Microsoft Edge](https://apps.microsoft.com/detail/9p6cmfv44zlt) from the [Microsoft Store](https://apps.microsoft.com).  This app enables you to remotely debug Microsoft Edge running on a Windows 10 or later device from your development machine.
 
 To learn how to set up your Windows device and connect to it from your development machine, see [Get started with remote debugging Windows devices](../devtools-guide-chromium/remote-debugging/windows.md).
 
-The [Remote Tools for Microsoft Edge (Beta)](https://www.microsoft.com/store/apps/9P6CMFV44ZLT) uses the same Microsoft Edge DevTools Protocol as [DevTools](../devtools-guide-chromium/overview.md) to communicate with Microsoft Edge running on the Windows 10 or later device you want to debug.  This app just prepends `/msedge/` and a process ID (`pid`) before each call to the protocol.  It supports the following HTTP endpoints.
+The [Remote Tools for Microsoft Edge](https://apps.microsoft.com/detail/9p6cmfv44zlt) uses the same Microsoft Edge DevTools Protocol as [DevTools](../devtools-guide-chromium/overview.md) to communicate with Microsoft Edge running on the Windows 10 or later device you want to debug.  This app just prepends `/msedge/` and a process ID (`pid`) before each call to the protocol.  It supports the following HTTP endpoints.
 
 The following Reference sections are for Remote Tools for Microsoft Edge.
 
diff --git a/microsoft-edge/progressive-web-apps-chromium/how-to/microsoft-store.md b/microsoft-edge/progressive-web-apps-chromium/how-to/microsoft-store.md
@@ -16,7 +16,7 @@ Publishing your Progressive Web App (PWA) to the [Microsoft Store](/windows/uwp/
 |---|---|
 | **Discoverability** | Users naturally look for apps in the app store.  When you publish to the Microsoft Store, millions of Windows users can discover your PWA alongside other Windows apps.  The Store showcases apps through categories, curated collections, and more.  App discovery portals provide an easy browsing and shopping experience for potential users of your app.  You can even enhance your Store listing with screenshots, a hero image, and video trailers - see [App screenshots, images, and trailers](/windows/apps/publish/publish-your-app/screenshots-and-images). |
 | **Trustworthiness** | Windows customers know they can trust their Microsoft Store purchases and downloads, because they adhere to the rigorous [Microsoft Store Policies](/windows/apps/publish/store-policies). |
-| **Easy install** | The Microsoft Store provides a consistent and user-friendly install experience across [all Windows 10 or later apps](https://www.microsoft.com/store/apps/windows). |
+| **Easy install** | The Microsoft Store provides a consistent and user-friendly install experience across [all Windows 10 or later apps](https://apps.microsoft.com). |
 | **App analytics** | The [Microsoft Partner Center dashboard](/windows/uwp/publish/index) provides [detailed analytics](/windows/uwp/publish/analytics) about your app's health, usage, and more. |
 
 To publish your PWA to the Microsoft Store, no code changes are required.  Instead, you create an app reservation in Microsoft Partner Center, package your PWA using PWA Builder, and then submit your package to the Microsoft Store.  The following sections explain these steps.
diff --git a/microsoft-edge/progressive-web-apps-chromium/index.md b/microsoft-edge/progressive-web-apps-chromium/index.md
@@ -94,7 +94,7 @@ To find examples of what PWAs can do, see [Myth Busting PWAs](https://www.davrou
 <!-- ====================================================================== -->
 ## The Microsoft Store
 
-Because Progressive Web Apps (PWAs) are just like other apps in the [Microsoft Store](https://www.microsoft.com/store/apps/windows), users can fully engage with them—from discovery, to installation, to execution—without<!-- em dashes--> ever opening the browser.
+Because Progressive Web Apps (PWAs) are just like other apps in the [Microsoft Store](https://apps.microsoft.com), users can fully engage with them—from discovery, to installation, to execution—without<!-- em dashes--> ever opening the browser.
 
 The Microsoft Store provides a trustworthy and familiar experience for users to install your app.  Additionally, you can view detailed usage statistics and charts that let you know how your apps in the Microsoft Store are doing.
 
diff --git a/microsoft-edge/webview2/how-to/remote-debugging-desktop.md b/microsoft-edge/webview2/how-to/remote-debugging-desktop.md
@@ -40,7 +40,7 @@ Attach Microsoft Edge DevTools remotely to a desktop WebView2 WinUI 2 (UWP) app
 
     ![Remote Debugging URL](./remote-debugging-desktop-images/remote-debugging-url.png)
 
-1.  Install [Remote Tools for Microsoft Edge](https://www.microsoft.com/store/productId/9P6CMFV44ZLT) from the Microsoft Store.
+1.  Install [Remote Tools for Microsoft Edge](https://apps.microsoft.com/detail/9p6cmfv44zlt) from the Microsoft Store.
 
 1.  In Microsoft Edge, go to the Device Portal URL that you previously noted.  Verify that the **Confirm security settings** page is loaded (in the **Windows Device Portal** tab):
 
diff --git a/microsoft-edge/webview2/how-to/remote-debugging-hololens.md b/microsoft-edge/webview2/how-to/remote-debugging-hololens.md
@@ -32,7 +32,7 @@ Attach Microsoft Edge DevTools remotely to a HoloLens 2 WebView2 WinUI 2 (UWP) a
 
     In **Connect using** > **Ethernet**, note the URL that will be used for the remote debugging connection.
 
-1.  Install [Remote Tools for Microsoft Edge](https://www.microsoft.com/store/productId/9P6CMFV44ZLT) from the Microsoft Store on your HoloLens 2 device.
+1.  Install [Remote Tools for Microsoft Edge](https://apps.microsoft.com/detail/9p6cmfv44zlt) from the Microsoft Store on your HoloLens 2 device.
 
 1.  In Microsoft Edge, go to the Device Portal URL that you previously noted.  Verify that the **Confirm security settings** page is loaded (in the **Windows Device Portal** tab):
 
diff --git a/microsoft-edge/webview2/how-to/webdriver.md b/microsoft-edge/webview2/how-to/webdriver.md
@@ -251,7 +251,7 @@ For more info about the `DebuggerAddress` property of the `EdgeOptions` object,
 
 1. Note the `browserProcessId` for the WebView2 process that you want to attach Microsoft Edge WebDriver to.  For example, the above screenshot shows the `browserProcessId` as `47860`.
 
-1. In your code, use the `wdpAddress` and `wdpProcessId` properties to tell Microsoft Edge WebDriver to connect to the [Remote Tools for Microsoft Edge](https://apps.microsoft.com/store/detail/9P6CMFV44ZLT) and the specific WebView2 process.
+1. In your code, use the `wdpAddress` and `wdpProcessId` properties to tell Microsoft Edge WebDriver to connect to the [Remote Tools for Microsoft Edge](https://apps.microsoft.com/detail/9p6cmfv44zlt) and the specific WebView2 process.
    * `wdpAddress` is defined as the Device Portal URL.
    * `wdpProcessId` is defined as the `browserProcessId` value that you noted in the previous step:
 
