Merge branch 'main' into user/mikehoffms/de-detached

Author: mikehoffms

.openpublishing.redirection.json

@@ -193,6 +193,11 @@
         "redirect_url": "/microsoft-edge/extensions-chromium/update/auto-update",
         "redirect_document_id": false
       },
+      {
+        "source_path": "./microsoft-edge/extensions-chromium/publish/add-ons-store-curation.md",
+        "redirect_url": "/microsoft-edge/extensions-chromium/publish/add-ons-curation",
+        "redirect_document_id": false
+      },
 // /Microsoft Edge extensions
 // ============================================================================
 // Progressive Web Apps

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

@@ -10,25 +10,27 @@ ms.date: 07/18/2023
 ---
 # Add custom UI to DevTools using extensions
 
-In addition to the tools available in Microsoft Edge DevTools, you can add new tools by installing Microsoft Edge extensions, or build your own extensions for your specific use cases.  Edge Add-ons extensions often extend the Microsoft Edge user interface with new buttons and panels, but can also extend DevTools, within Microsoft Edge, by adding new tool tabs in the **Activity Bar**.
+In addition to the tools available in Microsoft Edge DevTools, you can add new tools by installing Microsoft Edge extensions, or build your own extensions for your specific use cases.  A Microsoft Edge extension often extends the Microsoft Edge user interface with new buttons and panels, but can also extend DevTools within Microsoft Edge, by adding a new tool tab in the **Activity Bar**.
 
 
 <!-- ====================================================================== -->
 ## Find an extension that extends DevTools
 
