MicrosoftDocs · mikehoffms · Jun 16, 2026 · Jun 15, 2026 · Jun 16, 2026
diff --git a/microsoft-edge/devtools/css/index.md b/microsoft-edge/devtools/css/index.md
@@ -31,7 +31,7 @@ To learn the basics of using DevTools to view and change the CSS for a page, fol
 
 1. Open the [CSS Examples](https://microsoftedge.github.io/Demos/devtools-css-get-started/) demo page in a new window or tab. (To open a link in a new window or tab, right-click the link. Or, press and hold **Ctrl** (for Windows, Linux) or **Command** (for macOS) and then click the link.)
 
-   <!-- You can view the source files for the CSS Examples demo page at the [MicrosoftEdge/Demos > devtools-css-get-started](https://github.com/MicrosoftEdge/Demos/tree/main/devtools-css-get-started) repo folder. -->
+   <!-- You can view the source files for the CSS Examples demo page at the [MicrosoftEdge / Demos > devtools-css-get-started](https://github.com/MicrosoftEdge/Demos/tree/main/devtools-css-get-started) repo folder. -->
 
 1. Right-click the `Inspect Me!` text, and then select **Inspect**.
 

diff --git a/...-edge/devtools/css/reference-images/at-font-palette-values-at-rule-rendered.png b/...-edge/devtools/css/reference-images/at-font-palette-values-at-rule-rendered.png
diff --git a/microsoft-edge/devtools/css/reference-images/at-position-try-at-rule-rendered.png b/microsoft-edge/devtools/css/reference-images/at-position-try-at-rule-rendered.png
diff --git a/microsoft-edge/devtools/css/reference-images/at-position-try-popovertarget.png b/microsoft-edge/devtools/css/reference-images/at-position-try-popovertarget.png
diff --git a/microsoft-edge/devtools/css/reference-images/at-property-itemsize.png b/microsoft-edge/devtools/css/reference-images/at-property-itemsize.png
diff --git a/microsoft-edge/devtools/css/reference-images/at-property-tooltip.png b/microsoft-edge/devtools/css/reference-images/at-property-tooltip.png
diff --git a/microsoft-edge/devtools/css/reference-images/at-scope-at-rule-rendered.png b/microsoft-edge/devtools/css/reference-images/at-scope-at-rule-rendered.png
diff --git a/microsoft-edge/devtools/css/reference-images/cascade-layers.png b/microsoft-edge/devtools/css/reference-images/cascade-layers.png
diff --git a/microsoft-edge/devtools/css/reference-images/change-length-values.png b/microsoft-edge/devtools/css/reference-images/change-length-values.png
diff --git a/microsoft-edge/devtools/css/reference-images/copy-css-dropdown-menu.png b/microsoft-edge/devtools/css/reference-images/copy-css-dropdown-menu.png
diff --git a/microsoft-edge/devtools/css/reference-images/css-elements-computed-h1.png b/microsoft-edge/devtools/css/reference-images/css-elements-computed-h1.png
diff --git a/microsoft-edge/devtools/css/reference-images/css-elements-styles-h1-2.png b/microsoft-edge/devtools/css/reference-images/css-elements-styles-h1-2.png
diff --git a/microsoft-edge/devtools/css/reference-images/css-elements-styles-h1-highlight.png b/microsoft-edge/devtools/css/reference-images/css-elements-styles-h1-highlight.png
diff --git a/microsoft-edge/devtools/css/reference-images/css-elements-styles-h1.png b/microsoft-edge/devtools/css/reference-images/css-elements-styles-h1.png
diff --git a/...e/devtools/css/reference-images/css-elements-styles-insert-style-rule-below.png b/...e/devtools/css/reference-images/css-elements-styles-insert-style-rule-below.png
diff --git a/microsoft-edge/devtools/css/reference-images/dragging-control-point.png b/microsoft-edge/devtools/css/reference-images/dragging-control-point.png
diff --git a/microsoft-edge/devtools/css/reference-images/dragging-control-points.png b/microsoft-edge/devtools/css/reference-images/dragging-control-points.png
diff --git a/microsoft-edge/devtools/css/reference-images/easing-editor.png b/microsoft-edge/devtools/css/reference-images/easing-editor.png
diff --git a/microsoft-edge/devtools/css/reference-images/easing-function-ease-in-out.png b/microsoft-edge/devtools/css/reference-images/easing-function-ease-in-out.png
diff --git a/microsoft-edge/devtools/css/reference-images/easing-function-ease-in.png b/microsoft-edge/devtools/css/reference-images/easing-function-ease-in.png
diff --git a/microsoft-edge/devtools/css/reference-images/easing-function-ease-out.png b/microsoft-edge/devtools/css/reference-images/easing-function-ease-out.png
diff --git a/microsoft-edge/devtools/css/reference-images/easing-function-linear.png b/microsoft-edge/devtools/css/reference-images/easing-function-linear.png
diff --git a/microsoft-edge/devtools/css/reference-images/emulate-focused-page.png b/microsoft-edge/devtools/css/reference-images/emulate-focused-page.png
diff --git a/microsoft-edge/devtools/css/reference-images/insert-style-rule-below-icon.png b/microsoft-edge/devtools/css/reference-images/insert-style-rule-below-icon.png
diff --git a/microsoft-edge/devtools/css/reference-images/new-style-rule-icon.png b/microsoft-edge/devtools/css/reference-images/new-style-rule-icon.png
diff --git a/microsoft-edge/devtools/css/reference-images/position-try-rule-in-styles-tab.png b/microsoft-edge/devtools/css/reference-images/position-try-rule-in-styles-tab.png
diff --git a/microsoft-edge/devtools/css/reference-images/scope-rule-in-styles-tab.png b/microsoft-edge/devtools/css/reference-images/scope-rule-in-styles-tab.png
diff --git a/microsoft-edge/devtools/css/reference-images/the-tooltip-documentation.png b/microsoft-edge/devtools/css/reference-images/the-tooltip-documentation.png
diff --git a/microsoft-edge/devtools/css/reference-images/the-tooltip-specificity.png b/microsoft-edge/devtools/css/reference-images/the-tooltip-specificity.png
diff --git a/microsoft-edge/devtools/css/reference-images/the-value-a-custom-property.png b/microsoft-edge/devtools/css/reference-images/the-value-a-custom-property.png
diff --git a/...-edge/devtools/css/reference-images/toggle-common-rendering-emulations-icon.png b/...-edge/devtools/css/reference-images/toggle-common-rendering-emulations-icon.png
diff --git a/...osoft-edge/devtools/css/reference-images/toggle-common-rendering-emulations.png b/...osoft-edge/devtools/css/reference-images/toggle-common-rendering-emulations.png
diff --git a/microsoft-edge/devtools/css/reference-images/toggle-css-layers-view-icon.png b/microsoft-edge/devtools/css/reference-images/toggle-css-layers-view-icon.png
diff --git a/microsoft-edge/devtools/css/reference-images/various-links-highlighted.png b/microsoft-edge/devtools/css/reference-images/various-links-highlighted.png
diff --git a/microsoft-edge/devtools/css/reference-images/view-inherited-section.png b/microsoft-edge/devtools/css/reference-images/view-inherited-section.png
diff --git a/microsoft-edge/devtools/css/reference-images/view-pseudo-section.png b/microsoft-edge/devtools/css/reference-images/view-pseudo-section.png
diff --git a/microsoft-edge/devtools/css/reference-images/view-supports-rules.png b/microsoft-edge/devtools/css/reference-images/view-supports-rules.png
diff --git a/microsoft-edge/devtools/css/reference.md b/microsoft-edge/devtools/css/reference.md
diff --git a/microsoft-edge/devtools/customize/extensions.md b/microsoft-edge/devtools/customize/extensions.md
@@ -36,7 +36,7 @@ To install a Microsoft Edge extension that extends DevTools:
 
 1. Click the **Add extension** button.  A dialog indicates that the extension has been installed, and the Extensions (![Extensions icon](./extensions-images/extensions-icon.png)) button now lists the extension.
 
-1. Open a new tab or window, and then go to a page that contains content that's relevant for the DevTools extension.  For example, use the [TodoMVC React example page](https://todomvc.com/examples/react/dist/), or go to a live [Microsoft Edge Demos repo](https://github.com/MicrosoftEdge/Demos#demos) page, such as [demo-to-do](https://microsoftedge.github.io/Demos/demo-to-do/).
+1. Open a new tab or window, and then go to a page that contains content that's relevant for the DevTools extension.  For example, use the [TodoMVC React example page](https://todomvc.com/examples/react/dist/), or go to a live page in the [MicrosoftEdge / Demos](https://github.com/MicrosoftEdge/Demos) repo, such as [demo-to-do](https://microsoftedge.github.io/Demos/demo-to-do/).
 
 1. Open DevTools, such as by pressing **F12**.  In the case of this React extension, two new tabs are opened in the **Activity Bar**: **Components** and **Profiler**:
 

diff --git a/microsoft-edge/devtools/dom/index.md b/microsoft-edge/devtools/dom/index.md
@@ -40,7 +40,7 @@ When you are interested in a particular DOM node, **Inspect** is a fast way to o
 
 1. Open the [DOM Examples](https://microsoftedge.github.io/Demos/devtools-dom-get-started/) demo page in a new window or tab.  (To open a link in a new window or tab, right-click the link.  Or, press and hold **Ctrl** (Windows, Linux) or **Command** (macOS) and then click the link.)
 
-<!-- You can view the source files for the DOM Examples demo in the [MicrosoftEdge/Demos > devtools-dom-get-started](https://github.com/MicrosoftEdge/Demos/tree/main/devtools-dom-get-started) repo folder. -->
+<!-- You can view the source files for the DOM Examples demo in the [MicrosoftEdge / Demos > devtools-dom-get-started](https://github.com/MicrosoftEdge/Demos/tree/main/devtools-dom-get-started) repo folder. -->
 
 1. In the rendered webpage, under **Inspect a Node**, right-click **Michelangelo** and then select **Inspect**:
 

diff --git a/microsoft-edge/devtools/javascript/index.md b/microsoft-edge/devtools/javascript/index.md
@@ -35,7 +35,7 @@ The first step in debugging is to find a sequence of actions that consistently r
 
    Tip: Open Microsoft Edge in InPrivate Mode, to ensure that Microsoft Edge runs in a clean state. For more information, see [Browse InPrivate in Microsoft Edge](https://support.microsoft.com/microsoft-edge/browse-inprivate-in-microsoft-edge-cd2c9a48-0bc4-b98e-5e46-ac40c84e27e2)
 
-   <!-- You can view the source files for the Debugging demo at the [MicrosoftEdge/Demos > devtools-js-get-started](https://github.com/MicrosoftEdge/Demos/tree/main/devtools-js-get-started) repo folder. -->
+   <!-- You can view the source files for the Debugging demo at the [MicrosoftEdge / Demos > devtools-js-get-started](https://github.com/MicrosoftEdge/Demos/tree/main/devtools-js-get-started) repo folder. -->
 
 1. Enter **5** in the **Number 1** text box.
 

diff --git a/microsoft-edge/devtools/memory-problems/dom-leaks-memory-tool-detached-elements.md b/microsoft-edge/devtools/memory-problems/dom-leaks-memory-tool-detached-elements.md
@@ -124,7 +124,7 @@ Be sure to unmount components.  For long-running apps, small memory leaks of onl
 
 * [Tools for investigating detached elements](./index.md#tools-for-investigating-detached-elements) in _Fix memory problems_.
 * [Detached Elements demo webpage](https://microsoftedge.github.io/Demos/detached-elements/)
-   * [MicrosoftEdge/Demos > detached-elements](https://github.com/MicrosoftEdge/Demos/tree/main/detached-elements) repo folder - source code.<!-- link not in article -->
+   * [MicrosoftEdge / Demos > detached-elements](https://github.com/MicrosoftEdge/Demos/tree/main/detached-elements) repo folder - source code.<!-- link not in article -->
 
 <!-- possibly uncomment after PR https://github.com/MicrosoftDocs/edge-developer/pull/3290 is merged
 * [Detached Elements profiling type in Memory tool](../whats-new/2024/10/devtools-130.md#detached-elements-profiling-type-in-memory-tool) in _What's new in DevTools (Microsoft Edge 130)_.

diff --git a/microsoft-edge/devtools/memory-problems/heap-snapshots.md b/microsoft-edge/devtools/memory-problems/heap-snapshots.md
@@ -32,7 +32,7 @@ Use the heap profiler in the **Memory** tool to do the following:
 
 The DevTools heap profiler shows the memory distribution used by the JavaScript objects and by related DOM nodes on the rendered webpage.
 
-<!-- You can view the source files for the Heap Snapshots demo pages at the [MicrosoftEdge/Demos > devtools-memory-heap-snapshot](https://github.com/MicrosoftEdge/Demos/tree/main/devtools-memory-heap-snapshot) repo folder.
+<!-- You can view the source files for the Heap Snapshots demo pages at the [MicrosoftEdge / Demos > devtools-memory-heap-snapshot](https://github.com/MicrosoftEdge/Demos/tree/main/devtools-memory-heap-snapshot) repo folder.
 
 This article uses demo webpages sourced at https://github.com/MicrosoftEdge/Demos/tree/main/devtools-memory-heap-snapshot -
 *  [Example 3: Scattered objects](https://microsoftedge.github.io/Demos/devtools-memory-heap-snapshot/example-03.html)
@@ -313,7 +313,7 @@ At this point, the `<div id="tree">` element can be garbage-collected. Both `tre
 
 To understand where DOM nodes might leak, and how to detect such leakage, open the example webpage [Example 6: Leaking DOM nodes](https://microsoftedge.github.io/Demos/devtools-memory-heap-snapshot/example-06.html) in a new window or tab.
 
-<!-- You can view the source files for the Heap Snapshots demo pages at the [MicrosoftEdge/Demos > devtools-memory-heap-snapshot](https://github.com/MicrosoftEdge/Demos/tree/main/devtools-memory-heap-snapshot) repo folder. -->
+<!-- You can view the source files for the Heap Snapshots demo pages at the [MicrosoftEdge / Demos > devtools-memory-heap-snapshot](https://github.com/MicrosoftEdge/Demos/tree/main/devtools-memory-heap-snapshot) repo folder. -->
 
 
 <!-- ------------------------------ -->
@@ -327,7 +327,7 @@ Open the example webpage [Example 8: Recording heap allocations](https://microso
 
 To see why a DOM leak might be bigger than expected, open the example webpage [Example 9: DOM leaks bigger than expected](https://microsoftedge.github.io/Demos/devtools-memory-heap-snapshot/example-09.html) in a new window or tab.
 
-<!-- You can view the source files for the Heap Snapshots demo pages at the [MicrosoftEdge/Demos > devtools-memory-heap-snapshot](https://github.com/MicrosoftEdge/Demos/tree/main/devtools-memory-heap-snapshot) repo folder. -->
+<!-- You can view the source files for the Heap Snapshots demo pages at the [MicrosoftEdge / Demos > devtools-memory-heap-snapshot](https://github.com/MicrosoftEdge/Demos/tree/main/devtools-memory-heap-snapshot) repo folder. -->
 
 <!-- Example: Try this **demo** to play with detached DOM trees. -->
 

diff --git a/microsoft-edge/devtools/network/index.md b/microsoft-edge/devtools/network/index.md
@@ -67,7 +67,7 @@ To get the most out of this tutorial, open the demo and try out the features on
 
    ![The demo](./index-images/demo-page.png)
 
-   <!-- You can view the source files for this demo in the [MicrosoftEdge/Demos > devtools-css-get-started](https://github.com/MicrosoftEdge/Demos/tree/main/network-tutorial) repo folder: -->
+   <!-- You can view the source files for this demo in the [MicrosoftEdge / Demos > devtools-css-get-started](https://github.com/MicrosoftEdge/Demos/tree/main/network-tutorial) repo folder: -->
 
    <!--
    ![The demo in one window and this tutorial in a different window](../media/network-tutorial/windows.png)

diff --git a/microsoft-edge/devtools/performance/extension.md b/microsoft-edge/devtools/performance/extension.md
@@ -225,7 +225,7 @@ To record a profile and view the custom performance data of the Photo Gallery de
 1. Open the [Photo Gallery](https://microsoftedge.github.io/Demos/photo-gallery/) demo webpage in a new window or tab.
 
    Or, to be able to modify the sample code:
-   1. Clone the "MicrosoftEdge / Demos" repo, per [Clone the Edge Demos repo to your drive](../samples/index.md#clone-the-edge-demos-repo-to-your-drive) in _Sample code for DevTools_.
+   1. Clone the Demos repo, per [Clone the "MicrosoftEdge / Demos" repo to your drive](../samples/index.md#clone-the-microsoftedge--demos-repo-to-your-drive) in _Sample code for DevTools_.
    1. Start a localhost server in the cloned `/demos/` directory, per [Start the localhost server](../samples/index.md#start-the-localhost-server), in _Sample code for DevTools_.
    1. In the browser, go to `http://localhost:8080/photo-gallery/` or equivalent, in a new window or tab.
 

diff --git a/microsoft-edge/devtools/quick-source/quick-source-tool.md b/microsoft-edge/devtools/quick-source/quick-source-tool.md
@@ -62,7 +62,7 @@ For example, if not done already, clone the **MicrosoftEdge / Demos** repo to yo
 
 1. If not done already, install an up-to-date version of Node.js and npm from [Node.js](https://nodejs.org).
 
-1. Go to [MicrosoftEdge / Demos](https://github.com/MicrosoftEdge/Demos) in a new window or tab.
+1. Go to the [MicrosoftEdge / Demos](https://github.com/MicrosoftEdge/Demos) repo in a new window or tab.
 
 1. Click the **Code** drop-down button.
 
@@ -87,7 +87,7 @@ For example, if not done already, clone the **MicrosoftEdge / Demos** repo to yo
    ```
 
    For details about cloning a repo, see:
-   * [Clone the Edge Demos repo to your drive](../samples/index.md#clone-the-edge-demos-repo-to-your-drive) in _Sample code for DevTools_.
+   * [Clone the "MicrosoftEdge / Demos" repo to your drive](../samples/index.md#clone-the-microsoftedge--demos-repo-to-your-drive) in _Sample code for DevTools_.
    * [Clone the WebView2Samples repo](../../webview2/how-to/machine-setup.md#clone-the-webview2samples-repo) in _Set up your Dev environment for WebView2_.  Shows a different sample repo, but shows steps for several tools.
    * [Cloning a repository](https://docs.github.com/en/repositories/creating-and-managing-repositories/cloning-a-repository) - GitHub docs.