at Microsoft Edge Add-ons

Author: mikehoffms

.openpublishing.redirection.json

@@ -190,7 +190,7 @@
       },
       {
         "source_path": "./microsoft-edge/extensions-chromium/publish/add-ons-store-curation.md",
-        "redirect_url": "/microsoft-edge/extensions-chromium/publish/add-ons-site-curation",
+        "redirect_url": "/microsoft-edge/extensions-chromium/publish/add-ons-curation",
         "redirect_document_id": false
       },
 // /Microsoft Edge extensions

microsoft-edge/devtools-guide-chromium/customize/extensions.md

@@ -16,21 +16,21 @@ In addition to the tools available in Microsoft Edge DevTools, you can add new t
 <!-- ====================================================================== -->
 ## Find an extension that extends DevTools
 
-The Microsoft Edge Add-ons site has a **Developer tools** category that contains extensions that typically extend DevTools.  See the [Developer tools](https://microsoftedge.microsoft.com/addons/category/Developer-Tools) category at the Microsoft Edge Add-ons site.
+[Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/) has a **Developer tools** category that contains extensions that typically extend DevTools.  See the [Developer tools](https://microsoftedge.microsoft.com/addons/category/Developer-Tools) category.
 
-There is no way to know if 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 site is a good place to look.
+There is no way to know if 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](https://microsoftedge.microsoft.com/addons/) is a good place to look.
 
 
 <!-- ====================================================================== -->
 ## Install an extension in DevTools
 
 To install an Edge Add-ons extension that extends DevTools:
 
-1. Go to the [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/) site, 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 [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/), such as the [Developer tools](https://microsoftedge.microsoft.com/addons/category/Developer-Tools) category, and go to the extension 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 on the Microsoft Edge Add-ons site](./extensions-images/react-add-on-listing.png)
+   ![The React Developer Tools page at Microsoft Edge Add-ons](./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-guide-chromium/whats-new/2023/01/devtools-109.md

@@ -132,7 +132,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 the Microsoft Edge Add-ons site.
+* [Heap Snapshot Visualizer](https://microsoftedge.microsoft.com/addons/detail/heap-snapshot-visualizer/fceldlhognbemkgfacnffkdanocidgce) at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/).
 
 
 <!-- ====================================================================== -->

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

@@ -42,7 +42,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 the Microsoft Edge Add-ons site.
+* [React Developer Tools](https://microsoftedge.microsoft.com/addons/detail/react-developer-tools/gpphkfbcpidddadnkolkpfckpihlkkil) - extension at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/).
 * [What's New entries about Focus Mode](/search/?scope=Microsoft%20Edge&terms=focus%20mode)
 
 

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

@@ -14,13 +14,13 @@ ms.date: 05/05/2023
 per https://developer.chrome.com/docs/extensions/how-to/distribute/install-extensions
 -->
 
-Generally, extensions are distributed through the [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/) site.  There are some scenarios where you might need to distribute an extension by using alternate methods.  For example:
+Generally, extensions are distributed through [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/).  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 the Microsoft Edge Add-ons site are called _externally installed extensions_.  The following are alternate methods of distributing externally installed extensions:
+Extensions that aren't loaded from [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/) 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).
@@ -34,7 +34,7 @@ See also:
 <!-- ====================================================================== -->
 ## Gather initial information
 
-Make sure that you publish your extension in the Microsoft Edge Add-ons site<!-- 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 [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/)<!-- 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:
 
@@ -58,7 +58,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 in the Microsoft Edge Add-ons site.
+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/addons/).
 
     ```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 the Microsoft Edge Add-ons site on macOS and Linux:
+   *  Copy the following code to your preferences JSON file when installing from [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/) on macOS and Linux:
 
       ```json
       {

microsoft-edge/extensions-chromium/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/)
-* [Using the REST API for updating Microsoft Edge Add-ons](../update/api/using-addons-api.md) - to update an extension at the Microsoft Edge Add-ons site.
+* [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/addons/).

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

@@ -1,6 +1,6 @@
 ---
 title: Best practices for extensions
-description: Best Practices to implement an extension and list it at the Microsoft Edge Add-ons site.
+description: Best Practices to implement an extension and list it at Microsoft Edge Add-ons.
 author: MSEdgeTeam
 ms.author: msedgedevrel
 ms.topic: conceptual
@@ -10,7 +10,7 @@ ms.date: 11/20/2023
 ---
 # Best practices for extensions
 
-Follow these Best Practices to implement your extension and list it at the [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/) site.
+Follow these Best Practices to implement your extension and list it at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/).
 
 
 <!-- ====================================================================== -->

microsoft-edge/extensions-chromium/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 Add-on (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 the Microsoft Edge Add-ons site to opt into `file` access for each Microsoft Edge extension that requests access to `file` URLs.
+A Microsoft Edge Add-on (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/addons/) to opt into `file` access for each Microsoft Edge extension that requests access to `file` URLs.
 
 For Microsoft Edge Add-ons (extensions), host permission and content script pattern matching works as follows.
 

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

@@ -16,9 +16,9 @@ This article lists important changes being implemented as part of Manifest V3, w
 <!-- ====================================================================== -->
 ## 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.  While this offers flexibility to change code without resubmitting the extension to the Microsoft Edge Add-ons site, 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 [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/), it's possible to exploit the code after installation.
 
-To ensure that the [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons) site lists validated extensions, the Microsoft Edge extensions team disallows extensions from using remotely hosted code.  This change makes extensions more secure.
+To ensure that [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/) lists validated extensions, the Microsoft Edge extensions team disallows extensions from using remotely hosted code.  This change makes extensions more secure.
 
 Developers will 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 environment](https://developer.chrome.com/docs/extensions/mv2/sandboxingEval).
 

microsoft-edge/extensions-chromium/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 using the [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/) site, and your extension prompts users to install the host.
+*  Or, install your extension using [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/), and your extension prompts users to install the host.
 
 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 to the Microsoft Edge Add-ons site.  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 [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/).  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 extensions at the Microsoft Edge Add-ons site and the Chrome Web Store, you must add the extension IDs corresponding to both of the stores in the `allowed_origins` of the native messaging host manifest file.
+If you have an extension at both [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/) 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.
 
 This is required because only the native messaging host manifest file that corresponds to the first registry location that's found is read.