-The Edge Add-ons website has a **Developer tools** category that contains extensions that typically extend DevTools.  See the [Developer tools category](https://microsoftedge.microsoft.com/addons/category/Developer-Tools) on the Edge Add-ons website.
+The [Developer tools](https://microsoftedge.microsoft.com/addons/category/Developer-Tools) category at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/) contains extensions that typically extend DevTools.
 
-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 of the Edge Add-ons website 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 Microsoft Edge Add-ons is a good place to look.
 
 
 <!-- ====================================================================== -->
 ## Install an extension in DevTools
 
-To install an Edge Add-ons extension that extends DevTools:
+To install a Microsoft Edge extension that extends DevTools:
 
-1. Go to the [Edge Add-ons](https://microsoftedge.microsoft.com/addons/) website, such as the [Developer tools category](https://microsoftedge.microsoft.com/addons/category/Developer-Tools), 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:
+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.
 
-   ![The React Developer Tools page on the Edge Add-ons website](./extensions-images/react-add-on-listing.png)
+   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)
 
 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) - Microsoft Edge Add-ons Store.
+* [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 Edge Add-ons store
+* [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

@@ -1,6 +1,6 @@
 ---
 title: Alternative ways to distribute an extension
-description: How to distribute extensions using alternate methods that don't use verified stores.
+description: How to distribute a Microsoft Edge extension by using alternate methods that don't use verified browser extension stores.
 author: MSEdgeTeam
 ms.author: msedgedevrel
 ms.topic: conceptual
@@ -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 website. There are some scenarios where developers may need to distribute extensions using alternate methods. For example:
+Generally, a Microsoft Edge extension is distributed by publishing it at [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 Edge Add-ons store are referred to as _externally installed extensions_. The following are alternate methods of distributing externally installed extensions:
+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:
 
 * 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 website<!-- todo: but Intro says: "Generally, extensions are distributed through the Microsoft Edge Add-ons website. There are some scenarios where developers may need to distribute extensions using alternate methods." -->, 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:
 
@@ -44,7 +44,7 @@ Also, make sure that you have the following information:
 
 * The ID of your extension.  The ID information is available in Microsoft Edge at `edge://extensions` after you load the packed extension.
 
-The following examples use `1.0` as the version, and `aaaaaaaabbbbbbbbccccccccdddddddd` for the ID.
+The following examples use `1.0` as the version, and `aaaaaaaabbbbbbbbccccccccdddddddd` for the ID.  This ID is the CRX ID, which is a unique 32-character code which is the letters that are present at the end of your extension's URL.  This ID is generated automatically, and it cannot be customized.
 
 
 <!-- ====================================================================== -->
@@ -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 website.
+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
     {
@@ -80,7 +80,7 @@ To distribute your extension by using a preferences JSON file:
 
 1. Create a JSON file where the name of the file corresponds to the ID of your extension. For example, create a JSON file with the file name `aaaaaaaabbbbbbbbccccccccdddddddd.json`.
 
-   The name of the preferences JSON file is your Microsoft Edge extension's CRX ID, followed by a `.json` extension.  The CRX ID is a unique 32-character code which is the letters that are present at the end of your extension's URL.
+   The name of the preferences JSON file is your Microsoft Edge extension's CRX ID, followed by a `.json` extension.  The CRX ID is a unique 32-character code which is the letters that are present at the end of your extension's URL.  This ID is generated automatically, and it cannot be customized.
 
 1. Depending on your operating system, save the JSON file to one of the following folders:
 
@@ -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 website 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 website.
+* [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 on the Microsoft Edge Add-ons Store.  
+description: Best Practices to implement an extension and list it at Microsoft Edge Add-ons.
 author: MSEdgeTeam
 ms.author: msedgedevrel
 ms.topic: conceptual
@@ -10,13 +10,13 @@ ms.date: 11/20/2023
 ---
 # Best practices for extensions
 
-Follow these Best Practices to implement your extension and list it on the Microsoft Edge Add-ons Store.
+Follow these Best Practices to implement your extension and list it at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/).
 
 
 <!-- ====================================================================== -->
 ## Design a high-quality extension
 
-Build extensions that conform to Microsoft's standards for security, privacy, transparency, and user experience.
+Build an extension that conforms to Microsoft's standards for security, privacy, transparency, and user experience.
 
 **Security**: Make sure that your extension doesn't pose any security threats to users. 
 
@@ -26,4 +26,4 @@ Build extensions that conform to Microsoft's standards for security, privacy, tr
 
 **Store listing**: Make sure that your extension's store listing sets correct user expectations and clearly communicates what the extension does.
 
-We'll continue gathering input about Developer experiences with extensions and updating these Best Practices.
+We'll continue gathering input about Developer experiences with extensions, and updating these Best Practices.

microsoft-edge/extensions-chromium/developer-guide/csp.md

@@ -1,6 +1,6 @@
 ---
 title: Using Content Security Policy (CSP) to control which resources can be run
-description: Using Content Security Policy (CSP) to control which resources can be loaded and run by a Microsoft Edge add-on.
+description: Using Content Security Policy (CSP) to control which resources can be loaded and run by a Microsoft Edge extension.
 author: MSEdgeTeam
 ms.author: msedgedevrel
 ms.topic: conceptual
@@ -249,17 +249,15 @@ Currently, you can allowlist origins that have the following schemes: `blob`, `f
 
 For development ease, resources loaded over HTTP from servers on your local machine can be `allowlisted`.  You can allowlist script and object sources on any port of either `http://127.0.0.1` or `http://localhost`.
 
-> [!NOTE]
-> The restriction against resources loaded over HTTP applies only to those resources which are directly run.  You are still free, for example, to make `XMLHTTPRequest` connections to any origin you like; the default policy doesn't restrict `connect-src` or any of the other CSP directives in any way.
+The restriction against resources loaded over HTTP applies only to those resources which are directly run.  You are still free, for example, to make `XMLHTTPRequest` connections to any origin you like; the default policy doesn't restrict `connect-src` or any of the other CSP directives in any way.
 
 A relaxed policy definition which allows script resources to be loaded from `example.com` over HTTPS may look like:
 
 ```json
 "content_security_policy": "script-src 'self' https://example.com; object-src 'self'"
 ```
 
-> [!NOTE]
-> Both `script-src` and `object-src` are defined by the policy.  Microsoft Edge doesn't accept a policy that doesn't limit each of these values to (at least) '`self`'.
+Both `script-src` and `object-src` are defined by the policy.  Microsoft Edge doesn't accept a policy that doesn't limit each of these values to (at least) '`self`'.
 
 <!-- Making use of Google Analytics is the canonical example for this sort of policy definition.  It is common enough that an Analytics boilerplate of sorts is provided in the Event Tracking with Google Analytics sample extension, and a brief tutorial that goes into more detail.  -->
 
@@ -297,7 +295,7 @@ DOM injected scripts that run immediately upon injection into the page run as yo
 document.write("<script>alert(1);</script>");
  ```
 
-This content script causes an `alert` immediately upon the `document.write()`.  Note that this runs regardless of the policy a page specifies.  However, the behavior becomes more complicated both inside that DOM injected script and for any script that doesn't immediately run upon injection.
+This content script causes an `alert` immediately upon the `document.write()`.  This<!-- todo: script? alert? --> runs regardless of the policy that a page specifies.  However, the behavior becomes more complicated both inside that DOM injected script and for any script that doesn't immediately run upon injection.
 
 Imagine that your extension is running on a page that provides an associated CSP that specifies `script-src 'self'`.  Now imagine the content script runs the following code:
 

microsoft-edge/extensions-chromium/developer-guide/declare-permissions.md

@@ -74,7 +74,7 @@ The following table lists the currently available permission strings to use in y
 |:--- |:--- |
 | `activeTab` | Requests that the extension is granted permissions according to the `activeTab` specification. |
 | `alarms` | Gives your extension access to the `chrome.alarms` API. |
-| `background` | Makes Microsoft Edge start up early and shut down late, so that extensions may have a longer life. <br/>When any installed extension has `background` permission, Microsoft Edge runs invisibly as soon as the user logs into the user's computer, and before the user launches Microsoft Edge.  The `background` permission also makes Microsoft Edge continue running, even after its last window is closed, until the user explicitly quits Microsoft Edge. <br/>**Note:** Disabled extensions are treated as if they aren't installed. <br/>You should use the `background` permission with [background scripts](https://developer.chrome.com/docs/extensions/mv3/background_pages/).|
+| `background` | Makes Microsoft Edge start up early and shut down late, so that extensions may have a longer life. <br/>When any installed extension has `background` permission, Microsoft Edge runs invisibly as soon as the user logs into the user's computer, and before the user launches Microsoft Edge.  The `background` permission also makes Microsoft Edge continue running, even after its last window is closed, until the user explicitly quits Microsoft Edge. <br/>Disabled extensions are treated as if they aren't installed. <br/>You should use the `background` permission with [background scripts](https://developer.chrome.com/docs/extensions/mv3/background_pages/).|
 | `bookmarks` | Gives your extension access to the `chrome.bookmarks` API. |
 | `browsingData` | Gives your extension access to the `chrome.browsingData` API. |
 | `certificateProvider` | Gives your extension access to the `chrome.certificateProvider` API. |

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

@@ -49,7 +49,7 @@ Chromium has revised the timelines for ending support for Manifest V2.  See:
 
 To help you plan the migration of your extension from Manifest V2 to Manifest V3, consider the following schedule for support for Manifest V2 and V3 in Microsoft Edge and Microsoft Partner Center.
 
-The Microsoft Edge team will independently decide on MV3 migration timelines for Microsoft Edge Add-ons and share an update here.  We continue to analyze the concerns raised by extension developers and explore the optimal path for the Microsoft Edge Add-ons ecosystem.  Meanwhile, to plan the migration of your extension from Manifest V2 to Manifest V3, see [Manifest timeline for the Chromium browser engine](#manifest-timeline-for-the-chromium-browser-engine), above.
+The Microsoft Edge team will independently decide on MV3 migration timelines for Microsoft Edge extensions and share an update here.  We continue to analyze the concerns raised by extension developers and explore the optimal path for the Microsoft Edge extensions ecosystem.  Meanwhile, to plan the migration of your extension from Manifest V2 to Manifest V3, see [Manifest timeline for the Chromium browser engine](#manifest-timeline-for-the-chromium-browser-engine), above.
 
 
 **The Microsoft Edge team is currently in the process of updating this MV3 migration timeline.**