de-link 2nd occurrence in section

Author: mikehoffms

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

@@ -18,7 +18,7 @@ In addition to the tools available in Microsoft Edge DevTools, you can add new t
 
 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 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.
+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.
 
 
 <!-- ====================================================================== -->

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

@@ -20,7 +20,7 @@ Generally, a Microsoft Edge extension is distributed by publishing it at [Micros
 
 1. Network administrators want to distribute an extension throughout their organization.
 
-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:
+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).

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

@@ -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/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 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.
+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.
 
 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/minimize-page-load-time-impact.md

@@ -141,7 +141,11 @@ Use the following best practices when configuring where your content scripts are
 
 * Use the most specific URL patterns possible for the `matches` and `exclude_matches` properties in your extension manifest file. For example, if your content script only needs to run on webpages of the example.com domain, use `https://example.com/*` instead of "`*://*/*`.
 
-* To control whether your content script only runs in the top-level frame, or also in nested frames of the webpage that matches a URL pattern, use the `all_frames` property in your extension manifest file. By default, this property is set to `false`, which means that your content script will only run in the top-level frame. If your content script needs to access or modify the DOM in nested frames, set this property to `true`. Note that setting `all_frames` to `true` increases the amount of code that runs on a webpage.
+* To control whether your content script only runs in the top-level frame, or also in nested frames of the webpage that matches a URL pattern, use the `all_frames` property in your extension manifest file.
+
+   * By default, `all_frames` is `false`, which means that your content script will only run in the top-level frame.
+
+   * If your content script needs to access or modify the DOM in nested frames, set `all_frames` to `true`.  This increases the amount of code that runs on a webpage.
 
 
 <!-- ====================================================================== -->
@@ -181,7 +185,7 @@ _Long-running synchronous tasks_ are synchronous tasks that take a long time to
 
 Use asynchronous or non-blocking code, such as the Fetch API, JavaScript Promises, or Web Workers where possible. Asynchronous or non-blocking code allows the execution of other code while waiting for the completion of a task, without blocking the browser process that runs the webpage.
 
-Note that, although using Web Workers to move your complex code logic to another thread is a good practice, it might still slow down devices that have a low CPU core count or that are already busy.
+Although using Web Workers to move your complex code logic to another thread is a good practice, it might still slow down devices that have a low CPU core count or that are already busy.
 
 Below is an example using the Fetch API. While the data is being fetched, the browser is not blocked and can run other code:
 
@@ -223,11 +227,11 @@ chrome.runtime.sendMessage({type: 'request', data: 'some data'})
 <!-- ------------------------------ -->
 #### Run intensive tasks off the main thread
 
-Use Web Workers to run intensive tasks in your content script without blocking the thread that the browser uses to render the webpage. By using Web Workers, the code that runs the intensive tasks runs in a separate thread. Web Workers can improve the performance and responsiveness of your content script and of the webpages it runs on.
+Use Web Workers to run intensive tasks in your content script without blocking the thread that the browser uses to render the webpage.  By using Web Workers, the code that runs the intensive tasks runs in a separate thread.  Web Workers can improve the performance and responsiveness of your content script and of the webpages it runs on.
 
-Note that creating a Web Worker creates a new thread, which uses new resources on the devices. Using too many resources on low-end devices might lead to performance issues.
+Creating a Web Worker creates a new thread, which uses new resources on the devices.  Using too many resources on low-end devices might lead to performance issues.
 
-To communicate between your content script and Web Worker, use the `postMessage` and `onmessage` APIs. For example, to create a new Web Worker and send a message to it, use the following code:
+To communicate between your content script and Web Worker, use the `postMessage` and `onmessage` APIs.  For example, to create a new Web Worker and send a message to it, use the following code:
 
 ```javascript
 // Create a new Web Worker.

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

@@ -264,7 +264,7 @@ host is 1 MB, mainly to protect Microsoft Edge from misbehaving native applicati
 
 The first argument to the native messaging host is the origin of the caller, usually `chrome-extension://[ID of allowed extension]`.  This allows native messaging hosts to identify the source of the message when multiple extensions are specified in the `allowed_origins` key in the native messaging host manifest; see [Step 2: Create your native messaging host manifest file](#step-2-create-your-native-messaging-host-manifest-file), above.
 
-On Windows, the native messaging host is also passed a command line argument with a handle to the calling Microsoft Edge native window: `--parent-window=<decimal handle value>`.  This lets the native messaging host create native UI windows that are correctly parented.  Note that this value will be 0 if the calling context is a service worker.
+On Windows, the native messaging host is also passed a command line argument with a handle to the calling Microsoft Edge native window: `--parent-window=<decimal handle value>`.  This lets the native messaging host create native UI windows that are correctly parented.  This value will be 0 if the calling context is a service worker.
 
 When a messaging port is created by using [`runtime.connectNative`](https://developer.chrome.com/docs/extensions/reference/runtime/#method-connectNative), Microsoft Edge starts a native messaging host process and keeps it running until the port is destroyed.  On the other hand, when a message is sent by using [`runtime.sendNativeMessage`](https://developer.chrome.com/docs/extensions/reference/api/runtime#method-sendNativeMessage), without creating a messaging port, Microsoft Edge starts a new native messaging host process for each message.  In that case, the first message that's generated by the host process is handled as a response to the original request, and Microsoft Edge will pass it to the response callback specified when [`runtime.sendNativeMessage`](https://developer.chrome.com/docs/extensions/reference/api/runtime#method-sendNativeMessage) is called.  All other messages  generated by the native messaging host in that case are ignored.
 

microsoft-edge/extensions-chromium/developer-guide/port-chrome-extension.md

@@ -16,8 +16,7 @@ To port your Chrome extension:
 
 1. Review the Chrome extension APIs used in your extensions with the Microsoft Edge extensions [supported APIs](api-support.md) list.
 
-   > [!NOTE]
-   > If your extension uses APIs that aren't supported by Microsoft Edge, it might not port directly.
+   If your extension uses APIs that aren't supported by Microsoft Edge, it might not port directly.
 
 1. Remove the `update_url` field from the manifest file.
 

microsoft-edge/extensions-chromium/getting-started/picture-inserter-content-script.md

@@ -197,7 +197,7 @@ Instead of installing the sample from [Microsoft Edge Add-ons](https://microsoft
 
    The **Select the extension directory** dialog closes.
 
-   The extension is installed in the browser, similar to an extension that's installed from [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/):
+   The extension is installed in the browser, similar to an extension that's installed from Microsoft Edge Add-ons:
 
    ![Installed extensions page, showing a sideloaded extension](./picture-inserter-content-script-images/installed-extension.png)
 

microsoft-edge/extensions-chromium/getting-started/picture-viewer-popup-webpage.md

@@ -172,7 +172,7 @@ Instead of installing the sample from [Microsoft Edge Add-ons](https://microsoft
 
    The **Select the extension directory** dialog closes.
 
-   The extension is installed in the browser, similar to an extension that's installed from [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/):
+   The extension is installed in the browser, similar to an extension that's installed from Microsoft Edge Add-ons:
 
    ![Installed extensions page, showing a sideloaded extension](./picture-viewer-popup-webpage-images/installed-extension.png)