Globally standardize "the Microsoft Edge Add-ons store"

microsoft-edge/devtools/customize/extensions.md

@@ -16,21 +16,25 @@ In addition to the tools available in Microsoft Edge DevTools, you can add new t
 <!-- ====================================================================== -->
 ## Find an extension that extends DevTools
 
-The [Developer tools](https://microsoftedge.microsoft.com/addons/category/Developer-Tools) category at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) contains extensions that typically extend DevTools.
+The [Developer tools](https://microsoftedge.microsoft.com/addons/category/Developer-Tools) category at the [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) store contains extensions that typically extend DevTools.
 
-There is no way to know whether an extension extends the DevTools **Activity Bar**, without running it or looking at its source code, but the **Developer tools** category at Microsoft Edge Add-ons is a good place to look.
+There is no way to know whether an extension extends the DevTools **Activity Bar**, without running it or looking at its source code, but the **Developer tools** category at the Microsoft Edge Add-ons store is a good place to look.
 
 
 <!-- ====================================================================== -->
 ## Install an extension in DevTools
 
 To install a Microsoft Edge extension that extends DevTools:
 
-1. Go to [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com), such as the [Developer tools](https://microsoftedge.microsoft.com/addons/category/Developer-Tools) category, and go to the extension you want to install.
+1. Go to the [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) store.
+
+1. Go to a category, such as [Developer tools](https://microsoftedge.microsoft.com/addons/category/Developer-Tools).
+
+1. Go to the extension that you want to install.
 
    For example, go to the [React Developer Tools](https://microsoftedge.microsoft.com/addons/detail/react-developer-tools/gpphkfbcpidddadnkolkpfckpihlkkil) extension, which is the example used for the steps below:
 
-   ![The React Developer Tools page at Microsoft Edge Add-ons](./extensions-images/react-add-on-listing.png)
+   ![The React Developer Tools page at the Add-ons store](./extensions-images/react-add-on-listing.png)
 
 1. Click the **Get** button.  An installation dialog opens, **Add \<extension name\> to Microsoft Edge?**
 

microsoft-edge/devtools/whats-new/2023/01/devtools-109.md

@@ -135,7 +135,7 @@ Tree view:
 ![Heap Snapshot Visualizer in Tree mode](./devtools-109-images/heap-snapshot-visualizer-tree.png)
 
 See also:
-* [Heap Snapshot Visualizer](https://microsoftedge.microsoft.com/addons/detail/heap-snapshot-visualizer/fceldlhognbemkgfacnffkdanocidgce) at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com).
+* [Heap Snapshot Visualizer](https://microsoftedge.microsoft.com/addons/detail/heap-snapshot-visualizer/fceldlhognbemkgfacnffkdanocidgce) at the [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) store.
 
 
 <!-- ====================================================================== -->

microsoft-edge/devtools/whats-new/2023/08/devtools-116.md

@@ -44,7 +44,7 @@ See also:
 Prior to Microsoft Edge 116, if you were in Focus Mode while using the React Developer Tools extension, the state of a tool in DevTools wasn't maintained when you switched to another tool and then switched back.  This issue has been fixed.
 
 See also:
-* [React Developer Tools](https://microsoftedge.microsoft.com/addons/detail/react-developer-tools/gpphkfbcpidddadnkolkpfckpihlkkil) extension at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com).
+* [React Developer Tools](https://microsoftedge.microsoft.com/addons/detail/react-developer-tools/gpphkfbcpidddadnkolkpfckpihlkkil) extension at the [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) store.
 * [What's New entries about Focus Mode](/search/?scope=Microsoft%20Edge&terms=focus%20mode)
 
 
@@ -55,7 +55,7 @@ In the **Memory** tool, when there's more than one heap snapshot, a **Containmen
 
 ![The Containment Diff view in the Memory tool](./devtools-116-images/containment-diff.png)
 
-The **Containment Diff** view shows only the new objects, deleted objects, or objects in the retaining chain that will eventually lead to either a new or deleted node.  The dot symbol • means that it's a node in the retaining chain.  Expanding the view displays the node that's new or deleted.
+The **Containment Diff** view shows only the new objects, deleted objects, or objects in the retaining chain that will eventually lead to either a new or deleted node.  The dot symbol * means that it's a node in the retaining chain.  Expanding the view displays the node that's new or deleted.
 
 For example: 
 

microsoft-edge/extensions/contact.md

@@ -25,7 +25,7 @@ https://github.com/microsoft/MicrosoftEdge-Extensions/blob/main/README.md#issues
 Use the [Issues](https://github.com/microsoft/MicrosoftEdge-Extensions/issues) page of the **MicrosoftEdge-Extensions** repo for:
 
 * Communicating with the Extensions team:
-  * Report bugs or issues about [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) (the store) that affect all Edge extension developers or all Microsoft Edge extension users.
+  * Report bugs or issues about the [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) store that affect all Edge extension developers or all Microsoft Edge extension users.
   * Report bugs or issues about Microsoft Partner Center that affect all Edge extension developers or all Microsoft Edge extension users.
   * Suggest new features that could impact or benefit all Microsoft Edge extension developers.
   * Inquire about your Partner Center developer account for Microsoft Edge extensions.
@@ -52,7 +52,7 @@ Use the [Discussions](https://github.com/microsoft/MicrosoftEdge-Extensions/disc
 * Discussions with the Extensions team:
    * Follow the latest announcements and updates from the Microsoft Edge extensions team.
    * Request a feature for Edge extensions.
-   * Discuss how to improve UI features that are at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com).
+   * Discuss how to improve UI features that are at the [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) store.
    * Discuss how to improve extension publishing, management and listing processes or workflows.
    * Provide feedback about features for extensions publishing, extensions management, or processes or workflows for extensions listings.
 
@@ -69,7 +69,7 @@ See also:
 <!-- ====================================================================== -->
 ## Report copyright or trademark infringement
 
-If you think an item at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) violates a copyright or trademark, complete the [Reporting Infringement](https://www.microsoft.com/concern/dmca) form.  When filling in **Step 3: Where can the infringing material be found?**, in the **Product/Service/App** option, make sure to select **Microsoft Store on Windows**.  The Microsoft Edge extensions team will review your report and then take the necessary action.
+If you think an item at the [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) store violates a copyright or trademark, complete the [Reporting Infringement](https://www.microsoft.com/concern/dmca) form.  When filling in **Step 3: Where can the infringing material be found?**, in the **Product/Service/App** option, make sure to select **Microsoft Store on Windows**.  The Microsoft Edge extensions team will review your report and then take the necessary action.
 
 
 <!-- ====================================================================== -->

microsoft-edge/extensions/developer-guide/alternate-distribution-options.md

@@ -11,13 +11,13 @@ ms.date: 05/05/2023
 # Alternative ways to distribute an extension
 <!-- ~= Use alternative installation methods  https://developer.chrome.com/docs/extensions/how-to/distribute/install-extensions -->
 
-Generally, a Microsoft Edge extension is distributed by publishing it at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com).  There are some scenarios where you might need to distribute an extension by using alternate methods.  For example:
+Generally, a Microsoft Edge extension is distributed by publishing it at the [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) store.  There are some scenarios where you might need to distribute an extension by using alternate methods.  For example:
 
 1. The extension is associated with other software, and it should be installed together with the rest of the bundled software.
 
 1. Network administrators want to distribute an extension throughout their organization.
 
-Extensions that aren't loaded from Microsoft Edge Add-ons are called _externally installed extensions_.  The following are alternate methods of distributing externally installed extensions:
+Extensions that aren't loaded from the Microsoft Edge Add-ons store are called _externally installed extensions_.  The following are alternate methods of distributing externally installed extensions:
 
 * Use the Windows registry (Windows only).
 * Use a preferences JSON file (macOS and Linux).
@@ -32,7 +32,7 @@ See also:
 ## Gather initial information
 <!-- ~= https://developer.chrome.com/docs/extensions/how-to/distribute/install-extensions#prereqs -->
 
-Make sure that you publish your extension at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com)<!-- todo: but Intro says other scenarios -->, or package a `.crx` file and ensure that it installs successfully on your computer.  If you install the `.crx` file using the `update_url`, make sure you can go to your extension at that URL.
+Make sure that you publish your extension at the [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) store<!-- todo: but Intro says other scenarios -->, or package a `.crx` file and ensure that it installs successfully on your computer.  If you install the `.crx` file using the `update_url`, make sure you can go to your extension at that URL.
 
 Also, make sure that you have the following information:
 
@@ -57,7 +57,7 @@ To distribute your extension using the Windows registry:
 
 1.  Create a new key, or folder, under **Extensions** with the same name as the ID of your extension. For example, create the key with the name `aaaaaaaabbbbbbbbccccccccdddddddd`.
 
-1.  In the **Extensions** key, create the `update_url` property, and set the value to `https://edge.microsoft.com/extensionwebstorebase/v1/crx`.  The `update_url` property points to the `.crx` file of your extension at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com).
+1.  In the **Extensions** key, create the `update_url` property, and set the value to `https://edge.microsoft.com/extensionwebstorebase/v1/crx`.  The `update_url` property points to the `.crx` file of your extension at the [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) store.
 
     ```json
     {
@@ -122,7 +122,7 @@ To distribute your extension by using a preferences JSON file:
       }
       ```
 
-   * Copy the following code to your preferences JSON file when installing from [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) on macOS and Linux:
+   * Copy the following code to your preferences JSON file when installing from the [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) store on macOS and Linux:
 
       ```json
       {

microsoft-edge/extensions/developer-guide/api-support.md

@@ -133,4 +133,4 @@ This work is licensed under a [Creative Commons Attribution 4.0 International Li
 
 * [Chrome Extensions API reference for Manifest V2](https://developer.chrome.com/docs/extensions/mv2/reference/)
 * [Chrome Extensions API reference for Manifest V3](https://developer.chrome.com/docs/extensions/reference/api/)
-* [Use the REST API to update an extension at Microsoft Edge Add-ons](../update/api/using-addons-api.md) - to update an extension at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com).
+* [Use the REST API to update an extension](../update/api/using-addons-api.md) - to update an extension at the [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) store.

microsoft-edge/extensions/developer-guide/best-practices.md

@@ -10,7 +10,7 @@ ms.date: 09/22/2025
 ---
 # Best practices for extensions
 
-Follow these best practices to implement your extension and list it at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com).  Build an extension that conforms to Microsoft's standards for security, privacy, performance, and user experience.  These principles help ensure your extension is safe, reliable, and valuable to users.
+Follow these best practices to implement your extension and list it at the [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) store.  Build an extension that conforms to Microsoft's standards for security, privacy, performance, and user experience.  These principles help ensure your extension is safe, reliable, and valuable to users.
 
 The Microsoft Edge extensions team continues to gather feedback from developers and users to evolve these best practices.  To ensure that your extension remains compliant and competitive, review this guidance regularly.
 
@@ -89,4 +89,4 @@ Follow these best practices, to improve the quality, reliability, and user exper
 * [Minimize an extension's impact on page load time](./minimize-page-load-time-impact.md)
 
 External:
-* [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com)
+* [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) store

microsoft-edge/extensions/developer-guide/manifest-v3.md

@@ -53,8 +53,8 @@ For information about end of support for Manifest V2 extensions in the Chromium
 <!-- all links in article -->
 
 * [Migrate an extension from Manifest V2 to V3](./migrate-your-extension-from-manifest-v2-to-v3.md)
-* [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) store.
-* [Manifest V3 changes are now available to test in Microsoft Edge](https://blogs.windows.com/msedgedev/2020/10/14/extension-manifest-chromium-edge/) - blog post.
+* [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) store
+* [Manifest V3 changes are now available to test in Microsoft Edge](https://blogs.windows.com/msedgedev/2020/10/14/extension-manifest-chromium-edge/) blog post
 
 Chromium docs: 
 * [Chromium project](https://www.chromium.org/Home/)

microsoft-edge/extensions/developer-guide/match-patterns.md

@@ -23,7 +23,7 @@ See the License for the specific language governing permissions and
 limitations under the License.  -->
 # Defining match patterns for an extension to access file URLs
 
-A Microsoft Edge extension can request access to `file` URLs.  To enable this feature, you need to explicitly configure this access.  Access to `file` URLs isn't automatic.  You must visit the **Extensions management** page at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) to opt into `file` access for each Microsoft Edge extension that requests access to `file` URLs.
+A Microsoft Edge extension can request access to `file` URLs.  To enable this feature, you need to explicitly configure this access.  Access to `file` URLs isn't automatic.  To opt into `file` access for each Microsoft Edge extension that requests access to `file` URLs, you must visit the **Extensions management** page at the [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) store.
 
 For Microsoft Edge extension, host permission and content script pattern matching works as follows.
 

microsoft-edge/extensions/developer-guide/migrate-your-extension-from-manifest-v2-to-v3.md

@@ -38,9 +38,9 @@ Migrating an extension from using Manifest V2 to using Manifest V3 brings severa
 <!-- ====================================================================== -->
 ## Remotely hosted code
 
-Today, some parts of the extensions code are hosted remotely, and aren't included as part of the extension package during the validation process.  Although this offers the flexibility to change code without resubmitting the extension at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com), it's possible to exploit the code after installation.
+Today, some parts of the extensions code are hosted remotely, and aren't included as part of the extension package during the validation process.  Although this offers the flexibility to change code without resubmitting the extension at the [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) store, it's possible to exploit the code after installation.
 
-To ensure that the extensions at Microsoft Edge Add-ons are validated, the Microsoft Edge extensions team disallows extensions from using remotely hosted code.  This change makes extensions more secure.
+To ensure that the extensions at the Microsoft Edge Add-ons store are validated, the Microsoft Edge extensions team disallows extensions from using remotely hosted code.  This change makes extensions more secure.
 
 You'll need to package and submit all code that is used by the extension, for validation.  Alternatively, you can use the `eval()` function in a sandboxed iframe. See [Use eval() in sandboxed iframes](https://developer.chrome.com/docs/extensions/how-to/security/sandboxing-eval)<!-- chrome link ok, extension ref docs are there -->.
 
@@ -107,7 +107,7 @@ The Microsoft Edge extensions team publishes updates at our blog.  You can provi
 External:
 * [Manifest V3 changes are now available in Microsoft Edge](https://techcommunity.microsoft.com/t5/articles/manifest-v3-changes-are-now-available-in-microsoft-edge/m-p/1780254) - blog post.
 * [Extensions](/deployedge/microsoft-edge-policies#extensions) in _Microsoft Edge – Policies_.
-* [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) store.
+* [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) store
 
 Chromium docs:
 * [Migrate to Manifest V3](https://developer.chrome.com/docs/extensions/develop/migrate)<!-- chrome link ok -->

microsoft-edge/extensions/developer-guide/native-messaging.md

@@ -18,7 +18,7 @@ To acquire the extension and native app host, there are two different distributi
 
 * Package your extension and the host together.  When a user installs the package, both the extension and the host are installed.
 
-* Or, install your extension from [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com), and your extension prompts users to install the host.
+* Or, install your extension from the [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) store, and your extension prompts users to install the host.<!-- todo: consistent voice: who is referred to, Dev or user? -->
 
 To create your extension to send and receive messages with native app hosts, do the following steps.
 
@@ -129,7 +129,7 @@ Sideload your extension to test native messaging with the host.  To sideload you
 
 1. Copy the key from `microsoft_catalog_extension_id` (ID) from the extension listing on the page.
 
-When you're ready to distribute your extension to users, publish your extension at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com).  The extension ID of the published extension might differ from the ID that's used while sideloading your extension.  If the ID changed, update `allowed_origins` in the native messaging host manifest file with the ID of your published extension.
+When you're ready to distribute your extension to users, publish your extension at the [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) store.  The extension ID of the published extension might differ from the ID that's used while sideloading your extension.  If the ID changed, update `allowed_origins` in the native messaging host manifest file with the ID of your published extension.
 
 
 <!-- ====================================================================== -->
@@ -201,7 +201,7 @@ The `HKEY_CURRENT_USER\SOFTWARE\WOW6432Node` registry node is not searched on 64
 
 #### Extension IDs required for both stores
 
-If you have an extension both at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) and the Chrome Web Store, you must add the extension IDs that correspond to both of the stores<!-- todo: copy 'stores' def'n to top? --> in the `allowed_origins` of the native messaging host manifest file.
+If you have an extension both at the [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) store and the [Chrome Web Store](https://chrome.google.com/webstore/category/extensions), you must add the extension IDs that correspond to both of the stores, in the `allowed_origins` of the native messaging host manifest file.
 
 This is required because only the native messaging host manifest file that corresponds to the first registry location that's found is read.