develop extension not add-on

Author: mikehoffms

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

@@ -10,21 +10,21 @@ 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
 
-[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.
+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 at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/) 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](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:
+To install a Microsoft Edge extension that extends DevTools:
 
 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.
 

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 [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/).
+* [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,7 +14,7 @@ ms.date: 05/05/2023
 per https://developer.chrome.com/docs/extensions/how-to/distribute/install-extensions
 -->
 
-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:
+Generally, an 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.
 

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

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.**

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

@@ -23,9 +23,9 @@ 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 [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.
+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/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.
+For Microsoft Edge extension, host permission and content script pattern matching works as follows.
 
 Host permissions and content script matching are based on a set of URLs defined by match patterns.  A match pattern is essentially a URL that begins with a permitted scheme (`http`, `https`, `file`, or `ftp`, and that can contain '`*`' characters.  The special pattern `<all_urls>` matches any URL that starts with a permitted scheme.  Each match pattern has 3 parts:
 

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

@@ -18,7 +18,7 @@ This article lists important changes being implemented as part of Manifest V3, w
 
 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 [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.
+To ensure that the extensions at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/) are validated, 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 [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/), and your extension prompts users to install the host.
+*  Or, install your extension from [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.
 
@@ -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 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.
+If you have an extension both at [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.
 

microsoft-edge/extensions-chromium/index.md

@@ -13,7 +13,7 @@ ms.date: 08/20/2024
 
 A Microsoft Edge _extension_, also called an _add-on_, is a small app that developers use to add or modify features of Microsoft Edge to improve a user's browsing experience.  An extension provides a niche experience or function that is important to a target audience.  You publish a Microsoft Edge extension at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/).
 
-In articles about Microsoft Edge extensions, the word _stores_ includes [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/).
+In articles about Microsoft Edge extensions, and at Partner Center, the word _store_ includes [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/).
 
 You can create a Microsoft Edge extension if you have an idea or product that is based upon either a specific web browser, or improvements to features of specific webpages.  Examples of _companion experiences_ include ad blockers and password managers.
 
@@ -107,7 +107,7 @@ For more information on porting your Chrome extension to Microsoft Edge, see [Po
 
 
 <!-- ------------------------------ -->
-#### Publish to Microsoft Edge Add-ons
+#### Publish an extension at Microsoft Edge Add-ons
 
 You publish a Microsoft Edge extension at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/).
 
@@ -138,7 +138,7 @@ When you hover on a **Featured** badge, the tooltip reads: **This extension foll
 
 For example, the [Microsoft Editor: Spelling & Grammar Checker](https://microsoftedge.microsoft.com/addons/detail/microsoft-editor-spellin/hokifickgkhplphjiodbggjmoafhignh) extension has a **Featured** badge at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/).
 
-The Microsoft Edge Add-ons team reviews each extension for adherence to [Best practices for extensions](./developer-guide/best-practices.md) before granting the extension a **Featured** badge.  Badged extensions are curated solely for the purpose of providing Microsoft Edge users with secure browsing tools and high-quality experiences.  Developers cannot pay to receive a **Featured** badge for an extension.
+The Microsoft Edge extensions team reviews each extension for adherence to [Best practices for extensions](./developer-guide/best-practices.md) before granting the extension a **Featured** badge.  Badged extensions are curated solely for the purpose of providing Microsoft Edge users with secure browsing tools and high-quality experiences.  Developers cannot pay to receive a **Featured** badge for an extension.
 
 To help protect your browser settings, extensions that don't comply with the Best Practices for extensions are not badged.
 

microsoft-edge/extensions-chromium/publish/aad-account.md

@@ -1,6 +1,6 @@
 ---
 title: Add users to the Microsoft Edge program
-description: Adding and managing users from your organization onto the Microsoft Edge program to help manage the Partner Center account.  Enable your other team members to publish Microsoft Edge extensions to Microsoft Edge Add-ons using your Partner Center account.
+description: Adding and managing users from your organization onto the Microsoft Edge program to help manage the Partner Center account.  Enable your other team members to publish extensions at Microsoft Edge Add-ons using your Partner Center account.
 author: MSEdgeTeam
 ms.author: msedgedevrel
 ms.topic: conceptual