diff --git a/microsoft-edge/accessibility/build/index.md b/microsoft-edge/accessibility/build/index.md
index f2c13645de..797d2bf26d 100644
--- a/microsoft-edge/accessibility/build/index.md
+++ b/microsoft-edge/accessibility/build/index.md
@@ -21,7 +21,7 @@ Visit [HTML5Accessibility](https://html5accessibility.com) for information on wh
 <!-- ====================================================================== -->
 ## How accessibility works
 
-Assistive technologies add capabilities that computers don't usually have.  For example, a user who has low vision might use their keyboard in combination with assistive technology such as a screen reader, rather than directly using the browser with the mouse and screen.  
+Assistive technologies add capabilities that computers don't usually have.  For example, a user who has low vision might use their keyboard in combination with assistive technology such as a screen reader, rather than directly using the browser with the mouse and screen.
 
 For applications on Microsoft platforms and on the web, the assistive technology interacts with any combination of:
 * Microsoft [UI Automation](/windows/win32/winauto/uiauto-specandcommunitypromise).
diff --git a/microsoft-edge/dev-videos/index.md b/microsoft-edge/dev-videos/index.md
index 0c116fb8db..6a98c8cd64 100644
--- a/microsoft-edge/dev-videos/index.md
+++ b/microsoft-edge/dev-videos/index.md
@@ -31,7 +31,7 @@ The Microsoft Edge channel includes the following playlists:
 * [Extensions](https://www.youtube.com/playlist?list=PL4z1-7pjJU6ykO2iptfxT7T68W5WEK4ff)
 
 
-<!-- ====================================================================== 
+<!-- ======================================================================
 ## What's new in DevTools 115-125
 
 Date
@@ -39,7 +39,7 @@ Date
 [![Thumbnail image for video "What's new in DevTools 115-125"](./index-images/devtools-whatsnew-115-125.png)](url)
 
 Covers:
-* 
+*
 
 See also:
 * [What's new in DevTools (Microsoft Edge 125)](../devtools/whats-new/2024/05/devtools-125.md)
@@ -577,7 +577,9 @@ Mar. 17, 2022
 
 Microsoft Edge provides auto-generated alt text for images that don't include it. Auto-generated alt text helps users of assistive technology such as screen readers discover the meaning or intent of an images on the web.
 
-Many people who are blind or low-vision experience the web primarily through a screen reader: an assistive technology that reads the content of each page aloud.  Screen readers depend on having image labels (alternative text or "alt text") provided that allows them to describe visual content - like images and charts - so the user can understand the full content of the page.  Alt text is critical for making the web accessible, yet it's often overlooked.  More than half of the images processed by screen readers are missing alt text. 
+Many people who are blind or low-vision experience the web primarily through a screen reader: an assistive technology that reads the content of each page aloud.  Screen readers depend on having image labels (alternative text or "alt text") provided that allows them to describe visual content - like images and charts - so the user can understand the full content of the page.
+
+Alt text is critical for making the web accessible, yet it's often overlooked.  More than half of the images processed by screen readers are missing alt text.
 
 See also:
 * [Appears to say: Microsoft Edge now provides auto-generated image labels](https://blogs.windows.com/msedgedev/2022/03/17/appears-to-say-microsoft-edge-auto-generated-image-labels/) - blog post
@@ -782,7 +784,7 @@ Sep. 22, 2020
 
 [![Thumbnail image for video "The latest in developer tooling"](./index-images/latest-developer-tooling.png)](https://www.youtube.com/watch?v=BHeF7GV6nUM)
 
-Microsoft Edge developer tools help make web development, testing, and automation easier.  Learn how we prioritize accessibility in our tooling and applications, and how we help to empower others to do the same. 
+Microsoft Edge developer tools help make web development, testing, and automation easier.  Learn how we prioritize accessibility in our tooling and applications, and how we help to empower others to do the same.
 
 Covers:
 * DevTools extension for VS Code.
diff --git a/microsoft-edge/develop-web-microsoft-edge.md b/microsoft-edge/develop-web-microsoft-edge.md
index 4a03a767ee..5e4cfebce1 100644
--- a/microsoft-edge/develop-web-microsoft-edge.md
+++ b/microsoft-edge/develop-web-microsoft-edge.md
@@ -63,7 +63,7 @@ See [Overview of DevTools](./devtools/overview.md).
 
 <!-- ====================================================================== -->
 ## Microsoft Edge extensions
-   
+
 Create an extension for Microsoft Edge, to add to or modify the browser's features.  Extensions improve the browser experience, to provide a specialized function that's important to a target audience.
 
 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.
diff --git a/microsoft-edge/developer/index.yml b/microsoft-edge/developer/index.yml
index 13f7eafe12..44049f7978 100644
--- a/microsoft-edge/developer/index.yml
+++ b/microsoft-edge/developer/index.yml
@@ -12,7 +12,7 @@ metadata:
   author: MSEdgeTeam #Required; your GitHub user alias, with correct capitalization.
   ms.author: msedgedevrel #Required; microsoft alias of author; optional team alias.
   ms.date: 02/15/2024 #Required; mm/dd/yyyy format.
-  
+
 # How to create or update a landing page
 # https://review.learn.microsoft.com/help/contribute/contribute-how-to-write-landing-page?branch=main
 
diff --git a/microsoft-edge/devtools/about-tools.md b/microsoft-edge/devtools/about-tools.md
index 6c262aa9bc..265e9e640e 100644
--- a/microsoft-edge/devtools/about-tools.md
+++ b/microsoft-edge/devtools/about-tools.md
@@ -155,5 +155,5 @@ To restore all of the default tool tabs in the **Activity Bar** and **Quick View
 
 <!-- ====================================================================== -->
 ## See also
- 
+
 * [Overview of DevTools](overview.md) - Similar to the present article, but broader coverage, with a top-level introduction to DevTools.
diff --git a/microsoft-edge/devtools/accessibility/color-picker.md b/microsoft-edge/devtools/accessibility/color-picker.md
index d9b7e56f43..a8136df953 100644
--- a/microsoft-edge/devtools/accessibility/color-picker.md
+++ b/microsoft-edge/devtools/accessibility/color-picker.md
@@ -47,7 +47,7 @@ In DevTools, one way to view the contrast ratio of a text element is to use the
    ![The 'Contrast Ratio' section of the Color Picker shows two check marks and a value of 13.97](./color-picker-images/accessibility-elements-styles-paragraph-highlight-color-picker.png)
 
    The **Contrast ratio** section shows a score for the contrast ratio between the text and the background and an icon that indicates whether the contrast ratio meets recommendations:
-   
+
    * A red crossed-out circle means that the element doesn't meet the [minimum recommendation](https://www.w3.org/WAI/WCAG21/quickref/#contrast-minimum).
    * One check mark means that the element meets the minimum recommendation.
    * Two check marks means that the element meets the [enhanced recommendation](https://www.w3.org/WAI/WCAG21/quickref/#contrast-enhanced).
diff --git a/microsoft-edge/devtools/accessibility/emulate-vision-deficiencies.md b/microsoft-edge/devtools/accessibility/emulate-vision-deficiencies.md
index 539eb5db69..81839b5c78 100644
--- a/microsoft-edge/devtools/accessibility/emulate-vision-deficiencies.md
+++ b/microsoft-edge/devtools/accessibility/emulate-vision-deficiencies.md
@@ -13,7 +13,7 @@ ms.date: 12/04/2023
 To better meet the needs of users with [color vision deficiency](https://www.colourblindawareness.org) (color blindness) or blurred vision, Microsoft Edge DevTools allows you to simulate blurred vision and specific color vision deficiencies.  The **Emulate vision deficiencies** tool simulates the following categories:
 
 | Color vision deficiency | Details |
-|:--- |:--- |
+|---|---|
 | Blurred vision | The user has difficulty focusing on fine details. |
 | Protanopia | The user is unable to perceive any red light. |
 | Deuteranopia | The user is unable to perceive any green light. |
diff --git a/microsoft-edge/devtools/accessibility/focus.md b/microsoft-edge/devtools/accessibility/focus.md
index 537a7714e9..2673f2d8f0 100644
--- a/microsoft-edge/devtools/accessibility/focus.md
+++ b/microsoft-edge/devtools/accessibility/focus.md
@@ -1,7 +1,7 @@
 ---
 title: Track which element has focus
 description: Open the Console, create a Live Expression, and set the expression to document.activeElement.
-author: MSEdgeTeam 
+author: MSEdgeTeam
 ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
@@ -78,7 +78,7 @@ The result of the `document.activeElement` Live Expression is only a preview of
 
    ![The focused element, highlighted in the rendered webpage](./focus-images/highlighted-focused-element.png)
 
-1. Right-click the result of the Live Expression, and then select **Reveal in Elements panel**. 
+1. Right-click the result of the Live Expression, and then select **Reveal in Elements panel**.
 
    In the **Elements** tool, the DOM tree automatically expands and selects the DOM node that's currently focused:
 
diff --git a/microsoft-edge/devtools/accessibility/preferred-color-scheme-simulation.md b/microsoft-edge/devtools/accessibility/preferred-color-scheme-simulation.md
index d261e579c2..d7dab05f8a 100644
--- a/microsoft-edge/devtools/accessibility/preferred-color-scheme-simulation.md
+++ b/microsoft-edge/devtools/accessibility/preferred-color-scheme-simulation.md
@@ -14,7 +14,7 @@ Use the **Rendering** tool to see what your webpage looks like with different di
 
 Many operating systems have a way to display any application in darker or lighter colors.  Having a website that has a light scheme in a dark-mode operating system can be hard to read and can be an accessibility issue for some users.
 
-To test how a webpage will render when the user has selected dark or light mode, instead of changing your own machine's dark-mode or light-mode setting, you can select **Emulate CSS prefers-color-scheme: dark** or **light** in Microsoft Edge DevTools.  Or, you can make your webpage automatically select dark or light mode based on your own preferred settings on your machine, by selecting **No emulation**, which is the default. 
+To test how a webpage will render when the user has selected dark or light mode, instead of changing your own machine's dark-mode or light-mode setting, you can select **Emulate CSS prefers-color-scheme: dark** or **light** in Microsoft Edge DevTools.  Or, you can make your webpage automatically select dark or light mode based on your own preferred settings on your machine, by selecting **No emulation**, which is the default.
 
 You can select these settings from the **Rendering** tool or from the **Command Menu**, as described below.
 
diff --git a/microsoft-edge/devtools/accessibility/test-analyze-no-keyboard-support.md b/microsoft-edge/devtools/accessibility/test-analyze-no-keyboard-support.md
index 13d1c5d02d..b24bf5c177 100644
--- a/microsoft-edge/devtools/accessibility/test-analyze-no-keyboard-support.md
+++ b/microsoft-edge/devtools/accessibility/test-analyze-no-keyboard-support.md
@@ -93,7 +93,7 @@ The form's functionality is created by using JavaScript, and you can test this b
       }
     })
     ```
-    
+
 Using a `click` event listener to run code when a button is used is a good practice, because a `click` event fires both on mouse pointer and keyboard interaction.  However, the **Donate** button is implemented by using a `<div>` HTML element, which can't be focused with the keyboard.  The `click` event only runs when you use a mouse or another source of a `click` event, such as a special button that's available on some keyboards.
 
 This is a classic example where JavaScript was added to recreate the functionality that `<button>` elements provide natively.  Simulating the functionality of buttons by using `<div>` elements ended up producing an inaccessible experience.
diff --git a/microsoft-edge/devtools/accessibility/test-issues-tool.md b/microsoft-edge/devtools/accessibility/test-issues-tool.md
index 69e767bdc9..f6e8f4d030 100644
--- a/microsoft-edge/devtools/accessibility/test-issues-tool.md
+++ b/microsoft-edge/devtools/accessibility/test-issues-tool.md
@@ -59,9 +59,9 @@ To check whether input fields have labels connected to them, use the **Issues**
 1. Click the **Open in Elements** link.
 
    ![Elements tool showing the problematic HTML after clicking the link in the Issues tool](./test-issues-tool-images/a11y-testing-inspect-problematic-element.png)
-    
+
    The **Elements** tool opens, with the element highlighted in the DOM tree.  The **Styles** pane displays the applied CSS rules for the element.
-  
+
    The following code is now displayed:
 
    ```html
diff --git a/microsoft-edge/devtools/changes/changes-tool.md b/microsoft-edge/devtools/changes/changes-tool.md
index 8c8f62e4d2..783ee1439c 100644
--- a/microsoft-edge/devtools/changes/changes-tool.md
+++ b/microsoft-edge/devtools/changes/changes-tool.md
@@ -42,7 +42,7 @@ To open the **Changes** tool using the **Command Menu**:
    ![The Show Changes command in the Command Menu](changes-tool-images/changes-tool-command-menu.png)
 
 1. Press **Enter**.  The **Changes** tool opens in the **Quick View** panel:
-   
+
    ![The Changes tool in the Quick View panel](changes-tool-images/changes-tool-in-quick-view.png)
 
 See also:
@@ -98,7 +98,7 @@ If green circles stop appearing on files in DevTools, such as in the **Workspace
 
 * With DevTools displayed, long-click or right-click the **Refresh** button in Microsoft Edge, and then select **Empty cache and hard refresh**.
 
-<!-- 
+<!--
 * In DevTools, select **Customize and Control DevTools** (**...**) > **Restore defaults and refresh**. -->
 
 
diff --git a/microsoft-edge/devtools/console/console-debug-javascript.md b/microsoft-edge/devtools/console/console-debug-javascript.md
index 807df869d0..9d4d676477 100644
--- a/microsoft-edge/devtools/console/console-debug-javascript.md
+++ b/microsoft-edge/devtools/console/console-debug-javascript.md
@@ -144,7 +144,7 @@ Use defensive coding techniques to avoid the previous user experiences.  Make su
       return response;
    };
    ```
-   
+
 
 <!-- ====================================================================== -->
 ## Create errors and traces in the Console
@@ -184,7 +184,7 @@ To display two created error messages in the **Console**:
     first('Console');
     first('Microsoft Edge Canary');
     ```
-    
+
    There are three functions that request each other in succession:
 
    *  `first()`
@@ -237,7 +237,7 @@ To display the trace in the **Console**:
    here();
    there();
    ```
-    
+
    The result is a trace to display that `here()` is named `there()` and then `everywhere()`, and in the second example to display that it's named `everywhere()`.
 
    Here's the trace that's produced, in the **Console**:
diff --git a/microsoft-edge/devtools/console/console-dom-interaction.md b/microsoft-edge/devtools/console/console-dom-interaction.md
index 2f2e128ec3..68d4a62347 100644
--- a/microsoft-edge/devtools/console/console-dom-interaction.md
+++ b/microsoft-edge/devtools/console/console-dom-interaction.md
@@ -132,7 +132,7 @@ In this example, you use the `$$()` utility function to list all links on the we
    ```javascript
    $$('a');
    ```
-   
+
    ![The result of the $$('a') function in the Console, which is an array of <a> elements](./console-dom-interaction-images/list-of-links.png)
 
    `$$('a')` is short for `document.querySelectorAll('a')`.
@@ -205,7 +205,7 @@ In this example, you get all the headings on the webpage that have an `id` attri
    });
    console.log(headings.join("\n"));
    ```
-   
+
    The result is text that contains content for each section heading, followed by the full URL for the section heading:
 
    ![The Console tool, showing the list of all headings on the page, along with their URLs](./console-dom-interaction-images/heading-links.png)
@@ -335,7 +335,7 @@ unmonitorEvents(document.querySelector('img'));
 unmonitorEvents(document.querySelector('img'), ['mousedown', 'mouseup', 'click']);
 unmonitorEvents(window, ['resize', 'scroll']);
 ```
-   
+
 
 <!-- ====================================================================== -->
 ## Save DOM interaction scripts as snippets
diff --git a/microsoft-edge/devtools/console/console-filters.md b/microsoft-edge/devtools/console/console-filters.md
index dc8a179a2c..83949caec3 100644
--- a/microsoft-edge/devtools/console/console-filters.md
+++ b/microsoft-edge/devtools/console/console-filters.md
@@ -12,7 +12,7 @@ ms.date: 04/13/2021
 
 Use the filter options of the DevTools **Console** to reduce the noise from excessive console log messages, to better see the type of log messages that you're looking for.
 
-When you go to various webpages, you may find that the **Console** is flooded with all kinds of information.  Often the information isn't relevant to you, such as information about the page that another developer logged.  Or you might see logged information about violations and warnings about the performance of the current site, that you aren't able to change.  
+When you go to various webpages, you may find that the **Console** is flooded with all kinds of information.  Often the information isn't relevant to you, such as information about the page that another developer logged.  Or you might see logged information about violations and warnings about the performance of the current site, that you aren't able to change.
 
 You can filter console log messages in various ways:
 *  Filter by log level.
diff --git a/microsoft-edge/devtools/console/console-javascript.md b/microsoft-edge/devtools/console/console-javascript.md
index adcee1e8b1..66e25d9ea7 100644
--- a/microsoft-edge/devtools/console/console-javascript.md
+++ b/microsoft-edge/devtools/console/console-javascript.md
@@ -61,7 +61,7 @@ To try autocompletion while writing multi-part expressions:
 <!-- ====================================================================== -->
 ## Console history
 
-As with many other command-line environments, a history of the commands that you entered is available for reuse.  Press **Up Arrow** to display the commands that you entered previously.  
+As with many other command-line environments, a history of the commands that you entered is available for reuse.  Press **Up Arrow** to display the commands that you entered previously.
 
 Similarly, autocompletion keeps a history of the commands you previously typed.  You can type the first few letters of earlier commands, and your previous choices appear in a text box.
 
@@ -164,7 +164,7 @@ To get the last 50 issues that were filed on the [Microsoft Edge Developer Tools
    'https://api.github.com/repos/microsoft/vscode-edge-devtools/issues?state=all&per_page=50&page=1'
    )).json())
    ```
-   
+
 The **Console** is a great way to practice JavaScript and to do some quick calculations.  The real power is the fact that you have access to the [window](https://developer.mozilla.org/docs/Web/API/Window) object.  See [Interact with the DOM using the Console](console-dom-interaction.md).
 
 
diff --git a/microsoft-edge/devtools/console/console-log.md b/microsoft-edge/devtools/console/console-log.md
index 972e93d5b6..d26799591d 100644
--- a/microsoft-edge/devtools/console/console-log.md
+++ b/microsoft-edge/devtools/console/console-log.md
@@ -34,13 +34,13 @@ The `console` object has methods to log various levels of messages:
 console.log('This is a log message')
 
 // prints the text to the console as an informational message
-console.info('This is some information') 
+console.info('This is some information')
 
 // prints the text to the console as an error message
 console.error('This is an error')
 
 // prints the text to the console as a warning
-console.warn('This is a warning') 
+console.warn('This is a warning')
 ```
 
 
@@ -60,7 +60,7 @@ To try using the logging functions in the **Console**:
    ![The Console shows the messages from different log APIs](./console-log-images/console-log-examples.png)
 
    The `log()` and `info()` methods seem to do the same thing.  Use `info()` and `log()` for different log tasks, because that allows you to [filter Console messages](console-filters.md), to display only a subset of log entries.
-  
+
    The `error()` and `warn()` methods display an icon next to the message and a way to inspect the [stack trace](https://wikipedia.org/wiki/Stack_trace) of the message.
 
 1. Copy and paste any of the examples into the **Console**, and then press **Enter**.
@@ -84,9 +84,9 @@ let x = 2;
 console.log(x);
 
 // logs the name x and value of x
-console.log({x})   
+console.log({x})
 
-// logs a DOM reference  
+// logs a DOM reference
 console.log(document.querySelector('body'));
 
 // logs an Object
@@ -151,16 +151,16 @@ Use format specifiers to log certain values in different formats, and to convert
 console.log('%ix %s developer', 10, 'console');
 
 // logs PI => 3.141592653589793
-console.log(Math.PI); 
+console.log(Math.PI);
 
 // logs PI as an integer = 3
-console.log('%i', Math.PI); 
+console.log('%i', Math.PI);
 
 // logs the document body as a DOM node
-console.log('%o', document.body); 
+console.log('%o', document.body);
 
 // logs the body of the document as a JavaScript object with all properties
-console.log('%O', document.body); 
+console.log('%O', document.body);
 
 // shows the message as red and big
 console.log('%cImportant message follows','color:red;font-size:40px')
@@ -183,7 +183,7 @@ console.log('%cImportant message follows','color:red;font-size:40px')
    ```javascript
    console.log('%ix %s developer', 10, 'console'); // logs "10x console developer"
    ```
-   
+
 1. Click the expander triangles in the output results, to expand the data that's output by the above `log` statements that are in the webpage.
 
 1. If necessary, press **F5** to reload the page and re-populate the **Console** output.
diff --git a/microsoft-edge/devtools/console/index.md b/microsoft-edge/devtools/console/index.md
index 0b7b4645bd..808b1a3599 100644
--- a/microsoft-edge/devtools/console/index.md
+++ b/microsoft-edge/devtools/console/index.md
@@ -81,7 +81,7 @@ The most popular use case for the **Console** is logging information from your s
 console.log('This is a log message');
 
 // prints the text to the console as an informational message
-console.info('This is some information'); 
+console.info('This is some information');
 
 // prints the text to the console as an error message
 console.error('This is an error');
@@ -219,7 +219,7 @@ To change the rendered webpage:
 
 
 <!-- ------------------------------ -->
-#### Using the $$ Console utility method to 
+#### Using the $$ Console utility method
 
 The **Console Utility** methods make it easy to access and manipulate the current webpage.
 
diff --git a/microsoft-edge/devtools/console/live-expressions.md b/microsoft-edge/devtools/console/live-expressions.md
index a35f4de0dc..5ebaca6072 100644
--- a/microsoft-edge/devtools/console/live-expressions.md
+++ b/microsoft-edge/devtools/console/live-expressions.md
@@ -117,7 +117,7 @@ To use Live Expressions to avoid excessive Console log messages:
 1. Press **Ctrl+Shift+J** (Windows, Linux) or **Command+Option+J** (macOS).  The **Console** tool opens in DevTools, next to the demo webpage.
 
 1. Move your mouse around.
-   
+
    The values of the `x` and `y` variables are updated, but no log messages are displayed.
 
 1. In the **Console** tool, click the **Create live expression** (![The 'Create live expression' icon](./live-expressions-images/live-expression-icon.png)) icon next to the **Filter** text box, and then enter the JavaScript expression `x`.
diff --git a/microsoft-edge/devtools/console/reference.md b/microsoft-edge/devtools/console/reference.md
index 04414ac8a1..22881380a5 100644
--- a/microsoft-edge/devtools/console/reference.md
+++ b/microsoft-edge/devtools/console/reference.md
@@ -326,7 +326,7 @@ For more information, see [Monitor changes in JavaScript using Live Expressions]
 
 By default, the **Console** tool displays a preview of the value of an expression, as you type the JavaScript expression in the **Console**.
 
-To turn off the live preview as you type: 
+To turn off the live preview as you type:
 
 1. Click the **Console Settings** (![Console Settings icon](./reference-images/settings-button-icon.png)) button.
 
diff --git a/microsoft-edge/devtools/console/utilities.md b/microsoft-edge/devtools/console/utilities.md
index f0f7ce3570..deaaeb33a4 100644
--- a/microsoft-edge/devtools/console/utilities.md
+++ b/microsoft-edge/devtools/console/utilities.md
@@ -604,7 +604,7 @@ To monitor multiple events:
 You can also specify a collection of events by using one of the predefined sets of events.  The following table shows the available event types and the associated event mappings:
 
 | Event type | Corresponding mapped events |
-|:--- |:--- |
+|---|---|
 | `mouse` | "click", "dblclick", "mousedown", "mousemove", "mouseout", "mouseover", "mouseup", "mousewheel" |
 | `key` | "keydown", "keypress", "keyup", "textInput" |
 | `touch` | "touchcancel", "touchend", "touchmove", "touchstart" |
diff --git a/microsoft-edge/devtools/css/css-overview-tool.md b/microsoft-edge/devtools/css/css-overview-tool.md
index 70d3c6d3c6..f10bd1cad0 100644
--- a/microsoft-edge/devtools/css/css-overview-tool.md
+++ b/microsoft-edge/devtools/css/css-overview-tool.md
@@ -190,7 +190,7 @@ To find color contrast issues:
    ![Microsoft Edge, with the TODO list demo app and DevTools, showing a list of elements with a color contrast issue](./css-overview-tool-images/css-overview-tool-contrast-issues-elements.png)
 
 1. To open the corresponding element in the **Elements** tool, click an element in the list.
-  
+
    ![Microsoft Edge, with the TODO list demo app and DevTools, showing the Elements tool, with the color-contrast issue element selected](./css-overview-tool-images/css-overview-tool-contrast-issues-elements-tool.png)
 
 To help fix contrast issues, check out the [Text contrast](../accessibility/reference.md#text-contrast) section of the accessibility-testing DevTools features.
diff --git a/microsoft-edge/devtools/css/grid.md b/microsoft-edge/devtools/css/grid.md
index 2a04885cf0..428450cc60 100644
--- a/microsoft-edge/devtools/css/grid.md
+++ b/microsoft-edge/devtools/css/grid.md
@@ -224,7 +224,7 @@ To show line names in the grid overlay:
 
 See also:
 * [Layout using named grid lines](https://developer.mozilla.org/docs/Web/CSS/CSS_Grid_Layout/Layout_using_Named_Grid_Lines) at MDN.
-   
+
 
 <!-- ------------------------------ -->
 #### Show track sizes
@@ -245,7 +245,7 @@ To show track sizes in the grid overlay:
 Each line label shows the `authored size` (if defined in the CSS) and the `computed size`:
 
 | Size | Details |
-|:--- |:--- |
+|---|---|
 | `authored size` | The size defined in the CSS stylesheet.  Omitted from the label, if not defined. |
 | `computed size` | The actual size on screen. |
 
@@ -270,7 +270,7 @@ In the demo, the column sizes are defined as follows, in the CSS property `grid-
 The following track-size line labels are displayed on the grid columns, for the demo's element `<div class="snack-box">`:
 
 | Track size | Authored size | Computed size |
-|:--- |:--- |:--- |
+|---|---|---|
 | **1fr** &#x2022; **96.66px** | 1fr | 96.66px |
 | **2fr** &#x2022; **193.34px** | 2fr | 193.34px |
 
@@ -283,7 +283,7 @@ The line label on each grid column displays the `authored size` in addition to t
 The following track-size line labels are displayed on the grid rows, for the demo's element `<div class="snack-box">`:
 
 | Track size | Authored size | Computed size |
-|:--- |:--- |:--- |
+|---|---|---|
 | **80px** | n/a | 80px |
 | **80px** | n/a | 80px |
 
diff --git a/microsoft-edge/devtools/css/index.md b/microsoft-edge/devtools/css/index.md
index de9ea8e3f1..e191e32b4c 100644
--- a/microsoft-edge/devtools/css/index.md
+++ b/microsoft-edge/devtools/css/index.md
@@ -172,7 +172,7 @@ To debug or test the media queries that you defined in your CSS:
    ![Showing media queries in the Device Toolbar](./index-images/media-queries-showing-mq.png)
 
    The colored bars above the webpage represent the different media queries.
-       
+
 1. Hover over the boundaries in the bars to display the values of the different media queries.  Click each media query value to resize the webpage to match.
 
    ![Selecting a media query from the preview bar](./index-images/media-queries-select-bar.png)
diff --git a/microsoft-edge/devtools/css/print-preview.md b/microsoft-edge/devtools/css/print-preview.md
index ca649ba630..4a2c163c60 100644
--- a/microsoft-edge/devtools/css/print-preview.md
+++ b/microsoft-edge/devtools/css/print-preview.md
@@ -41,9 +41,9 @@ To force a page into print preview mode:
    <!-- the Command Menu way:
    1. In DevTools, open the **Command Menu**. To open the **Command Menu**, press **Ctrl+Shift+P** (Windows, Linux) or **Command+Shift+P** (macOS).
    1. Start typing **rendering**, select **Show Rendering**, and then press **Enter**. -->
-    
+
    The **Rendering** tool opens in the **Quick View** panel:
-   
+
    ![The Rendering tool, in the Quick View panel](./print-preview-images/rendering-tool.png)
 
 1. Scroll down to the **Emulate CSS media type** section, and then in the dropdown list, select **print** rather than **No emulation**:
diff --git a/microsoft-edge/devtools/css/reference.md b/microsoft-edge/devtools/css/reference.md
index bc2b5cdab9..f1ed05bac5 100644
--- a/microsoft-edge/devtools/css/reference.md
+++ b/microsoft-edge/devtools/css/reference.md
@@ -1264,7 +1264,7 @@ To adjust timings by a simple mouse-click, use the presets in the **Easing Edito
    | ease-out | Out, Cubic | `cubic-bezier(0.22, 0.61, 0.36, 1)` |
    | ease-out | Linear Out, Slow In | `cubic-bezier(0, 0, 0.2, 1)` |
    | ease-out | Out, Back | `cubic-bezier(0.18, 0.89, 0.32, 1.28)` |
-   
+
 See also:
 * [Bézier curve](https://developer.mozilla.org/docs/Glossary/Bezier_curve) at MDN.
 
diff --git a/microsoft-edge/devtools/device-mode/index.md b/microsoft-edge/devtools/device-mode/index.md
index 3041bb0cb0..c72ce9122d 100644
--- a/microsoft-edge/devtools/device-mode/index.md
+++ b/microsoft-edge/devtools/device-mode/index.md
@@ -170,7 +170,7 @@ If the **Device Type** list isn't displayed, select **More options** > **Add dev
 The **Device Type** list contains the following device types:
 
 | Device type | Rendering method | Cursor icon | Events triggered |
-|:--- |:--- |:--- |:--- |
+|---|---|---|---|
 | **Mobile** | Mobile | Circle | `touch` |
 | **Mobile (no touch)** | Mobile | Normal | `click` |
 | **Desktop** | Desktop | Normal | `click` |
@@ -250,7 +250,7 @@ The device frame for the iPhone 6/7/8:
 #### Add a custom mobile device
 <!-- https://developer.chrome.com/docs/devtools/device-mode/#custom -->
 
-If the mobile device option that you need isn't included on the default list, you can add a custom device.  
+If the mobile device option that you need isn't included on the default list, you can add a custom device.
 
 To add a custom device:
 
diff --git a/microsoft-edge/devtools/device-mode/override-user-agent.md b/microsoft-edge/devtools/device-mode/override-user-agent.md
index d7e25a2944..51decc8e54 100644
--- a/microsoft-edge/devtools/device-mode/override-user-agent.md
+++ b/microsoft-edge/devtools/device-mode/override-user-agent.md
@@ -28,7 +28,7 @@ To override the [user agent](https://developer.mozilla.org/docs/Glossary/User_ag
 1. Press **Ctrl+Shift+P** (Windows, Linux) or **Command+Shift+P** (macOS) to open the **Command Menu**.
 
    ![The Command Menu](./override-user-agent-images/device-mode-console-command-menu.png)
-    
+
 1. Type `network conditions`, select **Show Network conditions**, and then press **Enter** to open the **Network conditions** tool.
 
    ![Network Conditions from Command Menu](./override-user-agent-images/device-mode-console-command-menu-network-conditions.png)
diff --git a/microsoft-edge/devtools/dom/index.md b/microsoft-edge/devtools/dom/index.md
index ebe2279e7a..5f9dc6c38e 100644
--- a/microsoft-edge/devtools/dom/index.md
+++ b/microsoft-edge/devtools/dom/index.md
@@ -34,6 +34,7 @@ To understand the difference between the DOM and HTML, see [Appendix: HTML versu
 The DOM Tree of the **Elements** tool is where you do all DOM-related activities in DevTools.
 
 
+<!-- ------------------------------ -->
 #### Inspect a node
 
 When you are interested in a particular DOM node, **Inspect** is a fast way to open DevTools and investigate that node.
@@ -59,6 +60,7 @@ When you are interested in a particular DOM node, **Inspect** is a fast way to o
 Inspecting a node is also the first step towards viewing and changing the styles of a node.  See [Get started viewing and changing CSS](../css/index.md).
 
 
+<!-- ------------------------------ -->
 #### Navigate the DOM Tree with a keyboard
 
 Once you have selected a node in the DOM Tree, you can navigate the DOM Tree with your keyboard.
@@ -84,6 +86,7 @@ Once you have selected a node in the DOM Tree, you can navigate the DOM Tree wit
 1. Press the **Right Arrow** key.  The list expands.
 
 
+<!-- ------------------------------ -->
 #### Scroll into view
 
 When viewing the DOM Tree, you may find yourself interested in a DOM node that isn't currently visible in the rendered webpage.  For example, suppose that you scrolled to the bottom of the page, and you're interested in the `<h1>` node at the top of the page.  **Scroll into view** lets you quickly reposition the viewport so that you can see the node.
@@ -99,10 +102,11 @@ When viewing the DOM Tree, you may find yourself interested in a DOM node that i
 1. Right-click the `<p>Magritte</p>` node, and then select **Scroll into view**:
 
    ![Scroll into view](./index-images/scroll-into-view-dropdown.png)
-   
+
    Your viewport scrolls back up to display the **Magritte** node.  See [Appendix: Missing options](#appendix-missing-options) if the **Scroll into view** option isn't displayed.
 
 
+<!-- ------------------------------ -->
 #### Search for nodes
 
 You can search the DOM Tree by string, CSS selector, or XPath selector.
@@ -123,6 +127,8 @@ The Search bar also supports CSS and XPath selectors.
 
 You can edit the DOM in DevTools and view how the changes affect the page in real time.
 
+
+<!-- ------------------------------ -->
 #### Edit text content
 
 To edit the text content of a node, double-click the content in the DOM Tree, as follows:
@@ -137,6 +143,8 @@ To edit the text content of a node, double-click the content in the DOM Tree, as
 
 1. Delete `Michelle`, type `Leela`, then press **Enter** to confirm the change.  The text in the DOM changes from **Michelle** to **Leela**.
 
+
+<!-- ------------------------------ -->
 #### Edit or add attributes
 
 To edit an existing attribute, double-click the attribute name or value.
@@ -155,6 +163,8 @@ To add a new attribute, double-click the element for which to add an attribute,
 
    ![Add a style attribute to the node](./index-images/edit-attributes-inline-css.png)
 
+
+<!-- ------------------------------ -->
 #### Edit node tag name
 
 To edit the tag name of a node, double-click the tag name and then type in the new tag name.
@@ -169,7 +179,9 @@ To edit the tag name of a node, double-click the tag name and then type in the n
 
    ![Change the node type to button](./index-images/edit-node-type-button.png)
 
-#### Edit multiple nodes, text, and attributes 
+
+<!-- ------------------------------ -->
+#### Edit multiple nodes, text, and attributes
 
 To change the tag name, text content, or attributes of multiple nodes at once, you can edit part of the DOM by using the DOM tree's HTML text editor, as follows:
 
@@ -193,6 +205,8 @@ To change the tag name, text content, or attributes of multiple nodes at once, y
 
    ![The new DOM tree, with the an extra <p> node, after the HTML editor closed](./index-images/edit-html-editor-closed.png)
 
+
+<!-- ------------------------------ -->
 #### Reorder DOM nodes
 
 To reorder nodes in the DOM tree, drag the nodes, as follows:
@@ -205,6 +219,8 @@ To reorder nodes in the DOM tree, drag the nodes, as follows:
 
    ![Drag the node to the top of the list](./index-images/reorder-dom-nodes.png)
 
+
+<!-- ------------------------------ -->
 #### Force state
 
 You can force nodes to remain in states including `:active`, `:hover`, `:focus`, `:visited`, and `:focus-within`, as follows:
@@ -217,6 +233,8 @@ You can force nodes to remain in states including `:active`, `:hover`, `:focus`,
 
 1. Right-click `<p class="demo--hover">The Lord of the Flies</p>`, and then select **Force State** > **:hover**.  If that option isn't displayed, see [Appendix: Missing options](#appendix-missing-options), below.  The background color remains orange, even though you aren't actually hovering over the node.
 
+
+<!-- ------------------------------ -->
 #### Hide a node
 
 Press `H` to hide a node, as follows:
@@ -231,6 +249,8 @@ Press `H` to hide a node, as follows:
 
 1. Press the **H** key again.  The node is shown again.
 
+
+<!-- ------------------------------ -->
 #### Delete a node
 
 Press **Delete** to delete a node, as follows:
@@ -249,6 +269,8 @@ Press **Delete** to delete a node, as follows:
 
 DevTools provides a few shortcuts for accessing DOM nodes from the **Console** tool, or getting JavaScript references to each one.
 
+
+<!-- ------------------------------ -->
 #### Reference the currently-selected node with $0
 
 When you inspect a node, the `== $0` text next to the node means that you can reference this node in the Console with the variable `$0`.
@@ -269,6 +291,8 @@ When you inspect a node, the `== $0` text next to the node means that you can re
 
    ![The result of the second $0 expression in the Console](./index-images/reference-currently-selected-node-console-2.png)
 
+
+<!-- ------------------------------ -->
 #### Store as global variable
 
 If you need to refer back to a node many times, store it as a global variable.
@@ -283,6 +307,8 @@ If you need to refer back to a node many times, store it as a global variable.
 
    ![The result of the temp1 expression](./index-images/store-global-variable-console-temp1.png)
 
+
+<!-- ------------------------------ -->
 #### Copy JS path
 
 Copy the JavaScript path to a node when you need to reference it in an automated test.
@@ -305,6 +331,8 @@ Copy the JavaScript path to a node when you need to reference it in an automated
 
 DevTools enables you to pause the JavaScript of a page when the JavaScript modifies the DOM.
 
+
+<!-- ------------------------------ -->
 #### Break on attribute modifications
 
 Use attribute modification breakpoints when you want to pause the JavaScript that causes any attribute of a node to change.
@@ -325,6 +353,8 @@ Use attribute modification breakpoints when you want to pause the JavaScript tha
 
 1. Click **Resume Script** (![Resume Script](./index-images/resume-script-icon.png)) to resume the JavaScript execution.
 
+
+<!-- ------------------------------ -->
 #### Break on node removal
 
 If you want to pause when a particular node is removed, use node removal breakpoints.
@@ -339,6 +369,8 @@ If you want to pause when a particular node is removed, use node removal breakpo
 
 1. Select **Resume Script** (![Resume Script](./index-images/resume-script-icon.png)).
 
+
+<!-- ------------------------------ -->
 #### Break on subtree modifications
 
 After you put a subtree modification breakpoint on a node, DevTools pauses the page when any of the descendants of the node are added or removed.
diff --git a/microsoft-edge/devtools/elements-tool/elements-tool.md b/microsoft-edge/devtools/elements-tool/elements-tool.md
index fffdd7110b..02862da9c9 100644
--- a/microsoft-edge/devtools/elements-tool/elements-tool.md
+++ b/microsoft-edge/devtools/elements-tool/elements-tool.md
@@ -10,7 +10,7 @@ ms.date: 02/15/2022
 ---
 # Inspect, edit, and debug HTML and CSS with the Elements tool
 
-Use the **Elements** tool to inspect, edit, and debug your HTML and CSS.  You can edit in the tool while displaying the changes live in the browser.  
+Use the **Elements** tool to inspect, edit, and debug your HTML and CSS.  You can edit in the tool while displaying the changes live in the browser.
 
 Debug your HTML using the DOM tree, and inspect and work on the CSS for your webpage.
 
diff --git a/microsoft-edge/devtools/experimental-features/index.md b/microsoft-edge/devtools/experimental-features/index.md
index c1fd77b2a5..d2e184713a 100644
--- a/microsoft-edge/devtools/experimental-features/index.md
+++ b/microsoft-edge/devtools/experimental-features/index.md
@@ -10,13 +10,13 @@ ms.date: 08/03/2026
 # Experimental features in Microsoft Edge DevTools
 <!-- https://learn.microsoft.com/microsoft-edge/devtools/experimental-features/ -->
 
-<!-- 
+<!--
 Maintenance:
 
-First, inspect latest Canary and update sections: 
+First, inspect latest Canary and update sections:
    * This checkbox is present in Microsoft Edge Canary 123.
 b/c that might add new sections.
-After that, inspect latest Stable and update sections: 
+After that, inspect latest Stable and update sections:
    * This checkbox is present in Microsoft Edge Stable 123.
 
 *  Favor Canary over Stable re: sequencing.
@@ -172,9 +172,9 @@ Status:
 <!-- https://learn.microsoft.com/microsoft-edge/devtools/experimental-features/#enable-symbol-server-extension-support -->
 <!-- checkbox has a "(?)" link, that should point to the present section heading -->
 
-If this checkbox is selected, the [Edge DevTools Symbol Server Extension Test](https://microsoftedge.microsoft.com/addons/detail/edgedevtoolssymbolservere/cjfmbiajhehnmfdjnlmdmceolcdcblcp) extension is supported, giving the new experience for **Symbol Server** in an extension.  This extension is still in beta/test.  
+If this checkbox is selected, the [Edge DevTools Symbol Server Extension Test](https://microsoftedge.microsoft.com/addons/detail/edgedevtoolssymbolservere/cjfmbiajhehnmfdjnlmdmceolcdcblcp) extension is supported, giving the new experience for **Symbol Server** in an extension.  This extension is still in beta/test.
 
-If this checkbox is cleared, use DevTools > **Settings** > **Symbol Server** page. 
+If this checkbox is cleared, use DevTools > **Settings** > **Symbol Server** page.
 
 See also:
 * [Securely debug original code by publishing source maps to the Azure Artifacts symbol server](../javascript/publish-source-maps-to-azure.md)
@@ -270,7 +270,7 @@ To select this checkbox and then open the **Protocol monitor** tool:
 
 1. In **Quick View** at the bottom of DevTools, click the **More tools** (+) button, and then select **Protocol monitor**.
 
-   Or, open the **Command Menu**, such as by pressing **Ctrl+Shift+P** (Windows/Linux) or **Command+Shift+P** (macOS), and then type **protocol** in the text box.  Then select **Show Protocol monitor**.  
+   Or, open the **Command Menu**, such as by pressing **Ctrl+Shift+P** (Windows/Linux) or **Command+Shift+P** (macOS), and then type **protocol** in the text box.  Then select **Show Protocol monitor**.
 
    The **Protocol monitor** tool is displayed in the **Quick View** panel at the bottom of DevTools.
 
diff --git a/microsoft-edge/devtools/experimental-features/share-memory-traces.md b/microsoft-edge/devtools/experimental-features/share-memory-traces.md
index d54b5b9d1b..62ac1cdc45 100644
--- a/microsoft-edge/devtools/experimental-features/share-memory-traces.md
+++ b/microsoft-edge/devtools/experimental-features/share-memory-traces.md
@@ -118,10 +118,10 @@ To export memory information from the **Memory** tool:
 
    <!-- todo: expect the File type dropdown to have not just 1 item, but 2
 
-   when DevTools Settings > **Export .devtools memory traces** checkbox is cleared, **Save as type**'s lone item is 
+   when DevTools Settings > **Export .devtools memory traces** checkbox is cleared, **Save as type**'s lone item is
    **Performance traces (*.devtools; *.json; *.heapsnapshot)**
 
-   when DevTools Settings > **Export .devtools memory traces** checkbox is selected, **Save as type**'s lone item is 
+   when DevTools Settings > **Export .devtools memory traces** checkbox is selected, **Save as type**'s lone item is
    **Performance traces (*.devtools; *.json; *.devtools)**
    -->
 
diff --git a/microsoft-edge/devtools/inspect-styles/animations.md b/microsoft-edge/devtools/inspect-styles/animations.md
index fffc1d6a43..a7757c7010 100644
--- a/microsoft-edge/devtools/inspect-styles/animations.md
+++ b/microsoft-edge/devtools/inspect-styles/animations.md
@@ -75,7 +75,7 @@ By default, the **Animations** tool opens in the **Quick View** panel at the bot
 The Animation Inspector is grouped into four main sections (or panes).  This guide refers to each pane as follows:
 
 | Index | Pane | Description |
-|:--- |:--- |:--- |
+|---|---|---|
 | 1 | **Controls** | From here you can clear all currently captured Animation Groups, or change the speed of the currently selected Animation Group. |
 | 2 | **Overview** | Select an Animation Group here to inspect and modify it in the **Details** pane. |
 | 3 | **Timeline** | Pause and start an animation from here, or jump to a specific point in the animation. |
diff --git a/microsoft-edge/devtools/issues/index.md b/microsoft-edge/devtools/issues/index.md
index f0120183b4..aadeb2298e 100644
--- a/microsoft-edge/devtools/issues/index.md
+++ b/microsoft-edge/devtools/issues/index.md
@@ -74,7 +74,7 @@ Feedback in the **Issues** tool is provided by several sources, including the Ch
 <!-- ------------------------------ -->
 #### Placement of Issues tool: Quick View or Activity Bar
 
-By default, such as from the **Command Menu**, the **Issues** tool opens in the **Quick View** panel.  You can instead open it in the **Activity Bar**, or move it to the **Activity Bar**: 
+By default, such as from the **Command Menu**, the **Issues** tool opens in the **Quick View** panel.  You can instead open it in the **Activity Bar**, or move it to the **Activity Bar**:
 
 *  In the **Quick View** toolbar, right-click the **Inspect** tab and then select **Move to top Activity Bar**.
 
diff --git a/microsoft-edge/devtools/javascript/breakpoints.md b/microsoft-edge/devtools/javascript/breakpoints.md
index ad694d86a6..0316ef9dff 100644
--- a/microsoft-edge/devtools/javascript/breakpoints.md
+++ b/microsoft-edge/devtools/javascript/breakpoints.md
@@ -34,7 +34,7 @@ For an introductory tutorial using an existing webpage, see [Get started debuggi
 The most well-known type of breakpoint is line-of-code.  But line-of-code breakpoints may be inefficient to set, especially if you don't know exactly where to look, or if you are working with a large codebase.  You can save yourself time when debugging by knowing how and when to use the other types of breakpoints.
 
 | Breakpoint type | Use this when you want to pause... |
-|:--- |:--- |
+|---|---|
 | [Line-of-code](#line-of-code-breakpoints) | On an exact region of code.  |
 | [Conditional line-of-code](#conditional-line-of-code-breakpoints) | On an exact region of code, but only when some other condition is true.  |
 | [DOM](#dom-change-breakpoints) | On the code that changes or removes a specific DOM node, or the children.  |
@@ -248,7 +248,7 @@ When you're calling `debug()` from the **Console** tool, here's a technique to e
 <!-- ====================================================================== -->
 ## Logpoints
 
-A Logpoint is a breakpoint variant that doesn't "break" in the debugger, but instead logs a message directly to the console.  You insert a logpoint via DevTools the same way you would any other breakpoint. 
+A Logpoint is a breakpoint variant that doesn't "break" in the debugger, but instead logs a message directly to the console.  You insert a logpoint via DevTools the same way you would any other breakpoint.
 
 To set a logpoint:
 
diff --git a/microsoft-edge/devtools/javascript/consume-source-maps-from-azure.md b/microsoft-edge/devtools/javascript/consume-source-maps-from-azure.md
index 471390057d..f36498af8a 100644
--- a/microsoft-edge/devtools/javascript/consume-source-maps-from-azure.md
+++ b/microsoft-edge/devtools/javascript/consume-source-maps-from-azure.md
@@ -81,7 +81,7 @@ To connect to the symbol server by using a Personal Access Token (PAT), first ge
 1. Sign in to your Azure DevOps organization by going to `https://dev.azure.com/{yourorganization}`.
 
 1. In Azure DevOps, go to **User settings** > **Personal access tokens**:
-    
+
    ![The 'User settings' menu in Azure DevOps, with the 'Personal access tokens' command](./consume-source-maps-from-azure-images/ado-pat-settings.png)
 
    The **Personal Access Tokens** page appears:
diff --git a/microsoft-edge/devtools/javascript/guides/mark-content-scripts-library-code.md b/microsoft-edge/devtools/javascript/guides/mark-content-scripts-library-code.md
index 62fcb50077..f4b3d27bd0 100644
--- a/microsoft-edge/devtools/javascript/guides/mark-content-scripts-library-code.md
+++ b/microsoft-edge/devtools/javascript/guides/mark-content-scripts-library-code.md
@@ -46,7 +46,7 @@ To avoid pausing on extension code:
 
 * [Step 4: Step through the code](../index.md#step-4-step-through-the-code) in _Get started debugging JavaScript_
 * [Content scripts](https://developer.mozilla.org/docs/Mozilla/Add-ons/WebExtensions/Content_scripts) at MDN.
-<!-- 
+<!--
 * [Sample: Picture inserter using content script](../../../extensions/getting-started/picture-inserter-content-script.md)
 -->
 
diff --git a/microsoft-edge/devtools/javascript/index.md b/microsoft-edge/devtools/javascript/index.md
index 53e5de068e..a6951ff5ea 100644
--- a/microsoft-edge/devtools/javascript/index.md
+++ b/microsoft-edge/devtools/javascript/index.md
@@ -236,7 +236,7 @@ We've identified a possible fix for the bug.  Next, edit the JavaScript code dir
 
 1. Try out the demo with different values.  The demo now calculates correctly.
 
-1. When debugging your own project, after you identify the fix, you then fix your actual source code on the server, such as by editing your local source code and then re-deploying your fixed code to the server.  The previous steps only apply a fix to a temporary local copy of the code that's sent from the server.   
+1. When debugging your own project, after you identify the fix, you then fix your actual source code on the server, such as by editing your local source code and then re-deploying your fixed code to the server.  The previous steps only apply a fix to a temporary local copy of the code that's sent from the server.
 
 
 <!-- ====================================================================== -->
diff --git a/microsoft-edge/devtools/javascript/overrides.md b/microsoft-edge/devtools/javascript/overrides.md
index 2e741692a3..a98138e2a5 100644
--- a/microsoft-edge/devtools/javascript/overrides.md
+++ b/microsoft-edge/devtools/javascript/overrides.md
@@ -79,7 +79,7 @@ Next, add files to your Overrides folder, as follows.  This example will add a C
    In this example, the file is listed as: `microsoftedge.github.io/Demos/demo-to-do/styles > to-do-styles.css`
 
    The file is stored in a new directory that's in your overrides folder (such as in `C:\Users\myusername\overrides`).
- 
+
 1. In File Explorer or Finder, verify that DevTools created a subfolder that is named using the URL of the file (such as **microsoftedge.github.io**) and contains the correct directory structure, such as `C:\Users\myusername\overrides\microsoftedge.github.io\Demos\demo-to-do\styles`.  The overriding file is stored in this directory.
 
    In the editor pane of the **Sources** tool, a page icon with a purple dot is added to the file's tab. The purple dot indicates that the file is a local file that overrides the file that's returned from the web server:
diff --git a/microsoft-edge/devtools/javascript/publish-source-maps-to-azure.md b/microsoft-edge/devtools/javascript/publish-source-maps-to-azure.md
index 4b7465a453..14fc6adad2 100644
--- a/microsoft-edge/devtools/javascript/publish-source-maps-to-azure.md
+++ b/microsoft-edge/devtools/javascript/publish-source-maps-to-azure.md
@@ -37,7 +37,7 @@ To generate a PAT in Azure DevOps:
 1. Sign in to your Azure DevOps organization by going to `https://dev.azure.com/{yourorganization}`.
 
 1. In Azure DevOps, go to **User settings** > **Personal access tokens**:
-    
+
    ![The 'User settings' menu in Azure DevOps, with the 'Personal access tokens' command](./publish-source-maps-to-azure-images/ado-pat-settings.png)
 
    The **Personal Access Tokens** page appears:
diff --git a/microsoft-edge/devtools/javascript/reference.md b/microsoft-edge/devtools/javascript/reference.md
index 4595204617..f264db7d7b 100644
--- a/microsoft-edge/devtools/javascript/reference.md
+++ b/microsoft-edge/devtools/javascript/reference.md
@@ -409,7 +409,7 @@ Use the `# sourceURL` pragma to give a virtual file name to code blocks that are
   }
 
   console.log(sum(1, 2));
-  
+
   //# sourceURL=math-utilities.js
   ```
 
@@ -420,7 +420,7 @@ Use the `# sourceURL` pragma to give a virtual file name to code blocks that are
     padding: 1rem;
     border-radius: 0.5rem;
   }
-  
+
   /*# sourceURL=card-styles.css*/
   ```
 
diff --git a/microsoft-edge/devtools/memory-inspector/memory-inspector-tool.md b/microsoft-edge/devtools/memory-inspector/memory-inspector-tool.md
index 6b0b8747a7..8637963cd4 100644
--- a/microsoft-edge/devtools/memory-inspector/memory-inspector-tool.md
+++ b/microsoft-edge/devtools/memory-inspector/memory-inspector-tool.md
@@ -66,7 +66,7 @@ For example:
 1. From the `buffer` line you can open Memory inspector using one of the following methods:
 
     * Click on the **Reveal in Memory inspector panel** icon (![Reveal in Memory inspector panel icon](./memory-inspector-tool-images/memory-inspector-open-from-buffer-icon.png)) at the end of the `buffer` property line, or
- 
+
     * From the context menu. Right click the `buffer` property and select **Reveal in Memory inspector panel**.
 
     ![Open Memory inspector from the buffer property line context menu](./memory-inspector-tool-images/memory-inspector-open-from-buffer.png)
@@ -102,7 +102,7 @@ The Memory inspector panel includes three types of content:
 #### Navigation bar
 
 ![Memory inspector panel Navigation bar](./memory-inspector-tool-images/memory-inspector-panel-navigation-bar.png)
- 
+
 The **Enter address** text box shows the current byte address in hex format. You can change the value to jump to a new location in the memory buffer. Click in the text box and change the value to `0x00000008`. The Memory buffer immediately jumps to that byte address.
 
 Memory buffers may be longer than one page. Use the left and right arrow buttons to navigate **Previous page** (**<**) and **Next page** (**>**), respectively. If there is only one page of memory buffer data, the arrows take you to the beginning and ending of the page.
@@ -116,7 +116,7 @@ If the Memory buffer does not automatically update when stepping through values,
 #### Memory buffer
 
 ![Memory inspector panel Memory buffer](./memory-inspector-tool-images/memory-inspector-panel-memory-buffer.png)
- 
+
 Reading from the left side of the panel, the **address** is displayed in hex format. The currently selected address is bold.
 
 The **memory** is also shown in hex format, each byte separated by a space. The currently selected byte is highlighted. You can click on any byte or navigate using the arrow keys (left, right, up, and down).
@@ -128,7 +128,7 @@ The **ASCII representation** of the memory is shown on the right side of the pan
 #### Value inspector
 
 ![Memory inspector panel Value inspector](./memory-inspector-tool-images/memory-inspector-panel-value-inspector.png)
- 
+
 Click the current Endian type to switch between **Big endian** and **Little endian**.
 
 The main area shows each value and interpretation based on the settings. By default, all values are shown.
@@ -154,21 +154,21 @@ Complete the following steps to debug a webpage in Memory inspector.
 1. Click **Resume script execution** (![Resume script execution](./memory-inspector-tool-images/memory-inspector-resume-script-execution.png)) or press **F8** or **Ctrl +\\** to step through the code.
 
     The ASCII representation and the value interpretations are updated.
-    
+
     ![Memory inspector address values updated](./memory-inspector-tool-images/memory-inspector-address-values-updated.png)
 
 1. Click the **Jump to address** button (![Jump to address button](./memory-inspector-tool-images/memory-inspector-jump-to-address.png)) for **Pointer 32-bit** or **Pointer 64-bit** as needed to jump to the next active memory address. If next memory address is not available, the button is turned off (![Address out of memory range](./memory-inspector-tool-images/memory-inspector-address-out-of-range.png)) with the tooltip **Address out of memory range**.
 
 1. Customize the **Value inspector** to show only floating point values. Click **Toggle value type settings** (![Toggle value type settings gray](./memory-inspector-tool-images/memory-inspector-value-type-settings-toggle.png)) and clear all checkboxes except the two **Floating point** values.
-    
+
     ![Value type settings float](./memory-inspector-tool-images/memory-inspector-panel-value-type-settings-float.png)
 
 1. Click **Toggle value type settings** (![Toggle value type settings blue](./memory-inspector-tool-images/memory-inspector-value-type-settings-toggle-back.png)) to close the value type settings.
 
 1. Use the dropdown lists to change the encoding from `dec` to `sci`. The value representations are updated.
-    
+
     ![Memory inspector address values updated view](./memory-inspector-tool-images/memory-inspector-address-values-updated-sci.png)
-    
+
 1. Explore the memory buffer using the keyboard or navigation bar.
 
 1. Repeat steps **3** and **4** to observe value changes.
@@ -195,10 +195,10 @@ For example:
 
     ![Memory inspector set breakpoint in Wasm file](./memory-inspector-tool-images/memory-inspector-wasm-breakpoint.png)
 
-1. Click on the **Reveal in Memory inspector panel** icon (![Reveal in Memory inspector panel icon](./memory-inspector-tool-images/memory-inspector-open-from-buffer-icon.png)) at the end of the `$imports.memory` property line. 
+1. Click on the **Reveal in Memory inspector panel** icon (![Reveal in Memory inspector panel icon](./memory-inspector-tool-images/memory-inspector-open-from-buffer-icon.png)) at the end of the `$imports.memory` property line.
 
     The Wasm ArrayBuffer opens in **Memory inspector**.
-    
+
     ![Memory inspector panel Wasm](./memory-inspector-tool-images/memory-inspector-panel-wasm.png)
 
 
diff --git a/microsoft-edge/devtools/memory-problems/heap-snapshot-schema.md b/microsoft-edge/devtools/memory-problems/heap-snapshot-schema.md
index 9b6137109e..cd0bf74e81 100644
--- a/microsoft-edge/devtools/memory-problems/heap-snapshot-schema.md
+++ b/microsoft-edge/devtools/memory-problems/heap-snapshot-schema.md
@@ -101,7 +101,7 @@ The `.heapsnapshot` JSON data contains a root object that has the following prop
 
 ```json
 {
-    "snapshot": {     
+    "snapshot": {
         "meta": {},
         "node_count": 123,
         "edge_count": 456,
@@ -276,7 +276,7 @@ Similar to the `nodes` array, the `edges` top-level array contains all of the el
 
 Also similar to nodes, the total number of edges can be calculated by multiplying `snapshot.edge_count` by `snapshot.meta.edge_fields.length`. Edges are also stored as a sequence of numbers, which you will need to iterate on by groups of size `snapshot.meta.edge_fields.length`.
 
-However, to read the `edges` array correctly, you first need to read the `nodes` array, because each node knows how many edges it has. 
+However, to read the `edges` array correctly, you first need to read the `nodes` array, because each node knows how many edges it has.
 
 To re-create an edge, you need three pieces of information:
 
diff --git a/microsoft-edge/devtools/memory-problems/heap-snapshots.md b/microsoft-edge/devtools/memory-problems/heap-snapshots.md
index e3ae814bcb..ab8299b8ab 100644
--- a/microsoft-edge/devtools/memory-problems/heap-snapshots.md
+++ b/microsoft-edge/devtools/memory-problems/heap-snapshots.md
@@ -127,7 +127,7 @@ Each constructor in the list can be expanded to show the objects that were insta
 For each constructor in the list, the **Summary** view also shows a number such as **×123**, indicating the total number of objects created with the constructor. The **Summary** view also shows the following columns:
 
 | Column name | Description |
-|:--- |:--- |
+|---|---|
 | **Distance** | Displays the distance to the root using the shortest simple path of nodes.  See [Distance](./memory-101.md#distance) in _Memory terminology_. |
 | **Shallow size** | Displays the sum of shallow sizes of all objects created by a certain constructor function.  The _shallow size_ is the size of the JavaScript heap that's _directly_ held by an object. The shallow size of an object is usually small, because a JavaScript object often only stores its description of the object, not the values, in the object's directly held memory. Most JavaScript objects store their values in a _backing store_ that's elsewhere in the JavaScript heap, and only expose a small wrapper object on the portion of the JavaScript heap that's directly owned by the object. See [Shallow size](./memory-101.md#shallow-size) in _Memory terminology_. |
 | **Retained size** | Displays the maximum retained size among the same set of objects.  The size of memory that you can free after an object is deleted (and the dependents are made no longer reachable) is called the retained size.  See [Retained size](./memory-101.md#retained-size) in _Memory terminology_. |
@@ -155,7 +155,7 @@ To reveal the list of objects that were instantiated by a given constructor, exp
 The **Summary** view in the **Memory** tool includes the following special category names, which aren't based on constructors.  Most of these category names are displayed in parentheses.
 
 | Category name | Description |
-|:--- |:--- |
+|---|---|
 | **(array)** | Various internal array-like objects that don't directly correspond to objects visible from JavaScript, such as the contents of JavaScript arrays, or the named properties of JavaScript objects. |
 | **(compiled code)** | Internal data that V8 (Microsoft Edge's JavaScript engine) needs to run functions defined by JavaScript or WebAssembly. V8 automatically manages memory usage in this category: if a function runs many times, V8 uses more memory for that function so that the function runs faster. If a function hasn't run in a while, V8 might delete the internal data for that function. |
 | **(concatenated string)** | When two strings are concatenated together, such as when using the JavaScript `+` operator, V8 might choose to represent the result internally as a _concatenated string_. Rather than copying all of the characters of the two strings into a new string, V8 creates a small object which points to the two strings. |
@@ -203,7 +203,7 @@ The **Containment** view allows you to peek inside function closures, to observe
 The **Containment** view shows the following types of objects:
 
 | Containment view entry points | Description |
-|:--- |:--- |
+|---|---|
 | **DOMWindow objects** | Global objects for JavaScript code.  |
 | **GC roots** | The GC roots used by the garbage collector of the JavaScript virtual machine.  GC roots are comprised of built-in object maps, symbol tables, VM thread stacks, compilation caches, handle scopes, and global handles.  |
 | **Native objects** | Objects created by the browser such as DOM nodes and CSS rules, which are shown in the JavaScript virtual machine to allow automation. |
diff --git a/microsoft-edge/devtools/memory-problems/memory-101.md b/microsoft-edge/devtools/memory-problems/memory-101.md
index 2468f1d017..2b0bb22e1d 100644
--- a/microsoft-edge/devtools/memory-problems/memory-101.md
+++ b/microsoft-edge/devtools/memory-problems/memory-101.md
@@ -184,7 +184,7 @@ Memory for new JavaScript objects is allocated from a dedicated JavaScript heap
 * **Arrays**: An _array_ is an object that has numeric keys. Arrays are used extensively in the V8 VM for storing large amounts of data. Sets of key-value pairs that are used like dictionaries are implemented as arrays.
 
   A typical JavaScript object is stored as only one of two array types:
-  
+
   * An array for storing named properties.
   * An array for storing numeric elements.
 
diff --git a/microsoft-edge/devtools/network-request-blocking/network-request-blocking-tool.md b/microsoft-edge/devtools/network-request-blocking/network-request-blocking-tool.md
index cab872051f..7fa7c7b56e 100644
--- a/microsoft-edge/devtools/network-request-blocking/network-request-blocking-tool.md
+++ b/microsoft-edge/devtools/network-request-blocking/network-request-blocking-tool.md
@@ -36,15 +36,13 @@ To block a network request:
    * Type the full URL.
    * Type only the domain name, to block all requests from this domain.
    * Replace parts of the URL with `*`, for wildcard pattern matching.
-   
-   For example, `contoso.com` matches URLs like:
 
+   For example, `contoso.com` matches URLs like:
    * `https://contoso.com`
    * `https://subdomain.contoso.com`
    * `https://subdomain.contoso.com/path/to/resource`
 
    And `*.jpg` matches URLs like:
-   
    * `https://www.contoso.com/resource.jpg`
    * `http://third-party.com/6469272/163348534-b90ea1a3-c33cbeb1aed8.jpg`
 
diff --git a/microsoft-edge/devtools/network/reference.md b/microsoft-edge/devtools/network/reference.md
index c7808cf4a3..0b2f9a0a07 100644
--- a/microsoft-edge/devtools/network/reference.md
+++ b/microsoft-edge/devtools/network/reference.md
@@ -110,7 +110,7 @@ For a step-by-step walkthrough and introduction to the **Network** tool, see [In
 
 By default, DevTools records all network requests in the **Network** tool, so long as DevTools is open.
 
-For example: 
+For example:
 
 1. Go to a webpage, such as the [Inspect Network Activity](https://microsoftedge.github.io/Demos/network-tutorial/) demo page, in a new window or tab.
 
@@ -202,7 +202,7 @@ To capture a screenshot:
 1. Click the thumbnail of a screenshot to filter out any requests that occurred after the screenshot was captured.
 
 1. Double-click a screenshot thumbnail to zoom-in and view the screenshot.
- 
+
 1. Press **Esc** to close the screenshot viewer.
 
 
@@ -404,7 +404,7 @@ To observe WebSocket throttling:
 1. Go to a page that uses WebSockets, such as [Online WebSocket Tester](https://www.piesocket.com/websocket-tester), in a new window or tab.
 
 1. On the page, establish the WebSocket connection.
-    
+
    If you use the **Online WebSocket Tester** webpage, click the **Connect** button.
 
    If you don't create a PieSocket account to get an API Token, the webpage displays "Connection Established - {"error":"Unknown api key"}".
@@ -426,7 +426,7 @@ To observe WebSocket throttling:
    The console within the **Online WebSocket Tester** webpage displays **DevTools with throttling**.
 
 1. At the top of the **Network** tool, select the **Socket** filter button (shown below).
-    
+
 1. In the table, click your connection name, such as **channel_123?api_key=...**.
 
    Tabs appear.
@@ -598,7 +598,7 @@ You can use multiple properties simultaneously by separating each property with
 The complete list of supported properties:
 
 | Property | Details |
-|:--- | :--- |
+|---|---|
 | `cookie-domain` | Show the resources that set a specific cookie domain. |
 | `cookie-name` | Show the resources that set a specific cookie name. |
 | `cookie-path` | Show the resources that set a specific cookie path. |
@@ -815,15 +815,15 @@ To change how the **Waterfall** column sorts requests:
 * Right-click the header of the **Requests** table, click **Waterfall**, and then select one of the following options:
 
    * **Start Time** - The first request that was initiated is placed at the top.
-   
+
    * **Response Time** - The first request that started downloading is placed at the top.
-   
+
    * **End Time** - The first request that finished is placed at the top.
-   
+
    * **Total Duration** - The request with the shortest connection settings and request or response is placed at the top.
-   
+
    * **Latency** - The request that waited the shortest time for a response is placed at the top.
-      
+
 These descriptions assume that each respective option is ranked from shortest to longest.  Click the header of the **Waterfall** column to reverse the order.
 
 The following shows sorting the Waterfall by total duration.  The lighter portion of each bar is time spent waiting and the darker portion is time spent downloading bytes:
@@ -867,7 +867,7 @@ The **Waterfall** column is off by default.  To turn on the **Waterfall** column
 ###### Add or remove columns
 <!-- https://developer.chrome.com/docs/devtools/network/reference/#columns -->
 
-Right-click the header of the **Requests** table and select a column name to hide or show it.  The currently displayed columns have checkmarks next to them.
+Right-click the header of the **Requests** table and select a column name to hide or show it.  The currently displayed columns have checkmarks next to them:
 
 ![Adding a column to the **Requests** table](./reference-images/requests-add-column.png)
 
@@ -880,12 +880,12 @@ To add a custom column to the **Requests** table:
 
 1. Right-click the header of the **Requests** table and then select **Response Headers** > **Manage Header Columns**.
 
-   The **Manage Header Columns** popup window opens.
-
-1. Click the **Add custom header** button, enter the custom header name, and then click **Add**. 
+   The **Manage Header Columns** popup window opens:
 
    ![Adding a custom column to the **Requests** table](./reference-images/requests-add-custom-column.png)
 
+1. Click the **Add custom header** button, enter the custom header name, and then click the **Add** button.<!-- todo: show Add button like https://developer.chrome.com/static/docs/devtools/network/reference/image/adding-custom-column-th-19867e5fa8081_856.png -->
+
 
 <!-- ------------------------------ -->
 #### Group requests by inline frames
@@ -1015,7 +1015,7 @@ To refresh the **Requests** table, in the **Name** pane, click the name of the W
 
 The **Requests** table contains the following three columns:
 
-*  **Data**.  The message payload.  If the message is plain text, it is displayed here.  For binary opcodes, this column displays the name and code of the opcode.  The following opcodes are supported: 
+*  **Data**.  The message payload.  If the message is plain text, it is displayed here.  For binary opcodes, this column displays the name and code of the opcode.  The following opcodes are supported:
    * Continuation Frame
    * Binary Frame
    * Connection Close Frame
@@ -1685,7 +1685,7 @@ To copy the formatted JSON data of a JSON response:
 
 1. In the sidebar, select the **Preview** tab.
 
-1. Right-click the first line of the formatted JSON response preview and then select **Copy value**. 
+1. Right-click the first line of the formatted JSON response preview, and then select **Copy value**:
 
    ![The Copy Value right-click command](./reference-images/copy-json-value.png)
 
diff --git a/microsoft-edge/devtools/overview.md b/microsoft-edge/devtools/overview.md
index 0399f42c43..5375033a71 100644
--- a/microsoft-edge/devtools/overview.md
+++ b/microsoft-edge/devtools/overview.md
@@ -164,25 +164,25 @@ To have DevTools automatically open whenever you open a new tab in the browser:
 1. At the command line, open Microsoft Edge, passing in the `--auto-open-devtools-for-tabs` flag, as follows:
 
    Windows command prompt:
-   
+
    ```cmd
    start msedge --auto-open-devtools-for-tabs
    ```
-   
+
    Windows PowerShell:
-   
+
    ```powershell
    Start-Process -FilePath "msedge" -ArgumentList "--auto-open-devtools-for-tabs"
    ```
-   
+
    macOS Terminal:
-   
+
    ```bash
    /Applications/Microsoft\ Edge.app/Contents/MacOS/Microsoft\ Edge --auto-open-devtools-for-tabs
    ```
-   
+
    bash shell on Linux:
-   
+
    ```bash
    microsoft-edge --auto-open-devtools-for-tabs
    ```
diff --git a/microsoft-edge/devtools/performance/extension.md b/microsoft-edge/devtools/performance/extension.md
index 2b8ac7d2f9..c3448e5bb3 100644
--- a/microsoft-edge/devtools/performance/extension.md
+++ b/microsoft-edge/devtools/performance/extension.md
@@ -49,7 +49,7 @@ The **Performance** tool can display your own performance data, in addition to t
 * Building a framework and you need to visualize internal processes.
 * Developing a library and you want to track the impact of your code.
 * Building a complex web application with a lot of client-side processing.
-    
+
 The performance extensibility APIs make it possible to understand what's happening in your code.
 
 By injecting custom measurements and events, you can create tailored visualizations within the **Performance** tool.
@@ -126,11 +126,11 @@ The `console.timeStamp()` API is extended to allow for the creation of custom ti
 Syntax:
 
 ```javascript
-console.timeStamp(label: string, 
-                  start?: string|number, 
-                  end?: string|number, 
-                  trackName?: string, 
-                  trackGroup?: string, 
+console.timeStamp(label: string,
+                  start?: string|number,
+                  end?: string|number,
+                  trackName?: string,
+                  trackGroup?: string,
                   color?: DevToolsColor);
 ```
 
@@ -327,7 +327,7 @@ function loadPhoto(fileName) {
 }
 ```
 
-To view the resulting profile: 
+To view the resulting profile:
 
 1. Do the steps in [View your custom data in the performance profile](#view-your-custom-data-in-the-performance-profile), above.
 
@@ -407,7 +407,7 @@ function populateGallery(images) {
 }
 ```
 
-To view the resulting profile: 
+To view the resulting profile:
 
 1. Do the steps in [View your custom data in the performance profile](#view-your-custom-data-in-the-performance-profile), above.
 
@@ -517,7 +517,7 @@ addEventListener('click', e => {
 });
 ```
 
-To view the resulting profile: 
+To view the resulting profile:
 
 1. Do the steps in [View your custom data in the performance profile](#view-your-custom-data-in-the-performance-profile), above.
 
@@ -555,7 +555,7 @@ Demos:
 
 <!-- ====================================================================== -->
 > [!NOTE]
-> Portions of this page are modifications based on work created and [shared by Google](https://developers.google.com/terms/site-policies) and used according to terms described in the [Creative Commons Attribution 4.0 International License](https://creativecommons.org/licenses/by/4.0). 
+> Portions of this page are modifications based on work created and [shared by Google](https://developers.google.com/terms/site-policies) and used according to terms described in the [Creative Commons Attribution 4.0 International License](https://creativecommons.org/licenses/by/4.0).
 > The original page is found [here](https://developer.chrome.com/docs/devtools/performance/extension) and is authored by Andrés Olivares and Sofia Emelianova.
 
 [![Creative Commons License](../../media/cc-logo/88x31.png)](https://creativecommons.org/licenses/by/4.0)
diff --git a/microsoft-edge/devtools/performance/index.md b/microsoft-edge/devtools/performance/index.md
index 4b8a5eff55..475b531d41 100644
--- a/microsoft-edge/devtools/performance/index.md
+++ b/microsoft-edge/devtools/performance/index.md
@@ -267,7 +267,7 @@ After you verified that the animation isn't performing well, the next step is to
    Or, press **W**.
 
    You can now see the events that occur when a single frame of the animation is rendered. The **update** function is called, which, in turn, calls the **updateSlow** function, which triggers many **Recalculate Style** and **Layout** events:
-   
+
    ![The Animation Frame Fired event and its child events](./index-images/animation-frame-children.png)
 
 1. Click one of the purple **Layout** events.
@@ -355,7 +355,7 @@ Finally, we read `element.offsetTop` again, to adjust the direction of the icon.
 <!-- ====================================================================== -->
 ## Step 11: Analyze the optimized code
 
-The optimized code uses a different sequence of actions to do less work. Here is the same snippet of JavaScript from the optimized version of the app: 
+The optimized code uses a different sequence of actions to do less work. Here is the same snippet of JavaScript from the optimized version of the app:
 
 ```javascript
 // Read the current position.
@@ -412,7 +412,7 @@ See also:
 To get more comfortable with the **Performance** tool, practice profiling your webpages and analyzing the results.
 
 If you have any questions about your results, in the **Activity Bar**, select **Help** (![the Help icon in the Activity Bar](./index-images/help-icon.png)) > **Feedback**.  Or, press **Alt+Shift+I** (Windows, Linux) or **Option+Shift+I** (macOS).
- 
+
 Or, [file an issue on the MicrosoftEdge / DevTools repo](https://github.com/MicrosoftEdge/DevTools/issues).
 
 In your feedback, include screenshots or links to reproducible webpages, if possible.
@@ -422,7 +422,7 @@ There are many ways to improve runtime performance.  This article focused on one
 
 <!-- ====================================================================== -->
 > [!NOTE]
-> Portions of this page are modifications based on work created and [shared by Google](https://developers.google.com/terms/site-policies) and used according to terms described in the [Creative Commons Attribution 4.0 International License](https://creativecommons.org/licenses/by/4.0). 
+> Portions of this page are modifications based on work created and [shared by Google](https://developers.google.com/terms/site-policies) and used according to terms described in the [Creative Commons Attribution 4.0 International License](https://creativecommons.org/licenses/by/4.0).
 > The original page is found [here](https://developer.chrome.com/docs/devtools/performance) and is authored by Kayce Basques.
 
 [![Creative Commons License](../../media/cc-logo/88x31.png)](https://creativecommons.org/licenses/by/4.0)
diff --git a/microsoft-edge/devtools/performance/overview.md b/microsoft-edge/devtools/performance/overview.md
index a72ed4d42c..50afcc536b 100644
--- a/microsoft-edge/devtools/performance/overview.md
+++ b/microsoft-edge/devtools/performance/overview.md
@@ -64,7 +64,7 @@ The **Performance** tool displays local metrics for page interactions, and lets
 #### Open the Performance tool
 <!-- https://developer.chrome.com/docs/devtools/performance/overview#open_the_performance_panel -->
 
-To open the **Performance** tool: 
+To open the **Performance** tool:
 
 1. Go to a webpage, such as the [Exploring the universe](https://microsoftedge.github.io/Demos/exploring-the-universe/) demo, in a new window or tab.
 
@@ -120,7 +120,7 @@ When you initially open the **Performance** tool, Core Web Vitals metrics are di
 <!-- ------------------------------ -->
 #### Recorded profile timeline
 
-Also use the **Performance** tool to view a recorded performance trace, including: 
+Also use the **Performance** tool to view a recorded performance trace, including:
 * Record a performance profile.
 * Change capture settings.
 * Analyze a performance report.  Shows information about the performance of the page over the period of time where the recording occurred, such as:
@@ -129,7 +129,7 @@ Also use the **Performance** tool to view a recorded performance trace, includin
    * The styling and layout operations that occurred.
    * Other performance metrics over time, such as network requests and layout shifts.
 
-After you record a performance trace, the performance trace is displayed instead of **Local metrics**.  
+After you record a performance trace, the performance trace is displayed instead of **Local metrics**.
 
 
 <!-- ------------------------------ -->
@@ -301,7 +301,7 @@ Select the following options from the **Capture settings** menu:
 
 * Select the **Enable CSS selector stats (slow)** checkbox: Captures CSS selector statistics.  Significantly hinders performance.  See [View CSS selector costs in the Performance tool sidebar](../whats-new/2024/11/devtools-131.md#view-css-selector-costs-in-the-performance-tool-sidebar) in _What's new in DevTools (Microsoft Edge 131)_.
 
-* CPU throttling: Simulate slower CPU speeds.  See [Throttle the CPU while recording](../performance/reference.md#throttle-the-cpu-while-recording) in _Performance features reference_.  
+* CPU throttling: Simulate slower CPU speeds.  See [Throttle the CPU while recording](../performance/reference.md#throttle-the-cpu-while-recording) in _Performance features reference_.
 
 * Network throttling: Simulate slower network speeds.  See [Throttle the network while recording](../performance/reference.md#throttle-the-network-while-recording) in _Performance features reference_.
 
@@ -371,7 +371,7 @@ Discover other tools that can help you improve your website's performance:
 
 <!-- ====================================================================== -->
 > [!NOTE]
-> Portions of this page are modifications based on work created and [shared by Google](https://developers.google.com/terms/site-policies) and used according to terms described in the [Creative Commons Attribution 4.0 International License](https://creativecommons.org/licenses/by/4.0). 
+> Portions of this page are modifications based on work created and [shared by Google](https://developers.google.com/terms/site-policies) and used according to terms described in the [Creative Commons Attribution 4.0 International License](https://creativecommons.org/licenses/by/4.0).
 > The original page is found [here](https://developer.chrome.com/docs/devtools/performance/overview) and is authored by Dale St. Marthe and Sofia Emelianova.
 
 [![Creative Commons License](../../media/cc-logo/88x31.png)](https://creativecommons.org/licenses/by/4.0)
diff --git a/microsoft-edge/devtools/performance/performance-reference.md b/microsoft-edge/devtools/performance/performance-reference.md
index ae39446a71..83d21c879c 100644
--- a/microsoft-edge/devtools/performance/performance-reference.md
+++ b/microsoft-edge/devtools/performance/performance-reference.md
@@ -36,7 +36,7 @@ In the **Performance** tool, the **Main** section displays all events that are t
 The following properties are common to all event types in the **Performance** tool's **Main** section.  Additional properties that are specific to certain event types are listed in the subsequent sections below.
 
 | Property | When is it shown |
-|:--- |:--- |
+|---|---|
 | Aggregated time | For events with **nested events**, the time taken by each category of events. |
 | Call Stack | For events with **child events**, the time taken by each category of events. |
 | CPU time | How much CPU time the recorded event took. |
@@ -54,7 +54,7 @@ The following properties are common to all event types in the **Performance** to
 The following events are in the **Loading** category.
 
 | Event | Description |
-|:--- |:--- |
+|---|---|
 | Parse HTML |  Microsoft Edge ran the HTML parsing algorithm. |
 | Finish Loading |  A network request completed. |
 | Receive Data |  Data for a request was received.  There are one or more Receive Data events. |
@@ -66,7 +66,7 @@ The following events are in the **Loading** category.
 #### Additional properties for Loading events
 
 | Property | Description |
-|:--- |:--- |
+|---|---|
 | Resource | The URL of the requested resource. |
 | Preview | Preview of the requested resource (images only). |
 | Request Method | HTTP method used for the request (`GET` or `POST`, for example). |
@@ -83,7 +83,7 @@ See also [Properties common to all events](#properties-common-to-all-events), ab
 The following events are in the **Scripting** category.
 
 | Event | Description |
-|:--- |:--- |
+|---|---|
 | Animation Frame Fired | A scheduled animation frame fired, and its callback handler invoked. |
 | Cancel Animation Frame |  A scheduled animation frame was canceled. |
 | GC Event |  Garbage collection occurred. |
@@ -105,7 +105,7 @@ The following events are in the **Scripting** category.
 #### Additional properties for Scripting events
 
 | Property | Description |
-|:--- |:--- |
+|---|---|
 | Timer ID | The timer ID. |
 | Timeout | The timeout specified by the timer. |
 | Repeats | Boolean that specifies if the timer repeats. |
@@ -120,7 +120,7 @@ See also [Properties common to all events](#properties-common-to-all-events), ab
 The following events are in the **Rendering** category.
 
 | Event | Description |
-|:--- |:--- |
+|---|---|
 | Invalidate layout | The page layout was invalidated by a DOM change. |
 | Layout | A page layout was completed. |
 | Recalculate style | Microsoft Edge recalculated element styles. |
@@ -131,7 +131,7 @@ The following events are in the **Rendering** category.
 #### Additional properties for Rendering events
 
 | Property | Description |
-|:--- |:--- |
+|---|---|
 | Layout invalidated | For Layout records, the stack trace of the code that caused the layout to be invalidated. |
 | Nodes that need layout | For Layout records, the number of nodes that were marked as needing layout before the relayout started.  These are normally those nodes that were invalidated by developer code, plus a path upward to relayout root. |
 | Layout tree size | For Layout records, the total number of nodes under the relayout root (the node that Microsoft Edge starts the relayout). |
@@ -148,7 +148,7 @@ See also [Properties common to all events](#properties-common-to-all-events), ab
 The following events are in the **Painting** category.
 
 | Event | Description |
-|:--- |:--- |
+|---|---|
 | Composite Layers | The composited image layers for the Microsoft Edge rendering engine. |
 | Image Decode | An image resource was decoded. |
 | Image Resize | An image was resized from its native dimensions. |
@@ -159,7 +159,7 @@ The following events are in the **Painting** category.
 #### Additional properties for Painting events
 
 | Property | Description |
-|:--- |:--- |
+|---|---|
 | Location | For Paint events, the x and y coordinates of the paint rectangle. |
 | Dimensions | For Paint events, the height and width of the painted region. |
 
diff --git a/microsoft-edge/devtools/performance/reference.md b/microsoft-edge/devtools/performance/reference.md
index cc6a30f1f3..dbbc3a1983 100644
--- a/microsoft-edge/devtools/performance/reference.md
+++ b/microsoft-edge/devtools/performance/reference.md
@@ -1123,7 +1123,7 @@ To view WebSocket messages in the **Performance** tool:
    At the bottom of the chat form, a message is displayed, such as "John:v8g... connected."
 
 1. In the **Send a message** text box, enter a message, such as "Hello", and then click the **Send** button.
- 
+
    In the chat app, the message is displayed, such as "Hello":
 
    ![WebSocket messages in the Performance tool](./reference-images/websocket-messages.png)
diff --git a/microsoft-edge/devtools/performance/selector-stats.md b/microsoft-edge/devtools/performance/selector-stats.md
index 3c754c77d3..7fef1dc335 100644
--- a/microsoft-edge/devtools/performance/selector-stats.md
+++ b/microsoft-edge/devtools/performance/selector-stats.md
@@ -47,7 +47,7 @@ To record a performance trace with selector statistics:
 1. Select the **Enable CSS selector stats (slow)** checkbox:
 
    ![The "Enable CSS selector stats" checkbox in the Performance tool](./selector-stats-images/enable-feature.png)
- 
+
 1. Click the **Record** (![The Record icon](./selector-stats-images/record-icon.png)) button, and then run the scenario that you want to improve for your website or app.
 
 1. Click the **Stop** button.
@@ -81,7 +81,7 @@ The **Selector Stats** tab in the **Performance** tool contains a table of CSS s
 | **Match Count** | The number of elements the browser engine matched with this CSS selector. |
 | **% of slow-path non-matches** | The ratio of elements that didn't match with this CSS selector, to the elements that the browser engine attempted to match, and which required the browser engine to use less optimized code to match. |
 | **Selector** | The CSS selector that was matched. |
-| **Style Sheet** | The CSS style sheet that contains the CSS selector. | 
+| **Style Sheet** | The CSS style sheet that contains the CSS selector. |
 
 When finished, in the **Performance** tool, click the **Capture settings** (![Capture settings icon](./selector-stats-images/capture-settings-icon.png)) button, and then clear the **Enable CSS selector stats (slow)** checkbox.
 
diff --git a/microsoft-edge/devtools/performance/share-performance-traces.md b/microsoft-edge/devtools/performance/share-performance-traces.md
index d37b9bd9c0..892e41390e 100644
--- a/microsoft-edge/devtools/performance/share-performance-traces.md
+++ b/microsoft-edge/devtools/performance/share-performance-traces.md
@@ -150,7 +150,7 @@ See also:
 <!-- ====================================================================== -->
 ## Compress with gzip
 
-In the **Save performance trace** dialog within the **Performance** tool, the **Compress with gzip** checkbox is selected by default.  This option helps compress large performance traces to save disk space, and makes the importing and processing of trace files faster in DevTools. 
+In the **Save performance trace** dialog within the **Performance** tool, the **Compress with gzip** checkbox is selected by default.  This option helps compress large performance traces to save disk space, and makes the importing and processing of trace files faster in DevTools.
 
 * If this checkbox is selected, the default file name extension is `.gz`.
 * If this checkbox is cleared, the default file name extension is `.json`.
@@ -195,7 +195,7 @@ To open a saved trace file in DevTools:
    * **Rendering**
    * **Search**
    * **Sensors**
-    
+
 See also:
 * [Performance tool: Analyze your website's performance](./overview.md)
 * [Sources tool overview](../sources/index.md)
diff --git a/microsoft-edge/devtools/performance/unminify.md b/microsoft-edge/devtools/performance/unminify.md
index 194f1eba49..5eaf377ec8 100644
--- a/microsoft-edge/devtools/performance/unminify.md
+++ b/microsoft-edge/devtools/performance/unminify.md
@@ -11,9 +11,9 @@ ms.date: 03/08/2022
 # Display original function names in performance profiles
 
 If your build process compiles and minifies your code and combines it into a single file, the names of the functions displayed in a performance profile might be hard to understand.  Source maps map your compiled, minified code to your original source code files.  The **Performance** tool can use source maps to map minified function names after a recording has been made, back to their original names found in your original code.
-   
+
 To learn more about how DevTools uses source maps, see [Map the processed code to your original source code, for debugging](../javascript/source-maps.md).
-   
+
 To see your original function names in the flame chart in the **Performance** tool, use the **Unminify** (![The Unminify button icon](./unminify-images/unminify-icon.png)) button.
 
 Source mapping is used in DevTools to keep your client-side code readable and debuggable.  By clicking the **Unminify** button in the Performance tool, you can use source maps to create an unminified version of the performance profile you recorded.
@@ -26,7 +26,7 @@ An example of a performance profile flame chart, with some more meaningful funct
 
 ![The unminified flame chart in the performance profile, with meaningful function names restored](./unminify-images/unminified-perf-profile.png)
 
-When recording a performance profile in the **Performance** tool, the **Main** section of the profile displays detailed flame charts of JavaScript functions that were called during the recording.  
+When recording a performance profile in the **Performance** tool, the **Main** section of the profile displays detailed flame charts of JavaScript functions that were called during the recording.
 
 Ideally, in this flame chart view, you want to see the meaningful function names that are shown in your original source code.  However, if your production code is compiled, minified, or bundled, the **Performance** tool initially displays the function names that are extracted from your transformed, _production_ code.  These production function names might be obscure and might not easily map to function names in your original source code.
 
diff --git a/microsoft-edge/devtools/progressive-web-apps/protocol-handlers.md b/microsoft-edge/devtools/progressive-web-apps/protocol-handlers.md
index a0ee2d68db..617efa77e8 100644
--- a/microsoft-edge/devtools/progressive-web-apps/protocol-handlers.md
+++ b/microsoft-edge/devtools/progressive-web-apps/protocol-handlers.md
@@ -10,7 +10,7 @@ ms.date: 08/23/2022
 ---
 # Test Progressive Web App (PWA) protocol handling
 
-This article assumes that you have already defined protocol handlers in your PWA web app manifest and are debugging your app with the DevTools.  To learn about how to define and register protocols in your PWA, see [Handle protocols in a PWA](../../progressive-web-apps/how-to/handle-protocols.md).  
+This article assumes that you have already defined protocol handlers in your PWA web app manifest and are debugging your app by using DevTools.  To learn about how to define and register protocols in your PWA, see [Handle protocols in a PWA](../../progressive-web-apps/how-to/handle-protocols.md).
 
 Use the **Application** tool to verify and test that Microsoft Edge has successfully registered your app as a handler for protocols defined in your web app manifest.
 
@@ -27,45 +27,59 @@ If you have defined protocols correctly in your web app manifest, the **Applicat
 
 To verify that you have correctly defined protocol handlers:
 
-1. Navigate to your PWA in Microsoft Edge. You can use [the PWAmp demo application](https://microsoftedge.github.io/Demos/pwamp/).
+1. In Microsoft Edge, go to your PWA.  You can use [the PWAmp demo application](https://microsoftedge.github.io/Demos/pwamp/).
+
 1. Open DevTools (**F12**).
-1. Open the **Application** tool.
-1. Click **Manifest** to expand the dropdown list.
-1. Click **Protocol Handlers**.
 
-If protocol handlers haven't been defined in the web app manifest, or have been defined incorrectly, the following message is displayed:
+1. In the **Activity Bar**, select the **Application** tool.
+
+1. In the tree on the left, expand **Manifest**, and then select **Protocol Handlers**.
+
+   The **Manifest** page scrolls down to the **Protocol Handlers** section.
 
-![The Protocol Handlers section of the Manifest pane without protocols defined](./protocol-handlers-images/protocol-handlers-not-defined.png)
+   * If protocol handlers have not been defined in the web app manifest, or have been defined incorrectly, the following message is displayed: "Define protocol handlers in the manifest to register your app as a handler for custom protocols when your app is installed."
 
-If protocol handlers have been defined successfully in the web app manifest, the following message is displayed:
+      ![Protocol Handlers section, without protocols defined](./protocol-handlers-images/protocol-handlers-not-defined.png)
 
-![The Protocol Handlers section of the Manifest pane with protocols defined](./protocol-handlers-images/protocol-handlers-defined.png)
+   * If protocol handlers have been defined successfully in the web app manifest, the following message is displayed: "Found valid protocol handler registration in the manifest.  With the app installed, test the registered protocols."
 
-The **Protocol Handlers** section also makes it possible to test the protocol handlers you've defined.
+      ![Protocol Handlers section, with protocols defined](./protocol-handlers-images/protocol-handlers-defined.png)
 
 
 <!-- ====================================================================== -->
 ## Test protocols from the Application tool
 
-To test your protocol handlers from the **Application** tool, you must have already installed your PWA.  To learn how to install your PWA, see [Installing a PWA](../../progressive-web-apps/ux.md#installing-a-pwa).
+To test protocol handlers that you've defined, use the **Application** tool > **Manifest** page > **Protocol Handlers** section.
+
+To test your protocol handlers from the **Application** tool, you must first install your PWA; see [Installing a PWA](../../progressive-web-apps/ux.md#installing-a-pwa) in _Use Progressive Web Apps (PWAs) in Microsoft Edge_.
 
 The **Application** tool detects all the protocol handlers from your web app manifest.
 
-To test a handler:
+To test a protocol handler:
 
-1. Navigate to your PWA in Microsoft Edge and open DevTools (**F12**). You can use [the PWAmp demo application](https://microsoftedge.github.io/Demos/pwamp/).
+1. Open a PWA in Microsoft Edge.  You can use [the PWAmp demo application](https://microsoftedge.github.io/Demos/pwamp/).
 
-1. Open the **Application** tool and click **Manifest** > **Protocol Handlers**.
+1. Install the PWA; see [Installing a PWA](../../progressive-web-apps/ux.md#installing-a-pwa) in _Use Progressive Web Apps (PWAs) in Microsoft Edge_.
 
-1. Select the protocol you want to test by choosing from the dropdown list.
+1. Open DevTools (**F12**).
 
-1. Enter the rest of the URI in the text and click **Test protocol**.
+1. In the **Activity Bar**, select the **Application** tool.
 
-   Your PWA is launched.  Depending on your operating system (OS), you might need to allow Microsoft Edge to open your PWA and accept any OS-level permissions for registering your app as a handler for your protocol.
+1. In the tree on the left, expand **Manifest**, and then select **Protocol Handlers**.
 
-In the following screenshot, the URI `web+amp://files.freemusicarchive.org/storage-freemusicarchive-org/music/no_curator/Kevin_MacLeod/Jazz_Sampler/Kevin_MacLeod_-_AcidJazz.mp3` is being tested:
+   The **Manifest** page scrolls down to the **Protocol Handlers** section.
 
-![Testing the custom web+amp protocol from the Application tool](./protocol-handlers-images/test-protocol-handlers.png)
+1. In the dropdown list, select the protocol to test.
+
+1. Enter the rest of the URI in the text box, and then click the **Test protocol** button:
+
+   ![Testing the custom web+amp protocol from the Application tool](./protocol-handlers-images/test-protocol-handlers.png)
+
+   In the above example, the following URI is being tested:
+
+   `web+amp://files.freemusicarchive.org/storage-freemusicarchive-org/music/no_curator/Kevin_MacLeod/Jazz_Sampler/Kevin_MacLeod_-_AcidJazz.mp3`
+
+   Your PWA is launched.  Depending on your operating system (OS), you might need to allow Microsoft Edge to open your PWA and accept any OS-level permissions for registering your app as a handler for your protocol.
 
 
 <!-- ====================================================================== -->
diff --git a/microsoft-edge/devtools/progressive-web-apps/simulate-window-controls-overlay.md b/microsoft-edge/devtools/progressive-web-apps/simulate-window-controls-overlay.md
index e46af05364..1ba6e04e25 100644
--- a/microsoft-edge/devtools/progressive-web-apps/simulate-window-controls-overlay.md
+++ b/microsoft-edge/devtools/progressive-web-apps/simulate-window-controls-overlay.md
@@ -40,7 +40,7 @@ To simulate the WCO feature for Windows, Linux, and macOS in your PWA without ha
 
 1. In the **Window Controls Overlay** section on the right, select the checkbox **Emulate the Window Controls Overlay on** \<platform\>, and then select a platform, such as Windows, macOS, or Linux.
 
-   The simulated Window Controls Overlay is added to the rendered webpage: 
+   The simulated Window Controls Overlay is added to the rendered webpage:
 
    ![Overlay of window controls in upper right of demo webpage](./simulate-window-controls-overlay-images/demo-with-overlay.png)
 
diff --git a/microsoft-edge/devtools/quick-source/quick-source-tool.md b/microsoft-edge/devtools/quick-source/quick-source-tool.md
index 0cee503e02..9cd520ac13 100644
--- a/microsoft-edge/devtools/quick-source/quick-source-tool.md
+++ b/microsoft-edge/devtools/quick-source/quick-source-tool.md
@@ -133,7 +133,7 @@ Continue with the next section.
    cd ~/GitHub/demos/demo-to-do
    python -m SimpleHTTPServer  # Python 2
    ```
-  
+
    ``` bash
    # Python 3 option
    cd ~/GitHub/demos/demo-to-do
diff --git a/microsoft-edge/devtools/recorder/index.md b/microsoft-edge/devtools/recorder/index.md
index 2fc3d4e8ed..63d3935c5f 100644
--- a/microsoft-edge/devtools/recorder/index.md
+++ b/microsoft-edge/devtools/recorder/index.md
@@ -64,7 +64,7 @@ To start recording a new user flow:
 <!-- ====================================================================== -->
 ## Record other user flows
 
-To record a new user flow, after you've stopped the recording of the previous user flow: 
+To record a new user flow, after you've stopped the recording of the previous user flow:
 
 1. Click the **Create a new recording** (![Create a new recording button](./index-images/new-recording-icon.png)) button in the top-left corner of the **Recorder** tool:
 
@@ -205,7 +205,7 @@ To change the type of step when editing the details of a step:
 You can use the following types of steps when editing a step in a user flow.  Each step type has a list of properties that apply to the step.
 
 | Step type | Description | Properties |
-|:--- |:--- |:--- |
+|---|---|---|
 | `change` | Change the value of a form input field. | **selectors**: Ways to find the element that this step applies to. <br/>**value**: The value to set the form input field to. |
 | `click` | Click an element. | **selectors**: Ways to find the element this step applies to. <br/>**offsetX**/**offsetY**: How far from the top left corner of the element to click. |
 | `close` | Close the browser window. | None. |
@@ -313,7 +313,7 @@ To generate a test script and run it automatically with a test automation framew
    ![The Export button dropdown menu and the various test automation formats](./index-images/export-for-test.png)
 
    | Export format | Test automation framework |
-   |:--- |:--- |
+   |---|---|
    | `@puppeteer/replay` | Exports the user flow as a test script for the **Replay** library.  See the [puppeteer / replay](https://github.com/puppeteer/replay) repo. |
    | Puppeteer | Exports the user flow as a test script for the Puppeteer test automation framework.  See [Puppeteer](https://pptr.dev). |
    | Puppeteer (including Lighthouse analysis) | Exports the user flow as a test script for the Puppeteer test automation framework, and includes a Lighthouse analysis of the performance of the website. |
diff --git a/microsoft-edge/devtools/remote-debugging/windows.md b/microsoft-edge/devtools/remote-debugging/windows.md
index f86a2393d7..9c4bc6510b 100644
--- a/microsoft-edge/devtools/remote-debugging/windows.md
+++ b/microsoft-edge/devtools/remote-debugging/windows.md
@@ -34,9 +34,9 @@ To set up the host (debuggee) machine, use the following sub-sections, in order.
 
 1. If not already installed, on the Windows 10 or later device that you want to debug, install Microsoft Edge, from [Get to Know Microsoft Edge](https://www.microsoft.com/edge).
 
-1. If you're using a pre-installed version of Microsoft Edge on the host (debuggee) machine, verify that you have Microsoft Edge (Chromium) and not Microsoft Edge (EdgeHTML).  A quick way to check is to load `edge://settings/help` in the browser and confirm that the version number is 75 or higher.
+1. If you're using a pre-installed version of Microsoft Edge on the host (debuggee) machine, verify that you have Microsoft Edge (Chromium) and not Microsoft Edge (EdgeHTML).  A quick way to check is to load `edge://settings/help` in the browser and confirm that the version number is 75 or higher.<!-- todo: delete para --><!-- todo: global in repo, scrub "EdgeHTML" -->
 
-1. Go to `edge://flags` in Microsoft Edge. 
+1. In Microsoft Edge, go to `edge://flags`.
 
 1. In **Search flags**, type in **Enable remote debugging through Windows Device Portal**. Set that flag to **Enabled**. Then, click the **Restart** button to restart Microsoft Edge.
 
@@ -80,7 +80,7 @@ To set up the host (debuggee) machine, use the following sub-sections, in order.
 
    ![Note the IP address and connection port in the Settings](./windows-images/remote-debugging-windows-media-host-settings-ip-address.png)
 
-   You enter the information on the client (debugger) device in the next section, "Step 2: Set up the client (debugger machine)".  
+   You enter the information on the client (debugger) device in the next section, "Step 2: Set up the client (debugger machine)".
 
 1. Open tabs in Microsoft Edge and [Progressive Web Apps (PWAs)](../progressive-web-apps/index.md) on the host (debuggee) machine that you want to debug from the client (debugger) machine.
 
@@ -132,7 +132,7 @@ To see the default ports that are used by Device Portal, see the table in [Setup
 <!-- ---------- -->
 ###### Default ports
 
-The default port for `http` is `50080` and the default port for `https` is `50043`, but this isn't always the case, because Device Portal on desktop claims ports in the ephemeral range (\>50,000) to prevent collisions with existing port claims on the device.  
+The default port for `http` is `50080` and the default port for `https` is `50043`, but this isn't always the case, because Device Portal on desktop claims ports in the ephemeral range (\>50,000) to prevent collisions with existing port claims on the device.
 
 To see the default ports that are used by Device Portal, see the table in [Setup](/windows/uwp/debug-test-perf/device-portal#setup) in _Windows Device Portal overview_.
 
diff --git a/microsoft-edge/devtools/rendering-tools/index.md b/microsoft-edge/devtools/rendering-tools/index.md
index e8318021de..3e371b8377 100644
--- a/microsoft-edge/devtools/rendering-tools/index.md
+++ b/microsoft-edge/devtools/rendering-tools/index.md
@@ -64,7 +64,7 @@ If you notice quite a bit of jank (interruptions of rendering) in your JavaScrip
 The following are common JavaScript problems and potential solutions.
 
 | Problem | Example | Solution |
-|:--- |:--- |:--- |
+|---|---|---|
 | Expensive input handlers affecting response or animation. | Touch, parallax scrolling. | Let the browser handle touch and scrolls, or bind the listener as late as possible.  See [Expensive Input Handlers](https://calendar.perfplanet.com/2013/the-runtime-performance-checklist/#7_expensive_input_handlers) in _The Runtime Performance Checklist_ by Paul Lewis. |
 | Badly timed JavaScript affecting response, animation, load. | User scrolls right after page load, setTimeout / setInterval. | Optimize JavaScript runtime: use `requestAnimationFrame`, spread DOM manipulation over frames, use Web Workers; see [Using Web Workers](https://developer.mozilla.org/docs/Web/API/Web_Workers_API/Using_web_workers). |
 | Long-running JavaScript affecting response. | The [DOMContentLoaded event](https://developer.mozilla.org/docs/Web/API/Document/DOMContentLoaded_event) stalls, because it's swamped with JavaScript work. | Move pure computational work to Web Workers; see [Using Web Workers](https://developer.mozilla.org/docs/Web/API/Web_Workers_API/Using_web_workers).  If you need DOM access, use `requestAnimationFrame`.  <!-- See [Optimize JavaScript Execution](/web/fundamentals/performance/rendering/optimize-javascript-execution). --> |
@@ -108,7 +108,7 @@ To reduce the impact of `Recalculate Style` events, minimize use of CSS properti
 The following table describes some common style problems and potential solutions.
 
 | Problem | Example | Solution |
-|:--- |:--- |:--- |
+|---|---|---|
 | Expensive style calculations affecting response or animation. | Any CSS property that changes the geometry of an element, like the width, height, or position; the browser checks all other elements and recalculates the layout. | Avoid CSS that triggers layouts. |
 | Complex selectors affecting response or animation. | Nested selectors force the browser to know everything about all the other elements, including parents and children. | Reference an element in your CSS with just a class. |
 
@@ -155,7 +155,7 @@ The **Performance** pane identifies when a page causes forced synchronous layout
 The following table describes some common layout problems and potential solutions.
 
 | Problem | Example | Solution |
-|:--- |:--- |:--- |
+|---|---|---|
 | Forced synchronous layout affecting response or animation. | Forcing the browser to perform layout earlier in the pixel pipeline, resulting in repeating steps in the rendering process. | Batch your style reads first, then do any writes.  <!-- See [Avoid large, complex layouts and layout thrashing](/web/fundamentals/performance/rendering/avoid-large-complex-layouts-and-layout-thrashing). --> |
 | Layout thrashing affecting response or animation. | A loop that puts the browser into a read-write-read-write cycle, forcing the browser to recalculate layout over and over again. | Automatically batch read-write operations using [FastDom library](https://github.com/wilsonpage/fastdom). |
 
@@ -200,7 +200,7 @@ The Timeline Tool page is deprecated.
 The following table describes some common paint and composite problems and potential solutions.
 
 | Problem | Example | Solution |
-|:--- |:--- |:--- |
+|---|---|---|
 | Paint storms affecting response or animation. | Big paint areas or expensive paints affecting response or animation. | Avoid paint, promote elements that are moving to their own layer, use transforms and opacity.  <!-- See [Simplify paint complexity and reduce paint areas](/web/fundamentals/performance/rendering/simplify-paint-complexity-and-reduce-paint-areas). --> |
 | Layer explosions affecting animations. | Overpromotion of too many elements with `translateZ(0)` greatly affects animation performance. | Promote to layers sparingly, and only when you know it offers tangible improvements.  <!-- See [Stick to composite-only properties and manage layer count](/web/fundamentals/performance/rendering/stick-to-compositor-only-properties-and-manage-layer-count). --> |
 
diff --git a/microsoft-edge/devtools/rendering-tools/js-runtime.md b/microsoft-edge/devtools/rendering-tools/js-runtime.md
index cd053f4774..4fd68c0f79 100644
--- a/microsoft-edge/devtools/rendering-tools/js-runtime.md
+++ b/microsoft-edge/devtools/rendering-tools/js-runtime.md
@@ -136,9 +136,9 @@ After you record a memory allocation sampling profile, view the recording as a f
 The flame chart is split into two parts:
 
 | index | Part | Description |
-| --- |:--- |:--- |
-| 1 | Overview | A birds-eye view of the entire recording.  The height of the bars correspond to the depth of the call stack.  So, the higher the bar, the deeper the call stack.  |
-| 2 | Call Stacks | This is an in-depth view of the functions that were called during the recording.  The horizontal axis is time and vertical axis is the call stack.  The stacks are organized top-down.  So, the function on top called the one below it, and so on.  |
+|---|---|---|
+| 1 | Overview | A bird's-eye view of the entire recording.  The height of the bars correspond to the depth of the call stack.  So, the higher the bar, the deeper the call stack. |
+| 2 | Call Stacks | This is an in-depth view of the functions that were called during the recording.  The horizontal axis is time and vertical axis is the call stack.  The stacks are organized top-down.  So, the function on top called the one below it, and so on. |
 
 Functions are colored randomly.  There is no correlation to the colors used in the other panels.  However, functions are always colored the same across invocations, so that you can observe patterns in each runtime.
 
@@ -163,11 +163,11 @@ Click a function, to view it in the **Sources** tool.
 Hover on a function to display the name and timing data:
 
 | Detail | Description |
-|:--- |:--- |
-| **Name** | The name of the function.  |
-| **Self size** | The size of the current invocation of the function, including only the statements in the function.  |
-| **Total size** | The size of the current invocation of this function and any functions that it called.  |
-| **URL** | The location of the function definition in the form of `base.js:261` where `base.js` is the name of the file where the function is defined and `261` is the line number of the definition.  |
+|---|---|
+| **Name** | The name of the function. |
+| **Self size** | The size of the current invocation of the function, including only the statements in the function. |
+| **Total size** | The size of the current invocation of this function and any functions that it called. |
+| **URL** | The location of the function definition in the form of `base.js:261` where `base.js` is the name of the file where the function is defined and `261` is the line number of the definition. |
 <!--* **Aggregated self time**.  Aggregate time for all invocations of the function across the recording, not including functions called by this function.  -->
 <!--* **Aggregated total time**.  Aggregate total time for all invocations of the function, including functions called by this function.  -->
 <!--* **Not optimized**.  If the profiler has detected a potential optimization for the function it lists it here.  -->
@@ -178,7 +178,7 @@ Hover on a function to display the name and timing data:
 <!-- ====================================================================== -->
 ## Investigate memory allocation, with reduced garbage ("Include objects" checkboxes)
 
-By default, the **Allocation sampling** profiling type only reports allocations that are still alive at the end of the recording session.  Objects that are created, removed, and then garbage collected (GC'd) aren't displayed in the **Memory** tool when profiling using the **Allocation sampling** or **Allocations on timeline** profiling types.
+By default, the **Allocation sampling** profiling type only reports allocations that are still alive at the end of the recording session.  Objects that are created, removed, and then garbage-collected (GC'd) aren't displayed in the **Memory** tool when profiling using the **Allocation sampling** or **Allocations on timeline** profiling types.
 
 You can trust the browser to clean up garbage from your code.  However, it is important to consider that GC itself is an expensive operation and multiple GCs can slow down your user's experience of your website or app.  When recording in the **Performance** tool with the **Memory** checkbox turned on, you can see the GC operation happen at the steep cliffs (sudden decreases) in the heap chart:
 
@@ -204,7 +204,7 @@ To track objects that are discarded by garbage collection:
 
 1. Click the **Stop** button when you have finished all of your actions.
 
-DevTools now tracks all of the objects that were GC'd during the recording.  Use these settings to understand how much garbage your website or app is generating.  The data reported by **Allocation sampling** will help you identify the functions that are generating the most garbage.  
+DevTools now tracks all of the objects that were garbage-collected (GC'd) during the recording.  Use these settings to understand how much garbage your website or app is generating.  The data reported by **Allocation sampling** will help you identify the functions that are generating the most garbage.
 
 If you are investigating objects that were only GC'd during specific major or minor GC operations, configure the settings appropriately to track the operation you care about. To learn more about the differences between major and minor GC, see [Trash talk: the Orinoco garbage collector | V8 JavaScript engine developer blog](https://v8.dev/blog/trash-talk).
 
diff --git a/microsoft-edge/devtools/resources/index.md b/microsoft-edge/devtools/resources/index.md
index 3aa69b3b9b..a8686b5389 100644
--- a/microsoft-edge/devtools/resources/index.md
+++ b/microsoft-edge/devtools/resources/index.md
@@ -191,7 +191,7 @@ One way to view webpage resources grouped by file type is by using the **Frames*
 1. In DevTools, on the **Activity Bar**, select the **Application** tab.  If that tab isn't visible, click the **More Tools** (![The More Tools icon](./index-images/more-tools-icon-light-theme.png)) button.
 
    The **Application** tool opens and by default shows the **Manifest** pane first:
-   
+
    ![The Application tool](./index-images/application-mainfest.png)
 
 1. Scroll down to the **Frames** pane and then expand the folder that you're interested in:
diff --git a/microsoft-edge/devtools/samples/index.md b/microsoft-edge/devtools/samples/index.md
index b36588184c..3c11368afb 100644
--- a/microsoft-edge/devtools/samples/index.md
+++ b/microsoft-edge/devtools/samples/index.md
@@ -225,7 +225,7 @@ If you want to just download the Demos repo instead of cloning it:
 
 To download a single directory of the Demos repo:
 
-1. Go to [https://download-directory.github.io/](https://download-directory.github.io/) and then paste the URL [https://github.com/MicrosoftEdge/Demos/tree/main/demo-to-do](https://github.com/MicrosoftEdge/Demos/tree/main/demo-to-do).  
+1. Go to [https://download-directory.github.io/](https://download-directory.github.io/) and then paste the URL [https://github.com/MicrosoftEdge/Demos/tree/main/demo-to-do](https://github.com/MicrosoftEdge/Demos/tree/main/demo-to-do).
 
    The `.zip` file is placed in your download directory.  Unzip these webpage source files into a suitable location.
 
diff --git a/microsoft-edge/devtools/sensors/index.md b/microsoft-edge/devtools/sensors/index.md
index fc2cbbb3ed..b4ef4dee9e 100644
--- a/microsoft-edge/devtools/sensors/index.md
+++ b/microsoft-edge/devtools/sensors/index.md
@@ -98,9 +98,9 @@ To override your geolocation, [open the Sensors tool](#open-the-sensors-tool) an
 <!-- https://developer.chrome.com/docs/devtools/sensors#orientation -->
 
 Mobile devices have sensors which can detect their physical orientation.  Websites such as web-based games or mapping applications can make use of the device orientation to provide a better experience.  To learn about how to detect the device orientation, see [Device orientation events](https://developer.mozilla.org/docs/Web/API/Device_orientation_events), at MDN.
-    
+
 If you're building a UI that changes depending on the orientation of the user's device, you need to test your UI under different device orientations.
-    
+
 To simulate different device orientations, [open the Sensors tool](#open-the-sensors-tool), and then, from the **Orientation** list, select one of the following:
 
 * One of the preset orientations, like **Portrait upside down**:
@@ -242,7 +242,7 @@ To emulate CPU pressure on your website:
 
    The **Sensors** tool opens in the **Quick View** panel at the bottom of DevTools.
 
-1. In the **Sensors** tool, scroll down to the **CPU pressure** section, and then select one of the [human-readable pressure states](https://developer.mozilla.org/docs/Web/API/Compute_Pressure_API#pressure_states): 
+1. In the **Sensors** tool, scroll down to the **CPU pressure** section, and then select one of the [human-readable pressure states](https://developer.mozilla.org/docs/Web/API/Compute_Pressure_API#pressure_states):
 
    * **No override**
    * **Nominal**
@@ -272,7 +272,7 @@ MDN:
    * [Pressure states](https://developer.mozilla.org/docs/Web/API/Compute_Pressure_API#pressure_states) in _Compute Pressure API_.
 
 Demos:
-* [TODO app](https://microsoftedge.github.io/Demos/demo-to-do/) 
+* [TODO app](https://microsoftedge.github.io/Demos/demo-to-do/)
 * [Idle detection demo](https://microsoftedge.github.io/Demos/idle-detection/)
 
 Emscripten:
diff --git a/microsoft-edge/devtools/sources/index.md b/microsoft-edge/devtools/sources/index.md
index e14205abd7..cd40432007 100644
--- a/microsoft-edge/devtools/sources/index.md
+++ b/microsoft-edge/devtools/sources/index.md
@@ -170,7 +170,7 @@ To change how resources are grouped:
 
 Use the **Workspace** tab in the **Sources** tool to view and edit local files in DevTools.  The **Workspace** tab is useful when used in conjunction with a local web server as you can then load your local website in Edge, and edit its source files in DevTools.
 
-When you add a folder to the **Workspace** tab, the files and subfolders in that folder are displayed in the tab, and you can open files to view and edit them. 
+When you add a folder to the **Workspace** tab, the files and subfolders in that folder are displayed in the tab, and you can open files to view and edit them.
 
 The **Workspace** tab does not show the resources that the browser downloaded to display the webpage; the **Workspace** tab only shows the folders and files that are inside the local folders that you added.
 
@@ -407,7 +407,7 @@ After submitting the form, `console.log('A')`, which is at global scope, doesn't
 
 Minified files are automatically reformatted when you open them in the Editor pane.
 
-To revert the file to its original minified state, click the **Pretty print** button (![Format](./index-images/format-icon.png)), which is shown as braces, at the bottom of the Editor pane. 
+To revert the file to its original minified state, click the **Pretty print** button (![Format](./index-images/format-icon.png)), which is shown as braces, at the bottom of the Editor pane.
 
 ![The Pretty print button](./index-images/minified.png)
 
diff --git a/microsoft-edge/devtools/sources/opening-sources-in-vscode.md b/microsoft-edge/devtools/sources/opening-sources-in-vscode.md
index 7a4d986a01..c5afee544f 100644
--- a/microsoft-edge/devtools/sources/opening-sources-in-vscode.md
+++ b/microsoft-edge/devtools/sources/opening-sources-in-vscode.md
@@ -26,7 +26,7 @@ With this experiment enabled, suppose that in Microsoft Edge, you go to a local
 ![Microsoft Edge with a local file open](./opening-sources-in-vscode-images/local-project.png)
 
 <!-- todo:
-instead of using 
+instead of using:
 https://github.com/codepo8/simple-to-do
 use:
 https://github.com/MicrosoftEdge/Demos/tree/main/demo-to-do
diff --git a/microsoft-edge/devtools/speed/get-started.md b/microsoft-edge/devtools/speed/get-started.md
index a6146f89f8..f6ad6a2266 100644
--- a/microsoft-edge/devtools/speed/get-started.md
+++ b/microsoft-edge/devtools/speed/get-started.md
@@ -45,7 +45,7 @@ The **Lighthouse** tool provides links to content that's hosted on third-party w
 
 In this tutorial, you improve the performance of [Margie's travel](https://microsoftedge.github.io/Demos/travel-site/), a fictitious travel website that contains travel images, text descriptions, a few JavaScript-based user interactions, and an interactive map.
 
-The source files for the website are at [MicrosoftEdge / Demos > travel-site](https://github.com/MicrosoftEdge/Demos/tree/main/travel-site). 
+The source files for the website are at [MicrosoftEdge / Demos > travel-site](https://github.com/MicrosoftEdge/Demos/tree/main/travel-site).
 
 
 <!-- next two sections are reverse order vs upstream -->
@@ -342,18 +342,18 @@ Use the Intersection Observer API to detect when the map becomes visible to the
 
     const mapElIntersectionObserver = new IntersectionObserver(loadMapOnDemand);
     mapElIntersectionObserver.observe(MAP_CONTAINER_EL);
- 
+
     let map = null;
-   
+
     function loadMapOnDemand(entries) {
        if (map) {
          return;
        }
-   
+
        if (!entries.some(entry => entry.isIntersecting)) {
          return;
        }
-   
+
        const script = document.createElement('script');
        script.type = 'text/javascript';
        script.src = 'https://www.bing.com/api/maps/mapcontrol?callback=GetMap&key=Ap_eazGgpq5468v9MXr7Wu0zh30LQActgaT-tI_QxZQSm-Bd5qJxVKs_2B7NsqR4';
@@ -406,7 +406,7 @@ The first task, then, is to find code that you don't need to run on page load.
 
    ![The contact-form.css file in the Sources tool, with red bars next to the unused lines](./get-started-images/unused-css-source.png)
 
-   Only red bars are displayed in this source file, which means that the webpage doesn't need this file at all. 
+   Only red bars are displayed in this source file, which means that the webpage doesn't need this file at all.
 
 Now, remove the references to these files from the code:
 
@@ -519,7 +519,7 @@ Your latest report shows high **Time to Interactive** and **Total Blocking Time*
 Scroll down to the **Diagnostics** section which says to **Minimize main-thread work** and **Reduce JavaScript execution time**. The main thread is where the browser does most of the work that's needed to display a page, such as:
 
 * Parsing and running HTML.
-* Parsing and applying CSS to DOM elements. 
+* Parsing and applying CSS to DOM elements.
 * Running JavaScript.
 
 In this case, it looks like the biggest bottleneck is that the page runs too much JavaScript code on page load.
diff --git a/microsoft-edge/devtools/storage/application-tool.md b/microsoft-edge/devtools/storage/application-tool.md
index 5a1ab5b11b..9beeb68cd6 100644
--- a/microsoft-edge/devtools/storage/application-tool.md
+++ b/microsoft-edge/devtools/storage/application-tool.md
@@ -48,7 +48,7 @@ The **Application** tool has the following pages, listed on the left:
    * Preloads
    * This page
 
-* Frames 
+* Frames
    * top
 
 To interpret the **Storage** > **Usage** section in the **Application** tool, see [Storage quotas and eviction criteria](https://developer.mozilla.org/docs/Web/API/Storage_API/Storage_quotas_and_eviction_criteria) at MDN.
diff --git a/microsoft-edge/devtools/storage/cache.md b/microsoft-edge/devtools/storage/cache.md
index 0bc4003810..023dab1232 100644
--- a/microsoft-edge/devtools/storage/cache.md
+++ b/microsoft-edge/devtools/storage/cache.md
@@ -88,7 +88,7 @@ To learn more about cache data storage quota, see [Storage quotas and eviction c
 1. Click the resource that you want to delete.  DevTools highlights it to indicate that it is selected.
 
 1. Click **Delete Selected** (![Delete Selected](./cache-images/delete-icon.png)):
-   
+
    ![Selecting a resource to delete](./cache-images/delete-selected.png)
 
 
diff --git a/microsoft-edge/devtools/storage/cookies.md b/microsoft-edge/devtools/storage/cookies.md
index fe34baf4cd..be3ab12202 100644
--- a/microsoft-edge/devtools/storage/cookies.md
+++ b/microsoft-edge/devtools/storage/cookies.md
@@ -86,7 +86,7 @@ The **Cookies** table contains the following fields:
 
 * **Partition Key Site**. The _partition key_ of a cookie only exists when the cookie is set in partitioned storage and corresponds to the top-level site where the cookie was initially created. See [Cookies Having Independent Partitioned State (CHIPS)](https://developer.mozilla.org/docs/Web/Privacy/Guides/Privacy_sandbox/Partitioned_cookies) at MDN.
 
-* **Cross Site**. This attribute provides web developers a means to annotate cookies that are allowed to be set or sent in same-party, cross-site contexts. 
+* **Cross Site**. This attribute provides web developers a means to annotate cookies that are allowed to be set or sent in same-party, cross-site contexts.
 
 * **Priority**.  Contains `low`, `medium` (default), or `high` if the cookie is using the deprecated [Cookie Priority](https://bugs.chromium.org/p/chromium/issues/detail?id=232693) attribute.
 
@@ -208,7 +208,7 @@ To view third-party cookies in the **Application** tool:
    A tooltip reads **This attempt to set a cookie via a Set-Cookie header was blocked due to user preferences.**
 
    ![Cookies in Application tool that are blocked have an info icon](./cookies-images/cookie-blocked-application-tool.png)
-  
+
    **Stop blocking third-party cookies:**
 
 1. In Microsoft Edge, select **Settings and more** (![Settings and more icon](./cookies-images/settings-and-more-icon.png)) > **Settings** > **Privacy, search, and services**<!-- edge://settings/privacy -->.
@@ -238,7 +238,7 @@ To view blocked third-party cookies in the **Network** tool:
 
    DevTools opens.
 
-1. Select the **Network** tool. 
+1. Select the **Network** tool.
 
 1. Refresh the page.
 
diff --git a/microsoft-edge/devtools/storage/indexeddb.md b/microsoft-edge/devtools/storage/indexeddb.md
index 436fb1d85b..6c4a3f6137 100644
--- a/microsoft-edge/devtools/storage/indexeddb.md
+++ b/microsoft-edge/devtools/storage/indexeddb.md
@@ -86,7 +86,7 @@ IndexedDB keys and values aren't editable from the **Application** tool.  Howeve
 1. In DevTools, on the **Activity Bar**, select the **Console** tab.
 
 1. In the **Console** tool, run JavaScript code to edit the IndexedDB data. For example, to add a new value to the `keyval` object store, run the following code:
-   
+
    ```javascript
    let connection = indexedDB.open("keyval-store", 1);
 
diff --git a/microsoft-edge/devtools/webauthn/index.md b/microsoft-edge/devtools/webauthn/index.md
index 13099c9e6d..c0a9ad9829 100644
--- a/microsoft-edge/devtools/webauthn/index.md
+++ b/microsoft-edge/devtools/webauthn/index.md
@@ -47,11 +47,11 @@ You can emulate authenticators and debug the [Web Authentication API](https://w3
 1. In the **New authenticator** section, configure the following options:
 
     | Option | Value | Details |
-    |:--- |:--- |:--- |
-    | `Protocol` | [ctap2](https://fidoalliance.org/specs/fido-v2.0-id-20180227/fido-client-to-authenticator-protocol-v2.0-id-20180227.html) or [u2f](https://fidoalliance.org/specs/fido-u2f-v1.2-ps-20170411/fido-u2f-overview-v1.2-ps-20170411.html) | The protocol the virtual authenticator uses for encoding and decoding |
-    | `Transport` |   `usb`, `nfc`, `ble`, or `internal` | The virtual authenticator simulates the selected transport for communicating with clients in order to obtain an assertion for a specific credential.  See [Authenticator Transport Enumeration](https://w3c.github.io/webauthn#enum-transport) |
+    |---|---|---|
+    | `Protocol` | [ctap2](https://fidoalliance.org/specs/fido-v2.0-id-20180227/fido-client-to-authenticator-protocol-v2.0-id-20180227.html) or [u2f](https://fidoalliance.org/specs/fido-u2f-v1.2-ps-20170411/fido-u2f-overview-v1.2-ps-20170411.html) | The protocol the virtual authenticator uses for encoding and decoding. |
+    | `Transport` |   `usb`, `nfc`, `ble`, or `internal` | The virtual authenticator simulates the selected transport for communicating with clients in order to obtain an assertion for a specific credential.  See [Authenticator Transport Enumeration](https://w3c.github.io/webauthn#enum-transport). |
     |  `Supports resident keys` | Turn on (or off) using the checkbox | Turn on if your web app relies on resident keys (also known as client-side discoverable credentials).  See [Resident Key Requirement Enumeration](https://w3c.github.io/webauthn#enum-residentKeyRequirement). |
-    | `Supports user verification` | Turn on (or off) using the checkbox | Turn on if your web app relies on local authorization using gesture modalities like touch plus pin code, password entry, or biometric recognition.  See [User Verification](https://w3c.github.io/webauthn#user-verification) |
+    | `Supports user verification` | Turn on (or off) using the checkbox | Turn on if your web app relies on local authorization using gesture modalities like touch plus pin code, password entry, or biometric recognition.  See [User Verification](https://w3c.github.io/webauthn#user-verification). |
 
 1. Click the **Add** button.
 
diff --git a/microsoft-edge/devtools/whats-new/143.md b/microsoft-edge/devtools/whats-new/143.md
index 12bd642f8a..a7343170a7 100644
--- a/microsoft-edge/devtools/whats-new/143.md
+++ b/microsoft-edge/devtools/whats-new/143.md
@@ -54,7 +54,7 @@ When you export a performance trace, you can choose to include:
 * Resource content (HTML, CSS, and JavaScript content).
 * Script source maps.
 
-You can also choose whether the trace file is compressed. 
+You can also choose whether the trace file is compressed.
 
 Exporting a trace that includes this additional data is useful when sharing traces with others for debugging.
 
diff --git a/microsoft-edge/devtools/whats-new/150.md b/microsoft-edge/devtools/whats-new/150.md
index 0660e0507d..b02ead0372 100644
--- a/microsoft-edge/devtools/whats-new/150.md
+++ b/microsoft-edge/devtools/whats-new/150.md
@@ -11,7 +11,7 @@ ms.date: 07/21/2026
 # What's new in DevTools (Microsoft Edge 150)
 <!-- https://learn.microsoft.com/microsoft-edge/devtools/whats-new/150 -->
 
-These are the latest features in the Stable release of Microsoft Edge DevTools.  
+These are the latest features in the Stable release of Microsoft Edge DevTools.
 
 
 <!-- ====================================================================== -->
diff --git a/microsoft-edge/devtools/whats-new/151.md b/microsoft-edge/devtools/whats-new/151.md
index bd64658363..91dab8ce53 100644
--- a/microsoft-edge/devtools/whats-new/151.md
+++ b/microsoft-edge/devtools/whats-new/151.md
@@ -10,7 +10,7 @@ ms.date: 07/30/2026
 ---
 # What's new in DevTools (Microsoft Edge 151)
 
-These are the latest features in the Stable release of Microsoft Edge DevTools.  
+These are the latest features in the Stable release of Microsoft Edge DevTools.
 
 
 <!-- ====================================================================== -->
diff --git a/microsoft-edge/devtools/whats-new/2019/12/devtools.md b/microsoft-edge/devtools/whats-new/2019/12/devtools.md
index a881cf57f8..b7dadb2bf6 100644
--- a/microsoft-edge/devtools/whats-new/2019/12/devtools.md
+++ b/microsoft-edge/devtools/whats-new/2019/12/devtools.md
@@ -55,34 +55,42 @@ See also:
 
 <!-- dup entries: 2019/12, 2020/01 -->
 
-Many developers use other developer tools, like StackOverflow and Visual Studio Code, in their native language, not just in English.  We're excited to announce localization for the DevTools, which you can now use in one of 10 languages besides English:
-
-* Chinese (Simplified) - &#20013;&#25991;&#65288;&#31616;&#20307;&#65289;
-* Chinese (Traditional) - &#20013;&#25991;&#65288;&#32321;&#39636;&#65289;
-* French – fran&#231;ais
-* German - deutsch
-* Italian - italiano
-* Japanese - &#26085;&#26412;&#35486;
-* Korean - &#54620;&#44397;&#50612;
-* Portuguese - portugu&#234;s
-* Russian – &#1088;&#1091;&#1089;&#1089;&#1082;&#1080;&#1081;
-* Spanish - espa&#241;ol
+Many developers use other developer tools, such as Visual Studio Code and StackOverflow, in their native language, not just in English.  We're excited to announce localization for the DevTools, which you can now use in one of 10 languages besides English:
 
-<!--
-|  |  |
-|:--- |:--- |
-| Chinese (Simplified) - 中文（简体）| Chinese (Traditional) - 中文（繁體）|
-| French – français | German - deutsch |
-| Italian - italiano | Portuguese - português |
-| Korean - 한국어 | Japanese - 日本語 |
-| Russian – русский | Spanish - español |
--->
+* Chinese (Simplified) - &#20013;&#25991;&#65288;&#31616;&#20307;&#65289;<!-- 中文（简体) -->
+* Chinese (Traditional) - &#20013;&#25991;&#65288;&#32321;&#39636;&#65289;<!-- 中文（繁體) -->
+* French – fran&#231;ais<!-- français -->
+* German - deutsch<!-- deutsch -->
+* Italian - italiano<!-- italiano -->
+* Japanese - &#26085;&#26412;&#35486;<!-- 日本語 -->
+* Korean - &#54620;&#44397;&#50612;<!-- 한국어 -->
+* Portuguese - portugu&#234;s<!-- português -->
+* Russian – &#1088;&#1091;&#1089;&#1089;&#1082;&#1080;&#1081;<!-- русский -->
+* Spanish - espa&#241;ol<!-- español -->
+
+To have the DevTools UI automatically match the language that you use for Microsoft Edge:
+
+1. Go to `edge://flags` and set the **Enable localized Developer Tools** flag to **Enabled**.
+
+   Update 2026: These two flags no longer appear.
+
+1. Set the **Developer Tools experiments** flag to **Enabled**.
+
+1. Restart Microsoft Edge.
+
+1. Open DevTools.
+
+1. Go to **Settings** > **Preferences**, and then in the **Language** dropdown list, select **Browser UI language**.
+
+   The DevTools UI automatically matches the language that you use for Microsoft Edge in `edge://settings/languages`, such as German:
+
+   ![DevTools in German](./devtools-images/localized-devtools.png)
 
-Go to `edge://flags` and set the **Enable localized Developer Tools** flag to **Enabled**.  Also set the **Developer Tools experiments** flag to **Enabled**.  Restart Microsoft Edge and open the DevTools.  <!-- Press **F1** in the DevTools or go to Settings > Experiments and check the **Match browser language** checkbox.  -->  The DevTools match the language you use for Microsoft Edge in `edge://settings/languages`.
+If you want Microsoft Edge to be in one language and your DevTools to remain in English, in DevTools > **Settings** (**F1**) > **Preferences**, and then select a language (such as **English - English**), rather than selecting **Browser UI language**.
 
-![The DevTools in German](./devtools-images/localized-devtools.png)
+**Console** messages aren't localized.  Only the strings used in the DevTools UI are displayed in the language you use for Microsoft Edge.
 
-If you want to use the DevTools in a different language than the ones that are available, [tweet](https://aka.ms/tweet/edgedevtools) at us or click the [Send Feedback](../../../contact.md) icon.
+If you want to use DevTools in a different language than the ones that are available, [tweet](https://aka.ms/tweet/edgedevtools) at the Microsoft Edge DevTools team, or click the [Send Feedback](../../../contact.md) icon.
 
 Chromium issue [#941561](https://crbug.com/941561)
 
diff --git a/microsoft-edge/devtools/whats-new/2020/01/devtools.md b/microsoft-edge/devtools/whats-new/2020/01/devtools.md
index 6bb1642466..9f3d2419ae 100644
--- a/microsoft-edge/devtools/whats-new/2020/01/devtools.md
+++ b/microsoft-edge/devtools/whats-new/2020/01/devtools.md
@@ -55,38 +55,42 @@ See also:
 
 <!-- dup entries: 2019/12, 2020/01 -->
 
-Many developers use other developer tools, like StackOverflow and Visual Studio Code, in their native language, not just in English.  We're excited to announce localization for the DevTools, which you can now use in one of 10 languages besides English:
-
-* Chinese (Simplified) - &#20013;&#25991;&#65288;&#31616;&#20307;&#65289;
-* Chinese (Traditional) - &#20013;&#25991;&#65288;&#32321;&#39636;&#65289;
-* French – fran&#231;ais
-* German - deutsch
-* Italian - italiano
-* Japanese - &#26085;&#26412;&#35486;
-* Korean - &#54620;&#44397;&#50612;
-* Portuguese - portugu&#234;s
-* Russian – &#1088;&#1091;&#1089;&#1089;&#1082;&#1080;&#1081;
-* Spanish - espa&#241;ol
-
-<!--
-|  |  |
-|:--- |:--- |
-| Chinese (Simplified) - 中文(简体)（简体）| Chinese (Traditional) - 中文(繁體)（繁體）|
-| French – français | German - deutsch |
-| Italian - italiano | Portuguese - português |
-| Korean - 한국어 | Japanese - 日本語 |
-| Russian – русский | Spanish - español |
--->
-
-The DevTools automatically match the language you use for Microsoft Edge in `edge://settings/languages`.
-
-If you want Microsoft Edge to be in one language and your DevTools to remain in English, press **F1** in DevTools to open [Settings](../../../customize/index.md#settings) and disable **Match browser language**.
-
-![The DevTools in German](./devtools-images/localized-devtools.png)
+Many developers use other developer tools, such as Visual Studio Code and StackOverflow, in their native language, not just in English.  We're excited to announce localization for DevTools, which you can now use in one of 10 languages besides English:
+
+* Chinese (Simplified) - &#20013;&#25991;&#65288;&#31616;&#20307;&#65289;<!-- 中文（简体) -->
+* Chinese (Traditional) - &#20013;&#25991;&#65288;&#32321;&#39636;&#65289;<!-- 中文（繁體) -->
+* French – fran&#231;ais<!-- français -->
+* German - deutsch<!-- deutsch -->
+* Italian - italiano<!-- italiano -->
+* Japanese - &#26085;&#26412;&#35486;<!-- 日本語 -->
+* Korean - &#54620;&#44397;&#50612;<!-- 한국어 -->
+* Portuguese - portugu&#234;s<!-- português -->
+* Russian – &#1088;&#1091;&#1089;&#1089;&#1082;&#1080;&#1081;<!-- русский -->
+* Spanish - espa&#241;ol<!-- español -->
+
+To have the DevTools UI automatically match the language that you use for Microsoft Edge:
+
+1. Go to `edge://flags` and set the **Enable localized Developer Tools** flag to **Enabled**.
+
+   Update 2026: These two flags no longer appear.
+
+1. Set the **Developer Tools experiments** flag to **Enabled**.
+
+1. Restart Microsoft Edge.
+
+1. Open DevTools.
+
+1. Go to **Settings** > **Preferences**, and then in the **Language** dropdown list, select **Browser UI language**.
+
+   The DevTools UI automatically matches the language that you use for Microsoft Edge in `edge://settings/languages`, such as German:
+
+   ![DevTools in German](./devtools-images/localized-devtools.png)
+
+If you want Microsoft Edge to be in one language and your DevTools to remain in English, in DevTools > **Settings** (**F1**) > **Preferences**, and then select a language (such as **English - English**), rather than selecting **Browser UI language**.
 
 **Console** messages aren't localized.  Only the strings used in the DevTools UI are displayed in the language you use for Microsoft Edge.
 
-If you want to use the DevTools in a different language than the ones that are available, [tweet](https://twitter.com/intent/tweet?text=@EdgeDevTools) at us or click the **Send Feedback** icon.
+If you want to use DevTools in a different language than the ones that are available, [tweet](https://aka.ms/tweet/edgedevtools) at the Microsoft Edge DevTools team, or click the [Send Feedback](../../../contact.md) icon.
 
 Chromium issue [#941561](https://crbug.com/941561)
 
diff --git a/microsoft-edge/devtools/whats-new/2020/05/devtools.md b/microsoft-edge/devtools/whats-new/2020/05/devtools.md
index 918dd83513..ca8e7517ab 100644
--- a/microsoft-edge/devtools/whats-new/2020/05/devtools.md
+++ b/microsoft-edge/devtools/whats-new/2020/05/devtools.md
@@ -64,7 +64,7 @@ To try the experiment:
 
 1. Open **Settings** again, and select the **Shortcuts** section.
 
-1. Click the **Match shortcuts from preset** dropdown list, select **DevTools (Default)**, and then select **Visual Studio Code**.  
+1. Click the **Match shortcuts from preset** dropdown list, select **DevTools (Default)**, and then select **Visual Studio Code**.
 
 The keyboard shortcuts in DevTools now match the shortcuts for equivalent actions in Visual Studio Code.
 
diff --git a/microsoft-edge/devtools/whats-new/2020/08/devtools.md b/microsoft-edge/devtools/whats-new/2020/08/devtools.md
index 4b3965e9dc..33ea69c3c8 100644
--- a/microsoft-edge/devtools/whats-new/2020/08/devtools.md
+++ b/microsoft-edge/devtools/whats-new/2020/08/devtools.md
@@ -129,7 +129,7 @@ See also:
 Chromium issue: [#1094406](https://crbug.com/1094406)
 
 
-<!-- ------------------------------ 
+<!-- ------------------------------
 #### DevTools language enhancements
 
 Your feedback and internal discoveries uncovered which text strings used in the Microsoft Edge feedback should remain untranslated or create confusion when translated.
@@ -296,7 +296,7 @@ See also:
 DevTools now has better support for the following JavaScript language features:
 
 | JavaScript language feature | Details |
-|:--- |:--- |
+|---|---|
 | [Logical assignment operators](https://v8.dev/features/logical-assignment) | DevTools now supports logical assignment with the new `&&=`, `||=`, and `??=` operators in the **Console** and **Sources** tools.  |
 | Pretty-print [numeric separators](https://v8.dev/features/numeric-separators) | DevTools now properly pretty-prints the numeric separators in the **Sources** tool.  |
 
@@ -430,7 +430,7 @@ See also:
 * [Inspect, edit, and debug HTML and CSS with the Elements tool](../../../elements-tool/elements-tool.md)
 
 
-<!-- ---------- 
+<!-- ----------
 ###### Human-readable X-Client-Data header values in the Network panel
 
 When inspecting a network resource in the Network panel, DevTools now formats any `X-Client-Data` header values in **Headers** pane as code.
diff --git a/microsoft-edge/devtools/whats-new/2020/11/devtools.md b/microsoft-edge/devtools/whats-new/2020/11/devtools.md
index 7e10aecef3..c105d47302 100644
--- a/microsoft-edge/devtools/whats-new/2020/11/devtools.md
+++ b/microsoft-edge/devtools/whats-new/2020/11/devtools.md
@@ -311,7 +311,7 @@ See also:
 <!-- ------------------------------ -->
 #### Frame details view updates
 
-In the **Application** tool, there's a **Frames** section that provides a detailed view for each frame.  
+In the **Application** tool, there's a **Frames** section that provides a detailed view for each frame.
 
 See also:
 * [Application tool, to manage storage](../../../storage/application-tool.md)
diff --git a/microsoft-edge/devtools/whats-new/2021/01/devtools.md b/microsoft-edge/devtools/whats-new/2021/01/devtools.md
index 076721893c..554a7ea14b 100644
--- a/microsoft-edge/devtools/whats-new/2021/01/devtools.md
+++ b/microsoft-edge/devtools/whats-new/2021/01/devtools.md
@@ -215,10 +215,13 @@ See also:
 The [Microsoft Edge Developer Tools for Visual Studio Code](https://marketplace.visualstudio.com/items?itemName=ms-edgedevtools.vscode-edge-devtools) extension version 1.1.2 for Microsoft Visual Studio Code has the following changes since the previous release.  Microsoft Visual Studio Code updates extensions automatically.  To manually update to version 1.1.2, see [Update an extension manually](https://code.visualstudio.com/docs/editor/extension-gallery#_update-an-extension-manually).
 
 * Added a **Close instance** button to each item on the target list ([#248](https://github.com/microsoft/vscode-edge-devtools/pull/248))
+
 * Bumped Microsoft Edge DevTools version from 84.0.522.63 to [85.0.564.40](../../2020/06/devtools.md) ([#235](https://github.com/microsoft/vscode-edge-devtools/pull/235))
-* Included "Debugger for Microsoft Edge" as a dependency  ([#233](https://github.com/microsoft/vscode-edge-devtools/pull/233)).  
+
+* Included "Debugger for Microsoft Edge" as a dependency  ([#233](https://github.com/microsoft/vscode-edge-devtools/pull/233)).
 <!-- todo: consult w SME on desired presentation here -->
 <!-- old url: https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-edge -->
+
 * Implemented settings option to change extension themes ([#229](https://github.com/microsoft/vscode-edge-devtools/pull/229))
 
 You can file issues and contribute to the extension on the [vscode-edge-devtools GitHub repo](https://github.com/microsoft/vscode-edge-devtools).
@@ -299,7 +302,7 @@ You can now copy CSS properties quicker with a few new options in the right-clic
 Copy options for a CSS class in the right-click menu:
 
 | Option | Details |
-|:--- |:--- |
+|---|---|
 | **Copy selector** | Copy the current selector name. |
 | **Copy rule** | Copy the rule of the current selector. |
 | **Copy all declarations** | Copy all declarations under the current rule, including non-valid and prefixed properties. |
@@ -309,7 +312,7 @@ Copy options for a CSS class in the right-click menu:
 Copy options for a CSS property in the right-click menu:
 
 | Option | Details |
-|:--- |:--- |
+|---|---|
 | **Copy declaration** | Copy the declaration of the current line. |
 | **Copy property** | Copy the property of the current line. |
 | **Copy value** | Copy the value of the current line. |
diff --git a/microsoft-edge/devtools/whats-new/2021/02/devtools.md b/microsoft-edge/devtools/whats-new/2021/02/devtools.md
index e6aa866119..3b4ce6997f 100644
--- a/microsoft-edge/devtools/whats-new/2021/02/devtools.md
+++ b/microsoft-edge/devtools/whats-new/2021/02/devtools.md
@@ -45,7 +45,7 @@ To turn on the experiment, see [Turning an experiment on or off](../../../experi
 <!-- Title: DevTools Tooltips  -->
 <!-- Subtitle: Learn more about how to use DevTools with informative DevTools tooltips.  -->
 
-The DevTools Tooltips feature helps you learn about all the different tools and panes.  Hover over each outlined region of DevTools to learn more about how to use the tool.  To turn on Tooltips, do one of the following: 
+The DevTools Tooltips feature helps you learn about all the different tools and panes.  Hover over each outlined region of DevTools to learn more about how to use the tool.  To turn on Tooltips, do one of the following:
 
 <!-- todo: update for Focus Mode -->
 * Select **Customize and control DevTools** (`...`) > **Help** > **Toggle the DevTools Tooltips**.
@@ -56,7 +56,7 @@ Then hover over each outlined region of DevTools:
 
 ![DevTools Tooltips mode](./devtools-images/tooltips.png)
 
-To turn off Tooltips, press **Esc**.  
+To turn off Tooltips, press **Esc**.
 
 Update: This feature has been released and is no longer experimental.<!-- valid. -->
 <!-- To turn on the experiment, see [Turning an experiment on or off](../../../experimental-features/index.md#turning-an-experiment-on-or-off) and select the following checkboxes:
diff --git a/microsoft-edge/devtools/whats-new/2021/04/devtools.md b/microsoft-edge/devtools/whats-new/2021/04/devtools.md
index a3d1662643..ee78b5274b 100644
--- a/microsoft-edge/devtools/whats-new/2021/04/devtools.md
+++ b/microsoft-edge/devtools/whats-new/2021/04/devtools.md
@@ -58,7 +58,7 @@ See also:
 <!--  Title: Learn more about DevTools with DevTools Tooltips  -->
 <!--  Subtitle: Informative overlays are now available in the default DevTools interface.  -->
 
-The DevTools Tooltips feature helps you learn about all the different tools and panes.  Hover over each outlined region of DevTools to learn more about how to use the tool.  To turn on Tooltips, do any of the following: 
+The DevTools Tooltips feature helps you learn about all the different tools and panes.  Hover over each outlined region of DevTools to learn more about how to use the tool.  To turn on Tooltips, do any of the following:
 
 <!-- todo: update for Focus Mode -->
 * Select **Customize and control DevTools** (`...`) > **Help** > **Toggle the DevTools Tooltips**.
diff --git a/microsoft-edge/devtools/whats-new/2021/10/devtools.md b/microsoft-edge/devtools/whats-new/2021/10/devtools.md
index 312b8157af..268f4c7fa4 100644
--- a/microsoft-edge/devtools/whats-new/2021/10/devtools.md
+++ b/microsoft-edge/devtools/whats-new/2021/10/devtools.md
@@ -164,7 +164,7 @@ The **Command Menu** has been enhanced to make it easier to search for a file.
 See also:
 * [Command Menu](../../../command-menu/index.md)
 
-For the history of this feature, see Chromium issue [1201997](https://crbug.com/1201997). 
+For the history of this feature, see Chromium issue [1201997](https://crbug.com/1201997).
 
 
 <!-- ====================================================================== -->
diff --git a/microsoft-edge/devtools/whats-new/2021/11/devtools.md b/microsoft-edge/devtools/whats-new/2021/11/devtools.md
index 0baa79934e..026133420e 100644
--- a/microsoft-edge/devtools/whats-new/2021/11/devtools.md
+++ b/microsoft-edge/devtools/whats-new/2021/11/devtools.md
@@ -74,7 +74,7 @@ See also:
 For general information about this extension, see [Microsoft Edge DevTools extension for Visual Studio Code](../../../../visual-studio-code/microsoft-edge-devtools-extension.md).
 
 <!-- Title: Dockable browser screencast, device emulation, and live issue reporting, and in Microsoft Edge DevTools for Visual Studio Code -->
-<!-- Subtitle: Display your web project inside the editor, simulate different devices, and get notified about issues with your code while you develop it. --> 
+<!-- Subtitle: Display your web project inside the editor, simulate different devices, and get notified about issues with your code while you develop it. -->
 
 
 <!-- ------------------------------ -->
@@ -107,7 +107,7 @@ For details, see [Inline and live issue analysis](../../../../visual-studio-code
 <!-- Title: Get notified when DevTools cannot load your sourcemaps correctly -->
 <!-- Subtitle: The Sources tool now provides several places in the UI when DevTools can't fetch or parse your sourcemaps. -->
 
-In Microsoft Edge version 96, the **Sources** tool now provides several indications in the UI when DevTools cannot load your sourcemaps.  In the **Page** tab in the **Navigator** pane in the **Sources** tool, files that DevTools can't load sourcemaps for have a warning icon in place of the file icon.  
+In Microsoft Edge version 96, the **Sources** tool now provides several indications in the UI when DevTools cannot load your sourcemaps.  In the **Page** tab in the **Navigator** pane in the **Sources** tool, files that DevTools can't load sourcemaps for have a warning icon in place of the file icon.
 
 Selecting a file with the warning icon opens the file in the Sources tool with an infobar indicating that DevTools either couldn't fetch the sourcemap correctly from the server or couldn't parse the sourcemap correctly:
 
diff --git a/microsoft-edge/devtools/whats-new/2022/03/devtools.md b/microsoft-edge/devtools/whats-new/2022/03/devtools.md
index 087a855eaf..030addbc4d 100644
--- a/microsoft-edge/devtools/whats-new/2022/03/devtools.md
+++ b/microsoft-edge/devtools/whats-new/2022/03/devtools.md
@@ -25,7 +25,7 @@ These are the latest features in the Stable release of Microsoft Edge DevTools.
 <!-- Title: Debug JavaScript with source maps more easily -->
 <!-- Subtitle: Publish your source maps to Azure Artifacts Symbol Server and connect DevTools to it for an easier debugging experience. -->
 
-Azure Artifacts Symbol Server now supports storing the source maps that your build process produces when compiling, minifying, and bundling your code.  Instead of hosting source maps on your public server, you can now publish your source maps to the secure Azure Artifacts Symbol Server.  Then, connect DevTools to Symbol Server to have DevTools automatically fetch your source maps. 
+Azure Artifacts Symbol Server now supports storing the source maps that your build process produces when compiling, minifying, and bundling your code.  Instead of hosting source maps on your public server, you can now publish your source maps to the secure Azure Artifacts Symbol Server.  Then, connect DevTools to Symbol Server to have DevTools automatically fetch your source maps.
 
 By using source maps, you can see and debug your original source code in DevTools, rather than having to work with the compiled, minified, and bundled production code that's returned by your server.  Hosting your source maps on the Azure Artifacts Symbol Server allows you to see and work with your source code securely and privately, instead of placing your source maps on your server and revealing your original code publicly.
 
@@ -47,7 +47,7 @@ See also:
 <!-- Title: Debug your ASP.NET projects in Visual Studio with the Edge Developer Tools -->
 <!-- Subtitle: Get the Edge Developer Tools extension for VS today! -->
 
-Following up on the success of the Visual Studio Code integration, you can now also embed the Microsoft Edge Developer Tools in Microsoft Visual Studio to debug your ASP.NET projects live.  Download the [Microsoft Edge Developer Tools for Visual Studio](https://aka.ms/edgetools-for-vs) and try it out. 
+Following up on the success of the Visual Studio Code integration, you can now also embed the Microsoft Edge Developer Tools in Microsoft Visual Studio to debug your ASP.NET projects live.  Download the [Microsoft Edge Developer Tools for Visual Studio](https://aka.ms/edgetools-for-vs) and try it out.
 
 To try this feature:
 1. Make sure Visual Studio 2022 and the ASP.NET workload are installed.
diff --git a/microsoft-edge/devtools/whats-new/2022/09/devtools-106.md b/microsoft-edge/devtools/whats-new/2022/09/devtools-106.md
index d0c19e8574..0e5ff87880 100644
--- a/microsoft-edge/devtools/whats-new/2022/09/devtools-106.md
+++ b/microsoft-edge/devtools/whats-new/2022/09/devtools-106.md
@@ -1,6 +1,6 @@
 ---
 title: What's new in DevTools (Microsoft Edge 106)
-description: "Introducing the Command Palette. Filter and automatically fix code issues in DevTools for Visual Studio Code. DevTools now uses less disk space when caching sourcemaps. Chromium color themes have been deprecated. Accessibility improvements in Focus Mode and high contrast mode. And more."
+description: Introducing the Command Palette. Filter and automatically fix code issues in DevTools for Visual Studio Code. DevTools now uses less disk space when caching sourcemaps. Chromium color themes have been deprecated. Accessibility improvements in Focus Mode and high contrast mode. And more.
 author: MSEdgeTeam
 ms.author: msedgedevrel
 ms.topic: article
@@ -35,7 +35,7 @@ To enable the Command Palette experiment:
 
 1. In the **Command Palette** dropdown menu, select **Enabled**:
 
-   <!-- screenshot directly in What's New, to show where to see the keyboard shortcut along with version:-->
+   <!-- screenshot directly in What's New, to show where to see the keyboard shortcut along with version: -->
    ![The keyboard shortcut for Command Palette in the flags page for version 106](./devtools-106-images/command-palette-flags-shortcut-106.png)
 
    Note the keyboard shortcut, which is shown in the **Command Palette** section on the `edge://flags` page.
@@ -65,7 +65,7 @@ Let us know what commands you'd like to see in future versions of Microsoft Edge
 ## Filter and automatically fix code issues in DevTools for Visual Studio Code
 
 <!-- Subtitle: Let Visual Studio Code fix web issues for you or tell it never to bother you about them again. -->
- 
+
 The Microsoft Edge DevTools extension for Visual Studio Code now provides **Quick Fix** options, allowing you to fix issues automatically.
 
 To access the **Quick Fix** options:
@@ -114,7 +114,7 @@ See also:
 
 To improve reliability, the **Chromium Light** and **Chromium Dark** themes have been deprecated.  Users who previously had these themes selected will be automatically migrated to the **Light+** or **Dark+** theme, respectively:
 
-DevTools in **Light+** theme: 
+DevTools in **Light+** theme:
 
 ![DevTools in Light+ theme](./devtools-106-images/light-plus-theme.png)
 
@@ -149,7 +149,7 @@ See also:
 #### Computed styles are easier to see in high contrast mode
 
 In high contrast mode, in previous versions of Microsoft Edge, the expand and collapse buttons for computed styles didn't render correctly, in the **Computed** tab in the **Elements** tool.  In Microsoft Edge 106, this issue has been fixed.  The expand and collapse buttons are now visible in high contrast mode:
- 
+
 ![Computed styles in high contrast mode](./devtools-106-images/computed-styles-high-contrast-mode.png)
 
 See also:
diff --git a/microsoft-edge/devtools/whats-new/2022/10/devtools-107.md b/microsoft-edge/devtools/whats-new/2022/10/devtools-107.md
index 11520cff0c..cf175553c9 100644
--- a/microsoft-edge/devtools/whats-new/2022/10/devtools-107.md
+++ b/microsoft-edge/devtools/whats-new/2022/10/devtools-107.md
@@ -1,6 +1,6 @@
 ---
 title: What's new in DevTools (Microsoft Edge 107)
-description: "Automate WebView2 with Playwright. Focus Mode Activity Bar icons have tooltips. New shortcut key for Command Palette. Memory tool loads larger heap snapshots. Links in Application tool render in high contrast mode. And more."
+description: Automate WebView2 with Playwright. Focus Mode Activity Bar icons have tooltips. New shortcut key for Command Palette. Memory tool loads larger heap snapshots. Links in Application tool render in high contrast mode. And more.
 author: MSEdgeTeam
 ms.author: msedgedevrel
 ms.topic: article
@@ -91,7 +91,7 @@ See also:
 In previous versions of Microsoft Edge, links in the **Application** tool didn't render correctly in high contrast mode.  The links weren't visible, and they weren't the same color as defined in the high contrast setting.  In Microsoft Edge 107, this issue has been fixed.  Links in the **Application** tool now match the color that's defined in the high contrast setting:
 
 ![Links in High Contrast mode](./devtools-107-images/high-contrast-links.png)
- 
+
 See also:
 * [Windows high contrast mode](/fluent-ui/web-components/design-system/high-contrast)
 * [Debug a Progressive Web App (PWA)](../../../progressive-web-apps/index.md)
diff --git a/microsoft-edge/devtools/whats-new/2022/12/devtools-108.md b/microsoft-edge/devtools/whats-new/2022/12/devtools-108.md
index 72344c11aa..ebb18d766a 100644
--- a/microsoft-edge/devtools/whats-new/2022/12/devtools-108.md
+++ b/microsoft-edge/devtools/whats-new/2022/12/devtools-108.md
@@ -1,6 +1,6 @@
 ---
 title: What's new in DevTools (Microsoft Edge 108)
-description: "Microsoft Edge WebDriver is now available for macOS running on Apple M1. Improved DevTools navigation via Command Palette. Better support for high contrast mode in DevTools. In Focus Mode, disabling JavaScript now produces a warning icon for the Sources tool.  And more."
+description: Microsoft Edge WebDriver is now available for macOS running on Apple M1. Improved DevTools navigation via Command Palette. Better support for high contrast mode in DevTools. In Focus Mode, disabling JavaScript now produces a warning icon for the Sources tool.  And more.
 author: MSEdgeTeam
 ms.author: msedgedevrel
 ms.topic: article
diff --git a/microsoft-edge/devtools/whats-new/2023/01/devtools-109.md b/microsoft-edge/devtools/whats-new/2023/01/devtools-109.md
index a09fe5a46e..eff146d4f0 100644
--- a/microsoft-edge/devtools/whats-new/2023/01/devtools-109.md
+++ b/microsoft-edge/devtools/whats-new/2023/01/devtools-109.md
@@ -1,6 +1,6 @@
 ---
 title: What's new in DevTools (Microsoft Edge 109)
-description: "Export DevTools instances with enhanced traces.  Debug Recalculate Styles events in Performance tool with selector stats.  Track GC'd objects when Allocation sampling in Memory tool.  Heap Snapshot Visualizer.  Quick View in Focus Mode has all tools.  Navigate directly to Styles in Elements tool.  And more."
+description: Export DevTools instances with enhanced traces.  Debug Recalculate Styles events in Performance tool with selector stats.  Track GC'd objects when Allocation sampling in Memory tool.  Heap Snapshot Visualizer.  Quick View in Focus Mode has all tools.  Navigate directly to Styles in Elements tool.  And more.
 author: MSEdgeTeam
 ms.author: msedgedevrel
 ms.topic: article
@@ -114,7 +114,7 @@ Without selecting these options, the **Memory** tool will continue to work as it
 Select both options if you want to track garbage that is being generated by your website or app.  In the resulting profile, you'll be able to see garbage that was generated by your JavaScript functions that was then GC'd.  Use these options if you want to reduce the amount of garbage that your code is generating.  To learn more about the differences between major and minor GC, see [Trash talk: the Orinoco garbage collector](https://v8.dev/blog/trash-talk).
 
 ![Allocation sampling profiling options](./devtools-109-images/allocation-sampling-profiling-options.png)
- 
+
 See also:
 * [Investigate memory allocation, with reduced garbage ("Include objects" checkboxes)](../../../rendering-tools/js-runtime.md#investigate-memory-allocation-with-reduced-garbage-include-objects-checkboxes) in _Speed up JavaScript runtime ("Allocation sampling" profiling type)_.
 
diff --git a/microsoft-edge/devtools/whats-new/2023/02/devtools-110.md b/microsoft-edge/devtools/whats-new/2023/02/devtools-110.md
index 9143eae144..58657b29bc 100644
--- a/microsoft-edge/devtools/whats-new/2023/02/devtools-110.md
+++ b/microsoft-edge/devtools/whats-new/2023/02/devtools-110.md
@@ -1,6 +1,6 @@
 ---
 title: What's new in DevTools (Microsoft Edge 110)
-description: "Faster heap snapshots in Memory tool. Move tools between Activity Bar and Quick View in Focus Mode. Screen readers report when More Tools is expanded. Change Dock and Activity Bar location via keyboard. Screen readers announce which theme is selected. Improved support for contrast themes. And more."
+description: Faster heap snapshots in Memory tool. Move tools between Activity Bar and Quick View in Focus Mode. Screen readers report when More Tools is expanded. Change Dock and Activity Bar location via keyboard. Screen readers announce which theme is selected. Improved support for contrast themes. And more.
 author: MSEdgeTeam
 ms.author: msedgedevrel
 ms.topic: article
diff --git a/microsoft-edge/devtools/whats-new/2023/03/devtools-111.md b/microsoft-edge/devtools/whats-new/2023/03/devtools-111.md
index 39608c6993..51751d942b 100644
--- a/microsoft-edge/devtools/whats-new/2023/03/devtools-111.md
+++ b/microsoft-edge/devtools/whats-new/2023/03/devtools-111.md
@@ -1,6 +1,6 @@
 ---
 title: What's new in DevTools (Microsoft Edge 111)
-description: "Remote debugging of Microsoft Edge, PWAs, and WebView2 controls on HoloLens 2 devices. Device Mode toolbar has emulation controls for themes and vision deficiencies. Performance tool unminifies file and function names while profiling. Styles tab easier to use in Focus Mode. Copy Selector Stats table from Performance tool. In Focus Mode, assistive tech announces tool moved to Quick View. And more."
+description: Remote debugging of Microsoft Edge, PWAs, and WebView2 controls on HoloLens 2 devices. Device Mode toolbar has emulation controls for themes and vision deficiencies. Performance tool unminifies file and function names while profiling. Styles tab easier to use in Focus Mode. Copy Selector Stats table from Performance tool. In Focus Mode, assistive tech announces tool moved to Quick View. And more.
 author: MSEdgeTeam
 ms.author: msedgedevrel
 ms.topic: article
diff --git a/microsoft-edge/devtools/whats-new/2023/04/devtools-112.md b/microsoft-edge/devtools/whats-new/2023/04/devtools-112.md
index 8a58b05b76..211a0da528 100644
--- a/microsoft-edge/devtools/whats-new/2023/04/devtools-112.md
+++ b/microsoft-edge/devtools/whats-new/2023/04/devtools-112.md
@@ -1,6 +1,6 @@
 ---
 title: What's new in DevTools (Microsoft Edge 112)
-description: "The Performance tool can now unminify JavaScript running in out-of-process iframes, the CSS overview tool displays a list of non-simple selectors for quick performance wins, and more."
+description: The Performance tool can now unminify JavaScript running in out-of-process iframes, the CSS overview tool displays a list of non-simple selectors for quick performance wins, and more.
 author: MSEdgeTeam
 ms.author: msedgedevrel
 ms.topic: article
diff --git a/microsoft-edge/devtools/whats-new/2023/05/devtools-113.md b/microsoft-edge/devtools/whats-new/2023/05/devtools-113.md
index 78efbfa084..f9e0b39e6f 100644
--- a/microsoft-edge/devtools/whats-new/2023/05/devtools-113.md
+++ b/microsoft-edge/devtools/whats-new/2023/05/devtools-113.md
@@ -1,6 +1,6 @@
 ---
 title: What's new in DevTools (Microsoft Edge 113)
-description: "Debug JavaScript error stack traces with the experimental Crash analyzer tool. The Memory tool can now unminify object names in heap snapshots. The Issues tool has better support for keyboard navigation. And more."
+description: Debug JavaScript error stack traces with the experimental Crash analyzer tool. The Memory tool can now unminify object names in heap snapshots. The Issues tool has better support for keyboard navigation. And more.
 author: MSEdgeTeam
 ms.author: msedgedevrel
 ms.topic: article
diff --git a/microsoft-edge/devtools/whats-new/2023/06/devtools-114.md b/microsoft-edge/devtools/whats-new/2023/06/devtools-114.md
index 95ef074cf1..4b7edd9594 100644
--- a/microsoft-edge/devtools/whats-new/2023/06/devtools-114.md
+++ b/microsoft-edge/devtools/whats-new/2023/06/devtools-114.md
@@ -1,6 +1,6 @@
 ---
 title: What's new in DevTools (Microsoft Edge 114)
-description: "Aggregate Selector Stats in Performance tool. Issues tool warns when CSS properties trigger Layout. Memory tool loads enhanced traces larger than 1 GB. Memory tool accurately compares heap snapshots. CSS overview accessibility improvements. Debugging Microsoft Edge in VS Code supports high contrast. And more."
+description: Aggregate Selector Stats in Performance tool. Issues tool warns when CSS properties trigger Layout. Memory tool loads enhanced traces larger than 1 GB. Memory tool accurately compares heap snapshots. CSS overview accessibility improvements. Debugging Microsoft Edge in VS Code supports high contrast. And more.
 author: MSEdgeTeam
 ms.author: msedgedevrel
 ms.topic: article
diff --git a/microsoft-edge/devtools/whats-new/2023/07/devtools-115.md b/microsoft-edge/devtools/whats-new/2023/07/devtools-115.md
index 1885dcb82d..6096a78298 100644
--- a/microsoft-edge/devtools/whats-new/2023/07/devtools-115.md
+++ b/microsoft-edge/devtools/whats-new/2023/07/devtools-115.md
@@ -1,6 +1,6 @@
 ---
 title: What's new in DevTools (Microsoft Edge 115)
-description: "Improvements for connecting DevTools to Azure Artifacts symbol server. Snapshotting improvements for the Memory tool. Refreshing the DevTools icons and buttons. And more."
+description: Improvements for connecting DevTools to Azure Artifacts symbol server. Snapshotting improvements for the Memory tool. Refreshing the DevTools icons and buttons. And more.
 author: MSEdgeTeam
 ms.author: msedgedevrel
 ms.topic: article
@@ -13,7 +13,7 @@ ms.date: 08/18/2023
 These are the latest features in the Stable release of Microsoft Edge DevTools.
 
 
-<!-- ------------------------------ 
+<!-- ------------------------------
 todo video
 #### Video: What's new in DevTools 115-125
 
diff --git a/microsoft-edge/devtools/whats-new/2023/08/devtools-116.md b/microsoft-edge/devtools/whats-new/2023/08/devtools-116.md
index 9b4389088e..4cf909055f 100644
--- a/microsoft-edge/devtools/whats-new/2023/08/devtools-116.md
+++ b/microsoft-edge/devtools/whats-new/2023/08/devtools-116.md
@@ -1,6 +1,6 @@
 ---
 title: What's new in DevTools (Microsoft Edge 116)
-description: "Activity Bar has a Move Activity Bar button.  React Developer Tools extension works in Focus Mode.  A Containment Diff view in the Memory tool when multiple heap snapshots.  And more."
+description: Activity Bar has a Move Activity Bar button.  React Developer Tools extension works in Focus Mode.  A Containment Diff view in the Memory tool when multiple heap snapshots.  And more.
 author: MSEdgeTeam
 ms.author: msedgedevrel
 ms.topic: article
@@ -13,7 +13,7 @@ ms.date: 08/17/2023
 These are the latest features in the Stable release of Microsoft Edge DevTools.
 
 
-<!-- ------------------------------ 
+<!-- ------------------------------
 todo video
 #### Video: What's new in DevTools 115-125
 
@@ -57,7 +57,7 @@ In the **Memory** tool, when there's more than one heap snapshot, a **Containmen
 
 The **Containment Diff** view shows only the new objects, deleted objects, or objects in the retaining chain that will eventually lead to either a new or deleted node.  The dot symbol (![Dot symbol](./devtools-116-images/dot.png)) means that it's a node in the retaining chain.  Expanding the view displays the node that's new or deleted.
 
-For example: 
+For example:
 
 1. 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.
 
diff --git a/microsoft-edge/devtools/whats-new/2023/09/devtools-117.md b/microsoft-edge/devtools/whats-new/2023/09/devtools-117.md
index 1080cbb1c6..50457cb8e2 100644
--- a/microsoft-edge/devtools/whats-new/2023/09/devtools-117.md
+++ b/microsoft-edge/devtools/whats-new/2023/09/devtools-117.md
@@ -13,7 +13,7 @@ ms.date: 09/14/2023
 These are the latest features in the Stable release of Microsoft Edge DevTools.
 
 
-<!-- ------------------------------ 
+<!-- ------------------------------
 todo video
 #### Video: What's new in DevTools 115-125
 
@@ -51,7 +51,7 @@ Before Microsoft Edge 117, the Console was blank after closing and then re-openi
 
 
 <!-- ====================================================================== -->
-## Accessibility fixes 
+## Accessibility fixes
 
 In Microsoft Edge 117, the following accessibility issues have been addressed:
 
diff --git a/microsoft-edge/devtools/whats-new/2023/10/devtools-118.md b/microsoft-edge/devtools/whats-new/2023/10/devtools-118.md
index 5c8d761fd2..845f5b9a83 100644
--- a/microsoft-edge/devtools/whats-new/2023/10/devtools-118.md
+++ b/microsoft-edge/devtools/whats-new/2023/10/devtools-118.md
@@ -1,6 +1,6 @@
 ---
 title: What's new in DevTools (Microsoft Edge 118)
-description: "DevTools defaults to no throttling instead of offline. Updates to the 'Explain console errors/warnings with Copilot in Sidebar' experiment. And more."
+description: DevTools defaults to no throttling instead of offline. Updates to the 'Explain console errors/warnings with Copilot in Sidebar' experiment. And more.
 author: MSEdgeTeam
 ms.author: msedgedevrel
 ms.topic: article
@@ -13,7 +13,7 @@ ms.date: 10/12/2023
 These are the latest features in the Stable release of Microsoft Edge DevTools.
 
 
-<!-- ------------------------------ 
+<!-- ------------------------------
 todo video
 #### Video: What's new in DevTools 115-125
 
diff --git a/microsoft-edge/devtools/whats-new/2023/11/devtools-119.md b/microsoft-edge/devtools/whats-new/2023/11/devtools-119.md
index 31d06eefbe..28ae87f8cb 100644
--- a/microsoft-edge/devtools/whats-new/2023/11/devtools-119.md
+++ b/microsoft-edge/devtools/whats-new/2023/11/devtools-119.md
@@ -1,6 +1,6 @@
 ---
 title: What's new in DevTools (Microsoft Edge 119)
-description: "Increased text color contrast for Error pills (badges) in the Issues tool. Increased text color contrast for tree items on the left side of the Application tool. And more."
+description: Increased text color contrast for Error pills (badges) in the Issues tool. Increased text color contrast for tree items on the left side of the Application tool. And more.
 author: MSEdgeTeam
 ms.author: msedgedevrel
 ms.topic: article
@@ -13,7 +13,7 @@ ms.date: 11/02/2023
 These are the latest features in the Stable release of Microsoft Edge DevTools.
 
 
-<!-- ------------------------------ 
+<!-- ------------------------------
 todo video
 #### Video: What's new in DevTools 115-125
 
diff --git a/microsoft-edge/devtools/whats-new/2023/12/devtools-120.md b/microsoft-edge/devtools/whats-new/2023/12/devtools-120.md
index 1a0e5a0105..4b7dbee8ec 100644
--- a/microsoft-edge/devtools/whats-new/2023/12/devtools-120.md
+++ b/microsoft-edge/devtools/whats-new/2023/12/devtools-120.md
@@ -1,6 +1,6 @@
 ---
 title: What's new in DevTools (Microsoft Edge 120)
-description: "Edge DevTools has a new user interface. Explain with Copilot in DevTools is generally available. New Recorder tool to record and replay common user flows and measure performance. And more."
+description: Edge DevTools has a new user interface. Explain with Copilot in DevTools is generally available. New Recorder tool to record and replay common user flows and measure performance. And more.
 author: MSEdgeTeam
 ms.author: msedgedevrel
 ms.topic: article
@@ -13,7 +13,7 @@ ms.date: 12/07/2023
 These are the latest features in the Stable release of Microsoft Edge DevTools.
 
 
-<!-- ------------------------------ 
+<!-- ------------------------------
 todo video
 #### Video: What's new in DevTools 115-125
 
@@ -67,7 +67,7 @@ If you have any questions, comments, or feedback about the feature, please leave
 
 <!-- Subtitle: Debug and share common user journeys by recording them. You can generate a performance trace, and then analyze it by using the Performance tool. -->
 
-Use the **Recorder** tool to help you record and replay common user flows and measure performance.  You can edit your recordings and share them by importing and exporting. 
+Use the **Recorder** tool to help you record and replay common user flows and measure performance.  You can edit your recordings and share them by importing and exporting.
 
 The initial view in the **Recorder** tool gives an overview of how to use the tool:
 
diff --git a/microsoft-edge/devtools/whats-new/2024/01/devtools-121.md b/microsoft-edge/devtools/whats-new/2024/01/devtools-121.md
index ec3bfc8fac..fb6613377d 100644
--- a/microsoft-edge/devtools/whats-new/2024/01/devtools-121.md
+++ b/microsoft-edge/devtools/whats-new/2024/01/devtools-121.md
@@ -1,6 +1,6 @@
 ---
 title: What's new in DevTools (Microsoft Edge 121)
-description: "Z-index and DOM tabs in 3D View tool working correctly. Correct Hide debugger or Show debugger icon in Sources tool. Source map support in Coverage tool. Advanced filtering in Bottom-up, Call tree, and Event log tabs in Performance tool. Window Controls Overlay section for PWAs, in Application tool's Manifest section. And more."
+description: Z-index and DOM tabs in 3D View tool working correctly. Correct Hide debugger or Show debugger icon in Sources tool. Source map support in Coverage tool. Advanced filtering in Bottom-up, Call tree, and Event log tabs in Performance tool. Window Controls Overlay section for PWAs, in Application tool's Manifest section. And more.
 author: MSEdgeTeam
 ms.author: msedgedevrel
 ms.topic: article
@@ -13,7 +13,7 @@ ms.date: 01/25/2024
 These are the latest features in the Stable release of Microsoft Edge DevTools.
 
 
-<!-- ------------------------------ 
+<!-- ------------------------------
 todo video
 #### Video: What's new in DevTools 115-125
 
diff --git a/microsoft-edge/devtools/whats-new/2024/02/devtools-122.md b/microsoft-edge/devtools/whats-new/2024/02/devtools-122.md
index d9d80a1a9b..be5d1473c0 100644
--- a/microsoft-edge/devtools/whats-new/2024/02/devtools-122.md
+++ b/microsoft-edge/devtools/whats-new/2024/02/devtools-122.md
@@ -1,6 +1,6 @@
 ---
 title: What's new in DevTools (Microsoft Edge 122)
-description: "Copilot's explanation of Console errors includes a suggested fix. Keyboard shortcut to move through the open tools is working correctly. Icons are displayed correctly in high-contrast mode. And more." 
+description: Copilot's explanation of Console errors includes a suggested fix. Keyboard shortcut to move through the open tools is working correctly. Icons are displayed correctly in high-contrast mode. And more.
 author: MSEdgeTeam
 ms.author: msedgedevrel
 ms.topic: article
@@ -13,7 +13,7 @@ ms.date: 02/23/2024
 These are the latest features in the Stable release of Microsoft Edge DevTools.
 
 
-<!-- ------------------------------ 
+<!-- ------------------------------
 todo video
 #### Video: What's new in DevTools 115-125
 
diff --git a/microsoft-edge/devtools/whats-new/2024/03/devtools-123.md b/microsoft-edge/devtools/whats-new/2024/03/devtools-123.md
index 7df5e46480..c219b34216 100644
--- a/microsoft-edge/devtools/whats-new/2024/03/devtools-123.md
+++ b/microsoft-edge/devtools/whats-new/2024/03/devtools-123.md
@@ -1,6 +1,6 @@
 ---
 title: What's new in DevTools (Microsoft Edge 123)
-description: "Memory tool reports backing store sizes as part of an object's shallow size. Crash analyzer tool is available by default. Command Palette experimental feature has been removed. Undocked DevTools window is kept focused as the topmost window while inspecting a page. And more."
+description: Memory tool reports backing store sizes as part of an object's shallow size. Crash analyzer tool is available by default. Command Palette experimental feature has been removed. Undocked DevTools window is kept focused as the topmost window while inspecting a page. And more.
 author: MSEdgeTeam
 ms.author: msedgedevrel
 ms.topic: article
@@ -13,7 +13,7 @@ ms.date: 03/21/2024
 These are the latest features in the Stable release of Microsoft Edge DevTools.
 
 
-<!-- ------------------------------ 
+<!-- ------------------------------
 todo video
 #### Video: What's new in DevTools 115-125
 
diff --git a/microsoft-edge/devtools/whats-new/2024/04/devtools-124.md b/microsoft-edge/devtools/whats-new/2024/04/devtools-124.md
index 7f04ebc8f4..9aec459d9b 100644
--- a/microsoft-edge/devtools/whats-new/2024/04/devtools-124.md
+++ b/microsoft-edge/devtools/whats-new/2024/04/devtools-124.md
@@ -1,6 +1,6 @@
 ---
 title: What's new in DevTools (Microsoft Edge 124)
-description: "postMessage events and handlers are distinguished from other events on the timeline. Move a tab left or right in the Activity bar by right-clicking it. Network tab shows a warning icon when using overrides or throttling. And more."
+description: postMessage events and handlers are distinguished from other events on the timeline. Move a tab left or right in the Activity bar by right-clicking it. Network tab shows a warning icon when using overrides or throttling. And more.
 author: MSEdgeTeam
 ms.author: msedgedevrel
 ms.topic: article
@@ -13,7 +13,7 @@ ms.date: 04/18/2024
 These are the latest features in the Stable release of Microsoft Edge DevTools.
 
 
-<!-- ------------------------------ 
+<!-- ------------------------------
 todo video
 #### Video: What's new in DevTools 115-125
 
diff --git a/microsoft-edge/devtools/whats-new/2024/05/devtools-125.md b/microsoft-edge/devtools/whats-new/2024/05/devtools-125.md
index 340dd8a0a2..0097ff397f 100644
--- a/microsoft-edge/devtools/whats-new/2024/05/devtools-125.md
+++ b/microsoft-edge/devtools/whats-new/2024/05/devtools-125.md
@@ -1,6 +1,6 @@
 ---
 title: What's new in DevTools (Microsoft Edge 125)
-description: "New dedicated setting for CSS Selector Stats in Performance tool. The Edit and Resend function has been restored in the Network tool. And more."
+description: New dedicated setting for CSS Selector Stats in Performance tool. The Edit and Resend function has been restored in the Network tool. And more.
 author: MSEdgeTeam
 ms.author: msedgedevrel
 ms.topic: article
@@ -13,7 +13,7 @@ ms.date: 05/16/2024
 These are the latest features in the Stable release of Microsoft Edge DevTools.
 
 
-<!-- ------------------------------ 
+<!-- ------------------------------
 todo video
 #### Video: What's new in DevTools 115-125
 
diff --git a/microsoft-edge/devtools/whats-new/2024/06/devtools-126.md b/microsoft-edge/devtools/whats-new/2024/06/devtools-126.md
index ec4552f3a4..b98ee333d6 100644
--- a/microsoft-edge/devtools/whats-new/2024/06/devtools-126.md
+++ b/microsoft-edge/devtools/whats-new/2024/06/devtools-126.md
@@ -1,6 +1,6 @@
 ---
 title: What's new in DevTools (Microsoft Edge 126)
-description: "Icons for browser extensions are displayed instead of blank squares. The DevTools UI in Chinese has changed back to the original font. And more."
+description: Icons for browser extensions are displayed instead of blank squares. The DevTools UI in Chinese has changed back to the original font. And more.
 author: MSEdgeTeam
 ms.author: msedgedevrel
 ms.topic: article
diff --git a/microsoft-edge/devtools/whats-new/2024/07/devtools-127.md b/microsoft-edge/devtools/whats-new/2024/07/devtools-127.md
index 9ef670d2f9..e804d76cc2 100644
--- a/microsoft-edge/devtools/whats-new/2024/07/devtools-127.md
+++ b/microsoft-edge/devtools/whats-new/2024/07/devtools-127.md
@@ -1,6 +1,6 @@
 ---
 title: What's new in DevTools (Microsoft Edge 127)
-description: "Use Copilot to explain HTML and CSS in the Elements tool. And more."
+description: Use Copilot to explain HTML and CSS in the Elements tool. And more.
 author: MSEdgeTeam
 ms.author: msedgedevrel
 ms.topic: article
diff --git a/microsoft-edge/devtools/whats-new/2024/08/devtools-128.md b/microsoft-edge/devtools/whats-new/2024/08/devtools-128.md
index 11111477ea..f28e0ece29 100644
--- a/microsoft-edge/devtools/whats-new/2024/08/devtools-128.md
+++ b/microsoft-edge/devtools/whats-new/2024/08/devtools-128.md
@@ -1,6 +1,6 @@
 ---
 title: What's new in DevTools (Microsoft Edge 128)
-description: "Updated labels for selector stats. Fixed whitespace in Activity Bar right-click menus. And more."
+description: Updated labels for selector stats. Fixed whitespace in Activity Bar right-click menus. And more.
 author: MSEdgeTeam
 ms.author: msedgedevrel
 ms.topic: article
diff --git a/microsoft-edge/devtools/whats-new/2024/09/devtools-129.md b/microsoft-edge/devtools/whats-new/2024/09/devtools-129.md
index f6255a59be..f907bdc8e5 100644
--- a/microsoft-edge/devtools/whats-new/2024/09/devtools-129.md
+++ b/microsoft-edge/devtools/whats-new/2024/09/devtools-129.md
@@ -1,6 +1,6 @@
 ---
 title: What's new in DevTools (Microsoft Edge 129)
-description: "Unique breakpoint icons. Fixed CSS selector stats Copy table. Added Activity Bar icons. Fixed Security tool icons and device emulation. And more."
+description: Unique breakpoint icons. Fixed CSS selector stats Copy table. Added Activity Bar icons. Fixed Security tool icons and device emulation. And more.
 author: MSEdgeTeam
 ms.author: msedgedevrel
 ms.topic: article
diff --git a/microsoft-edge/devtools/whats-new/2024/10/devtools-130.md b/microsoft-edge/devtools/whats-new/2024/10/devtools-130.md
index d4f1282108..cceba18076 100644
--- a/microsoft-edge/devtools/whats-new/2024/10/devtools-130.md
+++ b/microsoft-edge/devtools/whats-new/2024/10/devtools-130.md
@@ -1,6 +1,6 @@
 ---
 title: What's new in DevTools (Microsoft Edge 130)
-description: "Detached Elements profile in Memory tool. Improved names of JavaScript objects in heap snapshots. Create collection or environment in Network Console.  Fixed icon bugs. Performance tab icon when throttled. High-contrast Warning count. And more."
+description: Detached Elements profile in Memory tool. Improved names of JavaScript objects in heap snapshots. Create collection or environment in Network Console.  Fixed icon bugs. Performance tab icon when throttled. High-contrast Warning count. And more.
 author: MSEdgeTeam
 ms.author: msedgedevrel
 ms.topic: article
diff --git a/microsoft-edge/devtools/whats-new/2024/11/devtools-131.md b/microsoft-edge/devtools/whats-new/2024/11/devtools-131.md
index a42e7e17e0..32e008224c 100644
--- a/microsoft-edge/devtools/whats-new/2024/11/devtools-131.md
+++ b/microsoft-edge/devtools/whats-new/2024/11/devtools-131.md
@@ -1,6 +1,6 @@
 ---
 title: What's new in DevTools (Microsoft Edge 131)
-description: "Can disable Edge experiment settings. View CSS selector stats information in Insights tab of sidebar panel in Performance tool. Fixed edit field to exit after pressing tab after auto-completion. Removed Visual Studio Code themes. And more."
+description: Can disable Edge experiment settings. View CSS selector stats information in Insights tab of sidebar panel in Performance tool. Fixed edit field to exit after pressing tab after auto-completion. Removed Visual Studio Code themes. And more.
 author: MSEdgeTeam
 ms.author: msedgedevrel
 ms.topic: article
@@ -74,7 +74,7 @@ See also:
 
 Pressing the **Tab** key after auto-completion now exits the edit field and focuses on the next focus point.  Before, pressing **Tab** would just indent the text.
 
-<!-- todo 
+<!-- todo
 See also:
 * []()
 -->
diff --git a/microsoft-edge/devtools/whats-new/2025/01/devtools-132.md b/microsoft-edge/devtools/whats-new/2025/01/devtools-132.md
index 098a798311..7380e6aae0 100644
--- a/microsoft-edge/devtools/whats-new/2025/01/devtools-132.md
+++ b/microsoft-edge/devtools/whats-new/2025/01/devtools-132.md
@@ -1,6 +1,6 @@
 ---
 title: What's new in DevTools (Microsoft Edge 132)
-description: "CSS selector costs include links in Insights sidebar. Right-click a tab to move it left or right in Quick View. Heap snapshot objects categorized by constructor names and source locations in Memory tool. And more."
+description: CSS selector costs include links in Insights sidebar. Right-click a tab to move it left or right in Quick View. Heap snapshot objects categorized by constructor names and source locations in Memory tool. And more.
 author: MSEdgeTeam
 ms.author: msedgedevrel
 ms.topic: article
@@ -20,7 +20,7 @@ These are the latest features in the Stable release of Microsoft Edge DevTools.
 
 The left sidebar in the **Performance** tool displays the costs of CSS selectors in the **Insights** tab when the **Enable CSS selector stats (slow)** checkbox is enabled.  Now, the selectors have links to the stylesheets that contain them.
 
-Some selectors might have more than one link when they are defined in multiple locations in a stylesheet or defined in multiple stylesheets.  For example, two links will be shown as **[1], [2]**. Selectors from user agent stylesheets or dynamically created stylesheets won't have links. 
+Some selectors might have more than one link when they are defined in multiple locations in a stylesheet or defined in multiple stylesheets.  For example, two links will be shown as **[1], [2]**. Selectors from user agent stylesheets or dynamically created stylesheets won't have links.
 
 ![CSS selector costs links](./devtools-132-images/selector-stats-links.png)
 
diff --git a/microsoft-edge/devtools/whats-new/2025/02/devtools-133.md b/microsoft-edge/devtools/whats-new/2025/02/devtools-133.md
index a194fe3066..2aa3080724 100644
--- a/microsoft-edge/devtools/whats-new/2025/02/devtools-133.md
+++ b/microsoft-edge/devtools/whats-new/2025/02/devtools-133.md
@@ -1,6 +1,6 @@
 ---
 title: What's new in DevTools (Microsoft Edge 133)
-description: "Move a tab left or right within the Elements or Sources tool. Screen reader improvements. And more."
+description: Move a tab left or right within the Elements or Sources tool. Screen reader improvements. And more.
 author: MSEdgeTeam
 ms.author: msedgedevrel
 ms.topic: article
diff --git a/microsoft-edge/devtools/whats-new/2025/03/devtools-134.md b/microsoft-edge/devtools/whats-new/2025/03/devtools-134.md
index 1ef99a25e3..702c7a500c 100644
--- a/microsoft-edge/devtools/whats-new/2025/03/devtools-134.md
+++ b/microsoft-edge/devtools/whats-new/2025/03/devtools-134.md
@@ -1,6 +1,6 @@
 ---
 title: What's new in DevTools (Microsoft Edge 134)
-description: "Forced reflow in the Performance Insights sidebar. Heap snapshot statistics account for every byte. Simplified DevTools Themes menu. And more."
+description: Forced reflow in the Performance Insights sidebar. Heap snapshot statistics account for every byte. Simplified DevTools Themes menu. And more.
 author: MSEdgeTeam
 ms.author: msedgedevrel
 ms.topic: article
@@ -24,7 +24,7 @@ The **Performance Insights** sidebar includes a new section called **Forced Refl
 
 
 <!-- ====================================================================== -->
-## Heap snapshot statistics account for every byte  
+## Heap snapshot statistics account for every byte
 
 <!-- Subtitle: View a memory allocation pie chart of your heap snapshot under Statistics-->
 
diff --git a/microsoft-edge/devtools/whats-new/2025/05/devtools-136.md b/microsoft-edge/devtools/whats-new/2025/05/devtools-136.md
index 4e047415e3..617aab996b 100644
--- a/microsoft-edge/devtools/whats-new/2025/05/devtools-136.md
+++ b/microsoft-edge/devtools/whats-new/2025/05/devtools-136.md
@@ -18,7 +18,7 @@ These are the latest features in the Stable release of Microsoft Edge DevTools.
 
 <!-- Subtitle: DOM elements with semantic errors are highlighted with a wavy line and a tooltip with a link. -->
 
-You can now easily identify semantic issues in the DOM tree of the **Elements** tool, such as: 
+You can now easily identify semantic issues in the DOM tree of the **Elements** tool, such as:
 * An invalid descendant of `<select>`.
 * Mismatched ARIA definitions.
 * Missing ARIA attributes.
diff --git a/microsoft-edge/devtools/whats-new/2025/06/devtools-137.md b/microsoft-edge/devtools/whats-new/2025/06/devtools-137.md
index 6530b63855..a46194c77d 100644
--- a/microsoft-edge/devtools/whats-new/2025/06/devtools-137.md
+++ b/microsoft-edge/devtools/whats-new/2025/06/devtools-137.md
@@ -32,7 +32,7 @@ To enable DevTools **Settings** sync:
 
    Your signed-in Microsoft Edge profile is displayed.
 
-1. In DevTools **Settings**, click the **Close** (![Close button](./devtools-137-images/close-button.png)) button. 
+1. In DevTools **Settings**, click the **Close** (![Close button](./devtools-137-images/close-button.png)) button.
 
 
 <!-- ====================================================================== -->
diff --git a/microsoft-edge/devtools/workspaces/workspace-tutorial.md b/microsoft-edge/devtools/workspaces/workspace-tutorial.md
index 5ab5e4a2b0..d958805f09 100644
--- a/microsoft-edge/devtools/workspaces/workspace-tutorial.md
+++ b/microsoft-edge/devtools/workspaces/workspace-tutorial.md
@@ -23,7 +23,7 @@ ms.date: 04/22/2025
    limitations under the License.  -->
 # Workspace tutorial (Sources tool Workspace tab)
 
-Use the following steps to use DevTools as an IDE, such as making webpage edits in the **Sources** tool's **Workspace** tab, saving changes to the source files on disk. 
+Use the following steps to use DevTools as an IDE, such as making webpage edits in the **Sources** tool's **Workspace** tab, saving changes to the source files on disk.
 
 You can read or follow these steps that show how to set up and using a workspace in DevTools.  After you set up a workspace, the changes that you make to the files in the workspace, by using DevTools, are saved on your local computer.
 
@@ -112,7 +112,7 @@ Continue with the next section.
    cd ~/GitHub/demos/workspaces
    python -m SimpleHTTPServer
    ```
-  
+
    ``` bash
    # Python 3 option
    cd ~/GitHub/demos/workspaces
diff --git a/microsoft-edge/dualengine/concepts/launching-internet-explorer.md b/microsoft-edge/dualengine/concepts/launching-internet-explorer.md
index eb74320e14..4f1bc83701 100644
--- a/microsoft-edge/dualengine/concepts/launching-internet-explorer.md
+++ b/microsoft-edge/dualengine/concepts/launching-internet-explorer.md
@@ -73,22 +73,22 @@ Contains a DWORD that indicates the location of the failure in the DualEngine st
 
 The DWORD maps to the following reasons:
 
-| DWORD | Reason                                                                                              |
-|:-----:|-----------------------------------------------------------------------------------------------------|
-|   0   | No failure.                                                                                         |
-|   1   | Unused.                                                                                             |
-|   2   | Unused.                                                                                             |
-|   3   | The version specified by the `DualEngineVersion` argument was 0.                                    |
-|   4   | Failed to canonicalize the path passed in via `DualEngineAdapter`; see the `StartupFailureHresult`. |
-|   5   | Unused.                                                                                             |
-|   6   | Unused.                                                                                             |
-|   7   | `LoadLibrary` failed for the provided adapter DLL; see the `StartupFailureHresult`.                 |
-|   8   | Could not find `DualEngineInitialize` in the adapter DLL.                                           |
-|   9   | The call to `DualEngineInitialize` failed; see the `StartupFailureHresult`.                         |
-|   10  | Failed to set the provided Application User Model ID; see the `StartupFailureHresult`.              |
-|   11  | DLL failed signature check.                                                                         |
-|   12  | Unused.                                                                                             |
-|   13  | DLL did not have IDENTITY LIMITEDACCESSFEATURE resource.                                            |
+| DWORD | Reason |
+|---|---|
+| 0 | No failure. |
+| 1 | Unused. |
+| 2 | Unused. |
+| 3 | The version specified by the `DualEngineVersion` argument was 0. |
+| 4 | Failed to canonicalize the path passed in via `DualEngineAdapter`; see the `StartupFailureHresult`. |
+| 5 | Unused. |
+| 6 | Unused. |
+| 7 | `LoadLibrary` failed for the provided adapter DLL; see the `StartupFailureHresult`.|
+| 8 | Could not find `DualEngineInitialize` in the adapter DLL.|
+| 9 | The call to `DualEngineInitialize` failed; see the `StartupFailureHresult`. |
+| 10 | Failed to set the provided Application User Model ID; see the `StartupFailureHresult`.|
+| 11 | DLL failed signature check. |
+| 12 | Unused. |
+| 13 | DLL did not have IDENTITY LIMITEDACCESSFEATURE resource. |
 
 
 <!-- ------------------------------ -->
diff --git a/microsoft-edge/dualengine/reference/accelerator.md b/microsoft-edge/dualengine/reference/accelerator.md
index 12545f272f..57345661fc 100644
--- a/microsoft-edge/dualengine/reference/accelerator.md
+++ b/microsoft-edge/dualengine/reference/accelerator.md
@@ -8,7 +8,7 @@ ms.service: microsoft-edge
 ms.subservice: windows-integration
 ms.date: 05/21/2024
 keywords: dual engine, dualengine, iemode, win32 apps, win32, edge, ie mode, edge html, ACCELERATOR
-topic_type: 
+topic_type:
 - APIRef
 api_name:
 - ACCELERATOR
@@ -24,8 +24,7 @@ api_location:
 # struct ACCELERATOR
 
 > [!IMPORTANT]
-> The DualEngine API is part of a Limited Access Feature (see [LimitedAccessFeatures class](/uwp/api/windows.applicationmodel.limitedaccessfeatures)). For more information or 
-> to request an unlock token, contact [Microsoft Support](https://go.microsoft.com/fwlink/?linkid=2271232).
+> The DualEngine API is part of a Limited Access Feature (see [LimitedAccessFeatures class](/uwp/api/windows.applicationmodel.limitedaccessfeatures)). For more information or to request an unlock token, contact [Microsoft Support](https://go.microsoft.com/fwlink/?linkid=2271232).
 
 Represents a keyboard accelerator (keyboard shortcut).
 
diff --git a/microsoft-edge/dualengine/reference/cryptdatablob.md b/microsoft-edge/dualengine/reference/cryptdatablob.md
index 8dbd66b9f8..479bdba6d5 100644
--- a/microsoft-edge/dualengine/reference/cryptdatablob.md
+++ b/microsoft-edge/dualengine/reference/cryptdatablob.md
@@ -8,7 +8,7 @@ ms.service: microsoft-edge
 ms.subservice: windows-integration
 ms.date: 05/21/2024
 keywords: dual engine, dualengine, iemode, win32 apps, win32, edge, ie mode, edge html, CryptDataBlob
-topic_type: 
+topic_type:
 - APIRef
 api_name:
 - CryptDataBlob
@@ -23,8 +23,7 @@ api_location:
 # struct CryptDataBlob
 
 > [!IMPORTANT]
-> The DualEngine API is part of a Limited Access Feature (see [LimitedAccessFeatures class](/uwp/api/windows.applicationmodel.limitedaccessfeatures)). For more information or 
-> to request an unlock token, contact [Microsoft Support](https://go.microsoft.com/fwlink/?linkid=2271232).
+> The DualEngine API is part of a Limited Access Feature (see [LimitedAccessFeatures class](/uwp/api/windows.applicationmodel.limitedaccessfeatures)). For more information or to request an unlock token, contact [Microsoft Support](https://go.microsoft.com/fwlink/?linkid=2271232).
 
 Represents an SSL Certificate.
 
diff --git a/microsoft-edge/dualengine/reference/dualengine-idl.md b/microsoft-edge/dualengine/reference/dualengine-idl.md
index b4882cec4d..a3eee947b7 100644
--- a/microsoft-edge/dualengine/reference/dualengine-idl.md
+++ b/microsoft-edge/dualengine/reference/dualengine-idl.md
@@ -8,7 +8,7 @@ ms.service: microsoft-edge
 ms.subservice: windows-integration
 ms.date: 05/21/2024
 keywords: dual engine, dualengine, iemode, win32 apps, win32, edge, ie mode, edge html
-topic_type: 
+topic_type:
 - APIRef
 api_name:
 - DualEngineInitialize
@@ -22,11 +22,12 @@ api_loction:
 # Globals
 
 > [!IMPORTANT]
-> The DualEngine API is part of a Limited Access Feature (see [LimitedAccessFeatures class](/uwp/api/windows.applicationmodel.limitedaccessfeatures)). For more information or 
-> to request an unlock token, contact [Microsoft Support](https://go.microsoft.com/fwlink/?linkid=2271232).
+> The DualEngine API is part of a Limited Access Feature (see [LimitedAccessFeatures class](/uwp/api/windows.applicationmodel.limitedaccessfeatures)). For more information or to request an unlock token, contact [Microsoft Support](https://go.microsoft.com/fwlink/?linkid=2271232).
 
 ## Summary
 
+<!-- gen'd .md; can keep table tagging as-is -->
+
  Members                        | Descriptions
 --------------------------------|---------------------------------------------
 [ACCELERATOREVENTTYPE](#acceleratoreventtype) | Specifies the type of accelerator event.
@@ -289,7 +290,7 @@ Flags that indicate the type of navigation that occurred.
 
  Values                         | Descriptions
 --------------------------------|---------------------------------------------
-NAVIGATIONFLAGS_NONE            | 
+NAVIGATIONFLAGS_NONE            |
 NAVIGATIONFLAGS_MAINFRAME            | Indicates that the top level page navigated, e.g.
 NAVIGATIONFLAGS_SAMEDOCUMENT            | Indicates that the navigation is within the same document, e.g. local anchor navigations.
 NAVIGATIONFLAGS_NEWPAGE            | Indicates that the navigation was to a new page, e.g.
diff --git a/microsoft-edge/dualengine/reference/dualenginecookie.md b/microsoft-edge/dualengine/reference/dualenginecookie.md
index 57d41dd4da..bce7963e54 100644
--- a/microsoft-edge/dualengine/reference/dualenginecookie.md
+++ b/microsoft-edge/dualengine/reference/dualenginecookie.md
@@ -8,7 +8,7 @@ ms.service: microsoft-edge
 ms.subservice: windows-integration
 ms.date: 05/21/2024
 keywords: dual engine, dualengine, iemode, win32 apps, win32, edge, ie mode, edge html, DualEngineCookie
-topic_type: 
+topic_type:
 - APIRef
 api_name:
 - DualEngineCookie
@@ -29,8 +29,7 @@ api_location:
 # struct DualEngineCookie
 
 > [!IMPORTANT]
-> The DualEngine API is part of a Limited Access Feature (see [LimitedAccessFeatures class](/uwp/api/windows.applicationmodel.limitedaccessfeatures)). For more information or 
-> to request an unlock token, contact [Microsoft Support](https://go.microsoft.com/fwlink/?linkid=2271232).
+> The DualEngine API is part of a Limited Access Feature (see [LimitedAccessFeatures class](/uwp/api/windows.applicationmodel.limitedaccessfeatures)). For more information or to request an unlock token, contact [Microsoft Support](https://go.microsoft.com/fwlink/?linkid=2271232).
 
 Represents the constituent parts of a cookie.
 
diff --git a/microsoft-edge/dualengine/reference/dualenginenewwindowoptions.md b/microsoft-edge/dualengine/reference/dualenginenewwindowoptions.md
index 812d7f6a83..b928466205 100644
--- a/microsoft-edge/dualengine/reference/dualenginenewwindowoptions.md
+++ b/microsoft-edge/dualengine/reference/dualenginenewwindowoptions.md
@@ -8,7 +8,7 @@ ms.service: microsoft-edge
 ms.subservice: windows-integration
 ms.date: 05/21/2024
 keywords: dual engine, dualengine, iemode, win32 apps, win32, edge, ie mode, edge html, DualEngineNewWindowOptions
-topic_type: 
+topic_type:
 - APIRef
 api_name:
 - DualEngineNewWindowOptions
@@ -34,8 +34,7 @@ api_location:
 # struct DualEngineNewWindowOptions
 
 > [!IMPORTANT]
-> The DualEngine API is part of a Limited Access Feature (see [LimitedAccessFeatures class](/uwp/api/windows.applicationmodel.limitedaccessfeatures)). For more information or 
-> to request an unlock token, contact [Microsoft Support](https://go.microsoft.com/fwlink/?linkid=2271232).
+> The DualEngine API is part of a Limited Access Feature (see [LimitedAccessFeatures class](/uwp/api/windows.applicationmodel.limitedaccessfeatures)). For more information or to request an unlock token, contact [Microsoft Support](https://go.microsoft.com/fwlink/?linkid=2271232).
 
 Represents the requested state of a new window.
 
diff --git a/microsoft-edge/dualengine/reference/dualenginesessionfactory.md b/microsoft-edge/dualengine/reference/dualenginesessionfactory.md
index fe053d6124..c1fa96bd1a 100644
--- a/microsoft-edge/dualengine/reference/dualenginesessionfactory.md
+++ b/microsoft-edge/dualengine/reference/dualenginesessionfactory.md
@@ -8,7 +8,7 @@ ms.service: microsoft-edge
 ms.subservice: windows-integration
 ms.date: 05/21/2024
 keywords: dual engine, dualengine, iemode, win32 apps, win32, edge, ie mode, edge html, DualEngineSessionFactory
-topic_type: 
+topic_type:
 - APIRef
 api_name:
 - DualEngineSessionFactory
@@ -24,8 +24,7 @@ api_location:
 # interface DualEngineSessionFactory
 
 > [!IMPORTANT]
-> The DualEngine API is part of a Limited Access Feature (see [LimitedAccessFeatures class](/uwp/api/windows.applicationmodel.limitedaccessfeatures)). For more information or 
-> to request an unlock token, contact [Microsoft Support](https://go.microsoft.com/fwlink/?linkid=2271232).
+> The DualEngine API is part of a Limited Access Feature (see [LimitedAccessFeatures class](/uwp/api/windows.applicationmodel.limitedaccessfeatures)). For more information or to request an unlock token, contact [Microsoft Support](https://go.microsoft.com/fwlink/?linkid=2271232).
 
 Factory object for DualEngine interfaces.
 
@@ -46,7 +45,7 @@ Returns the known DualEngine interface version, if there is one.
 > public STDMETHOD([GetSpecifiedVersion](#getspecifiedversion))(__out UINT * version) const
 
 ###### Parameters
-* `version` A pointer to a UINT where the version will be stored if there is one. 
+* `version` A pointer to a UINT where the version will be stored if there is one.
 
 ###### Returns
 S_OK if a known version was found, E_FAIL if it was not.
@@ -58,11 +57,12 @@ Gets a DualEngine Session object of the requested version.
 > public STDMETHOD([GetVersionedBrowserSession](#getversionedbrowsersession))(__in UINT version, __out IUnknown ** ppSession)
 
 > [!IMPORTANT]
-> This method must be called after Internet Explorer calls the export on DualEngineReady. See [Creating a DualEngine adapter plugin DLL](../concepts/adapter-dll.md). 
+> This method must be called after Internet Explorer calls the export on DualEngineReady. See [Creating a DualEngine adapter plugin DLL](../concepts/adapter-dll.md).
+
 ###### Parameters
-* `version` The version of the Session object to get. 
+* `version` The version of the Session object to get.
 
-* `ppSession` The Session object, if the version requested is supported. 
+* `ppSession` The Session object, if the version requested is supported.
 
 ###### Returns
 An HRESULT that indicates whether session creation was successful.
@@ -76,11 +76,12 @@ Called to unlock the DualEngine interface.
 > [!IMPORTANT]
 > This MUST be called successfully before any other methods on this interface can be called.
 
-Equivalent to `Windows::ApplicationModel::LimitedAccessFeatures::TryUnlockFeature` except it checks the adapter dll for the identity resource instead of the process .exe. 
+Equivalent to `Windows::ApplicationModel::LimitedAccessFeatures::TryUnlockFeature` except it checks the adapter dll for the identity resource instead of the process .exe.
+
 ###### Parameters
-* `token` The LAF token provided by Microsoft. 
+* `token` The LAF token provided by Microsoft.
 
-* `attestation` The attestation string provided by Microsoft. 
+* `attestation` The attestation string provided by Microsoft.
 
 ###### Returns
 An HRESULT that indicates whether unlocking was successful.
diff --git a/microsoft-edge/dualengine/reference/idualengine20browser.md b/microsoft-edge/dualengine/reference/idualengine20browser.md
index f5578b3354..fbca4bb78d 100644
--- a/microsoft-edge/dualengine/reference/idualengine20browser.md
+++ b/microsoft-edge/dualengine/reference/idualengine20browser.md
@@ -8,7 +8,7 @@ ms.service: microsoft-edge
 ms.subservice: windows-integration
 ms.date: 05/21/2024
 keywords: dual engine, dualengine, iemode, win32 apps, win32, edge, ie mode, edge html, IDualEngine20Browser
-topic_type: 
+topic_type:
 - APIRef
 api_name:
 - IDualEngine20Browser
@@ -56,8 +56,7 @@ api_location:
 # interface IDualEngine20Browser
 
 > [!IMPORTANT]
-> The DualEngine API is part of a Limited Access Feature (see [LimitedAccessFeatures class](/uwp/api/windows.applicationmodel.limitedaccessfeatures)). For more information or 
-> to request an unlock token, contact [Microsoft Support](https://go.microsoft.com/fwlink/?linkid=2271232).
+> The DualEngine API is part of a Limited Access Feature (see [LimitedAccessFeatures class](/uwp/api/windows.applicationmodel.limitedaccessfeatures)). For more information or to request an unlock token, contact [Microsoft Support](https://go.microsoft.com/fwlink/?linkid=2271232).
 
 ```cpp
 interface IDualEngine20Browser
@@ -155,7 +154,7 @@ Enables or disables Caret Browsing mode.
 > public HRESULT [DualEngineEnableCaretMode](#dualengineenablecaretmode)(BOOL fEnable)
 
 ###### Parameters
-* `fEnable` Specifies whether caret browsing should be enabled. 
+* `fEnable` Specifies whether caret browsing should be enabled.
 
 #### DualEngineExecNavigationCommand
 
@@ -173,11 +172,11 @@ Finds an instance of text on the page.
 > public HRESULT [DualEngineFindOnPage](#dualenginefindonpage)(int iRequestID, LPCWSTR pszFindText, BOOL fFindNext, BOOL fForward)
 
 ###### Parameters
-* `iRequestID` An ID to use correlate find on page requests and events. 
+* `iRequestID` An ID to use correlate find on page requests and events.
 
-* `pszFindText` The text to find on the page. 
+* `pszFindText` The text to find on the page.
 
-* `fFindNext` Indicates whether the selection should move to the next instance the find text, true advances the selection and false does not. 
+* `fFindNext` Indicates whether the selection should move to the next instance the find text, true advances the selection and false does not.
 
 * `fForward` Indicates the direction the selection should me, true moves forward and false moves backwards.
 
@@ -194,7 +193,7 @@ Provides a response to a geolocation permission request.
 > public HRESULT [DualEngineGeolocationPermissionResponse](#dualenginegeolocationpermissionresponse)(LPCWSTR pszUri, SITE_PERMISSION_RESPONSE response)
 
 ###### Parameters
-* `pszUri` The URI the geolocation request was from. 
+* `pszUri` The URI the geolocation request was from.
 
 * `response` The response to the request.
 
@@ -214,17 +213,17 @@ Initializes the browser object with an URL.
 > public HRESULT [DualEngineInitialize](#dualengineinitialize)([IDualEngine20BrowserObserver](idualengine20browserobserver.md) * pDualEngineObserver, DUALENGINECONFIGURATION config, EngineSwitchingPolicyFlags engineSwitchingPolicyFlags, [SentinelEntryInfo](tagsentinelentryinfo.md) sentinelEntryInfo, LPCWSTR pszUrl, HWND hwndHost, HWND * phwnd)
 
 ###### Parameters
-* `pDualEngineObserver` A pointer to the observer for this browser. 
+* `pDualEngineObserver` A pointer to the observer for this browser.
 
-* `config` Configuration flags for the desired browser behavior. 
+* `config` Configuration flags for the desired browser behavior.
 
-* `engineSwitchingPolicyFlags` Flags that determine how engine switching is handled. 
+* `engineSwitchingPolicyFlags` Flags that determine how engine switching is handled.
 
-* `sentinelEntryInfo` The number of history items before and after the initial navigation for this instance. 
+* `sentinelEntryInfo` The number of history items before and after the initial navigation for this instance.
 
-* `pszUrl` The inital URL to navigate to. 
+* `pszUrl` The inital URL to navigate to.
 
-* `hwndHost` The HWND of the host window that the browser window will be parented to. 
+* `hwndHost` The HWND of the host window that the browser window will be parented to.
 
 * `phwnd` The HWND of the browser window.
 
@@ -235,23 +234,23 @@ Initializes the browser object with an URL; this version allows for additional i
 > public HRESULT [DualEngineInitialize2](#dualengineinitialize2)([IDualEngine20BrowserObserver](idualengine20browserobserver.md) * pDualEngineObserver, DUALENGINECONFIGURATION config, EngineSwitchingPolicyFlags engineSwitchingPolicyFlags, [SentinelEntryInfo](tagsentinelentryinfo.md) sentinelEntryInfo, LPCWSTR pszUrl, HWND hwndHost, HWND * phwnd, LPCWSTR pszReferrer, LPCWSTR pszHeaders, VARIANT * postData)
 
 ###### Parameters
-* `pDualEngineObserver` A pointer to the observer for this browser. 
+* `pDualEngineObserver` A pointer to the observer for this browser.
 
-* `config` Configuration flags for the desired browser behavior. 
+* `config` Configuration flags for the desired browser behavior.
 
-* `engineSwitchingPolicyFlags` Flags that determine how engine switching is handled. 
+* `engineSwitchingPolicyFlags` Flags that determine how engine switching is handled.
 
-* `sentinelEntryInfo` The number of history items before and after the initial navigation for this instance. 
+* `sentinelEntryInfo` The number of history items before and after the initial navigation for this instance.
 
-* `pszUrl` The inital URL to navigate to. 
+* `pszUrl` The inital URL to navigate to.
 
-* `hwndHost` The HWND of the host window that the browser window will be parented to. 
+* `hwndHost` The HWND of the host window that the browser window will be parented to.
 
-* `phwnd` The HWND of the browser window. 
+* `phwnd` The HWND of the browser window.
 
-* `pszReferrer` The HTTP Referer request header for the initial navigation. 
+* `pszReferrer` The HTTP Referer request header for the initial navigation.
 
-* `pszHeaders` Additional headers to send to the server for the initial navigation. 
+* `pszHeaders` Additional headers to send to the server for the initial navigation.
 
 * `postData` Data to be sent to the server as part of a HTTP POST transaction for the initial navigation.
 
@@ -262,21 +261,21 @@ Initializes the browser object using tab recovery data.
 > public HRESULT [DualEngineInitializeWithRecoveryData](#dualengineinitializewithrecoverydata)(REFGUID guidTabId, ULONG ulEntryId, [IDualEngine20BrowserObserver](idualengine20browserobserver.md) * pDualEngineObserver, DUALENGINECONFIGURATION config, EngineSwitchingPolicyFlags engineSwitchingPolicyFlags, [SentinelEntryInfo](tagsentinelentryinfo.md) sentinelEntryInfo, LPCWSTR pszUrl, HWND hwndHost, HWND * phwnd)
 
 ###### Parameters
-* `guidTabId` The GUID for the source recovery data file to initialize this instance with. 
+* `guidTabId` The GUID for the source recovery data file to initialize this instance with.
 
-* `ulEntryId` The ID of the entry in the travel log to navigate to after recovery. 
+* `ulEntryId` The ID of the entry in the travel log to navigate to after recovery.
 
-* `pDualEngineObserver` A pointer to the observer for this browser. 
+* `pDualEngineObserver` A pointer to the observer for this browser.
 
-* `config` Configuration flags for the desired browser behavior. 
+* `config` Configuration flags for the desired browser behavior.
 
-* `engineSwitchingPolicyFlags` Flags that determine how engine switching is handled. 
+* `engineSwitchingPolicyFlags` Flags that determine how engine switching is handled.
 
-* `sentinelEntryInfo` The number of history items before and after the initial navigation for this instance. 
+* `sentinelEntryInfo` The number of history items before and after the initial navigation for this instance.
 
-* `pszUrl` The inital URL to navigate to. 
+* `pszUrl` The inital URL to navigate to.
 
-* `hwndHost` The HWND of the host window that the browser window will be parented to. 
+* `hwndHost` The HWND of the host window that the browser window will be parented to.
 
 * `phwnd` The HWND of the browser window.
 
@@ -296,7 +295,7 @@ Navigates to a URL.
 > public HRESULT [DualEngineNavigate](#dualenginenavigate)(LPCWSTR pszUrl, BOOL fSkipOnBeforeUnload)
 
 ###### Parameters
-* `pszUrl` The URL to navigate to. 
+* `pszUrl` The URL to navigate to.
 
 * `fSkipOnBeforeUnload` Whether to skip the `onBeforeUnload` handling.
 
@@ -307,13 +306,13 @@ Navigates to a URL, with additional information about the navigation.
 > public HRESULT [DualEngineNavigate2](#dualenginenavigate2)(LPCWSTR pszUrl, BOOL fSkipOnBeforeUnload, LPCWSTR pszReferrer, LPCWSTR pszHeaders, VARIANT * postData)
 
 ###### Parameters
-* `pszUrl` The URL to navigate to. 
+* `pszUrl` The URL to navigate to.
 
-* `fSkipOnBeforeUnload` Whether to skip the `onBeforeUnload` handling. 
+* `fSkipOnBeforeUnload` Whether to skip the `onBeforeUnload` handling.
 
-* `pszReferrer` The HTTP Referer request header for this navigation. 
+* `pszReferrer` The HTTP Referer request header for this navigation.
 
-* `pszHeaders` Additional headers to send to the server for this navigation. 
+* `pszHeaders` Additional headers to send to the server for this navigation.
 
 * `postData` Data to be sent to the server as part of a HTTP POST transaction for this navigation.
 
@@ -324,7 +323,7 @@ Notifies that navigation entries have been deleted.
 > public HRESULT [DualEngineNotifyNavigationEntriesDeleted](#dualenginenotifynavigationentriesdeleted)(BOOL fShouldDeleteEntries, [SentinelEntryInfo](tagsentinelentryinfo.md) sentinelEntryInfo)
 
 ###### Parameters
-* `fShouldDeleteEntries` Indicates whether the browser should delete all the entries in it's list. 
+* `fShouldDeleteEntries` Indicates whether the browser should delete all the entries in it's list.
 
 * `sentinelEntryInfo` The number of history items before and after the initial navigation for this instance.
 
@@ -395,11 +394,11 @@ Sets the size and position of the browser window.
 > public HRESULT [DualEngineSetPosition](#dualenginesetposition)(int x, int y, int iWidth, int iHeight)
 
 ###### Parameters
-* `x` The new position of the left side of the window, in client coordinates. 
+* `x` The new position of the left side of the window, in client coordinates.
 
-* `y` The new position of the top of the window, in client coordinates. 
+* `y` The new position of the top of the window, in client coordinates.
 
-* `iWidth` The new width of the window, in pixels. 
+* `iWidth` The new width of the window, in pixels.
 
 * `iHeight` The new height of the window, in pixels.
 
@@ -409,7 +408,7 @@ Changes the Theater mode state of the browser.
 
 > public HRESULT [DualEngineSetTheaterFullscreen](#dualenginesettheaterfullscreen)(BOOL fFullscreen)
 
-In theater mode, the browsers window fills the entire screen and displays a toolbar that has a minimal set of navigation buttons. A status bar is also provided in the upper-right corner of the screen. Explorer bars, such as History and Favorites, are displayed as an autohide pane on the left edge of the screen in theater mode. 
+In theater mode, the browsers window fills the entire screen and displays a toolbar that has a minimal set of navigation buttons. A status bar is also provided in the upper-right corner of the screen. Explorer bars, such as History and Favorites, are displayed as an autohide pane on the left edge of the screen in theater mode.
 ###### Parameters
 * `fFullscreen` If `true` and not currently in theater mode, the browser will enter theater mode; if `false` and currently in theater mode, the browser will exit theater mode.
 
@@ -420,7 +419,7 @@ Adjusts the top margin of the browser window when it is being displayed in theat
 > public HRESULT [DualEngineSetTheaterMargins](#dualenginesettheatermargins)(BOOL fTheaterShowing, int yTheaterThreshold)
 
 ###### Parameters
-* `fTheaterShowing` Indicates whether the host is currently in theater mode. 
+* `fTheaterShowing` Indicates whether the host is currently in theater mode.
 
 * `yTheaterThreshold` The size in pixels of the margin between the top of the screen and the fullscreen browser window.
 
@@ -440,7 +439,7 @@ Changes the style of the browser window.
 > public HRESULT [DualEngineSetWindowStyle](#dualenginesetwindowstyle)(int wlStyle, int wlExStyle)
 
 ###### Parameters
-* `wlStyle` The Window Style value to set. 
+* `wlStyle` The Window Style value to set.
 
 * `wlExStyle` The Extended Windows Style value to set.
 
@@ -460,7 +459,7 @@ Sends a simulated key input.
 > public HRESULT [DualEngineSimulateKeyInput](#dualenginesimulatekeyinput)(DWORD vKey, KEYACTION keyAction)
 
 ###### Parameters
-* `vKey` The virtual keycode to simulate. 
+* `vKey` The virtual keycode to simulate.
 
 * `keyAction` The key action to simulate.
 
@@ -471,9 +470,9 @@ Sends a simulated mouse input.
 > public HRESULT [DualEngineSimulateMouseInput](#dualenginesimulatemouseinput)(DWORD x, DWORD y, MOUSEACTION mouseAction)
 
 ###### Parameters
-* `x` The x coordinate. 
+* `x` The x coordinate.
 
-* `y` The y coordinate. 
+* `y` The y coordinate.
 
 * `mouseAction` The mouse action to simulate.
 
diff --git a/microsoft-edge/dualengine/reference/idualengine20browserobserver.md b/microsoft-edge/dualengine/reference/idualengine20browserobserver.md
index 43632e8910..35781907b0 100644
--- a/microsoft-edge/dualengine/reference/idualengine20browserobserver.md
+++ b/microsoft-edge/dualengine/reference/idualengine20browserobserver.md
@@ -8,7 +8,7 @@ ms.service: microsoft-edge
 ms.subservice: windows-integration
 ms.date: 05/21/2024
 keywords: dual engine, dualengine, iemode, win32 apps, win32, edge, ie mode, edge html, IDualEngine20BrowserObserver
-topic_type: 
+topic_type:
 - APIRef
 api_name:
 - IDualEngine20BrowserObserver
@@ -71,8 +71,7 @@ api_location:
 # interface IDualEngine20BrowserObserver
 
 > [!IMPORTANT]
-> The DualEngine API is part of a Limited Access Feature (see [LimitedAccessFeatures class](/uwp/api/windows.applicationmodel.limitedaccessfeatures)). For more information or 
-> to request an unlock token, contact [Microsoft Support](https://go.microsoft.com/fwlink/?linkid=2271232).
+> The DualEngine API is part of a Limited Access Feature (see [LimitedAccessFeatures class](/uwp/api/windows.applicationmodel.limitedaccessfeatures)). For more information or to request an unlock token, contact [Microsoft Support](https://go.microsoft.com/fwlink/?linkid=2271232).
 
 ```cpp
 interface IDualEngine20BrowserObserver
@@ -152,7 +151,7 @@ Raised when the browser wants to stop hosting content and have the navigation to
 > public HRESULT [ContinueNavigationInEdge](#continuenavigationinedge)(LPCWSTR pszUrl, ULONG ulCookieSyncVersion)
 
 ###### Parameters
-* `pszUrl` The URL that should be navigated to. 
+* `pszUrl` The URL that should be navigated to.
 
 * `ulCookieSyncVersion` A number that can be used to correlate a navigation with a specific cookie state.
 
@@ -163,13 +162,13 @@ Raised when the browser wants to stop hosting content and have the navigation to
 > public HRESULT [ContinueNavigationInEdge2](#continuenavigationinedge2)(LPCWSTR pszUrl, ULONG ulCookieSyncVersion, LPCWSTR pszReferrer, LPCWSTR pszHeaders, VARIANT * postData)
 
 ###### Parameters
-* `pszUrl` The URL that should be navigated to. 
+* `pszUrl` The URL that should be navigated to.
 
-* `ulCookieSyncVersion` A number that can be used to correlate a navigation with a specific cookie state. 
+* `ulCookieSyncVersion` A number that can be used to correlate a navigation with a specific cookie state.
 
-* `pszReferrer` The HTTP Referer request header. 
+* `pszReferrer` The HTTP Referer request header.
 
-* `pszHeaders` Additional HTTP headers. 
+* `pszHeaders` Additional HTTP headers.
 
 * `postData` HTTP POST data, such as form data.
 
@@ -189,7 +188,7 @@ Raised when the browser has deleted all entries in its travel log except for the
 > public HRESULT [OnAllButCurrentEntryDeleted](#onallbutcurrententrydeleted)([VisibleListUpdateEntry](visiblelistupdateentry.md) * pVisibleListEntries, int cVisibleListEntries)
 
 ###### Parameters
-* `pVisibleListEntries` A list containing the new travel log entries since the last update. In this case it will only have the current active entry. 
+* `pVisibleListEntries` A list containing the new travel log entries since the last update. In this case it will only have the current active entry.
 
 * `cVisibleListEntries` The number of items in `pVisibleListEntries`
 
@@ -248,9 +247,9 @@ Raised when a document is completely loaded and initialized.
 > public HRESULT [OnDocumentComplete](#ondocumentcomplete)(ULONG ulCurrentEntryId, [VisibleListUpdateEntry](visiblelistupdateentry.md) * pVisibleListEntries, int cVisibleListEntries)
 
 ###### Parameters
-* `ulCurrentEntryId` The travel log entry ID for the page that raised this event. 
+* `ulCurrentEntryId` The travel log entry ID for the page that raised this event.
 
-* `pVisibleListEntries` A list containing the new travel log entries since the last update. 
+* `pVisibleListEntries` A list containing the new travel log entries since the last update.
 
 * `cVisibleListEntries` The number of items in `pVisibleListEntries`
 
@@ -279,9 +278,9 @@ Raised when find on page results change.
 > public HRESULT [OnFindOnPageResult](#onfindonpageresult)(int iRequestID, int cMatches, int iActiveMatch)
 
 ###### Parameters
-* `iRequestID` An ID to correlate results with [IDualEngine20Browser::DualEngineFindOnPage()](idualengine20browser.md#dualenginefindonpage) requests. 
+* `iRequestID` An ID to correlate results with [IDualEngine20Browser::DualEngineFindOnPage()](idualengine20browser.md#dualenginefindonpage) requests.
 
-* `cMatches` The count of matches. 
+* `cMatches` The count of matches.
 
 * `iActiveMatch` The index of the selected match.
 
@@ -298,7 +297,7 @@ Raised when geolocation data is accessed.
 > public HRESULT [OnGeolocationFeatureInUse](#ongeolocationfeatureinuse)(LPCWSTR pszContextUrl, SITE_PERMISSION_FEATURE_MODE featureMode)
 
 ###### Parameters
-* `pszContextUrl` The URL of the page accessing geolocation data. 
+* `pszContextUrl` The URL of the page accessing geolocation data.
 
 * `featureMode` Indicates whether the access was blocked or allowed.
 
@@ -327,11 +326,11 @@ Raised when a navigation has been completed; provides status information about t
 > public HRESULT [OnIndicatorItemsSet](#onindicatoritemsset)(BOOL fProtectedMode, BOOL fEnhancedProtectedMode, DWORD dwUrlZone, BOOL fEnterpriseMode)
 
 ###### Parameters
-* `fProtectedMode` Indicates whether the browser is in Protected Mode. 
+* `fProtectedMode` Indicates whether the browser is in Protected Mode.
 
-* `fEnhancedProtectedMode` Indicates whether the browser is in Enhanced Protected Mode. 
+* `fEnhancedProtectedMode` Indicates whether the browser is in Enhanced Protected Mode.
 
-* `dwUrlZone` The zone of the current URL. 
+* `dwUrlZone` The zone of the current URL.
 
 * `fEnterpriseMode` Indicates whether the browser is in Enterprise Mode.
 
@@ -363,21 +362,21 @@ Raised when a navigation has been completed.
 > public HRESULT [OnNavigationComplete](#onnavigationcomplete)(REFGUID guidTabId, ULONG ulCurrentEntryId, [VisibleListUpdateEntry](visiblelistupdateentry.md) * pVisibleListEntries, int cVisibleListEntries, DWORD dwNavFlags, SECURELOCKICON secureLockIcon, DWORD dwSecurityFlags, [CryptDataBlob](cryptdatablob.md) * pDualEngineCertificates, int cCertificateChainBlobs)
 
 ###### Parameters
-* `guidTabId` The recovery GUID for tab. 
+* `guidTabId` The recovery GUID for tab.
 
-* `ulCurrentEntryId` The ID representing this navigation in the visible-entries list. 
+* `ulCurrentEntryId` The ID representing this navigation in the visible-entries list.
 
-* `pVisibleListEntries` A list containing the new travel log entries since the last update. 
+* `pVisibleListEntries` A list containing the new travel log entries since the last update.
 
-* `cVisibleListEntries` The number of items in `pVisibleListEntries`. 
+* `cVisibleListEntries` The number of items in `pVisibleListEntries`.
 
-* `dwNavFlags` Flags indicating the type of navigation that occurred. 
+* `dwNavFlags` Flags indicating the type of navigation that occurred.
 
-* `secureLockIcon` The security state of the page. 
+* `secureLockIcon` The security state of the page.
 
-* `dwSecurityFlags` Flags indicating any certificate errors for the page. 
+* `dwSecurityFlags` Flags indicating any certificate errors for the page.
 
-* `pDualEngineCertificates` A list containing the certificate chain for the current entry's page. 
+* `pDualEngineCertificates` A list containing the certificate chain for the current entry's page.
 
 * `cCertificateChainBlobs` The number of items in `pDualEngineCertificates`.
 
@@ -403,11 +402,11 @@ Raised when a new window has been created.
 > public HRESULT [OnNewWindow](#onnewwindow)([IDualEngine20Browser](idualengine20browser.md) * pNewBrowser, HWND hwnd, const [DualEngineNewWindowOptions](dualenginenewwindowoptions.md) * options, [IDualEngine20BrowserObserver](idualengine20browserobserver.md) ** ppObserver)
 
 ###### Parameters
-* `pNewBrowser` The browser object for the new window. 
+* `pNewBrowser` The browser object for the new window.
 
-* `hwnd` The handle for the new window. 
+* `hwnd` The handle for the new window.
 
-* `options` The options that the new window was created with. 
+* `options` The options that the new window was created with.
 
 * `ppObserver` The observer object for the new window.
 
@@ -418,7 +417,7 @@ Raised when a popup window was blocked.
 > public HRESULT [OnPopupBlocked](#onpopupblocked)(LPCWSTR pszContextUrl, LPCWSTR pszPopupUrl)
 
 ###### Parameters
-* `pszContextUrl` The URL of the page that issued the command to open the popup. 
+* `pszContextUrl` The URL of the page that issued the command to open the popup.
 
 * `pszPopupUrl` The URL of the popup page.
 
@@ -435,11 +434,11 @@ Raised when the browser has successfully handled a previous [IDualEngine20Browse
 > public HRESULT [OnReadyToExitRegion](#onreadytoexitregion)(REFGUID guidClonedTabId, ULONG ulCurrentEntryId, [VisibleListUpdateEntry](visiblelistupdateentry.md) * pVisibleListEntriesComplete, int cVisibleListEntriesComplete)
 
 ###### Parameters
-* `guidClonedTabId` The GUID of the tab recovery data file backing the exited region. 
+* `guidClonedTabId` The GUID of the tab recovery data file backing the exited region.
 
-* `ulCurrentEntryId` The travel log entry ID for the page that raised this event. 
+* `ulCurrentEntryId` The travel log entry ID for the page that raised this event.
 
-* `pVisibleListEntriesComplete` A list containing the new travel log entries since the last update. 
+* `pVisibleListEntriesComplete` A list containing the new travel log entries since the last update.
 
 * `cVisibleListEntriesComplete` The number of items in `pVisibleListEntriesComplete`
 
@@ -471,7 +470,7 @@ Raised when processing a keyboard accelerator and it is determined that the brow
 > public HRESULT [OnUnhandledKeyboardAccelerator](#onunhandledkeyboardaccelerator)(LPMSG lpMsg)
 
 ###### Parameters
-* `lpMsg` The win32 message for the unhandled keyboard accelerator. 
+* `lpMsg` The win32 message for the unhandled keyboard accelerator.
 
 #### OnUnhandledKeyboardAcceleratorAsync
 
@@ -479,13 +478,13 @@ Raised when processing a keyboard accelerator and it is determined that browser
 
 > public HRESULT [OnUnhandledKeyboardAcceleratorAsync](#onunhandledkeyboardacceleratorasync)(LPMSG pMsg, BOOL isShiftDown, BOOL isCtrlDown, BOOL isAltDown)
 
-In this version of the method, the event is raised asynchronously and keyboard state may have changed since it was processed, so the state of the modifier keys is provided. 
+In this version of the method, the event is raised asynchronously and keyboard state may have changed since it was processed, so the state of the modifier keys is provided.
 ###### Parameters
-* `pMsg` The win32 message for the unhandled keyboard accelerator. 
+* `pMsg` The win32 message for the unhandled keyboard accelerator.
 
-* `isShiftDown` Indicates whether the **Shift** key was pressed. 
+* `isShiftDown` Indicates whether the **Shift** key was pressed.
 
-* `isCtrlDown` Indicates whether the **Ctrl** key was pressed. 
+* `isCtrlDown` Indicates whether the **Ctrl** key was pressed.
 
 * `isAltDown` Indicates whether the **Alt** key was pressed.
 
@@ -511,9 +510,9 @@ Raised when the browser is requesting the host to navigate to a URL in a new win
 > public HRESULT [OpenURLInEdge](#openurlinedge)(LPCWSTR pszUrl, const [DualEngineNewWindowOptions](dualenginenewwindowoptions.md) * options, ULONG ulCookieSyncVersion)
 
 ###### Parameters
-* `pszUrl` The URL to navigate to. 
+* `pszUrl` The URL to navigate to.
 
-* `options` Options to apply to the new window. 
+* `options` Options to apply to the new window.
 
 * `ulCookieSyncVersion` A number that can be used to correlate a navigation with a specific cookie state.
 
@@ -524,15 +523,15 @@ Raised when the browser is requesting the host to navigate to a URL in a new win
 > public HRESULT [OpenURLInEdge2](#openurlinedge2)(LPCWSTR pszUrl, const [DualEngineNewWindowOptions](dualenginenewwindowoptions.md) * options, ULONG ulCookieSyncVersion, LPCWSTR pszReferrer, LPCWSTR pszHeaders, VARIANT * postData)
 
 ###### Parameters
-* `pszUrl` The URL to navigate to. 
+* `pszUrl` The URL to navigate to.
 
-* `options` Options to apply to the navigation. 
+* `options` Options to apply to the navigation.
 
-* `ulCookieSyncVersion` A number that can be used to correlate a navigation with a specific cookie state. 
+* `ulCookieSyncVersion` A number that can be used to correlate a navigation with a specific cookie state.
 
-* `pszReferrer` The HTTP Referer request header. 
+* `pszReferrer` The HTTP Referer request header.
 
-* `pszHeaders` Additional HTTP headers. 
+* `pszHeaders` Additional HTTP headers.
 
 * `postData` HTTP POST data, such as form data.
 
@@ -543,7 +542,7 @@ Raised when a page has been requested to be added to favorites.
 > public HRESULT [RequestHostAddFavorite](#requesthostaddfavorite)(LPCWSTR pszTitle, LPCWSTR pszUrl)
 
 ###### Parameters
-* `pszTitle` The title of the page. 
+* `pszTitle` The title of the page.
 
 * `pszUrl` The URL of the page.
 
@@ -563,7 +562,7 @@ Raised when focus is being requested to move to the host window.
 > public HRESULT [RequestHostFocus](#requesthostfocus)(DUALENGINE_FOCUSDIRECTION focusDirection, const MSG * msg)
 
 ###### Parameters
-* `focusDirection` The direction that focus is moving. 
+* `focusDirection` The direction that focus is moving.
 
 * `msg` A pointer to the message that caused the focus change.
 
@@ -589,13 +588,13 @@ Raised when the browser requests that the host change its size or position.
 > public HRESULT [RequestHostPositionChanged](#requesthostpositionchanged)(LONG nX, LONG nY, LONG nWidth, LONG nHeight, ULONGLONG hSyncEvent)
 
 ###### Parameters
-* `nX` The requested window X position. 
+* `nX` The requested window X position.
 
-* `nY` The requested window Y position. 
+* `nY` The requested window Y position.
 
-* `nWidth` The requested window width. 
+* `nWidth` The requested window width.
 
-* `nHeight` The requested window height. 
+* `nHeight` The requested window height.
 
 * `hSyncEvent` A handle to the event object that should be signaled when the change is complete.
 
@@ -623,9 +622,9 @@ Raised when the host is requested to take or give up focus.
 
 > public HRESULT [RequestHostWindowFocusSync](#requesthostwindowfocussync)(BOOL fFocus, ULONGLONG hSyncEvent)
 
-In this version of the method, the browser will wait until the provided event is signaled. 
+In this version of the method, the browser will wait until the provided event is signaled.
 ###### Parameters
-* `fFocus` Indicates what should be done with focus. If `true`, focus should be taken; otherwise it should be relinquished. 
+* `fFocus` Indicates what should be done with focus. If `true`, focus should be taken; otherwise it should be relinquished.
 
 * `hSyncEvent` A handle to the event object that should be signaled when the change is complete.
 
@@ -636,11 +635,11 @@ Raised when the favicon has changed.
 > public HRESULT [UpdateHostFavicon](#updatehostfavicon)(ULONG ulCurrentEntryId, LPCWSTR spszCurrentUrl, LPCWSTR * pIconUrls, int cIconUrls)
 
 ###### Parameters
-* `ulCurrentEntryId` The travel log entry ID for the page that raised this event. 
+* `ulCurrentEntryId` The travel log entry ID for the page that raised this event.
 
-* `spszCurrentUrl` The URL of the page. 
+* `spszCurrentUrl` The URL of the page.
 
-* `pIconUrls` A list of favicon URLs. 
+* `pIconUrls` A list of favicon URLs.
 
 * `cIconUrls` The number of items in `pIconUrls`.
 
@@ -651,7 +650,7 @@ Raised when the title of the page has been updated.
 > public HRESULT [UpdateHostTitle](#updatehosttitle)(ULONG ulCurrentEntryId, LPCWSTR pszTitle)
 
 ###### Parameters
-* `ulCurrentEntryId` The ID of the page in the visible-entries list that raised this event. 
+* `ulCurrentEntryId` The ID of the page in the visible-entries list that raised this event.
 
 * `pszTitle` The new title.
 
@@ -662,6 +661,6 @@ Raised when security information of the page has changed.
 > public HRESULT [UpdateSecureLockIcon](#updatesecurelockicon)(ULONG ulCurrentEntryId, SECURELOCKICON secureLockIcon)
 
 ###### Parameters
-* `ulCurrentEntryId` The travel log entry for this change. 
+* `ulCurrentEntryId` The travel log entry for this change.
 
 * `secureLockIcon` The state of the security information.
diff --git a/microsoft-edge/dualengine/reference/idualengine20browsersession.md b/microsoft-edge/dualengine/reference/idualengine20browsersession.md
index ba5e144707..2cf55de8b3 100644
--- a/microsoft-edge/dualengine/reference/idualengine20browsersession.md
+++ b/microsoft-edge/dualengine/reference/idualengine20browsersession.md
@@ -8,7 +8,7 @@ ms.service: microsoft-edge
 ms.subservice: windows-integration
 ms.date: 05/21/2024
 keywords: dual engine, dualengine, iemode, win32 apps, win32, edge, ie mode, edge html, IDualEngine20BrowserSession
-topic_type: 
+topic_type:
 - APIRef
 api_name:
 - IDualEngine20BrowserSession
@@ -38,8 +38,7 @@ api_location:
 # interface IDualEngine20BrowserSession
 
 > [!IMPORTANT]
-> The DualEngine API is part of a Limited Access Feature (see [LimitedAccessFeatures class](/uwp/api/windows.applicationmodel.limitedaccessfeatures)). For more information or 
-> to request an unlock token, contact [Microsoft Support](https://go.microsoft.com/fwlink/?linkid=2271232).
+> The DualEngine API is part of a Limited Access Feature (see [LimitedAccessFeatures class](/uwp/api/windows.applicationmodel.limitedaccessfeatures)). For more information or to request an unlock token, contact [Microsoft Support](https://go.microsoft.com/fwlink/?linkid=2271232).
 
 ```cpp
 interface IDualEngine20BrowserSession
@@ -86,9 +85,9 @@ Duplicates an active tab's recovery data.
 > public HRESULT [CloneActiveTabRecoveryData](#cloneactivetabrecoverydata)(HWND hwndBrowser, REFGUID guidSrcFile, REFGUID guidDestFile)
 
 ###### Parameters
-* `hwndBrowser` The HWND of the hosted browser window. 
+* `hwndBrowser` The HWND of the hosted browser window.
 
-* `guidSrcFile` The GUID for the source recovery data file to copy. 
+* `guidSrcFile` The GUID for the source recovery data file to copy.
 
 * `guidDestFile` The GUID to associate with the new tab recovery data file.
 
@@ -99,7 +98,7 @@ Duplicates an inactive tab's recovery data.
 > public HRESULT [CloneInactiveTabRecoveryData](#cloneinactivetabrecoverydata)(REFGUID guidSrcFile, REFGUID guidDestFile)
 
 ###### Parameters
-* `guidSrcFile` The GUID for the source recovery data file to copy. 
+* `guidSrcFile` The GUID for the source recovery data file to copy.
 
 * `guidDestFile` The GUID to associate with the new tab recovery data file.
 
@@ -119,7 +118,7 @@ Deletes all but the provided tab recovery data files.
 > public HRESULT [DeleteAllButRecoverableRecoveryFiles](#deleteallbutrecoverablerecoveryfiles)(int cRecoverableGUIDs, LPCWSTR * rgpszRecoverableGUIDs)
 
 ###### Parameters
-* `cRecoverableGUIDs` The number of GUIDs in `rgpszRecoverableGUIDs`. 
+* `cRecoverableGUIDs` The number of GUIDs in `rgpszRecoverableGUIDs`.
 
 * `rgpszRecoverableGUIDs` An array of GUIDs representing tab recovery data files that are not to be deleted.
 
@@ -139,7 +138,7 @@ Returns a list of keyboard accelerators that should be forwarded from the Host.
 > public HRESULT [GetRequestedHostForwardedAccelerators](#getrequestedhostforwardedaccelerators)(DWORD * pcAccels, [ACCELERATOR](accelerator.md) ** prgAccels)
 
 ###### Parameters
-* `pcAccels` The number of accelerators in `prgAccels`. 
+* `pcAccels` The number of accelerators in `prgAccels`.
 
 * `prgAccels` A list of keyboard accelerators that should be forwarded. When finished the caller must free the memory allocated for the list with `CoTaskMemFree`.
 
@@ -150,13 +149,13 @@ Initializes the session.
 > public HRESULT [Initialize](#initialize)(DWORD cAccels, [ACCELERATOR](accelerator.md) * rgHostPriorityAccels, [IDualEngine20BrowserSessionObserver](idualengine20browsersessionobserver.md) * pSessionObserver, LPCWSTR pszProfilePath, LPCWSTR pszProfileId)
 
 ###### Parameters
-* `cAccels` The number of accelerators in `rgHostPriorityAccels`. 
+* `cAccels` The number of accelerators in `rgHostPriorityAccels`.
 
-* `rgHostPriorityAccels` A list of keyboard accelerators to have the session forward to the host. 
+* `rgHostPriorityAccels` A list of keyboard accelerators to have the session forward to the host.
 
-* `pSessionObserver` An observer for events from this session. 
+* `pSessionObserver` An observer for events from this session.
 
-* `pszProfilePath` The path to host's profile path where the session will store relevant files. 
+* `pszProfilePath` The path to host's profile path where the session will store relevant files.
 
 * `pszProfileId` The host's profile ID to associate with this session.
 
@@ -185,7 +184,7 @@ Sets hang detection messages that will be sent to the session by the host to det
 > public HRESULT [SetHangDetectionMessages](#sethangdetectionmessages)(UINT uiSyncHungCheckMsg, UINT uiAsyncHungCheckMsg)
 
 ###### Parameters
-* `uiSyncHungCheckMsg` The window message ID of the message that the host will synchronously wait on to be handled. 
+* `uiSyncHungCheckMsg` The window message ID of the message that the host will synchronously wait on to be handled.
 
 * `uiAsyncHungCheckMsg` The window message ID of the message that the host will asynchronously wait on. Browsers signal the host by calling [IDualEngine20BrowserObserver::OnAsyncHungCheckReply()](idualengine20browserobserver.md#onasynchungcheckreply).
 
@@ -226,7 +225,7 @@ Sets site permissions for the session.
 <!-- ---------- -->
 ###### Parameters
 
-* `sitePermissionKind` The type of site permission that is being set. 
+* `sitePermissionKind` The type of site permission that is being set.
 
 * `pszPermissionData` A serialized string of the permission data to set.
 
@@ -305,6 +304,6 @@ Sends cookie data to the session process.
 > public HRESULT [SyncCookies](#synccookies)(const [DualEngineCookie](dualenginecookie.md) * pCookies, DWORD cCookies)
 
 ###### Parameters
-* `pCookies` An array of cookies to be sent to the session. 
+* `pCookies` An array of cookies to be sent to the session.
 
 * `cCookies` The number of items in `pCookies`.
diff --git a/microsoft-edge/dualengine/reference/idualengine20browsersessionobserver.md b/microsoft-edge/dualengine/reference/idualengine20browsersessionobserver.md
index c9b84d3350..fa3f42aa50 100644
--- a/microsoft-edge/dualengine/reference/idualengine20browsersessionobserver.md
+++ b/microsoft-edge/dualengine/reference/idualengine20browsersessionobserver.md
@@ -8,7 +8,7 @@ ms.service: microsoft-edge
 ms.subservice: windows-integration
 ms.date: 05/21/2024
 keywords: dual engine, dualengine, iemode, win32 apps, win32, edge, ie mode, edge html, IDualEngine20BrowserSessionObserver
-topic_type: 
+topic_type:
 - APIRef
 api_name:
 - IDualEngine20BrowserSessionObserver
@@ -24,8 +24,7 @@ api_location:
 # interface IDualEngine20BrowserSessionObserver
 
 > [!IMPORTANT]
-> The DualEngine API is part of a Limited Access Feature (see [LimitedAccessFeatures class](/uwp/api/windows.applicationmodel.limitedaccessfeatures)). For more information or 
-> to request an unlock token, contact [Microsoft Support](https://go.microsoft.com/fwlink/?linkid=2271232).
+> The DualEngine API is part of a Limited Access Feature (see [LimitedAccessFeatures class](/uwp/api/windows.applicationmodel.limitedaccessfeatures)). For more information or to request an unlock token, contact [Microsoft Support](https://go.microsoft.com/fwlink/?linkid=2271232).
 
 ```cpp
 interface IDualEngine20BrowserSessionObserver
@@ -58,7 +57,7 @@ Raised when the session Download window is requesting to navigate to a URL.
 > public HRESULT [NavigateDownloadLink](#navigatedownloadlink)(BSTR url, VARIANT * PostData)
 
 ###### Parameters
-* `url` The URL that should be navigated to. 
+* `url` The URL that should be navigated to.
 
 * `PostData` HTTP POST data, such as form data.
 
@@ -71,9 +70,9 @@ Raised when a cookie is set in the session, if reverse cookie sync is enabled.
 See [IDualEngine20BrowserSession::SetReverseCookieSync](idualengine20browsersession.md#setreversecookiesync).
 
 ###### Parameters
-* `pCookies` The cookies that were set. 
+* `pCookies` The cookies that were set.
 
-* `cCookies` The number of cookies in `pCookies`. 
+* `cCookies` The number of cookies in `pCookies`.
 
 * `ulCookieSyncVersion` A number that can be used to correlate the specific cookie state with a navigation.
 
diff --git a/microsoft-edge/dualengine/reference/index.md b/microsoft-edge/dualengine/reference/index.md
index 7032e8d410..29ab64d80e 100644
--- a/microsoft-edge/dualengine/reference/index.md
+++ b/microsoft-edge/dualengine/reference/index.md
@@ -11,11 +11,12 @@ ms.date: 05/21/2024
 ---
 # DualEngine Win32 C++ Reference
 
+<!-- the .md files in this dir are gen'd; generally keep them as-is -->
+
 > [!IMPORTANT]
-> The DualEngine API is part of a Limited Access Feature (see [LimitedAccessFeatures class](/uwp/api/windows.applicationmodel.limitedaccessfeatures)). For more information or 
-> to request an unlock token, contact [Microsoft Support](https://go.microsoft.com/fwlink/?linkid=2271232).
+> The DualEngine API is part of a Limited Access Feature (see [LimitedAccessFeatures class](/uwp/api/windows.applicationmodel.limitedaccessfeatures)). For more information or to request an unlock token, contact [Microsoft Support](https://go.microsoft.com/fwlink/?linkid=2271232).
 
-The Microsoft DualEngine API enables you to host and control an Internet Explorer instance within your app.  For more information, see [Introduction to the Microsoft DualEngine API](../intro.md) and [Getting started with the DualEngine API](../get-started.md). 
+The Microsoft DualEngine API enables you to host and control an Internet Explorer instance within your app.  For more information, see [Introduction to the Microsoft DualEngine API](../intro.md) and [Getting started with the DualEngine API](../get-started.md).
 
 ## Globals
 
diff --git a/microsoft-edge/dualengine/reference/tagsentinelentryinfo.md b/microsoft-edge/dualengine/reference/tagsentinelentryinfo.md
index e2654cabe1..0f032583a7 100644
--- a/microsoft-edge/dualengine/reference/tagsentinelentryinfo.md
+++ b/microsoft-edge/dualengine/reference/tagsentinelentryinfo.md
@@ -8,7 +8,7 @@ ms.service: microsoft-edge
 ms.subservice: windows-integration
 ms.date: 05/21/2024
 keywords: dual engine, dualengine, iemode, win32 apps, win32, edge, ie mode, edge html, tagSentinelEntryInfo
-topic_type: 
+topic_type:
 - APIRef
 api_name:
 - tagSentinelEntryInfo
@@ -23,8 +23,7 @@ api_location:
 # struct tagSentinelEntryInfo
 
 > [!IMPORTANT]
-> The DualEngine API is part of a Limited Access Feature (see [LimitedAccessFeatures class](/uwp/api/windows.applicationmodel.limitedaccessfeatures)). For more information or 
-> to request an unlock token, contact [Microsoft Support](https://go.microsoft.com/fwlink/?linkid=2271232).
+> The DualEngine API is part of a Limited Access Feature (see [LimitedAccessFeatures class](/uwp/api/windows.applicationmodel.limitedaccessfeatures)). For more information or to request an unlock token, contact [Microsoft Support](https://go.microsoft.com/fwlink/?linkid=2271232).
 
 Represents the position of the current region in the travel log.
 
diff --git a/microsoft-edge/dualengine/reference/visiblelistupdateentry.md b/microsoft-edge/dualengine/reference/visiblelistupdateentry.md
index 7413b8eb42..00199bcb34 100644
--- a/microsoft-edge/dualengine/reference/visiblelistupdateentry.md
+++ b/microsoft-edge/dualengine/reference/visiblelistupdateentry.md
@@ -8,7 +8,7 @@ ms.service: microsoft-edge
 ms.subservice: windows-integration
 ms.date: 05/21/2024
 keywords: dual engine, dualengine, iemode, win32 apps, win32, edge, ie mode, edge html, VisibleListUpdateEntry
-topic_type: 
+topic_type:
 - APIRef
 api_name:
 - VisibleListUpdateEntry
@@ -26,8 +26,7 @@ api_location:
 # struct VisibleListUpdateEntry
 
 > [!IMPORTANT]
-> The DualEngine API is part of a Limited Access Feature (see [LimitedAccessFeatures class](/uwp/api/windows.applicationmodel.limitedaccessfeatures)). For more information or 
-> to request an unlock token, contact [Microsoft Support](https://go.microsoft.com/fwlink/?linkid=2271232).
+> The DualEngine API is part of a Limited Access Feature (see [LimitedAccessFeatures class](/uwp/api/windows.applicationmodel.limitedaccessfeatures)). For more information or to request an unlock token, contact [Microsoft Support](https://go.microsoft.com/fwlink/?linkid=2271232).
 
 Represents a change to a travel log entry.
 
diff --git a/microsoft-edge/extensions/developer-guide/declare-permissions.md b/microsoft-edge/extensions/developer-guide/declare-permissions.md
index d3a010b14f..4b11ac502b 100644
--- a/microsoft-edge/extensions/developer-guide/declare-permissions.md
+++ b/microsoft-edge/extensions/developer-guide/declare-permissions.md
@@ -71,7 +71,7 @@ Here's an example of the permissions part of a manifest file:
 The following table lists the currently available permission strings to use in your manifest, and the descriptions.
 
 | Permission string | Details |
-|:--- |:--- |
+|---|---|
 | `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/>Disabled extensions are treated as if they aren't installed. <br/>You should use the `background` permission with service workers; see [About extension service workers](https://developer.chrome.com/docs/extensions/develop/concepts/service-workers)<!-- chrome link ok, no doc'n of service workers in extensions at lmc --> at developer.chrome.com. |
diff --git a/microsoft-edge/extensions/developer-guide/devtools-extension-sample.md b/microsoft-edge/extensions/developer-guide/devtools-extension-sample.md
index 45e6f3b7ef..6917a6e9cf 100644
--- a/microsoft-edge/extensions/developer-guide/devtools-extension-sample.md
+++ b/microsoft-edge/extensions/developer-guide/devtools-extension-sample.md
@@ -181,7 +181,7 @@ Download the "main" branch of the Demos repo, as follows:
    <h2>Custom DevTools Tool</h2>
    ```
 
-   to:  
+   to: 
 
    ```html
    <h2>My Custom DevTools Tool</h2>
@@ -199,7 +199,7 @@ Download the "main" branch of the Demos repo, as follows:
    "name": "Custom DevTools Tool",
    ```
 
-   to:  
+   to: 
 
    ```json
    "name": "My Custom DevTools Tool",
diff --git a/microsoft-edge/extensions/developer-guide/devtools-extension.md b/microsoft-edge/extensions/developer-guide/devtools-extension.md
index 07c5426614..9bead2805c 100644
--- a/microsoft-edge/extensions/developer-guide/devtools-extension.md
+++ b/microsoft-edge/extensions/developer-guide/devtools-extension.md
@@ -325,7 +325,7 @@ When the user clicks the `sayHello` button, `devtools.js` runs code directly in
 
 When the user clicks anywhere in the inspected window, the DevTools extensions receive a message with `request.click == true` and the mouse position information.
 
-See also: 
+See also:
 * [devtools.js](https://github.com/MicrosoftEdge/Demos/blob/main/devtools-extension/devtools.js) - source file in repo.
 * [Supported APIs for Microsoft Edge extensions](../developer-guide/api-support.md)
    * [chrome.devtools.panels](https://developer.chrome.com/docs/extensions/reference/api/devtools/panels)
diff --git a/microsoft-edge/extensions/developer-guide/manifest-v3.md b/microsoft-edge/extensions/developer-guide/manifest-v3.md
index 147e7d490b..65f4252a67 100644
--- a/microsoft-edge/extensions/developer-guide/manifest-v3.md
+++ b/microsoft-edge/extensions/developer-guide/manifest-v3.md
@@ -56,7 +56,7 @@ For information about end of support for Manifest V2 extensions in the Chromium
 * [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) website
 * [Manifest V3 changes are now available to test in Microsoft Edge](https://blogs.windows.com/msedgedev/2020/10/14/extension-manifest-chromium-edge/) blog post
 
-Chromium docs: 
+Chromium docs:
 * [Chromium project](https://www.chromium.org/Home/)
 * [Manifest V2 support timeline](https://developer.chrome.com/docs/extensions/develop/migrate/mv2-deprecation-timeline)<!-- chrome link ok here -->
 * [The phase-out timeline](https://developer.chrome.com/blog/resuming-the-transition-to-mv3#the_phase-out_timeline)<!-- chrome link ok here --> in _Resuming the transition to Manifest V3_.
diff --git a/microsoft-edge/extensions/developer-guide/match-patterns.md b/microsoft-edge/extensions/developer-guide/match-patterns.md
index 19cf641e6b..928d2f1d26 100644
--- a/microsoft-edge/extensions/developer-guide/match-patterns.md
+++ b/microsoft-edge/extensions/developer-guide/match-patterns.md
@@ -54,7 +54,7 @@ The meaning of `*` depends on whether it is in the scheme, host, or path part.
 ## Examples of valid patterns
 
 | Pattern | What it does | Examples of matching URLs |
-|:--- |:--- |:--- |
+|---|---|---|
 | `http://*/*` | Matches any URL that uses the http scheme | `http://www.google.com` `http://example.org/foo/bar.html` |
 | `http://*/foo*` | Matches any URL that uses the http scheme, on any host, as long as the path starts with `/foo` | `http://example.com/foo/bar.html` `http://www.google.com/foo` |
 | `https://*.google.com/foo*bar` | Matches any URL that uses the https scheme, is on a `google.com` host (such as `www.google.com`, `docs.google.com`, or `google.com`), as long as the path starts with `/foo` and ends with `bar` | `https://www.google.com/foo/baz/bar` `https://docs.google.com/foobar` |
@@ -71,7 +71,7 @@ The meaning of `*` depends on whether it is in the scheme, host, or path part.
 Here are some examples of `_invalid_` pattern matches:
 
 | Bad pattern | Why it is bad |
-|:--- |:--- |
+|---|---|
 | `http://www.foo.com` | No `_path_` |
 | `http://*foo/bar` | '`*`' in the host can be followed only by a '`.`' or '`/`' |
 | `http://foo.*.bar/baz` | If '`*`' is in the `_host_`, it must be the first character |
diff --git a/microsoft-edge/extensions/developer-guide/migrate-your-extension-from-manifest-v2-to-v3.md b/microsoft-edge/extensions/developer-guide/migrate-your-extension-from-manifest-v2-to-v3.md
index a1136c2b47..5628db1200 100644
--- a/microsoft-edge/extensions/developer-guide/migrate-your-extension-from-manifest-v2-to-v3.md
+++ b/microsoft-edge/extensions/developer-guide/migrate-your-extension-from-manifest-v2-to-v3.md
@@ -74,7 +74,7 @@ Enterprises can continue to use the blocking behavior of the Web Request API for
 <!-- ====================================================================== -->
 ## Background service workers
 
-To migrate your extensions from background pages to service workers, see [Migrate to a service worker](https://developer.chrome.com/docs/extensions/develop/migrate/to-service-workers)<!-- chrome link ok -->.  
+To migrate your extensions from background pages to service workers, see [Migrate to a service worker](https://developer.chrome.com/docs/extensions/develop/migrate/to-service-workers)<!-- chrome link ok -->. 
 
 
 <!-- ====================================================================== -->
diff --git a/microsoft-edge/extensions/developer-guide/native-messaging.md b/microsoft-edge/extensions/developer-guide/native-messaging.md
index 1f8549a03b..fa85774104 100644
--- a/microsoft-edge/extensions/developer-guide/native-messaging.md
+++ b/microsoft-edge/extensions/developer-guide/native-messaging.md
@@ -138,7 +138,7 @@ When you're ready to distribute your extension to users, publish your extension
 The final step involves copying the native messaging host manifest file to your computer, and making sure that this manifest file is correctly configured.  To ensure your native messaging host manifest file is placed in the expected location, do the following steps.  The location varies by platform.
 
 On Linux and macOS:
-* Make sure that you provide **read** permissions on the native messaging host manifest file. 
+* Make sure that you provide **read** permissions on the native messaging host manifest file.
 * Make sure that you provide **run** permissions on the host runtime.
 
 ##### [Windows](#tab/windows/)
diff --git a/microsoft-edge/extensions/developer-guide/run-compiled-code.md b/microsoft-edge/extensions/developer-guide/run-compiled-code.md
index e0cccf4adf..747a1cc7f6 100644
--- a/microsoft-edge/extensions/developer-guide/run-compiled-code.md
+++ b/microsoft-edge/extensions/developer-guide/run-compiled-code.md
@@ -27,7 +27,7 @@ To enhance web security and performance, Native Client (NaCl) is no longer suppo
 
 NaCl is a sandbox for running compiled C and C++ code in browsers efficiently and securely, independently of the user's operating system.  WebAssembly (Wasm) is recommended instead of NaCl.
 
-To Run compiled code in an extension, we recommend using WebAssembly instead of NaCl.  See: 
+To Run compiled code in an extension, we recommend using WebAssembly instead of NaCl.  See:
 * [WebAssembly Migration Guide](https://developer.chrome.com/docs/native-client/migration)<!-- chrome link ok, not doc'd at lmc --> in Chrome docs.
 * [WebAssembly](https://developer.mozilla.org/docs/WebAssembly) at MDN.
 * [webassembly.org](https://webassembly.org)
diff --git a/microsoft-edge/extensions/index.md b/microsoft-edge/extensions/index.md
index af937d65ce..a908dce1f6 100644
--- a/microsoft-edge/extensions/index.md
+++ b/microsoft-edge/extensions/index.md
@@ -56,7 +56,7 @@ Add-ons for Microsoft Edge include extensions and themes.  As an extension devel
 
 ![The Microsoft Edge Add-ons website](./index-images/edge-add-ons-website.png)
 
-To find an extension, you use the **Search extensions, themes, and more** text box.  For example, to find extensions about Bing, enter "Bing", and then click a result.  
+To find an extension, you use the **Search extensions, themes, and more** text box.  For example, to find extensions about Bing, enter "Bing", and then click a result. 
 
 The product detail page for the [Microsoft Bing Homepage](https://microsoftedge.microsoft.com/addons/detail/microsoft-bing-homepage/cjmjijnpnollocennnapedpaeecninea) extension appears:
 
@@ -150,7 +150,7 @@ For more information on porting your Chrome extension to Microsoft Edge, see [Po
 
 You publish a Microsoft Edge extension at the [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) website.
 
-To start publishing a Microsoft Edge extension, you must [register for a developer account](https://developer.microsoft.com/registration) with a Microsoft account (MSA) email account to submit your extension listing at the Microsoft Edge Add-ons website.  The email address of a Microsoft account (MSA) includes `@outlook.com`, `@live.com`, or `@hotmail.com`.  
+To start publishing a Microsoft Edge extension, you must [register for a developer account](https://developer.microsoft.com/registration) with a Microsoft account (MSA) email account to submit your extension listing at the Microsoft Edge Add-ons website.  The email address of a Microsoft account (MSA) includes `@outlook.com`, `@live.com`, or `@hotmail.com`. 
 
 When you choose an email address to register, consider whether you must transfer or share ownership of the Microsoft Edge extension with other people in your organization.  After registration is complete, you can submit an extension listing.
 
@@ -191,9 +191,9 @@ The **Featured** badge indicates that:
 
 * The extension has been reviewed and selected through an automated system.
 
-* The extension offers a reliable and high-quality experience for Microsoft Edge users. 
+* The extension offers a reliable and high-quality experience for Microsoft Edge users.
 
-The **Featured** badge is not a judgment of safety.  An extension that doesn't have the **Featured** badge is not necessarily unsafe; the extension simply doesn't meet the current threshold for Featured status. 
+The **Featured** badge is not a judgment of safety.  An extension that doesn't have the **Featured** badge is not necessarily unsafe; the extension simply doesn't meet the current threshold for Featured status.
 
 The **Featured** badge at the Microsoft Edge Add-ons website is intended to help users discover extensions that meet a high bar for quality, reliability, security, privacy, and user experience at the time of evaluation.
 
@@ -207,19 +207,19 @@ Microsoft regularly re-evaluates badged extensions and may update, revoke, or re
 <!-- ------------------------------ -->
 #### Reasons why the Featured badge could be revoked
 
-The **Featured** badge isn't permanent.  An extension might lose the **Featured** badge if the extension no longer meets the evolving standards, or if the extension's quality signals degrade over time. 
+The **Featured** badge isn't permanent.  An extension might lose the **Featured** badge if the extension no longer meets the evolving standards, or if the extension's quality signals degrade over time.
 
-To maintain a high-quality ecosystem, Microsoft periodically re-evaluates all badged extensions.  A **Featured** badge might be removed due to: 
+To maintain a high-quality ecosystem, Microsoft periodically re-evaluates all badged extensions.  A **Featured** badge might be removed due to:
 
-* Decline in user experience or performance metrics. 
+* Decline in user experience or performance metrics.
 
-* Outdated or incomplete store listing information. 
+* Outdated or incomplete store listing information.
 
-* Security or privacy concerns. 
+* Security or privacy concerns.
 
-* Changes in Microsoft's evaluation criteria. 
+* Changes in Microsoft's evaluation criteria.
 
-All decisions about the **Featured** badge are final and not subject to individual review.  There is no manual application or appeal process.  The **Featured** badge is awarded and revoked based on internal evaluation criteria and tooling. 
+All decisions about the **Featured** badge are final and not subject to individual review.  There is no manual application or appeal process.  The **Featured** badge is awarded and revoked based on internal evaluation criteria and tooling.
 
 To improve your extension's quality and eligibility for the **Featured** badge, see [Best practices for extensions](./developer-guide/best-practices.md).
 
diff --git a/microsoft-edge/extensions/landing/index.yml b/microsoft-edge/extensions/landing/index.yml
index f083126274..6a581369af 100644
--- a/microsoft-edge/extensions/landing/index.yml
+++ b/microsoft-edge/extensions/landing/index.yml
@@ -117,7 +117,7 @@ landingContent:
         links:
           - text: Port a Chrome extension to Microsoft Edge
             url: ../developer-guide/port-chrome-extension.md
- 
+
       - linkListType: concept
         links:
           - text: Add a custom tool in Microsoft Edge DevTools
diff --git a/microsoft-edge/extensions/publish/add-ons-badge.md b/microsoft-edge/extensions/publish/add-ons-badge.md
index 422feb9b7f..d8cd00ad53 100644
--- a/microsoft-edge/extensions/publish/add-ons-badge.md
+++ b/microsoft-edge/extensions/publish/add-ons-badge.md
@@ -31,7 +31,7 @@ The Microsoft Edge Add-ons badge is not the same as the Microsoft brand logo, an
 <!-- ====================================================================== -->
 ## Download the badge image files
 
-Download the complete set of `.png` files: 
+Download the complete set of `.png` files:
 
 * [Microsoft_Edge_Add-ons_badge_image_files.zip](https://raw.githubusercontent.com/microsoft/MicrosoftEdge-Extensions/refs/heads/main/assets/Microsoft_Edge_Add-ons_badge_image_files.zip) (from the [MicrosoftEdge-Extensions](https://github.com/microsoft/MicrosoftEdge-Extensions) repo).
 
diff --git a/microsoft-edge/extensions/publish/create-dev-account.md b/microsoft-edge/extensions/publish/create-dev-account.md
index 7322ce78de..02034a8b4e 100644
--- a/microsoft-edge/extensions/publish/create-dev-account.md
+++ b/microsoft-edge/extensions/publish/create-dev-account.md
@@ -171,7 +171,7 @@ In the **Contact info** section, enter contact information that Microsoft will u
 
 For a company account, you must use the registered email address that's associated with your organization.
 
-After registration is complete, you receive a confirmation email.  
+After registration is complete, you receive a confirmation email. 
 
 
 <!-- ------------------------------ -->
@@ -217,7 +217,7 @@ Ensure that all documents (such as utility bills, DUNS ID, or government records
 * Clear, complete, and match your legal business profile.
 * Uploaded in the correct section at Partner Center, under [Account settings | Legal info](https://partner.microsoft.com/dashboard/account/v3/organization/legalinfo).
 
-If your application was rejected: 
+If your application was rejected:
 * In the **Legal Info** tab, click **Fix now**.
 * Re-upload documents with comments explaining your appeal.
 
diff --git a/microsoft-edge/extensions/publish/extensions-analytics.md b/microsoft-edge/extensions/publish/extensions-analytics.md
index aac7dad722..4d2a498a9a 100644
--- a/microsoft-edge/extensions/publish/extensions-analytics.md
+++ b/microsoft-edge/extensions/publish/extensions-analytics.md
@@ -16,7 +16,7 @@ You can view extension metrics from your [Partner Center dashboard](https://part
 
 For example, you can identify regions in which the number of installations for your extension has increased in the past three months. You can also export this report as a CSV file.
 
-Follow these steps to view your extension's analytics dashboard:  
+Follow these steps to view your extension's analytics dashboard: 
 
 1. Go to your Partner Center account and select an extension.
 
diff --git a/microsoft-edge/extensions/publish/manage-settings.md b/microsoft-edge/extensions/publish/manage-settings.md
index 9bce8f9bd0..3377ac7505 100644
--- a/microsoft-edge/extensions/publish/manage-settings.md
+++ b/microsoft-edge/extensions/publish/manage-settings.md
@@ -41,7 +41,7 @@ If you change any of your contact details, the Microsoft Edge extension team mig
 Review the following settings in the Account settings section.
 
 | Account Settings | Description |
-|:--- |:--- |
+|---|---|
 | Verification status | Review your verification status when your account is going through the verification process.  For example, your account is verified when you first create an account, or after you update your contact information. |
 | Programs | Review information about enrolled programs or other programs that might be of interest to you. |
 | Agreements | Review the agreements that your account accepted. |
diff --git a/microsoft-edge/extensions/publish/publish-extension.md b/microsoft-edge/extensions/publish/publish-extension.md
index 43a43c1e63..7d79a74a4b 100644
--- a/microsoft-edge/extensions/publish/publish-extension.md
+++ b/microsoft-edge/extensions/publish/publish-extension.md
@@ -110,7 +110,7 @@ The following fields in the manifest file are automatically included in your ext
 *  The `Name` field, which populates the **Extension name** on the **Details for \<language\>** page.
 
 *  The `Description` field, which populates the **Description** on the **Details for \<language\>** page.
-   
+  
    Fill in the `Description` field, to explicitly provide a catchy description that will be displayed at the top of the listing for the extension.
 
    * If you include a `short description` in the extension manifest file, that short description is displayed in your store listing.
@@ -241,7 +241,7 @@ Define the specific markets in which you plan to offer your extension.  The defa
    | **Website** | Optional | A webpage that provides additional information about the extension.  The website URL must point to a webpage on your own website, not the web listing for the extension at the Microsoft Edge Add-ons website.  The **Website** URL helps users learn more about the extension, its features, and any other relevant information. |
    | **Support contact detail** | Optional | The URL to your support webpage, or the email address to contact your support team. |
    | **Mature content** | Optional | Checkbox to specify whether the extension includes mature content.  This extension rating helps determine the appropriate age group of the target audience of the extension.  To help determine whether the extension has _mature content_, see [Developer policies for the Microsoft Edge Add-ons website](/legal/microsoft-edge/extensions/developer-policies). |
-   
+  
    The properties (your developer/organization name, **Website** URL, and **Support contact detail**) that you submitted during registration are displayed to users at the Microsoft Edge Add-ons website.
 
    You have now filled in the **Properties** page for the extension at Partner Center.
@@ -512,7 +512,7 @@ You can generate descriptions up to 10 times per hour.  If you exceed this limit
 ![The Provide inputs text box with a limit message](./publish-extension-images/generation-limit.png)
 
 If generation fails, an error message is displayed, such as "Something went wrong while generating your description.  Try again":
- 
+
 ![The Provide inputs text box with an error message](./publish-extension-images/generation-error.png)
 
 
@@ -798,7 +798,7 @@ Developer Agreement & Legal:
 * [Developer policies for the Microsoft Edge Add-ons website](/legal/microsoft-edge/extensions/developer-policies)
 
 Support.microsoft.com:
-* [Extensions New Support Request](https://support.microsoft.com/supportrequestform/e7a381be-9c9a-fafb-ed76-262bc93fd9e4) 
+* [Extensions New Support Request](https://support.microsoft.com/supportrequestform/e7a381be-9c9a-fafb-ed76-262bc93fd9e4)
 
 Support.google.com:
 * [YouTube advertising formats](https://support.google.com/youtube/answer/2467968?ref_topic=7072227)
diff --git a/microsoft-edge/extensions/publish/reply-user-reviews.md b/microsoft-edge/extensions/publish/reply-user-reviews.md
index 6fedae2c05..5cf290504a 100644
--- a/microsoft-edge/extensions/publish/reply-user-reviews.md
+++ b/microsoft-edge/extensions/publish/reply-user-reviews.md
@@ -20,7 +20,7 @@ To view your extension's **Reviews** page:
 
    Or, on the **Home** > **Edge** breadcrumb path, click the star rating of an extension on the **Overview** page.
 
-![Microsoft Partner Center reviews feature](./reply-user-reviews-images/user-reviews.png) 
+![Microsoft Partner Center reviews feature](./reply-user-reviews-images/user-reviews.png)
 
 
 <!-- ====================================================================== -->
diff --git a/microsoft-edge/extensions/publish/verify-microsoft-edge-program.md b/microsoft-edge/extensions/publish/verify-microsoft-edge-program.md
index c303f40dbf..de716ea52f 100644
--- a/microsoft-edge/extensions/publish/verify-microsoft-edge-program.md
+++ b/microsoft-edge/extensions/publish/verify-microsoft-edge-program.md
@@ -119,7 +119,7 @@ There are three possible results when you check your verification status:
 
 * **Pending**: The verification process has started but isn't complete. If you've completed the email verification step, no further action is required on your part. Verification usually takes three to five business days. You can monitor verification status at **Account Settings | Legal Info**.
 
-* **Action Required/Rejected**: The information you submitted couldn't be verified. The reason, and instructions for how to appeal, appear in the **Account Verification** pane. See [Appealing a rejected application](#appealing-a-rejected-application) in the next section. 
+* **Action Required/Rejected**: The information you submitted couldn't be verified. The reason, and instructions for how to appeal, appear in the **Account Verification** pane. See [Appealing a rejected application](#appealing-a-rejected-application) in the next section.
 
 
 <!-- ====================================================================== -->
diff --git a/microsoft-edge/extensions/release-notes/archive.md b/microsoft-edge/extensions/release-notes/archive.md
index a1a1a8c3ba..0f1d26467f 100644
--- a/microsoft-edge/extensions/release-notes/archive.md
+++ b/microsoft-edge/extensions/release-notes/archive.md
@@ -299,7 +299,7 @@ Microsoft Partner Center only accepts new Manifest V3 Microsoft Edge extension s
 <!-- ------------------------------ -->
 #### You can respond to user reviews about your Microsoft Edge extension
 
-At Partner Center, you can reply to user reviews and feedback about your extension that's published at the [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) website. 
+At Partner Center, you can reply to user reviews and feedback about your extension that's published at the [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) website.
 
 To share your feedback and comments about this feature, see [You can now respond to user reviews on your Microsoft Edge Add-ons page](https://github.com/microsoft/MicrosoftEdge-Extensions/discussions/18) in **Discussions** in the MicrosoftEdge-Extensions repo.
 
diff --git a/microsoft-edge/extensions/release-notes/index.md b/microsoft-edge/extensions/release-notes/index.md
index ce92f56ae3..9323547f6f 100644
--- a/microsoft-edge/extensions/release-notes/index.md
+++ b/microsoft-edge/extensions/release-notes/index.md
@@ -47,7 +47,7 @@ The following updates have been deployed to production, addressing key issues an
 <!-- ====================================================================== -->
 ## URL validation and security
 
-* URL-related error messages have clearer wording. 
+* URL-related error messages have clearer wording.
 
 * Unreachable URLs are now detected in the following fields:
 
diff --git a/microsoft-edge/extensions/samples/picture-inserter-content-script.md b/microsoft-edge/extensions/samples/picture-inserter-content-script.md
index bb8c44b4a1..47077cad62 100644
--- a/microsoft-edge/extensions/samples/picture-inserter-content-script.md
+++ b/microsoft-edge/extensions/samples/picture-inserter-content-script.md
@@ -9,7 +9,7 @@ ms.subservice: extensions
 ms.date: 01/16/2025
 ---
 # Sample: Picture inserter using content script
-<!-- 
+<!--
 longer name would get truncated in Extensions pop-up:
 "name": "Picture inserter using a content scr...",
 -->
@@ -133,7 +133,7 @@ You are now free to modify the code in your working branch, without altering the
 
    GitHub Desktop opens, with the **MicrosoftEdge-Extensions** repo selected in the upper left dropdown list.
 
-   Or, in GitHub Desktop, the **Clone a repository** dialog opens: 
+   Or, in GitHub Desktop, the **Clone a repository** dialog opens:
 
    ![The "Clone a repository" dialog in GitHub Desktop](./picture-viewer-popup-webpage-images/clone-a-repo-dbox-ghd.png)
 
@@ -396,7 +396,7 @@ chrome.runtime.onMessage.addListener(function(request, sender, sendResponse) {
 
 In `content.js`, the `addListener` method takes a single parameter that's a function.  That function's first parameter, `request`, contains the details of the message that's being passed in.
 
-In `content.js`, when an event is processed by the listener, the listener function that's passed into `addListener` is run.  The first parameter of the passed-in listener function is a `request` object that has attributes as assigned by `sendMessage`.  
+In `content.js`, when an event is processed by the listener, the listener function that's passed into `addListener` is run.  The first parameter of the passed-in listener function is a `request` object that has attributes as assigned by `sendMessage`. 
 
 In `popup.js`, for the `chrome.tabs.sendMessage` method call, the attributes of the second parameter for `sendMessage` are `url`, `imageDivId`, and `tabId`.
 
diff --git a/microsoft-edge/extensions/samples/picture-viewer-popup-webpage.md b/microsoft-edge/extensions/samples/picture-viewer-popup-webpage.md
index 4dfc1c48d6..6be9ebe079 100644
--- a/microsoft-edge/extensions/samples/picture-viewer-popup-webpage.md
+++ b/microsoft-edge/extensions/samples/picture-viewer-popup-webpage.md
@@ -108,7 +108,7 @@ You are now free to modify the code in your working branch, without altering the
 
    GitHub Desktop opens, with the **MicrosoftEdge-Extensions** repo selected in the upper left dropdown list.
 
-   Or, in GitHub Desktop, the **Clone a repository** dialog opens: 
+   Or, in GitHub Desktop, the **Clone a repository** dialog opens:
 
    ![The "Clone a repository" dialog in GitHub Desktop](./picture-viewer-popup-webpage-images/clone-a-repo-dbox-ghd.png)
 
diff --git a/microsoft-edge/extensions/update/api/addons-api-reference.md b/microsoft-edge/extensions/update/api/addons-api-reference.md
index de84ca939a..bbad2a3157 100644
--- a/microsoft-edge/extensions/update/api/addons-api-reference.md
+++ b/microsoft-edge/extensions/update/api/addons-api-reference.md
@@ -396,7 +396,7 @@ The response includes an operation ID, to send to other endpoints.
     "status": "Failed",
     "message": "Can't publish extension as your extension submission is in progress. Please try again later.",
     "errorCode": "InProgressSubmission",
-    "errors": null    
+    "errors": null   
 }
 ```
 
@@ -412,7 +412,7 @@ The response includes an operation ID, to send to other endpoints.
     "status": "Failed",
     "message": "Can't publish extension as your extension is being unpublished. Please try after you've unpublished.",
     "errorCode": "UnpublishInProgress",
-    "errors": null    
+    "errors": null   
 }
 ```
 
diff --git a/microsoft-edge/extensions/update/api/using-addons-api.md b/microsoft-edge/extensions/update/api/using-addons-api.md
index 6a42db5b1e..37010c5a93 100644
--- a/microsoft-edge/extensions/update/api/using-addons-api.md
+++ b/microsoft-edge/extensions/update/api/using-addons-api.md
@@ -10,7 +10,7 @@ ms.date: 09/19/2024
 ---
 # Use the REST API to update an extension
 
-Use this REST API to programmatically update an extension (or a theme) that's been published at the [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) website, to automate the process of uploading and publishing new versions of your extension.  You can integrate these REST API endpoints directly into your continuous integration/continuous delivery (CI/CD) pipeline, to publish extension package updates at the Microsoft Edge Add-ons website without using Partner Center. 
+Use this REST API to programmatically update an extension (or a theme) that's been published at the [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) website, to automate the process of uploading and publishing new versions of your extension.  You can integrate these REST API endpoints directly into your continuous integration/continuous delivery (CI/CD) pipeline, to publish extension package updates at the Microsoft Edge Add-ons website without using Partner Center.
 
 This REST API exposes endpoints for:
 * [Uploading a package to update an existing submission](#uploading-a-package-to-update-an-existing-submission)
@@ -170,7 +170,7 @@ You can generate multiple client secrets for your Client ID.  For example, you c
 
 You obtain an access token by sending a POST message to an access token URL.  The Partner Center UI shows the access token URL, which is the same as in this article.  You then include the access token in the header when using an API endpoint, such as the endpoint for [Uploading a package to update an existing submission](#uploading-a-package-to-update-an-existing-submission), below.
 
-<!-- 
+<!--
 After you've acquired the necessary authorization for your application, get access tokens for APIs.  To get a token (an OAuth token) by using the client credentials grant, send a POST request to the access token URL.  The tenant information is available in the access token URL that you received at Partner Center.
 "acquired the necessary authorization" - not casual per corp style
 "get access tokens" - plural or singular?  one token per endpoint?
@@ -289,7 +289,7 @@ Body content: the package file to upload
 
 ---
 
-`$productID` is the product ID of the Microsoft Edge extension that you want to update. 
+`$productID` is the product ID of the Microsoft Edge extension that you want to update.
 
 To get the product ID:
 
@@ -300,7 +300,7 @@ To get the product ID:
 1. Select the extension for which you want the product ID.
 
    The **Extension overview** page opens.  The product ID is shown in the page.  (The product ID is also shown as the GUID in the URL in the Address bar, between `microsoftedge/` and `/packages`.)
- 
+
 1. In the **Extension identity** section (or from the Address bar), select and copy the **Product ID**.
 
 
diff --git a/microsoft-edge/extensions/update/auto-update.md b/microsoft-edge/extensions/update/auto-update.md
index e6c81e3eb2..ea16d7d6de 100644
--- a/microsoft-edge/extensions/update/auto-update.md
+++ b/microsoft-edge/extensions/update/auto-update.md
@@ -23,8 +23,8 @@ ms.date: 11/04/2022
    limitations under the License.  -->
 # Set an externally installed extension to automatically update
 
-<!-- todo: 
-update article per https://developer.chrome.com/docs/apps/autoupdate 
+<!-- todo:
+update article per https://developer.chrome.com/docs/apps/autoupdate
 improve intro lead-in sequencing
 -->
 
@@ -34,7 +34,7 @@ Every few hours, Microsoft Edge checks whether each installed extension or app h
 
 In order to maintain user privacy, Microsoft Edge doesn't send any `Cookie` headers with auto-update manifest requests, and ignores any `Set-Cookie` headers in the responses to those requests.
 
-When you set your extension to automatically update on users' machines, your extension shares the following benefits with Microsoft Edge: 
+When you set your extension to automatically update on users' machines, your extension shares the following benefits with Microsoft Edge:
 
 * Incorporate bug and security fixes.
 * Add new features or performance enhancements.
@@ -83,7 +83,7 @@ The updated manifest returned by the server should be an XML document; for examp
 The updated manifest XML file defines the following attributes:
 
 | Attribute | Details |
-|:--- |:--- |
+|---|---|
 | `appid` | The extension ID is generated based on a hash of the public key.  To find the ID of an extension, open Microsoft Edge and see `edge://extensions`. |
 | `codebase` | A URL to the `.crx` file. |
 | `version` | This attribute value is used by Microsoft Edge to determine whether it should download the `.crx` file specified by `codebase`.  It should match the value of `version` in the `manifest.json` file of the `.crx` file. |
@@ -156,7 +156,7 @@ In a future release, instead of issuing multiple `GET` requests, a single `POST`
 
 As new APIs are released for the Microsoft Edge extensions system, you might want to release an updated version of your extension or app that only works with newer versions of Microsoft Edge.  When Microsoft Edge is automatically updated, it can take a few days before most of your users update to that new release.
 
-To ensure that a specific update applies only to Microsoft Edge versions that are current or newer than a specific version, add the `prodversionmin` attribute in your update manifest.  
+To ensure that a specific update applies only to Microsoft Edge versions that are current or newer than a specific version, add the `prodversionmin` attribute in your update manifest. 
 
 For example, in the following code, the `prodversionmin` attribute value of `3.0.193.0` specifies that your app is automatically updated to version `2.0` only when the user is running Microsoft Edge `3.0.193.0` or newer:
 
diff --git a/microsoft-edge/extensions/update/transfer-ownership.md b/microsoft-edge/extensions/update/transfer-ownership.md
index 36a486c4ae..6800d583ab 100644
--- a/microsoft-edge/extensions/update/transfer-ownership.md
+++ b/microsoft-edge/extensions/update/transfer-ownership.md
@@ -36,7 +36,7 @@ The current owner of the extension must send an email, as follows:
    * The target publisher's seller ID and name (the new owner).
    * The MSA email address for the source publisher extension owner (the current owner).
    * The MSA email address for the target publisher extension owner (the new owner).
- 
+
 1. Send the email.
 
 
diff --git a/microsoft-edge/index.yml b/microsoft-edge/index.yml
index 23554be2e2..6a7b4a0137 100644
--- a/microsoft-edge/index.yml
+++ b/microsoft-edge/index.yml
@@ -502,15 +502,15 @@ conceptualContent:
 #             - text: Introduction to the Microsoft DualEngine API
 #               url: ./dualengine/intro.md
 #               itemType: overview
- 
+
 #             - text: Getting started with the DualEngine API
 #               url: ./dualengine/get-started.md
 #               itemType: get-started
- 
+
 #             - text: Creating a DualEngine adapter plugin DLL
 #               url: ./dualengine/concepts/adapter-dll.md
 #               itemType: how-to-guide
- 
+
 #             - text: Launching Internet Explorer
 #               url: ./dualengine/concepts/launching-internet-explorer.md
 #               itemType: how-to-guide
diff --git a/microsoft-edge/playwright/index.md b/microsoft-edge/playwright/index.md
index 4c2d7deb86..c3fe217021 100644
--- a/microsoft-edge/playwright/index.md
+++ b/microsoft-edge/playwright/index.md
@@ -31,7 +31,7 @@ npm i -D @playwright/test
 To install browsers, run the following command, which downloads [Chromium](https://www.chromium.org/Home), [Firefox](https://www.mozilla.org/firefox), and [WebKit](https://webkit.org):
 
 ```console
-npx playwright install 
+npx playwright install
 ```
 
 
@@ -125,13 +125,13 @@ const playwright = require('playwright');
 
 `example.js` is a simple demonstration of the automation and testing scenarios that are enabled by Playwright.  To take screenshots in other web browsers, change the above code from `await playwright.chromium.launch` to the following code:
 
-Firefox: 
+Firefox:
 
 ```javascript
   const browser = await playwright.firefox.launch({
 ```
 
-WebKit: 
+WebKit:
 
 ```javascript
   const browser = await playwright.webkit.launch({
diff --git a/microsoft-edge/progressive-web-apps/how-to/app-actions.md b/microsoft-edge/progressive-web-apps/how-to/app-actions.md
index de0fa22241..07d48cccc7 100644
--- a/microsoft-edge/progressive-web-apps/how-to/app-actions.md
+++ b/microsoft-edge/progressive-web-apps/how-to/app-actions.md
@@ -158,7 +158,7 @@ For a PWA to use App Actions, the `share_target` field must be present in the PW
 
 * The method must be "POST".
 * The `enctype` must be `multipart/form-data`.
-* `text` and `url` in `params` are required to support App Actions. 
+* `text` and `url` in `params` are required to support App Actions.
 * `files` is optional.  You can omit `files` if you don't want your PWA to support the normal _share target_ feature.
 
 Example `share_target` declaration, from [Demos/wami/manifest.json](https://github.com/MicrosoftEdge/Demos/blob/main/wami/manifest.json):
@@ -185,7 +185,7 @@ See also:
 
 The entity of an App Action is passed to the PWA through POST share data.  To handle POST share data, you can use or combine the following approaches:
 
-* Handle POST share data by using server-side code. 
+* Handle POST share data by using server-side code.
 
 * In a service worker, use a fetch event listener to intercept the HTTP POST request.  This provides a better experience for offline users.  See:
 
@@ -209,7 +209,7 @@ Explanation of the `formData` keys:
 
 * **url:** The protocol URI (for example, `web+wami://paint` in the sample) that identifies which App Action triggered the launch.  The input parameter value must be identical to the value that you set in the PWA's web app manifest `share_target.params.url`.
 
-* **files:** File objects attached to the App Action invocation. 
+* **files:** File objects attached to the App Action invocation.
 
 
 <!-- ------------------------------ -->
@@ -394,7 +394,7 @@ To test App Actions for your PWA:
 <!-- all links in file -->
 
 * [Receiving shared content](./share.md#receiving-shared-content)
-* [Publish a PWA to the Microsoft Store](./microsoft-store.md) 
+* [Publish a PWA to the Microsoft Store](./microsoft-store.md)
    * [Package your PWA for the Store](./microsoft-store.md#package-your-pwa-for-the-store) in _Publish a PWA to the Microsoft Store_.
 
 Windows articles:
@@ -413,7 +413,7 @@ Sites:
 * [PWABuilder.Windows.Chromium tester](https://pwabuilder-windows-docker.azurewebsites.net/)
 
 MDN:
-* [launch_handler](https://developer.mozilla.org/docs/Web/Progressive_web_apps/Manifest/Reference/launch_handler) 
+* [launch_handler](https://developer.mozilla.org/docs/Web/Progressive_web_apps/Manifest/Reference/launch_handler)
 * [share_target](https://developer.mozilla.org/docs/Web/Progressive_web_apps/Manifest/Reference/share_target)
    * [Receiving share data using POST](https://developer.mozilla.org/docs/Web/Progressive_web_apps/Manifest/Reference/share_target#receiving_share_data_using_post) in _share_target_.
    * [Receiving shared files](https://developer.mozilla.org/docs/Web/Progressive_web_apps/Manifest/Reference/share_target#receiving_shared_files) in _share_target_.
diff --git a/microsoft-edge/progressive-web-apps/how-to/background-syncs.md b/microsoft-edge/progressive-web-apps/how-to/background-syncs.md
index 1571e7b30a..336084fbb1 100644
--- a/microsoft-edge/progressive-web-apps/how-to/background-syncs.md
+++ b/microsoft-edge/progressive-web-apps/how-to/background-syncs.md
@@ -402,7 +402,7 @@ To start a background fetch:
 
 ```javascript
 navigator.serviceWorker.ready.then(async registration => {
-    const fetch = await registration.backgroundFetch.fetch('my-download-id', 
+    const fetch = await registration.backgroundFetch.fetch('my-download-id',
                                                            fileUrls, options);
 });
 ```
diff --git a/microsoft-edge/progressive-web-apps/how-to/best-practices.md b/microsoft-edge/progressive-web-apps/how-to/best-practices.md
index e1b6bf65b9..7cd4de5ba2 100644
--- a/microsoft-edge/progressive-web-apps/how-to/best-practices.md
+++ b/microsoft-edge/progressive-web-apps/how-to/best-practices.md
@@ -204,7 +204,7 @@ To test your app in multiple environments, consider the following techniques:
 <!-- ====================================================================== -->
 ## Support deep linking
 
-To improve discovery and sharing of your app through the web and social media, route each page of your app to a unique URL and support [Deep linking](https://wikipedia.org/wiki/Deep_linking).  
+To improve discovery and sharing of your app through the web and social media, route each page of your app to a unique URL and support [Deep linking](https://wikipedia.org/wiki/Deep_linking). 
 
 
 <!-- ======================================================================
diff --git a/microsoft-edge/progressive-web-apps/how-to/handle-files.md b/microsoft-edge/progressive-web-apps/how-to/handle-files.md
index 0e0b121e2f..174104bb53 100644
--- a/microsoft-edge/progressive-web-apps/how-to/handle-files.md
+++ b/microsoft-edge/progressive-web-apps/how-to/handle-files.md
@@ -144,7 +144,7 @@ To use the demo:
    ```
    Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat.
 
-   * Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. 
+   * Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur.
 
    * Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
 
diff --git a/microsoft-edge/progressive-web-apps/how-to/icon-theme-color.md b/microsoft-edge/progressive-web-apps/how-to/icon-theme-color.md
index 218542d7df..eb75e2e52f 100644
--- a/microsoft-edge/progressive-web-apps/how-to/icon-theme-color.md
+++ b/microsoft-edge/progressive-web-apps/how-to/icon-theme-color.md
@@ -52,7 +52,7 @@ In the web app manifest file, app icons are defined with the `icons` member:
 Each icon in the `icons` array should come with at least the `src` and `sizes` properties.  An icon can also have the `type` and `purpose` properties.
 
 | Property | Description |
-|:--- |:--- |
+|---|---|
 | `src` | The path to the image file, which can be a relative path from the app root folder, or an absolute URL. |
 | `sizes` | A space-separated list of sizes that the corresponding image can be used for. |
 | `type` | An optional hint for the OS to quickly detect the image type. |
@@ -111,7 +111,7 @@ Your PWA can be enhanced on Windows by supplying the images with specific dimens
     * 100x100 - store tile 2x display scale
     * 200x200 - store tile 4x display scale
     * 620x300 - splash screen
-    * 775x375 - splash screen 1.25x display scale  
+    * 775x375 - splash screen 1.25x display scale 
     * 930x450 - splash screen 1.5x display scale
     * 1240x600 - splash screen 2x display scale
     * 2480x1200 - splash screen 4x display scale
@@ -175,19 +175,19 @@ Your PWA can be enhanced on Windows by supplying the images with specific dimens
 
 Consider, for example, how your app icon might show different content depending on the available surface area:
 
-* Small surface: App icon (44x44) in taskbar, showing a small, abbreviated logo: 
+* Small surface: App icon (44x44) in taskbar, showing a small, abbreviated logo:
 
-![The small size icon](./icon-theme-color-images/windows-image-app-icon.png) 
+![The small size icon](./icon-theme-color-images/windows-image-app-icon.png)
 
-* Larger surface: Medium tile (150x150) in start menu, showing the full logo of the app:  
+* Larger surface: Medium tile (150x150) in start menu, showing the full logo of the app: 
 
-![The medium size icon](./icon-theme-color-images/windows-image-small-tile.png) 
+![The medium size icon](./icon-theme-color-images/windows-image-small-tile.png)
 
-* Wide surface: Wide tile in start menu, showing a more articulated app icon: 
+* Wide surface: Wide tile in start menu, showing a more articulated app icon:
 
-![The wide size icon](./icon-theme-color-images/windows-image-wide-tile.png) 
+![The wide size icon](./icon-theme-color-images/windows-image-wide-tile.png)
 
-Notice how the content of the icon changed. This is possible only through the use of higher levels of icon support. We recommend developers choose higher levels to give the best experience for your Windows users.  
+Notice how the content of the icon changed. This is possible only through the use of higher levels of icon support. We recommend developers choose higher levels to give the best experience for your Windows users. 
 
 
 <!-- ------------------------------ -->
@@ -197,7 +197,7 @@ Below you'll find a description of each app icon and where they show up in Windo
 
 The normal app icon that's shown in the start menu, task bar, or task manager.
 
-![App Icon](./icon-theme-color-images/windows-image-app-icon.png) 
+![App Icon](./icon-theme-color-images/windows-image-app-icon.png)
 
 * 44x44
 * 55x55 (1.25x scale)
@@ -207,7 +207,7 @@ The normal app icon that's shown in the start menu, task bar, or task manager.
 
 The small tile is shown in the start menu when the user set your app's tile to small size.
 
-![Small tile](./icon-theme-color-images/windows-image-small-tile.png) 
+![Small tile](./icon-theme-color-images/windows-image-small-tile.png)
 
 * 71x71
 * 89x89 (1.25x scale)
@@ -240,7 +240,7 @@ The large tile icon is in the start menu when the user sets your app's tile to l
 ![Large tile](./icon-theme-color-images/windows-image-large-tile.png)
 
 * 310x310
-* 388x388 (1.25x scale)  
+* 388x388 (1.25x scale) 
 * 465x465 (1.5x scale)
 * 620x620 (2x scale)
 * 1240x1240 (4x scale)
@@ -269,7 +269,7 @@ The splash screen asset is shown as the splash screen for your app. Currently su
 <!-- ------------------------------ -->
 #### Target sized images
 
-In addition to the standard scale factor sizes described above, we also recommend creating "target-size" assets. We call these assets target-size because they target specific sizes, such as 16 pixels, rather than specific scale factors, such as 400. Target-size assets are for Windows surfaces that don't use the scaling plateau system. 
+In addition to the standard scale factor sizes described above, we also recommend creating "target-size" assets. We call these assets target-size because they target specific sizes, such as 16 pixels, rather than specific scale factors, such as 400. Target-size assets are for Windows surfaces that don't use the scaling plateau system.
 
 For example, the **Apps & features** Windows setting uses app icons with specific sizes
 
diff --git a/microsoft-edge/progressive-web-apps/how-to/index.md b/microsoft-edge/progressive-web-apps/how-to/index.md
index 1ebe9b34ab..e6d72faa4e 100644
--- a/microsoft-edge/progressive-web-apps/how-to/index.md
+++ b/microsoft-edge/progressive-web-apps/how-to/index.md
@@ -119,7 +119,7 @@ The remaining sections explain the files that make up the PWA sample.
 
 A regular web app only runs in the browser.  By adding a web app manifest, the web app becomes a Progressive Web App (PWA).  The web app manifest enables browsers that support PWAs to install the web app as a Progressive Web App on the device.
 
-A _web app manifest_ is a JSON file containing metadata about the Progressive Web App, such as its name, description, icons, and the various operating system features it uses.  The JSON code describes the app to the host operating system.  The manifest file provides basic information about the Progressive Web App, for the device's operating system to use.  
+A _web app manifest_ is a JSON file containing metadata about the Progressive Web App, such as its name, description, icons, and the various operating system features it uses.  The JSON code describes the app to the host operating system.  The manifest file provides basic information about the Progressive Web App, for the device's operating system to use. 
 
 The file name `manifest.json` is a common convention, not a strict requirement.
 
@@ -172,7 +172,7 @@ This sample [sw.js](https://github.com/MicrosoftEdge/Demos/blob/main/temperature
 
 ```javascript
 const CACHE_NAME = `temperature-converter-v1`;
-    
+   
 // Use the install event to pre-cache all initial resources.
 self.addEventListener('install', event => {
   event.waitUntil((async () => {
@@ -197,7 +197,7 @@ self.addEventListener('fetch', event => {
         try {
           // If the resource was not in the cache, try the network.
           const fetchResponse = await fetch(event.request);
-    
+   
           // Save the resource in the cache and return it.
           cache.put(event.request, fetchResponse.clone());
           return fetchResponse;
@@ -214,7 +214,7 @@ This service worker explicitly caches three files:
 * `./converter.js`
 * `./converter.css`
 
-Two additional files are are cached automatically by the browser: 
+Two additional files are are cached automatically by the browser:
 * The icon file (`.png`).
 * The manifest file (`.json`).
 
diff --git a/microsoft-edge/progressive-web-apps/how-to/microsoft-store.md b/microsoft-edge/progressive-web-apps/how-to/microsoft-store.md
index 61b964a592..a2c6384c11 100644
--- a/microsoft-edge/progressive-web-apps/how-to/microsoft-store.md
+++ b/microsoft-edge/progressive-web-apps/how-to/microsoft-store.md
@@ -129,7 +129,7 @@ Use this feature to measure distinct traffic from your PWA that was installed fr
 
 By default, a PWA that's installed from the [Microsoft Store](https://apps.microsoft.com) displays an additional UI when the app is redirected to a locale-specific domain.  The added UI shows the URL and page title.  This UI is added because navigation to the locale-specific domain is considered _out of scope_.
 
-The following figure shows the UI that is introduced when a user moves outside the scope of a PWA. 
+When a user moves outside the scope of a PWA, the following UI is introduced:
 
 ![The additional UI with URL and page title when the app is redirected to another domain](./microsoft-store-images/locale-redirection-additional-ui.png)
 
diff --git a/microsoft-edge/progressive-web-apps/how-to/offline.md b/microsoft-edge/progressive-web-apps/how-to/offline.md
index cb5d7b172c..c2964e8e4a 100644
--- a/microsoft-edge/progressive-web-apps/how-to/offline.md
+++ b/microsoft-edge/progressive-web-apps/how-to/offline.md
@@ -17,7 +17,7 @@ There are several ways in which a PWA can store data on a device, such as local
 The following table describes the different options, and the rest of this article goes into more details and usage scenarios for each option.
 
 | Storage option | Description |
-|:--- |:--- |
+|---|---|
 | Web Storage | Web Storage has two types: session and local.  Web Storage is useful to store small amounts of data from your app's front-end code.  The data is structured as key-value pairs and is only available to the current app origin.  In the case of session storage, the data is cleared when the session ends, for example when the app is closed, or when the user browses to another origin in the same window or tab.  Local storage persists until the app removes the data. |
 | IndexedDB | IndexedDB is an API for storing larger amounts of structured data.  The API is asynchronous and can be used both from your app's front-end code and service worker code.  Use the IndexedDB API to store a significant amount of structured data on the client, or binary data, such as encrypted media objects or files. |
 | Cache | The Cache API can be used to manage cached resources.  The Cache API is Promise-based and allows developers to store and retrieve many web resources — HTML, CSS, JavaScript, images, JSON, and so on.  Usually, the Cache API is used within the context of a service worker, but it's also available to your app's front-end code. |
diff --git a/microsoft-edge/progressive-web-apps/how-to/push.md b/microsoft-edge/progressive-web-apps/how-to/push.md
index 0e74ebcd0a..288b79adf9 100644
--- a/microsoft-edge/progressive-web-apps/how-to/push.md
+++ b/microsoft-edge/progressive-web-apps/how-to/push.md
@@ -88,10 +88,10 @@ function urlBase64ToUint8Array(base64String) {
   var base64 = (base64String + padding)
       .replace(/\-/g, '+')
       .replace(/_/g, '/');
-  
+ 
   var rawData = window.atob(base64);
   var outputArray = new Uint8Array(rawData.length);
-  
+ 
   for (var i = 0; i < rawData.length; ++i) {
     outputArray[i] = rawData.charCodeAt(i);
   }
diff --git a/microsoft-edge/progressive-web-apps/how-to/share.md b/microsoft-edge/progressive-web-apps/how-to/share.md
index ffe1a746f3..181acd2033 100644
--- a/microsoft-edge/progressive-web-apps/how-to/share.md
+++ b/microsoft-edge/progressive-web-apps/how-to/share.md
@@ -271,7 +271,7 @@ Apps can also handle shared files. To handle files in your PWA, you must use the
             "files": [
                 {
                     "name": "textFile",
-                    "accept": ["text/plain", "text/html", "text/css", 
+                    "accept": ["text/plain", "text/html", "text/css",
                                "text/javascript"]
                 }
             ]
diff --git a/microsoft-edge/progressive-web-apps/how-to/sidebar.md b/microsoft-edge/progressive-web-apps/how-to/sidebar.md
index d793af7fa4..e6ef38a3a3 100644
--- a/microsoft-edge/progressive-web-apps/how-to/sidebar.md
+++ b/microsoft-edge/progressive-web-apps/how-to/sidebar.md
@@ -141,7 +141,7 @@ You can detect when your app runs in the sidebar by using User-Agent Client Hint
 To detect when your app runs in the sidebar, do either of the following:
 
 * On your web server, read the `Sec-CH-UA` HTTPS request header and look for the `Edge Side Panel` brand. For example:
-    
+   
     ```https
     Sec-CH-UA: "Microsoft Edge";v="112", "Edge Side Panel";v="1", "Placeholder;Browser Brand";v="99"
     ```
diff --git a/microsoft-edge/progressive-web-apps/how-to/widgets.md b/microsoft-edge/progressive-web-apps/how-to/widgets.md
index 0f08b8f9c9..27f0508c48 100644
--- a/microsoft-edge/progressive-web-apps/how-to/widgets.md
+++ b/microsoft-edge/progressive-web-apps/how-to/widgets.md
@@ -106,8 +106,8 @@ Each entry in the `widgets` array contains several fields, as shown below:
 
 In the above example, a music player application defines a mini player widget. A widget definition in the web app manifest has the following required and optional fields:
 
-| Field | Description | Required |
-|:--- |:--- |:--- |
+| Field | Description | Required? |
+|---|---|---|
 | `name` | The title of the widget, presented to users. | Yes |
 | `short_name` | An alternative short version of the name. | No |
 | `description` | A description of what the widget does. | Yes |
@@ -440,7 +440,7 @@ The PWAmp widget displays the current song and buttons to play the previous or n
 The service worker global object (or [ServiceWorkerGlobalScope](https://developer.mozilla.org/docs/Web/API/ServiceWorkerGlobalScope)) contains a `widgets` attribute that exposes the following Promise-based methods:
 
 | Method | Description | Parameters | Return value |
-|:--- |:--- |:--- |:--- |
+|---|---|---|---|
 | `getByTag(tag)` | Gets a widget by tag. | The widget tag | A Promise that resolves to the [widget object](#widget-object) that matches the tag, or `undefined`. |
 | `getByInstanceId(id)` | Gets a widget by instance ID. | The widget instance ID | A Promise that resolves to the corresponding [widget object](#widget-object), or `undefined`. |
 | `getByHostId(id)` | Gets widgets by host ID. | The host ID | An array of [widget objects](#widget-object) found in that host. |
@@ -514,7 +514,7 @@ This object is passed as an argument to listeners of service worker widget event
 For the `widgetinstall`, `widgetuninstall`, and `widgetresume` event types, the `widgetEvent` object has the following properties:
 
 | Property | Description | Type |
-|:--- |:--- |:--- |
+|---|---|---|
 | `widget` | The widget instance that triggered the event. | [widget](#widget-object) |
 | `instanceId` | The widget instance ID. | `String` |
 | `hostId` | The widget host ID. | `String` |
@@ -528,7 +528,7 @@ This object is passed as an argument to listeners of service worker widget event
 The `widgetClickEvent` object has the following properties:
 
 | Property | Description | Type |
-|:--- |:--- |:--- |
+|---|---|---|
 | `action` | The action that triggered the event, as defined in the `actions.verb` fields of the widget template. See [Define widget actions](#define-widget-actions). | `String` |
 | `widget` | The widget instance that triggered the event. | [widgetInstance](#widgetinstance-object) |
 | `hostId` | The widget host ID. | `String` |
diff --git a/microsoft-edge/progressive-web-apps/how-to/window-controls-overlay.md b/microsoft-edge/progressive-web-apps/how-to/window-controls-overlay.md
index 5755eed12d..da126a11b6 100644
--- a/microsoft-edge/progressive-web-apps/how-to/window-controls-overlay.md
+++ b/microsoft-edge/progressive-web-apps/how-to/window-controls-overlay.md
@@ -53,11 +53,11 @@ The [`env()`](https://developer.mozilla.org/docs/Web/CSS/env) CSS function can b
 Four environment variables are added by the Window Controls Overlay feature:
 
 | Variable | Description |
-|:--- |:---
-| `titlebar-area-x` | Distance, in `px`, of the area normally occupied by the title bar from the left side of the window |
-| `titlebar-area-y` | Distance, in `px`, of the area normally occupied by the title bar from the top side of the window |
-| `titlebar-area-width` | Width of the title bar area, in `px` |
-| `titlebar-area-height` | Height of the title bar area, in `px` |
+|---|---|
+| `titlebar-area-x` | The distance, in `px`, of the area normally occupied by the title bar from the left side of the window. |
+| `titlebar-area-y` | The distance, in `px`, of the area normally occupied by the title bar from the top side of the window. |
+| `titlebar-area-width` | The width of the title bar area, in `px`. |
+| `titlebar-area-height` | The height of the title bar area, in `px`. |
 
 You can use these environment variables to position and size your own content where the title bar would normally appear, when the window controls overlay feature is disabled:
 
diff --git a/microsoft-edge/progressive-web-apps/landing/index.yml b/microsoft-edge/progressive-web-apps/landing/index.yml
index ba06645ccf..af04b5ec80 100644
--- a/microsoft-edge/progressive-web-apps/landing/index.yml
+++ b/microsoft-edge/progressive-web-apps/landing/index.yml
@@ -98,7 +98,7 @@ landingContent:
 
           - text: Provide in-app purchases with the Digital Goods API
             url: ../how-to/digital-goods-api.md
-            
+           
 # =============================================================================
 # Row 2
 # -----------------------------------------------------------------------------
diff --git a/microsoft-edge/progressive-web-apps/samples/index.md b/microsoft-edge/progressive-web-apps/samples/index.md
index 3dc7b931d4..06d0a0cd1e 100644
--- a/microsoft-edge/progressive-web-apps/samples/index.md
+++ b/microsoft-edge/progressive-web-apps/samples/index.md
@@ -36,7 +36,7 @@ This demo is in the [webmaxru / bpm-counter](https://github.com/webmaxru/bpm-cou
 BPM Techno uses the following features:
 
 | Feature | Description | Documentation |
-|:--- |:--- |:--- |
+|---|---|---|
 | Shortcuts | BPM Techno defines a shortcut that lets users upload an audio file in the app. | [Define app shortcuts (long-press or right-click menus)](../how-to/shortcuts.md) |
 | File Handling | BPM Techno natively handles `*.mp3` files. | [Handle files in a PWA](../how-to/handle-files.md) |
 | Share Target | Other apps can share audio files with BPM Techno, through the operating system sharing dialog. | [Receiving shared content](../how-to/share.md#receiving-shared-content) |
@@ -58,7 +58,7 @@ This demo is in the [pwa-builder / web-whiteboard](https://github.com/pwa-builde
 Webboard uses the following features:
 
 | Feature | Description | Documentation |
-|:--- |:--- |:--- |
+|---|---|---|
 | Web Share | Drawings can be shared with other apps through the operating system sharing dialog. | [Sharing content](../how-to/share.md#sharing-content) |
 
 
diff --git a/microsoft-edge/progressive-web-apps/samples/temperature-converter-source-files.md b/microsoft-edge/progressive-web-apps/samples/temperature-converter-source-files.md
index 8e05a3913a..a9bd231a4f 100644
--- a/microsoft-edge/progressive-web-apps/samples/temperature-converter-source-files.md
+++ b/microsoft-edge/progressive-web-apps/samples/temperature-converter-source-files.md
@@ -10,7 +10,7 @@ ms.date: 10/17/2025
 ---
 # Temperature converter source files
 
-The sample Temperature converter Progressive Web App (PWA) 
+Source files for the Temperature converter Progressive Web App (PWA) sample.
 
 See also:
 * [/temperature-converter/](https://github.com/MicrosoftEdge/Demos/tree/main/temperature-converter/) - source code directory.
@@ -259,7 +259,7 @@ See also:
 
 ```javascript
 const CACHE_NAME = `temperature-converter-v1`;
-    
+   
 // Use the install event to pre-cache all initial resources.
 self.addEventListener('install', event => {
   event.waitUntil((async () => {
@@ -284,7 +284,7 @@ self.addEventListener('fetch', event => {
         try {
           // If the resource was not in the cache, try the network.
           const fetchResponse = await fetch(event.request);
-    
+   
           // Save the resource in the cache and return it.
           cache.put(event.request, fetchResponse.clone());
           return fetchResponse;
@@ -323,7 +323,7 @@ The main directory for a Progressive Web App (PWA)'s source code can contain a R
 
 Source code:
 * [/temperature-converter/](https://github.com/MicrosoftEdge/Demos/tree/main/temperature-converter/)
-   * [index.html](https://github.com/MicrosoftEdge/Demos/blob/main/temperature-converter/index.html) 
+   * [index.html](https://github.com/MicrosoftEdge/Demos/blob/main/temperature-converter/index.html)
    * [converter.css](https://github.com/MicrosoftEdge/Demos/blob/main/temperature-converter/converter.css)
    * [converter.js](https://github.com/MicrosoftEdge/Demos/blob/main/temperature-converter/converter.js)
    * [manifest.json](https://github.com/MicrosoftEdge/Demos/blob/main/temperature-converter/manifest.json)
diff --git a/microsoft-edge/progressive-web-apps/samples/temperature-converter.md b/microsoft-edge/progressive-web-apps/samples/temperature-converter.md
index ad637d1e34..97ef3e217d 100644
--- a/microsoft-edge/progressive-web-apps/samples/temperature-converter.md
+++ b/microsoft-edge/progressive-web-apps/samples/temperature-converter.md
@@ -384,7 +384,7 @@ Confirm that the service worker (`sw.js`) is running when you open the PWA as a
 ## Step 10: Use DevTools to turn off the internet connection and test the PWA offline
 
 Try the Progressive Web App (PWA) as an offline app, as follows:
- 
+
 1. In the DevTools window, open the **Network** (![The Network icon](./temperature-converter-images/network-icon.png)) tool.
 
 1. Near the top, in the **Throttling**<!-- no tooltip --> menu to the right of the **Disable cache** checkbox, change from **No throttling** to **Offline**:
@@ -548,7 +548,7 @@ Create a working branch and switch to it, as follows:
 1. In the **Explorer** pane, open `/temperature-converter/manifest.json`.
 
 1. In `manifest.json`, change the app's name in two lines from "Temperature converter" to "TC", as follows:
-   
+  
    Change from:
 
    ```json
diff --git a/microsoft-edge/progressive-web-apps/ux.md b/microsoft-edge/progressive-web-apps/ux.md
index 3499e70e03..3c435e5f4c 100644
--- a/microsoft-edge/progressive-web-apps/ux.md
+++ b/microsoft-edge/progressive-web-apps/ux.md
@@ -24,15 +24,17 @@ See also:
 
 When Microsoft Edge determines that a website is an installable Progressive Web App (PWA), the **App available** (![The "App available" icon](./ux-images/app-available-icon.png)) icon appears in the Address bar.
 
-1.  Click the **App available** (![The "App available" icon](./ux-images/app-available-icon.png)) icon to install the PWA.
+1. Click the **App available** (![The "App available" icon](./ux-images/app-available-icon.png)) icon:
 
-    ![The installation prompt in Microsoft Edge](./ux-images/edge-app-install-flyout.png)
+   ![The installation prompt in Microsoft Edge](./ux-images/edge-app-install-flyout.png)
 
-1.  Click **Install** to complete the installation and run the PWA in Windows.
+1. Click the **Install** button.
+
+   The installation completes, and the PWA runs in Windows.
 
 Many PWAs are also present on the [Microsoft Store](https://apps.microsoft.com), and can be installed directly from there, without needing to open Microsoft Edge.
 
-To install a PWA from the Microsoft Store, select **Get** on the app page:
+To install a PWA from the Microsoft Store, on the app's page, click the **Get** button:
 
 ![Installing an app from the Microsoft Store](./ux-images/install-webboard-microsoft-store.png)
 
@@ -208,7 +210,7 @@ The **App info** menu contains the following:
    * **Extensions** - List of extensions that Microsoft Edge has installed.
 
    * **More tools**
-    
+   
 
 <!-- ====================================================================== -->
 ## Limitations
diff --git a/microsoft-edge/progressive-web-apps/whats-new/pwa.md b/microsoft-edge/progressive-web-apps/whats-new/pwa.md
index 3142e98836..f101c0d3e5 100644
--- a/microsoft-edge/progressive-web-apps/whats-new/pwa.md
+++ b/microsoft-edge/progressive-web-apps/whats-new/pwa.md
@@ -10,7 +10,7 @@ ms.date: 10/24/2023
 ---
 # What's new in PWAs
 
-The following are the updates to Progressive Web Apps (PWAs) and Web Apps, from the Microsoft Edge Web Apps team.  To try new features, read these announcements.  
+The following are the updates to Progressive Web Apps (PWAs) and Web Apps, from the Microsoft Edge Web Apps team.  To try new features, read these announcements. 
 
 To stay up to date with the latest and greatest features, download a preview channel of Microsoft Edge (Beta, Dev, or Canary); go to [Become a Microsoft Edge Insider](https://www.microsoft.com/edge/download/insider).
 
@@ -169,7 +169,7 @@ Microsoft Edge version 96 is scheduled to become the Stable release on Nov. 18,
 
 
 <!-- ------------------------------ -->
-#### Store apps registered as URL handlers hide custom tab UI 
+#### Store apps registered as URL handlers hide custom tab UI
 
 Store-installed PWAs that are participating in the [URL Handlers origin trial](#url-handlers-origin-trial) will no longer show the Chrome Custom Tab (CCT) when redirecting from the PWA's domain to a matching domain name with a different top-level domain (TLD). This redirecting often happens in apps with locale-specific domains; for example, redirecting from `contoso.com` to `contoso.ca` for users in Canada.
 
diff --git a/microsoft-edge/puppeteer/index.md b/microsoft-edge/puppeteer/index.md
index 9144e89926..d37e0be85d 100644
--- a/microsoft-edge/puppeteer/index.md
+++ b/microsoft-edge/puppeteer/index.md
@@ -48,7 +48,7 @@ To use `puppeteer-core` to launch Microsoft Edge:
 
     ```javascript
     const puppeteer = require('puppeteer-core');
-    
+   
     (async () => {
       const browser = await puppeteer.launch({
         executablePath: 'C:\\Program Files (x86)\\Microsoft\\Edge Dev\\Application\\msedge.exe'
@@ -56,11 +56,11 @@ To use `puppeteer-core` to launch Microsoft Edge:
       const page = await browser.newPage();
       await page.goto('https://www.microsoft.com/edge/download/insider');
       await page.screenshot({path: 'example.png'});
-    
+   
       await browser.close();
     })();
     ```
-    
+   
 1.  Follow the next steps to find the executable path and then change `executablePath` to point to your installation of Microsoft Edge.  For example, on macOS, the `executablePath` for Microsoft Edge Canary should be set to `/Applications/Microsoft\ Edge\ Canary.app/`.
 
 1.  To find the `executablePath`, a simple manual approach is to go to `edge://version` and copy the **Executable path** on that page.
@@ -70,19 +70,19 @@ To use `puppeteer-core` to launch Microsoft Edge:
     ```console
     npm i edge-paths
     ```
-    
+   
     ```console
     yarn add edge-paths
     ```
-    
+   
 1.  Then, if you're using `edge-paths` to find the executable path, run code like the following sample. It uses the [edge-paths](https://www.npmjs.com/package/edge-paths) package to programmatically find the path to your installation of Microsoft Edge on your OS:
 
     ```javascript
     const edgePaths = require("edge-paths");
-    
+   
     const EDGE_PATH = edgePaths.getEdgePath();
     ```
-    
+   
 1.  Now that you've found the executable path (either manually or programmatically), in `example.js`, set `executablePath: EDGE_PATH`.  Save your changes.
 
 1.  Run `example.js` from the command line:
diff --git a/microsoft-edge/test-and-automation/webhint.md b/microsoft-edge/test-and-automation/webhint.md
index 7a0d10d973..bd934f9471 100644
--- a/microsoft-edge/test-and-automation/webhint.md
+++ b/microsoft-edge/test-and-automation/webhint.md
@@ -15,4 +15,4 @@ As of Apr. 2022, the webhint extension for Visual Studio Code is no longer being
 
 [Webhint Visual Studio Code extension](https://marketplace.visualstudio.com/items?itemName=webhint.vscode-webhint) at Visual Studio Marketplace.
 
-[webhint](https://webhint.io) is a customizable linting tool, to improve the accessibility, performance, cross-browser compatibility, PWA compatibility, and security of your site.  The webhint extension checks your code for best practices and common errors. 
+[webhint](https://webhint.io) is a customizable linting tool, to improve the accessibility, performance, cross-browser compatibility, PWA compatibility, and security of your site.  The webhint extension checks your code for best practices and common errors.
diff --git a/microsoft-edge/toc.yml b/microsoft-edge/toc.yml
index e391b10cc7..4d139343d2 100644
--- a/microsoft-edge/toc.yml
+++ b/microsoft-edge/toc.yml
@@ -494,7 +494,7 @@
             - name: About the list of tools
               href: ./devtools/about-tools.md
 # =============================================================================
-# Default tools 
+# Default tools
 # -----------------------------------------------------------------------------
             - name: Inspect tool
               items:
@@ -680,7 +680,7 @@
 # -----------------------------------------------------------------------------
             - name: Performance tool  # = upstream TOC bucket "Performance"
               items:
-                - name: "Performance tool: Analyze your website's performance"  # = Performance > Overview 
+                - name: "Performance tool: Analyze your website's performance"  # = Performance > Overview
                   href: ./devtools/performance/overview.md
                   displayName: Performance tool
 
@@ -735,7 +735,7 @@
 
                 - name: Record heap snapshots using the Memory tool ("Heap snapshot" profiling type)
                   href: ./devtools/memory-problems/heap-snapshots.md
-                  displayName: Memory tool 
+                  displayName: Memory tool
 
                 - name: Use Allocation instrumentation on timeline ("Allocations on timeline" profiling type)
                   href: ./devtools/memory-problems/allocation-profiler.md
@@ -1523,7 +1523,10 @@
                 - name: Release notes for the WebView2 Runtime
                   href: ./webview2/release-notes/runtime/index.md
 
-                - name: Preview Runtime 152.0.4181.0 (Aug. 3, 2026)
+                - name: Preview Runtime 153.n.nnnn.nn (Mmm. dd, yyyy)
+                  href: ./webview2/release-notes/runtime/153.md
+
+                - name: Runtime 152.n.nnnn.nn (Mmm. dd, yyyy)
                   href: ./webview2/release-notes/runtime/152.md
 
                 - name: Runtime 151.0.4129.50 (Aug. 3, 2026)
@@ -1550,11 +1553,11 @@
                 - name: Runtime 144.0.3719.77 (Jan. 27, 2026)
                   href: ./webview2/release-notes/runtime/144.md
 
-                - name: Runtime 143.0.3650.58 (Dec. 8, 2025)
-                  href: ./webview2/release-notes/runtime/143.md
-
                 - name: Archive
                   items:
+                    - name: Runtime 143.0.3650.58 (Dec. 8, 2025)
+                      href: ./webview2/release-notes/runtime/143.md
+
                     - name: Runtime 142.0.3595.46 (Nov. 3, 2025)
                       href: ./webview2/release-notes/runtime/142.md
 
@@ -1762,6 +1765,9 @@
                 - name: Release notes for WebView2 SDKs
                   href: ./webview2/release-notes/sdk/index.md
 
+                - name: SDK n.n.nnnn.nn, for Runtime 152 (Mmm. dd, yyyy)
+                  href: ./webview2/release-notes/sdk/1-0-nnnn-nn.md
+
                 - name: SDK 1.0.4181-prerelease, for Runtime 152 (Aug. 3, 2026)
                   href: ./webview2/release-notes/sdk/1-0-4181-prerelease.md
 
@@ -2612,7 +2618,7 @@
           href: ./visual-studio-code/ide-integration.md
 
       # - name: Use DevTools as an IDE
-      #   href: 
+      #   href:
 
         - name: DevTools extension for Visual Studio Code # aux jump page
           href: ./visual-studio-code/microsoft-edge-devtools-extension/devtools-extension.md
diff --git a/microsoft-edge/visual-studio-code/ide-integration.md b/microsoft-edge/visual-studio-code/ide-integration.md
index 7e04c232f6..9eccdc6bc6 100644
--- a/microsoft-edge/visual-studio-code/ide-integration.md
+++ b/microsoft-edge/visual-studio-code/ide-integration.md
@@ -68,7 +68,7 @@ Use webhint, a customizable linting tool, to improve the functionality of your s
 
 webhint checks your code for best practices and common errors.  Identify and fix problems in your files, including HTML, CSS, JavaScript, and TypeScript.  Hints appear as wavy underlines in the text editor, and are summarized in the **Problems** pane.
 
-See also: 
+See also:
 * [webhint extension for Visual Studio Code](../test-and-automation/webhint.md)
 
 
diff --git a/microsoft-edge/visual-studio-code/microsoft-edge-devtools-extension.md b/microsoft-edge/visual-studio-code/microsoft-edge-devtools-extension.md
index f418219de3..5fe03869f7 100644
--- a/microsoft-edge/visual-studio-code/microsoft-edge-devtools-extension.md
+++ b/microsoft-edge/visual-studio-code/microsoft-edge-devtools-extension.md
@@ -43,7 +43,7 @@ The DevTools extension for Visual Studio Code is one of several different ways t
 
 | Approach | Pros and Cons | Article |
 |---|---|---|
-| Browser > DevTools > **Elements** tool | You have to manually copy changes from DevTools into your source files. | [Inspect, edit, and debug HTML and CSS with the Elements tool](../devtools/elements-tool/elements-tool.md)| 
+| Browser > DevTools > **Elements** tool | You have to manually copy changes from DevTools into your source files. | [Inspect, edit, and debug HTML and CSS with the Elements tool](../devtools/elements-tool/elements-tool.md)|
 | Browser > DevTools > **Sources** tool > **Workspace** tab to define a **Workspace** | Always saves the changes, which could discourage experimenting | [Select a local Workspace, to use DevTools to edit files and save changes to disk](../devtools/sources/index.md) in _Sources tool overview_ |
 | Browser > DevTools > **Settings** > **Experiments** > **Open source files in Visual Studio Code** | Always saves the changes, which could discourage experimenting | Experiments > [Opening source files in Visual Studio Code](../devtools/sources/opening-sources-in-vscode.md). |
 | Microsoft Edge DevTools extension for Visual Studio Code | Automatically opens and edits the CSS source file but doesn't automatically save the file, so you get to choose whether to save the edits. | The present article. |
diff --git a/microsoft-edge/visual-studio-code/microsoft-edge-devtools-extension/debugging-a-webpage.md b/microsoft-edge/visual-studio-code/microsoft-edge-devtools-extension/debugging-a-webpage.md
index 5b5723ec2b..8faeac153b 100644
--- a/microsoft-edge/visual-studio-code/microsoft-edge-devtools-extension/debugging-a-webpage.md
+++ b/microsoft-edge/visual-studio-code/microsoft-edge-devtools-extension/debugging-a-webpage.md
@@ -94,7 +94,7 @@ To start the Visual Studio Code debugger along with DevTools, by using the usual
    * On the **Activity Bar**, click the **Run and Debug** icon (![Run and Debug icon](./debugging-a-webpage-images/run-and-debug-icon.png)), and then in the **Run and Debug** Side Bar, click the **Run and Debug** button, as shown below.
 
    * Open the Visual Studio Code command palette, start typing the word **debug**, and then select **Debug: Open Link**.
-    
+   
    ![Start Microsoft Edge DevTools from the JavaScript debugger](./debugging-a-webpage-images/start-session.png)
 
    **Microsoft Edge Tools** doesn't appear in the above screenshot, because for this screenshot, DevTools was uninstalled.
diff --git a/microsoft-edge/visual-studio-code/microsoft-edge-devtools-extension/device-state-emulation.md b/microsoft-edge/visual-studio-code/microsoft-edge-devtools-extension/device-state-emulation.md
index 5d2ad301f7..d49f2f7f9a 100644
--- a/microsoft-edge/visual-studio-code/microsoft-edge-devtools-extension/device-state-emulation.md
+++ b/microsoft-edge/visual-studio-code/microsoft-edge-devtools-extension/device-state-emulation.md
@@ -51,7 +51,7 @@ Click the **Rotate** button (![The Rotate button](./device-state-emulation-image
 ## Emulate CSS Media Features button
 <!-- toolbar item 5. Emulate CSS media features -->
 
-Use the **Emulate CSS media features** button (![Emulate CSS media features](./device-state-emulation-images/emulate-css-media-features-button.png)) to: 
+Use the **Emulate CSS media features** button (![Emulate CSS media features](./device-state-emulation-images/emulate-css-media-features-button.png)) to:
 * Emulate CSS media queries.
 * Test how your product looks in print mode.
 * Switch between dark and light mode.
diff --git a/microsoft-edge/visual-studio-code/microsoft-edge-devtools-extension/get-started-launch-instance.md b/microsoft-edge/visual-studio-code/microsoft-edge-devtools-extension/get-started-launch-instance.md
index 0d521f9335..1da83d3d37 100644
--- a/microsoft-edge/visual-studio-code/microsoft-edge-devtools-extension/get-started-launch-instance.md
+++ b/microsoft-edge/visual-studio-code/microsoft-edge-devtools-extension/get-started-launch-instance.md
@@ -111,7 +111,7 @@ Opening a folder gives you the opportunity to grant trust to the folder, so that
 
 1. In the **Edge DevTools: Browser** tab, click the **Close DevTools** or **Open DevTools** button a couple times.  The other **DevTools** tab opens and closes, saving space.
 
-1. Along the top of Visual Studio Code, right-click the tabs and arrange them to show the various tabs at the same time: 
+1. Along the top of Visual Studio Code, right-click the tabs and arrange them to show the various tabs at the same time:
 
    * The Side Bar, showing **Microsoft Edge Tools** > **Targets**.
    * The `index.html` editor.
diff --git a/microsoft-edge/visual-studio-code/microsoft-edge-devtools-extension/get-started-launch-project.md b/microsoft-edge/visual-studio-code/microsoft-edge-devtools-extension/get-started-launch-project.md
index 7e95055239..f4fccf1e17 100644
--- a/microsoft-edge/visual-studio-code/microsoft-edge-devtools-extension/get-started-launch-project.md
+++ b/microsoft-edge/visual-studio-code/microsoft-edge-devtools-extension/get-started-launch-project.md
@@ -58,14 +58,14 @@ These steps explain how to start http-server by using the cross-platform git bas
    ```bash
    npx http-server
    ```
-   
+  
    ![Starting the server](./get-started-launch-project-images/git-bash-starting-server-2nd-time.png)
 
    Information about the server and localhost URL is displayed, such as:
 
    ```bash
    Starting up http-server, serving ./
-   
+  
    Available on:
    http://10.0.1.8:8080
    http://127.0.0.1:8080
@@ -81,7 +81,7 @@ These steps explain how to start http-server by using the cross-platform git bas
 This section is in support of clicking the **Launch Project** button.
 
 1. In Visual Studio Code, select **File** > **Open Folder**.  Select your project directory that contains `index.html` for the cloned **demo-to-do** sample in the Demos repo, such as `C:\Users\username\Documents\GitHub\Demos\demo-to-do\`.
-   
+  
    ![The demo-to-do sample folder opened in Visual Studio Code](./get-started-launch-project-images/demo-todo-folder-opened.png)
 
    Just like in the repo's [demo-to-do](https://github.com/MicrosoftEdge/Demos/tree/main/demo-to-do) folder, initially there's no `.vscode` folder, and no `launch.json` file in that folder.
@@ -97,7 +97,7 @@ This section is in support of clicking the **Launch Project** button.
 1. In several places in the `launch.json` file, on each of the `"url"` lines, scroll to the right , and note the comment, "Provide your project's url":
 
    ```javascript
-   "url": "c:\\Users\\username\\.vscode\\extensions\\ms-edgedevtools.vscode-edge-devtools-2.1.1\\out\\startpage\\index.html", 
+   "url": "c:\\Users\\username\\.vscode\\extensions\\ms-edgedevtools.vscode-edge-devtools-2.1.1\\out\\startpage\\index.html",
    // Provide your project's url to finish configuring
    ```
 
diff --git a/microsoft-edge/visual-studio-code/microsoft-edge-devtools-extension/install.md b/microsoft-edge/visual-studio-code/microsoft-edge-devtools-extension/install.md
index 3217d724e2..8bfeb1a32b 100644
--- a/microsoft-edge/visual-studio-code/microsoft-edge-devtools-extension/install.md
+++ b/microsoft-edge/visual-studio-code/microsoft-edge-devtools-extension/install.md
@@ -215,7 +215,7 @@ These steps start the server for the first time.
 
    ```console
    Starting up http-server, serving ./
-   
+  
    Available on:
    http://10.0.1.8:8080
    http://127.0.0.1:8080
diff --git a/microsoft-edge/visual-studio-code/microsoft-edge-devtools-extension/open-devtools-and-embedded-browser.md b/microsoft-edge/visual-studio-code/microsoft-edge-devtools-extension/open-devtools-and-embedded-browser.md
index 283a3d487a..de38e84ebb 100644
--- a/microsoft-edge/visual-studio-code/microsoft-edge-devtools-extension/open-devtools-and-embedded-browser.md
+++ b/microsoft-edge/visual-studio-code/microsoft-edge-devtools-extension/open-devtools-and-embedded-browser.md
@@ -161,7 +161,7 @@ Continue below.
 1. In several places in the `launch.json` file, on each of the `"url"` lines, scroll to the right, and note the comment, "Provide your project's url to finish configuring":
 
    ```javascript
-   "url": "c:\\Users\\username\\.vscode\\extensions\\ms-edgedevtools.vscode-edge-devtools-2.1.1\\out\\startpage\\index.html", 
+   "url": "c:\\Users\\username\\.vscode\\extensions\\ms-edgedevtools.vscode-edge-devtools-2.1.1\\out\\startpage\\index.html",
    // Provide your project's url to finish configuring
    ```
 
@@ -212,7 +212,7 @@ See also:
 
 If DevTools is able to correlate and establish the workspace mapping between the files downloaded from the server and the files in the folder that you opened, DevTools provides its full functionality, including CSS mirror editing of your local source files when you change CSS in DevTools.
 
-If DevTools can't map the files in the **Edge DevTools: Browser** tab to the files in the folder that you opened in Visual Studio Code's Explorer, you can inspect webpages, and you can change them, such as changing CSS values in the **Sources** tab of the **Elements** tool in the **Edge DevTools** tab.  In this case, though, you can't use CSS mirror editing though, to have DevTools automatically edit your source files.  Options include: 
+If DevTools can't map the files in the **Edge DevTools: Browser** tab to the files in the folder that you opened in Visual Studio Code's Explorer, you can inspect webpages, and you can change them, such as changing CSS values in the **Sources** tab of the **Elements** tool in the **Edge DevTools** tab.  In this case, though, you can't use CSS mirror editing though, to have DevTools automatically edit your source files.  Options include:
 
 * Clear the **CSS mirror editing** checkbox in **Styles** tab and continue experimenting with CSS changes.
 
@@ -220,7 +220,6 @@ If DevTools can't map the files in the **Edge DevTools: Browser** tab to the fil
 
 * Grant trust to a folder by opening it in Visual Studio Code.
 
-
 For example:
 
 1. Open a folder that's in your local copy of the Demos repo, such as `C:\Users\username\Documents\GitHub\Demos\demo-to-do\`, as described in [Get started using the DevTools extension for Visual Studio Code](./get-started.md).
@@ -238,6 +237,7 @@ For example:
    The above image shows using the **Styles** tab with **CSS mirror editing** checkbox selected, used to enlarge the body text to **24pt**.  The **Edge DevTools: Browser** tab renders the page as you change the value.  The tab's Address bar contains a URL rather than a file path.  Because **CSS mirror editing** checkbox selected and the corresponding `.css` file is found in a writeable local folder, the `.css` file on the local drive is automatically edited to `24pt;`.
 
 
+<!-- ------------------------------ -->
 #### Avoiding error messages about mirroring or mapping
 
 Next, try changing CSS without a matching folder opened:
@@ -258,7 +258,7 @@ Next, try changing CSS without a matching folder opened:
 
    ![The Microsoft Edge Tools Side Bar when viewing a URL](./open-devtools-and-embedded-browser-images/limited-css-edit-ability-for-remote-url.png)
 
-Options in this case include: 
+Options in this case include:
 
 * Clear the **CSS mirror editing** checkbox in **Styles** tab and continue experimenting with CSS changes (without automatic editing of CSS in source files).  This prevents further error messages about mapping to source files for CSS mirror editing.
 
@@ -270,6 +270,7 @@ See also:
 * [Troubleshooting the DevTools extension](./troubleshooting.md)
 
 
+<!-- ------------------------------ -->
 #### URLs, file paths, and opening a matching folder
 
 In some cases, behavior of DevTools is different for file paths than for URLs.
diff --git a/microsoft-edge/visual-studio/index.md b/microsoft-edge/visual-studio/index.md
index 463129bdb4..70d21ee816 100644
--- a/microsoft-edge/visual-studio/index.md
+++ b/microsoft-edge/visual-studio/index.md
@@ -70,7 +70,7 @@ Next, run and debug the ASP.NET Core web app project in Visual Studio, as follow
    ![Turn on script debugging in Visual Studio](./index-images/enable-script-debugging.png)
 
 1. In the same dropdown list, select **Web Browser** > the preview channel of Microsoft Edge that you want Visual Studio to launch, such as Microsoft Edge Canary, Dev, or Beta.
- 
+
    ![Select the preview channel of Microsoft Edge that you want Visual Studio to launch](./index-images/set-web-browser.png)
 
    To download a preview channel of Microsoft Edge (Beta, Dev, or Canary), go to [Become a Microsoft Edge Insider](https://www.microsoft.com/edge/download/insider).
@@ -119,7 +119,7 @@ To attach the Visual Studio debugger to an instance of Microsoft Edge that's alr
    ```console
    start msedge --remote-debugging-port=9222
    ```
-    
+   
 1. In Visual Studio, select **Debug** > **Attach to Process** or **Ctrl+Alt+P**.
 
    ![Selecting 'Debug > Attach to Process' in Visual Studio](./index-images/attach-to-process.png)
diff --git a/microsoft-edge/web-platform/devtools-mcp-server.md b/microsoft-edge/web-platform/devtools-mcp-server.md
index afedc92bc1..c849f8d5d5 100644
--- a/microsoft-edge/web-platform/devtools-mcp-server.md
+++ b/microsoft-edge/web-platform/devtools-mcp-server.md
@@ -48,7 +48,7 @@ Chrome DevTools for agents (`chrome-devtools-mcp`) lets your coding agent (such
 Chrome DevTools for agents (`chrome-devtools-mcp`) lets your coding agent (such as Copilot, Antigravity, Claude, or Cursor) control and inspect a live Chromium-based browser, including Microsoft Edge and WebView2.
 <!-- / end of copied to top of article -->
 
-Chrome DevTools for agents acts as a Model-Context-Protocol (MCP) server, giving your AI coding assistant access to the full power of Microsoft Edge DevTools for reliable automation, in-depth debugging, and performance analysis. 
+Chrome DevTools for agents acts as a Model-Context-Protocol (MCP) server, giving your AI coding assistant access to the full power of Microsoft Edge DevTools for reliable automation, in-depth debugging, and performance analysis.
 
 The Chrome DevTools MCP server supports connecting to any Chromium-based browser, including Microsoft Edge and WebView2.  Because the server is built for the Google Chrome browser, you need to provide extra configuration to point the server at Microsoft Edge or a WebView2 instance.
 
@@ -77,7 +77,7 @@ The examples in this guide use the VS Code `mcp.json` format.  If you're using a
 ## Launch Edge
 
 Use this configuration to let your coding agent launch Microsoft Edge for you.
-   
+  
 With this configuration, the Model-Context-Protocol (MCP) server, which your agent connects to, launches Edge, by using the `--executablePath` flag pointing to the Edge binary.
 
 Copy and paste the configuration snippet for your platform into your VS Code `mcp.json`.  These examples use Edge Stable.
@@ -175,10 +175,10 @@ These are default install locations.  Paths may vary based on user configuration
 | Stable | `%ProgramFiles(x86)%\Microsoft\Edge\Application\msedge.exe` |
 | Beta | `%ProgramFiles(x86)%\Microsoft\Edge Beta\Application\msedge.exe` |
 | Dev | `%ProgramFiles(x86)%\Microsoft\Edge Dev\Application\msedge.exe` |
-| Canary | `%LOCALAPPDATA%\Microsoft\Edge SxS\Application\msedge.exe` |  
+| Canary | `%LOCALAPPDATA%\Microsoft\Edge SxS\Application\msedge.exe` | 
 
 ##### [macOS](#tab/macos/)
-   
+  
 | Channel | Default Path |
 |---|---|
 | Stable | `/Applications/Microsoft Edge.app/Contents/MacOS/Microsoft Edge` |
@@ -355,7 +355,7 @@ These are default locations.  Paths may vary based on user configuration, versio
 
 WebView2 doesn't have a "launch" scenario; instead, the host app creates the WebView2 instance.
 
-The MCP server connects to the WebView2 instance via auto-connect, similar to [Auto-connect to a running Edge instance](#auto-connect-to-a-running-edge-instance), above.  
+The MCP server connects to the WebView2 instance via auto-connect, similar to [Auto-connect to a running Edge instance](#auto-connect-to-a-running-edge-instance), above. 
 
 
 <!-- ------------------------------ -->
diff --git a/microsoft-edge/web-platform/how-to-detect-win11-images/acceptCH.svg b/microsoft-edge/web-platform/how-to-detect-win11-images/acceptCH.svg
index 491b8bd602..de60a515f3 100644
--- a/microsoft-edge/web-platform/how-to-detect-win11-images/acceptCH.svg
+++ b/microsoft-edge/web-platform/how-to-detect-win11-images/acceptCH.svg
@@ -71,7 +71,7 @@ skinparam useBetaStyle false
 	network {
 			FontColor #2196F3
 	BorderColor #2196F3
-	BackgroundColor transparent    
+	BackgroundColor transparent   
 		LineColor #2196F3
 		LineThickness 1.0
 		FontColor #1a78c2
@@ -136,7 +136,7 @@ skinparam shadowing             true
 skinparam roundcorner           8
 skinparam ParticipantPadding    40
 skinparam BoxPadding            40
-skinparam Padding               10 
+skinparam Padding               10
 skinparam TitleFontColor	    #222
 skinparam TitleFontSize	    	20
 skinparam TitleBorderThickness 	0
diff --git a/microsoft-edge/web-platform/how-to-detect-win11-images/criticalCH.svg b/microsoft-edge/web-platform/how-to-detect-win11-images/criticalCH.svg
index 46582dd018..ed29b4d0ef 100644
--- a/microsoft-edge/web-platform/how-to-detect-win11-images/criticalCH.svg
+++ b/microsoft-edge/web-platform/how-to-detect-win11-images/criticalCH.svg
@@ -4,7 +4,7 @@
 participant "Client (Browser)" as c
 participant "Server (Website)" as s
 c -> s: **Request Headers** \n user-agent: <UA string> \n sec-ch-ua: ... \n sec-ch-ua-mobile: ... \n ...
-s- -> c: **Response Headers** \n Accept-CH: sec-ch-ua-platform \n Critical-CH: sec-ch-ua-platform 
+s- -> c: **Response Headers** \n Accept-CH: sec-ch-ua-platform \n Critical-CH: sec-ch-ua-platform
 c -> s: **Request Headers** \n user-agent: <UA string> \n sec-ch-ua: ... \n sec-ch-ua-mobile: ... \n sec-ch-ua-platform: ... \n...
 @enduml
 
@@ -72,7 +72,7 @@ skinparam useBetaStyle false
 	network {
 			FontColor #2196F3
 	BorderColor #2196F3
-	BackgroundColor transparent    
+	BackgroundColor transparent   
 		LineColor #2196F3
 		LineThickness 1.0
 		FontColor #1a78c2
@@ -137,7 +137,7 @@ skinparam shadowing             true
 skinparam roundcorner           8
 skinparam ParticipantPadding    40
 skinparam BoxPadding            40
-skinparam Padding               10 
+skinparam Padding               10
 skinparam TitleFontColor	    #222
 skinparam TitleFontSize	    	20
 skinparam TitleBorderThickness 	0
@@ -446,7 +446,7 @@ skinparam stack {
 participant "Client (Browser)" as c
 participant "Server (Website)" as s
 c -> s: **Request Headers** \n user-agent: <UA string> \n sec-ch-ua: ... \n sec-ch-ua-mobile: ... \n ...
-s- -> c: **Response Headers** \n Accept-CH: sec-ch-ua-platform \n Critical-CH: sec-ch-ua-platform 
+s- -> c: **Response Headers** \n Accept-CH: sec-ch-ua-platform \n Critical-CH: sec-ch-ua-platform
 c -> s: **Request Headers** \n user-agent: <UA string> \n sec-ch-ua: ... \n sec-ch-ua-mobile: ... \n sec-ch-ua-platform: ... \n...
 @enduml
 
diff --git a/microsoft-edge/web-platform/how-to-detect-win11.md b/microsoft-edge/web-platform/how-to-detect-win11.md
index dcd193a373..9ca18bc351 100644
--- a/microsoft-edge/web-platform/how-to-detect-win11.md
+++ b/microsoft-edge/web-platform/how-to-detect-win11.md
@@ -127,7 +127,7 @@ Currently, website servers must send the `Accept-CH` response header to the brow
 <!-- To edit SVG go to link: http://www.plantuml.com/plantuml/uml/LOrDIWD144RtVOeogpZGSu11Gc8sMIlYnasbyvaqz4zRLQtNTsH0CgiFwZtgxTLOhEVa7ko63CfiaCY-TaknmBKPnn0R5wFDCKNCktsM-gEGnmsnKbWxhv1l26tVSTPeM1nrWVoETA9XUC5NXngTm1U83WDz5EeAyNn5iOcUtWwa9h5STtz84Nou-SuJZUEuklXSpp7X7ypZrC-Xi8IqrQ9ObmuXe9a_dgQxFosnVLR9RezowJdz0W00 -->
 ![Requests using only Accept-CH header](./how-to-detect-win11-images/acceptCH.svg)
 
-During this initial request, the client will record the `Accept-CH` preferences and on subsequent requests include `sec-ch-ua-platform` by default. 
+During this initial request, the client will record the `Accept-CH` preferences and on subsequent requests include `sec-ch-ua-platform` by default.
 
 To further optimize this flow, the new `Critical-CH` header can be used in addition to the `Accept-CH` header to reissue the request header immediately, without the need for a page reload. The following diagram shows the browser sending request headers to the server including `user agent: <UA string>` and receiving response headers including `Accept-CH: sec-ch-ua-platform` and `Critical-CH: sec-ch-ua-platform`. The browser then sends request headers to the server immediately.
 
diff --git a/microsoft-edge/web-platform/languagedetector-api.md b/microsoft-edge/web-platform/languagedetector-api.md
index 9c69fdc9d9..f81faa99da 100644
--- a/microsoft-edge/web-platform/languagedetector-api.md
+++ b/microsoft-edge/web-platform/languagedetector-api.md
@@ -100,7 +100,7 @@ To see the Language Detector API in action, and view existing code that uses thi
    The model starts detecting the language of the text.
 
    The output is generated in the response section of the page.
-   
+  
    The output displays:
    * The name of the detected language.
    * The percent certainty of which language.
@@ -193,7 +193,7 @@ You can follow the progress of the model download by using the `monitor` option.
 // to monitor the model download.
 const session = await LanguageDetector.create({
   monitor: m => {
-    // Use the monitor object argument to add a listener for the 
+    // Use the monitor object argument to add a listener for the
     // downloadprogress event.
     m.addEventListener("downloadprogress", event => {
       // The event is an object with the loaded and total properties.
@@ -287,7 +287,7 @@ To destroy a session by creating an `AbortController` object, create a `Language
 // Create an AbortController object.
 const controller = new AbortController();
 
-// Create a Language Detector session and pass the 
+// Create a Language Detector session and pass the
 // AbortController object by using the signal option.
 const session = await LanguageDetector.create({
   signal: controller.signal
diff --git a/microsoft-edge/web-platform/prompt-api.md b/microsoft-edge/web-platform/prompt-api.md
index 10068f4677..ac79e8f649 100644
--- a/microsoft-edge/web-platform/prompt-api.md
+++ b/microsoft-edge/web-platform/prompt-api.md
@@ -151,7 +151,7 @@ By default, the Prompt API uses the Phi-4-mini model.  To use Aion-1.0-Instruct
 1. In Edge Canary or Edge Dev, open a new tab or window and go to `edge://flags`.
 
 1. In the search box at the top of the page, enter **Enable prerelease on-device language model**.
-  
+ 
 1. In the **Enable prerelease on-device language model** drop-down list, select **Enabled**, and then click the **Restart** button:
 
    ![Flags page showing the prerelease on-device language model flag](./prompt-api-images/prerelease-model-flag-for-prompt-api.png)
@@ -320,7 +320,7 @@ You can follow the progress of the model download by using the `monitor` option.
 // download.
 const session = await LanguageModel.create({
   monitor: m => {
-    // Use the monitor object argument to add an listener for the 
+    // Use the monitor object argument to add an listener for the
     // downloadprogress event.
     m.addEventListener("downloadprogress", event => {
       // The event is an object with the loaded and total properties.
diff --git a/microsoft-edge/web-platform/proofreader-api.md b/microsoft-edge/web-platform/proofreader-api.md
index 5d357e57d0..f7a6248d05 100644
--- a/microsoft-edge/web-platform/proofreader-api.md
+++ b/microsoft-edge/web-platform/proofreader-api.md
@@ -243,7 +243,7 @@ You can follow the progress of the model download by using the `monitor` option.
 // download.
 const session = await Proofreader.create({
   monitor: m => {
-    // Use the monitor object argument to add an listener for the 
+    // Use the monitor object argument to add an listener for the
     // downloadprogress event.
     m.addEventListener("downloadprogress", event => {
       // The event is an object with the loaded and total properties.
@@ -346,7 +346,7 @@ Alternatively, you can create an `AbortController` object, create a `Proofreader
 // Create an AbortController object.
 const controller = new AbortController();
 
-// Create a Proofreader session and pass the 
+// Create a Proofreader session and pass the
 // AbortController signal object by using the signal option.
 const session = await Proofreader.create({ signal: controller.signal });
 
diff --git a/microsoft-edge/web-platform/release-notes/140.md b/microsoft-edge/web-platform/release-notes/140.md
index 588b936793..0b76be7a64 100644
--- a/microsoft-edge/web-platform/release-notes/140.md
+++ b/microsoft-edge/web-platform/release-notes/140.md
@@ -329,7 +329,7 @@ See also:
 
 The `highlightsFromPoint` API lets you interact with custom highlights by detecting which highlights exist at a specific point within a document.
 
-The `highlightsFromPoint` API is useful for apps where multiple highlights may overlap or exist within the shadow DOM.  This API makes it possible to manage dynamic interactions that have custom highlights more effectively, such as by responding to user clicks or hover events on highlighted regions, to trigger custom tooltips, context menus, or other interactive features. 
+The `highlightsFromPoint` API is useful for apps where multiple highlights may overlap or exist within the shadow DOM.  This API makes it possible to manage dynamic interactions that have custom highlights more effectively, such as by responding to user clicks or hover events on highlighted regions, to trigger custom tooltips, context menus, or other interactive features.
 
 See also:
 * [CSS Custom Highlight API](https://developer.mozilla.org/docs/Web/API/CSS_Custom_Highlight_API) at MDN.
diff --git a/microsoft-edge/web-platform/release-notes/145.md b/microsoft-edge/web-platform/release-notes/145.md
index cef56cf1fe..9d34b3b995 100644
--- a/microsoft-edge/web-platform/release-notes/145.md
+++ b/microsoft-edge/web-platform/release-notes/145.md
@@ -380,7 +380,7 @@ To define a cookie's expiry time, you can now use the `maxAge` attribute when us
 This is in addition to the `expires` attribute, which already controls a cookie's expiry time.  The new, `maxAge` attribute:
 
 * Provides an alternative option that can sometimes be more intuitive than the `expires` attribute.
-* Aligns the Cookie Store API with the options that are provided by `document.cookie` and the `Set-Cookie` HTTP Header.  
+* Aligns the Cookie Store API with the options that are provided by `document.cookie` and the `Set-Cookie` HTTP Header. 
 
 See also:
 * [Cookie Store API](https://developer.mozilla.org/docs/Web/API/Cookie_Store_API) at MDN.
diff --git a/microsoft-edge/web-platform/release-notes/146.md b/microsoft-edge/web-platform/release-notes/146.md
index 54cefb13ee..cd6b71485f 100644
--- a/microsoft-edge/web-platform/release-notes/146.md
+++ b/microsoft-edge/web-platform/release-notes/146.md
@@ -243,7 +243,7 @@ WebGPU Compatibility mode adds an opt-in, lightly restricted subset of the WebGP
 
 By opting into this mode and following its constraints, you can extend the reach of your WebGPU application to many older devices that don't have the modern, explicit graphics APIs that core WebGPU requires.
 
-* For a simple app, the only required change is to set the `featureLevel` option to `"compatibility"` when calling `requestAdapter()`. 
+* For a simple app, the only required change is to set the `featureLevel` option to `"compatibility"` when calling `requestAdapter()`.
 
 * For a more advanced app, some modifications might be necessary, to accommodate for the Compatibility mode's restrictions.  However, because Compatibility mode uses a subset of the WebGPU API, your app will also work on browsers that don't support Compatibility mode.
 
diff --git a/microsoft-edge/web-platform/release-notes/147.md b/microsoft-edge/web-platform/release-notes/147.md
index 1dd60d18fe..e6695d0269 100644
--- a/microsoft-edge/web-platform/release-notes/147.md
+++ b/microsoft-edge/web-platform/release-notes/147.md
@@ -197,7 +197,7 @@ See also:
 <!-- ------------------------------ -->
 #### `<install>` HTML element
 
-The `<install>` HTML element represents a button that, upon activation, prompts the user to choose whether to install a progressive web app. 
+The `<install>` HTML element represents a button that, upon activation, prompts the user to choose whether to install a progressive web app.
 
 The content and appearance of the install button is controlled by Microsoft Edge and provides users with a consistent experience across web apps.
 
@@ -423,7 +423,7 @@ See also:
 
 Support for using XSLT stylesheets to transform XML data into SVG files has been removed.
 
-Previously, a specially crafted XML file could contain an XSL stylesheet that transforms generic XML data into an SVG file.  This capability is now deprecated and has been removed. 
+Previously, a specially crafted XML file could contain an XSL stylesheet that transforms generic XML data into an SVG file.  This capability is now deprecated and has been removed.
 
 
 <!-- ====================================================================== -->
@@ -474,7 +474,7 @@ Expires on Apr. 21, 2026.
 
 Detect and measure audio glitches and playout latency in real-time by using the `AudioPlayoutStats` interface.
 
-To optimize your audio application's user experience and responsiveness: 
+To optimize your audio application's user experience and responsiveness:
 * Monitor fallback frame events.
 * Calculate the fraction of silence that's due to underperformance.
 * Track average latency, minimum latency, and maximum latency.
diff --git a/microsoft-edge/web-platform/release-notes/150.md b/microsoft-edge/web-platform/release-notes/150.md
index 3ae270ce8f..19c88824e7 100644
--- a/microsoft-edge/web-platform/release-notes/150.md
+++ b/microsoft-edge/web-platform/release-notes/150.md
@@ -332,7 +332,7 @@ See also:
 
 
 <!-- ------------------------------ -->
-#### `MediaStreamTrackProcessor` frame counters 
+#### `MediaStreamTrackProcessor` frame counters
 
 The `discardedFrames` and `totalFrames` attributes are now available on the `MediaStreamTrackProcessor` interface.
 
diff --git a/microsoft-edge/web-platform/release-notes/151.md b/microsoft-edge/web-platform/release-notes/151.md
index 8f777d042d..0fcc51262f 100644
--- a/microsoft-edge/web-platform/release-notes/151.md
+++ b/microsoft-edge/web-platform/release-notes/151.md
@@ -283,7 +283,7 @@ See also:
 
 
 <!-- todo: when support is added in edge, uncomment section and move to correct relnotes page -->
-<!-- ------------------------------ 
+<!-- ------------------------------
 #### Support for unspoken punctuation in the Web Speech API
 
 The `SpeechRecognition` interface of the Web Speech API now has an `unspokenPunctuation` boolean attribute.
diff --git a/microsoft-edge/web-platform/release-notes/152.md b/microsoft-edge/web-platform/release-notes/152.md
index f72961a7a8..974d7072e1 100644
--- a/microsoft-edge/web-platform/release-notes/152.md
+++ b/microsoft-edge/web-platform/release-notes/152.md
@@ -49,7 +49,7 @@ See [What's new in DevTools (Microsoft Edge 152)](../../devtools/whats-new/152.m
 ## WebView2
 
 See:
-* [Preview Runtime 152.0.4181.0 (Aug. 3, 2026)](../../webview2/release-notes/runtime/152.md)
+* [Runtime 152.n.nnnn.nn (Mmm. dd, yyyy)](../../webview2/release-notes/runtime/152.md)
 * [SDK 1.0.4181-prerelease, for Runtime 152 (Aug. 3, 2026)](../../webview2/release-notes/sdk/1-0-4181-prerelease.md)
 
 
diff --git a/microsoft-edge/web-platform/site-impacting-changes.md b/microsoft-edge/web-platform/site-impacting-changes.md
index a629fa063d..2e99573073 100644
--- a/microsoft-edge/web-platform/site-impacting-changes.md
+++ b/microsoft-edge/web-platform/site-impacting-changes.md
@@ -15,7 +15,7 @@ This article highlights:
 * High-impact web platform changes, which might impact browser compatibility on your site, and which the Microsoft Edge team is tracking especially closely.
 
 For more information about other changes in Microsoft Edge, see [Release notes for Microsoft Edge web platform](./release-notes/index.md).
-  
+ 
 The web platform is a collection of technologies used for building webpages, including HTML, CSS, JavaScript, and many other open standards.  The web platform constantly evolves to improve the user experience, security, and privacy.  In some cases, these changes may affect the functionality of existing webpages.
 
 For functionality and compatibility reasons, Microsoft Edge adopts nearly all of the Chromium project's changes to the web platform.  However, Microsoft retains full control of the Microsoft Edge browser and may defer or reject changes. The Microsoft Edge team decides if the change benefits browser users.
@@ -98,9 +98,9 @@ This article uses the following notation for browser release numbers.
 | v123 | The feature or change ships in Microsoft Edge version 123. |
 | v123 (Chrome+1) | The feature or change ships in Microsoft Edge version 123, which is one release after the feature or change ships in Chrome version 122. |
 | v123 (Chrome+2) | The feature or change ships in Microsoft Edge version 123, which is two releases after the feature or change ships in Chrome version 121. |
-| Beta v123 | The feature or change ships in version 123 of the Beta preview channel of Microsoft Edge. | 
-| Dev v123 | The feature or change ships in version 123 of the Dev preview channel of Microsoft Edge. | 
-| Canary v123 | The feature or change ships in version 123 of the Canary preview channel of Microsoft Edge. | 
+| Beta v123 | The feature or change ships in version 123 of the Beta preview channel of Microsoft Edge. |
+| Dev v123 | The feature or change ships in version 123 of the Dev preview channel of Microsoft Edge. |
+| Canary v123 | The feature or change ships in version 123 of the Canary preview channel of Microsoft Edge. |
 
 
 <!-- ====================================================================== -->
diff --git a/microsoft-edge/web-platform/tracking-prevention.md b/microsoft-edge/web-platform/tracking-prevention.md
index 6c8f0876a2..294db89889 100644
--- a/microsoft-edge/web-platform/tracking-prevention.md
+++ b/microsoft-edge/web-platform/tracking-prevention.md
@@ -224,7 +224,7 @@ The **Block** and **Allow** options on the `edge://settings/content/cookies` pag
 * [Storage Access API](https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/master/StorageAccessAPI/explainer.md)
 
 disconnect.me:
-* [disconnect.me](https://disconnect.me) 
+* [disconnect.me](https://disconnect.me)
 * [Tracker Protection lists](https://github.com/disconnectme/disconnect-tracking-protection)
 * [entities.json](https://github.com/disconnectme/disconnect-tracking-protection/blob/master/entities.json) list - defines groups of URLs that are owned by the same parent organization/company.
 * [services.json](https://github.com/disconnectme/disconnect-tracking-protection/blob/master/services.json) - tracking protection list categories.
diff --git a/microsoft-edge/web-platform/translator-api.md b/microsoft-edge/web-platform/translator-api.md
index 73e8446561..7ecae3627f 100644
--- a/microsoft-edge/web-platform/translator-api.md
+++ b/microsoft-edge/web-platform/translator-api.md
@@ -101,9 +101,9 @@ To see the Translator API in action, and review existing code that uses the API:
 1. Click the **Translate** button.
 
    If the model for the specified language pair hasn't been downloaded before, the download starts.
-   
+  
    ![Status indicator showing model downloading progress](./translator-api-images/model-downloading.png)
-   
+  
    If the model download doesn't start, restart Microsoft Edge and try again.
 
    After the model has downloaded, the model starts generating a translation of the text from the source language into the target language.
@@ -198,7 +198,7 @@ const session = await Translator.create({
   sourceLanguage: "en",
   targetLanguage: "es",
   monitor: m => {
-    // Use the monitor object argument to add an listener for the 
+    // Use the monitor object argument to add an listener for the
     // downloadprogress event.
     m.addEventListener("downloadprogress", event => {
       // The event is an object with the loaded and total properties.
@@ -336,7 +336,7 @@ To destroy a session by creating an `AbortController` object, create a `Translat
 // Create an AbortController object.
 const controller = new AbortController();
 
-// Create a Translator session and pass the 
+// Create a Translator session and pass the
 // AbortController object by using the signal option.
 const session = await Translator.create({
   sourceLanguage: "en",
diff --git a/microsoft-edge/web-platform/user-agent-guidance.md b/microsoft-edge/web-platform/user-agent-guidance.md
index 133008da44..4b4f95b988 100644
--- a/microsoft-edge/web-platform/user-agent-guidance.md
+++ b/microsoft-edge/web-platform/user-agent-guidance.md
@@ -30,7 +30,7 @@ You may want to provide different experiences to users based on their browser.
 Mechanisms for browser detection:
 
 | Mechanism | Server-side | Client-side |
-|:--- |:--- |:--- |
+|---|---|---|
 | **User-Agent Client Hints** (recommended) | `Sec-CH-UA` HTTPS header | `navigator.userAgentData` JavaScript method |
 | **User-Agent string** (legacy) | `User-Agent` HTTPS header | `navigator.userAgent` JavaScript method |
 
@@ -78,7 +78,7 @@ Sec-CH-UA-Platform: "Windows"
 The following table shows all available hints request headers with sample values.
 
 | User-Agent request header | Example User-Agent response value |
-|:--- |:--- |
+|---|---|
 | `Sec-CH-UA` | `"Not_A Brand";v="8", "Chromium";v="120", "Microsoft Edge";v="120"` |
 | `Sec-CH-UA-Mobile` | `?0` |
 | `Sec-CH-UA-Full-Version` | `120.0.2210.91` |
@@ -240,7 +240,7 @@ Platform identifiers change based on the operating system, and version numbers i
 On desktop operating systems, Microsoft Edge is commonly identified by the `Edg` token in the User-Agent string.  However, a different token for Microsoft Edge is used on some device platforms, as follows:
 
 | Platform | Identifier token |
-|:--- |:--- |
+|---|---|
 | Desktop (Windows/Mac/Linux) | `Edg` |
 | iPhone/iPad | `EdgiOS` |
 | Android (Mobile/tablet) | `EdgA`|
diff --git a/microsoft-edge/web-platform/web-platform.md b/microsoft-edge/web-platform/web-platform.md
index 6996a10a30..b7fa49f9d5 100644
--- a/microsoft-edge/web-platform/web-platform.md
+++ b/microsoft-edge/web-platform/web-platform.md
@@ -109,6 +109,6 @@ See [View a JSON file or server response with formatting](./json-viewer.md).
 ## See also
 
 * [Web technology for developers](https://developer.mozilla.org/docs/Web) at MDN.
-<!-- 
+<!--
 * [Web Platform](https://developer.chrome.com/docs/web-platform) - Chrome docs.
 -->
diff --git a/microsoft-edge/web-platform/writing-assistance-apis.md b/microsoft-edge/web-platform/writing-assistance-apis.md
index 6d0fc5289c..bbaccf275d 100644
--- a/microsoft-edge/web-platform/writing-assistance-apis.md
+++ b/microsoft-edge/web-platform/writing-assistance-apis.md
@@ -151,7 +151,7 @@ By default, the Writing Assistance APIs use the Phi-4-mini model.  To use Aion-1
 1. In Edge Canary or Edge Dev, open a new tab or window and go to `edge://flags`.
 
 1. In the search box at the top of the page, enter **Enable prerelease on-device language model**.
-  
+ 
 1. In the **Enable prerelease on-device language model** drop-down list, select **Enabled**, and then click the **Restart** button:
 
    ![Flags page showing the prerelease on-device language model flag](./writing-assistance-apis-images/prerelease-model-flag-for-wa-apis.png)
@@ -202,7 +202,7 @@ To use the Writer API or the Rewriter API in Microsoft Edge:
    If your device performance class is **High** or greater, the Writing Assistance APIs are supported on your device.
 
    If your device performance class is **Medium** or **Low**, the Writing Assistance APIs are only supported through the prerelease Aion-1.0-Instruct model, which is available starting with Edge version 150.0.4070.  To test the Aion-1.0-Instruct model, see [Enable Aion-1.0-Instruct for the Writing Assistance APIs](#enable-aion-10-instruct-for-the-writing-assistance-apis), above.
-                                                       
+                                                      
   If you notice issues with these models, please [file a new issue](https://github.com/MicrosoftEdge/MSEdgeExplainers/issues/new?template=writing-assistance-api.md) in the MSEdgeExplainers repo.
 
 
@@ -345,7 +345,7 @@ You can follow the progress of the model download by using the `monitor` option.
 // download.
 const session = await Summarizer.create({
   monitor: m => {
-    // Use the monitor object argument to add an listener for the 
+    // Use the monitor object argument to add an listener for the
     // downloadprogress event.
     m.addEventListener("downloadprogress", event => {
       // The event is an object with the loaded and total properties.
@@ -584,7 +584,7 @@ Example using a `Writer` session:
 // Create an AbortController object.
 const controller = new AbortController();
 
-// Create a Summarizer, Writer, or Rewriter session and pass the 
+// Create a Summarizer, Writer, or Rewriter session and pass the
 // AbortController object by using the signal option.
 const session = await Writer.create({ signal: controller.signal });
 
diff --git a/microsoft-edge/webdriver/capabilities-edge-options.md b/microsoft-edge/webdriver/capabilities-edge-options.md
index 44fc06c7b4..e7e38d8376 100644
--- a/microsoft-edge/webdriver/capabilities-edge-options.md
+++ b/microsoft-edge/webdriver/capabilities-edge-options.md
@@ -47,7 +47,7 @@ For standard capabilities that `EdgeDriver` accepts, see [Selenium documentation
 Most Microsoft Edge-specific capabilities are exposed through the `EdgeOptions` object.  In some languages, the capabilities are implemented by the `EdgeOptions` class.  In other languages, the capabilities are stored under the `ms:edgeOptions` dictionary in `DesiredCapabilities`.
 
 | Capability | Type | Details |
-|:--- |:--- |:--- |
+|---|---|---|
 | `args` | list of strings | List of command-line arguments to pass to the Microsoft Edge process on launch. Arguments with an associated value should be separated by an `=` sign (for example, `['start-maximized', 'user-data-dir=/tmp/temp_profile']`). If you're launching a WebView2 app, then these arguments are passed to your app instead of the underlying Microsoft Edge browser process. To pass arguments to the browser process when launching a WebView2 app, use [webviewOptions.additionalBrowserArguments](#webviewoptions-object) instead. |
 | `binary` | string | Path to the Microsoft Edge binary to use (on macOS, the path should be the actual binary, not just the app.  for example, `/Applications/Microsoft Edge.app/Contents/MacOS/Microsoft Edge`). |
 | `debuggerAddress` | string | An address of a debugger server to which to connect, in the form of `hostname/ip:port`, for example `127.0.0.1:38947`. |
@@ -74,7 +74,7 @@ Most Microsoft Edge-specific capabilities are exposed through the `EdgeOptions`
 The `perfLoggingPrefs` dictionary has the following format. All keys are optional.
 
 | Key | Type | Default value | Details |
-|:--- |:--- |:--- |:--- |
+|---|---|---|---|
 | `bufferUsageReportingInterval` | positive integer | 1000 | The requested number of milliseconds between DevTools trace buffer usage events.  For example, if 1000, then once per second, DevTools reports how full the trace buffer is.  If a report indicates the buffer usage is 100%, a warning is issued. |
 | `enableNetwork` | boolean | true | To collect (or not collect) events from Network domain. |
 | `enablePage` | boolean | true | To collect (or not collect) events from Page domain. |
@@ -87,7 +87,7 @@ The `perfLoggingPrefs` dictionary has the following format. All keys are optiona
 The `webviewOptions` dictionary is used to configure the WebView2 environment when launching a WebView2 app. It has the following format. All keys are optional.
 
 | Key | Type | Default value | Details |
-|:--- |:--- |:--- |:--- |
+|---|---|---|---|
 | `browserExecutableFolder` | string | (empty) | Path to a folder containing a fixed version WebView2 runtime to use. For more information about using a fixed version runtime distribution with WebView2, see [Distribute a WebView2 app and the WebView2 Runtime](../webview2/concepts/distribution.md#the-fixed-version-runtime-distribution-mode). |
 | `userDataFolder` | string | (empty) | Path to the user data folder that WebView2 will use. If `userDataFolder` isn't specified, Microsoft Edge WebDriver will create a temporary user data folder. For more information about managing the user data folder with WebView2, see [Manage the user data folder](../webview2/concepts/user-data-folder.md). |
 | `additionalBrowserArguments` | list of strings |  | List of command-line arguments that WebView2 will pass to the browser process on launch. Arguments with an associated value should be separated by an `=` sign (for example, `['start-maximized', 'log-level=0']`). |
@@ -99,6 +99,6 @@ The `webviewOptions` dictionary is used to configure the WebView2 environment wh
 The following list contains all of the Microsoft Edge-specific capabilities that `EdgeDriver` returns when you create a new session.
 
 | Capability | Type | Details |
-|:--- |:--- |:--- |
+|---|---|---|
 | `msedge.msedgedriverVersion` | string | The version of EdgeDriver. |
 | `msedge.userDataDir` | string | The path to the user data folder used by the Microsoft Edge instance. |
diff --git a/microsoft-edge/webdriver/ie-mode.md b/microsoft-edge/webdriver/ie-mode.md
index 9014a1bb1f..861730b36a 100644
--- a/microsoft-edge/webdriver/ie-mode.md
+++ b/microsoft-edge/webdriver/ie-mode.md
@@ -120,11 +120,11 @@ import org.openqa.selenium.ie.InternetExplorerDriver;
 import org.openqa.selenium.ie.InternetExplorerOptions;
 
 public class IEDriverSample {
-    public static void main(String[] args) {        
+    public static void main(String[] args) {       
         InternetExplorerOptions ieOptions = new InternetExplorerOptions();
         ieOptions.attachToEdgeChrome();
         ieOptions.withEdgeExecutablePath("C:\\Program Files (x86)\\Microsoft\\Edge\\Application\\msedge.exe");
-        
+       
         WebDriver driver = new InternetExplorerDriver(ieOptions);
 
         driver.get("http://www.bing.com");
@@ -317,7 +317,7 @@ After the `click` method is called on a button that opens a new window, the test
 
 ```java
 int initialHandleCount = driver.getWindowHandles().size();
-driver.findElement(By.id("<Id of the button that will open a new window>")).click();        
+driver.findElement(By.id("<Id of the button that will open a new window>")).click();       
 Set<String> newHandles = driver.getWindowHandles();
 while (newHandles.size() == initialHandleCount) {
     newHandles = driver.getWindowHandles();
diff --git a/microsoft-edge/webview2/concepts/basic-authentication.md b/microsoft-edge/webview2/concepts/basic-authentication.md
index af75e4c25e..550c216a7d 100644
--- a/microsoft-edge/webview2/concepts/basic-authentication.md
+++ b/microsoft-edge/webview2/concepts/basic-authentication.md
@@ -98,7 +98,7 @@ later, check:  Teams > Team > channel > Files > dir > file name -->
 
 1. The WebView2 control renders the error page that's returned by the HTTP server.  The rendering occurs between the `ContentLoading` event and `DOMContentLoaded` event.
    <!-- "10. Renders the error page (DOMContentLoaded, NavigationCompleted)" -->
-   
+  
 1. The HTTP server might accept the authentication credentials and return the requested document.
    <!-- "11. Accepts authentication and returns the requested document" -->
 
@@ -121,10 +121,10 @@ For more realistic code, see the subsequent section.
 ##### [C#](#tab/csharp)
 
 ```csharp
-// Prerequisite: Before using this code, make sure you read the section "Use HTTPS 
+// Prerequisite: Before using this code, make sure you read the section "Use HTTPS
 // for sending credentials" in this article.
     webView.CoreWebView2.BasicAuthenticationRequested += delegate (
-       object sender, 
+       object sender,
        CoreWebView2BasicAuthenticationRequestedEventArgs args)
     {
         args.Response.UserName = "user";
@@ -140,7 +140,7 @@ For more realistic code, see the subsequent section.
 ##### [C++](#tab/cpp)
 
 ```cpp
-// Prerequisite: Before using this code, make sure you read the section "Use HTTPS 
+// Prerequisite: Before using this code, make sure you read the section "Use HTTPS
 // for sending credentials" in this article.
 if (auto webView10 = m_webView.try_query<ICoreWebView2_10>())
 {
@@ -191,10 +191,10 @@ This example builds upon the above sample, by adding the following features:
 ##### [C#](#tab/csharp)
 
 ```csharp
-// Prerequisite: Before using this code, make sure you read the section "Use HTTPS 
+// Prerequisite: Before using this code, make sure you read the section "Use HTTPS
 // for sending credentials" in this article.
 webView.CoreWebView2.BasicAuthenticationRequested += delegate (
-    object sender, 
+    object sender,
     CoreWebView2BasicAuthenticationRequestedEventArgs args)
 {
     // We need to show UI asynchronously so we obtain a deferral.
@@ -265,7 +265,7 @@ webView.CoreWebView2.BasicAuthenticationRequested += delegate (
 ##### [C++](#tab/cpp)
 
 ```cpp
-// Prerequisite: Before using this code, make sure you read the section "Use HTTPS 
+// Prerequisite: Before using this code, make sure you read the section "Use HTTPS
 // for sending credentials" in this article.
 if (auto webView10 = m_webView.try_query<ICoreWebView2_10>())
 {
@@ -312,11 +312,11 @@ if (auto webView10 = m_webView.try_query<ICoreWebView2_10>())
                         // as it may have important site specific information for the
                         // end user to provide the correct username and password.
                         prompt += L"\r\nChallenge: ";
-                        prompt += challenge.get(); 
+                        prompt += challenge.get();
 
                         // Use an app or UI framework method to get input from the end user.
                         TextInputDialog dialog(
-                            mainWindowHwnd, 
+                            mainWindowHwnd,
                             L"Authentication Request",
                             L"User name and password",
                             prompt.c_str(),
diff --git a/microsoft-edge/webview2/concepts/browser-features.md b/microsoft-edge/webview2/concepts/browser-features.md
index 583b26c616..39576fc66a 100644
--- a/microsoft-edge/webview2/concepts/browser-features.md
+++ b/microsoft-edge/webview2/concepts/browser-features.md
@@ -75,7 +75,7 @@ The following table displays the WebView2 features that differ from the Microsof
 The following WebView2 platform features are currently unavailable:
 
 | Feature | Details |
-|:--- | :--- |
+|---|---|
 | Push Notifications | This feature isn't implemented in WebView2. |
 | Web Payment API | This feature is turned off. |
 | Periodic Background Sync | Periodic Background Sync events will never trigger. |
@@ -128,7 +128,7 @@ To avoid such changes to your keyboard shortcuts, you can set `AreBrowserAcceler
 The following shortcuts are always turned off in WebView2, or are effectively turned off.  An asterisk (`*`) indicates that the shortcut isn't turned off, but the feature that it accesses is turned off, or the feature doesn't apply to WebView2.
 
 | Action | Shortcut |
-|:--- |:--- |
+|---|---|
 | Add to Favorites | **Ctrl+D** |
 | Add All Tabs to Favorites | **Ctrl+Shift+D** |
 | Focus Location | **Ctrl+L**, **Alt+D** |
@@ -175,7 +175,7 @@ The following shortcuts are always turned off in WebView2, or are effectively tu
 The following keyboard shortcuts are always turned off, except in windows that display when the `NewWindowRequested` event isn't handled:
 
 | Action | Shortcut |
-|:--- |:--- |
+|---|---|
 | Close Tab | **Ctrl+W**, **Ctrl+F4** |
 | Close Window | **Ctrl+Shift+W** |
 | Fullscreen | **F11** |
@@ -187,7 +187,7 @@ The following keyboard shortcuts are always turned off, except in windows that d
 If you set `AreBrowserAcceleratorKeysEnabled` to `FALSE`, the following additional keyboard shortcuts are turned off:
 
 | Action | Shortcut |
-|:--- |:--- |
+|---|---|
 | Stop | **Esc** |
 | Find on Page | **Ctrl+F** |
 | Find Next | **Ctrl+G** |
diff --git a/microsoft-edge/webview2/concepts/clear-browsing-data.md b/microsoft-edge/webview2/concepts/clear-browsing-data.md
index 6c1396b81c..b805632961 100644
--- a/microsoft-edge/webview2/concepts/clear-browsing-data.md
+++ b/microsoft-edge/webview2/concepts/clear-browsing-data.md
@@ -132,7 +132,7 @@ private void ClearAutofillData()
         // Offset the current time by one hour to clear the browsing data from the
         // last hour.
         CoreWebView2BrowsingDataKinds dataKinds = (CoreWebView2BrowsingDataKinds)
-                                 (CoreWebView2BrowsingDataKinds.GeneralAutofill | 
+                                 (CoreWebView2BrowsingDataKinds.GeneralAutofill |
                                   CoreWebView2BrowsingDataKinds.PasswordAutosave);
         await profile.ClearBrowsingDataAsync(dataKinds, startTime, endTime);
     }
@@ -164,10 +164,10 @@ void ClearAutofillData()
         double endTime = (double)std::time(nullptr);
         double startTime = endTime - 3600;
         // Get the current time and offset the current time by 3600 seconds to clear
-        // the data from the start time (one hour ago), until the end time (present 
+        // the data from the start time (one hour ago), until the end time (present
         // time).
         // This clears the data for the last hour.
-        COREWEBVIEW2_BROWSING_DATA_KINDS dataKinds = 
+        COREWEBVIEW2_BROWSING_DATA_KINDS dataKinds =
             (COREWEBVIEW2_BROWSING_DATA_KINDS)
             (COREWEBVIEW2_BROWSING_DATA_KINDS_GENERAL_AUTOFILL |
             COREWEBVIEW2_BROWSING_DATA_KINDS_PASSWORD_AUTOSAVE);
diff --git a/microsoft-edge/webview2/concepts/developer-guide.md b/microsoft-edge/webview2/concepts/developer-guide.md
index 7cf8529a92..7c823b49d4 100644
--- a/microsoft-edge/webview2/concepts/developer-guide.md
+++ b/microsoft-edge/webview2/concepts/developer-guide.md
@@ -40,7 +40,7 @@ See [Detect if a WebView2 Runtime is already installed](./distribution.md#detect
 <!-- ------------------------------ -->
 #### Handle updates of the WebView2 Runtime
 
-When using the Evergreen WebView2 Runtime, handle Evergreen WebView2 Runtime updates.  Updates of the Evergreen WebView2 Runtime are automatically downloaded, but a running WebView2 app will continue using its current version of the WebView2 Runtime, potentially missing security updates.  To adopt the new version, an app must release all references to previous WebView2 objects or restart.  Implementing a `NewBrowserVersionAvailable` event handler can prompt users to restart the app for updates, with a recommendation to save user state before exiting for a seamless transition. 
+When using the Evergreen WebView2 Runtime, handle Evergreen WebView2 Runtime updates.  Updates of the Evergreen WebView2 Runtime are automatically downloaded, but a running WebView2 app will continue using its current version of the WebView2 Runtime, potentially missing security updates.  To adopt the new version, an app must release all references to previous WebView2 objects or restart.  Implementing a `NewBrowserVersionAvailable` event handler can prompt users to restart the app for updates, with a recommendation to save user state before exiting for a seamless transition.
 
 See [Handle Evergreen WebView2 Runtime updates](./distribution.md#handle-evergreen-webview2-runtime-updates) in _Distribute your app and the WebView2 Runtime_.
 
@@ -58,9 +58,9 @@ Follow the guidance in [Prerelease testing using preview channels](../how-to/pre
 <!-- ------------------------------ -->
 #### Use feature detection for newer APIs
 
-When using the Evergreen WebView2 Runtime, use feature detection to test whether the installed Runtime supports recently added APIs.  To run a WebView2 app that was developed with a particular version of the Webview2 SDK, the client must have a compatible version of the WebView2 Runtime installed. 
+When using the Evergreen WebView2 Runtime, use feature detection to test whether the installed Runtime supports recently added APIs.  To run a WebView2 app that was developed with a particular version of the Webview2 SDK, the client must have a compatible version of the WebView2 Runtime installed.
 
-When using the Evergreen WebView2 Runtime, there are some scenarios where the runtime on a client hasn't been automatically updated to the latest version.  Additionally, some group policies pause updating of the runtime.  As a result, when you push an update to your WebView2 app, the app might not work if it tries to call newer APIs that aren't available in the client's installed runtime.  Therefore, you should use feature detection to make sure that the newer APIs that are used by your WebView2 app are supported by the WebView2 Runtime that's installed on the client. 
+When using the Evergreen WebView2 Runtime, there are some scenarios where the runtime on a client hasn't been automatically updated to the latest version.  Additionally, some group policies pause updating of the runtime.  As a result, when you push an update to your WebView2 app, the app might not work if it tries to call newer APIs that aren't available in the client's installed runtime.  Therefore, you should use feature detection to make sure that the newer APIs that are used by your WebView2 app are supported by the WebView2 Runtime that's installed on the client.
 
 See [Feature-detecting to test whether the installed Runtime supports recently added APIs](./versioning.md#feature-detecting-to-test-whether-the-installed-runtime-supports-recently-added-apis) in _Prerelease and Release SDKs for WebView2_.
 
diff --git a/microsoft-edge/webview2/concepts/distribution.md b/microsoft-edge/webview2/concepts/distribution.md
index e92a47e46a..908b47b148 100644
--- a/microsoft-edge/webview2/concepts/distribution.md
+++ b/microsoft-edge/webview2/concepts/distribution.md
@@ -199,7 +199,7 @@ If you have an offline deployment scenario, where app deployment has to work ent
 
 New versions of the Evergreen WebView2 Runtime are automatically downloaded to the client.  The client uses the new version of the WebView2 Runtime when your WebView2 app is restarted.  However, if your app runs continuously, your app will continue to use the previous version of the WebView2 Runtime.  This has security implications, because the previous version of the WebView2 Runtime might have security vulnerabilities that are fixed in the new version.  You should consider whether it is important for your app to adopt the latest version of the WebView2 Runtime as soon as possible, based on your app's threat model.  For example, if your WebView2 app accesses third-party content, that content should be considered untrusted, so your app would need to use the latest version of the WebView2 Runtime.
 
-To use the new version of the WebView2 Runtime, you need to either release all references to the previous WebView2 environment objects, or restart your app.  The next time your app creates a new WebView2 environment, the app will use the new version of the WebView2 Runtime.  To accomplish this, you can have an event handler for the `NewBrowserVersionAvailable` event, to have your app automatically notify the user to restart the app.  If your app handles restarting the app, consider saving the user state before the WebView2 app exits. 
+To use the new version of the WebView2 Runtime, you need to either release all references to the previous WebView2 environment objects, or restart your app.  The next time your app creates a new WebView2 environment, the app will use the new version of the WebView2 Runtime.  To accomplish this, you can have an event handler for the `NewBrowserVersionAvailable` event, to have your app automatically notify the user to restart the app.  If your app handles restarting the app, consider saving the user state before the WebView2 app exits.
 
 ##### [.NET/C#](#tab/dotnetcsharp)
 
@@ -267,7 +267,7 @@ To use the Fixed Version distribution mode:
       * Alternatively, use `EnsureCoreWebView2Async` ([WPF](/dotnet/api/microsoft.web.webview2.wpf.webview2.ensurecorewebview2async)/[WinForms](/dotnet/api/microsoft.web.webview2.winforms.webview2.ensurecorewebview2async)) to specify the environment.  Use the `browserExecutableFolder` parameter in [CoreWebView2Environment.CreateAsync](/dotnet/api/microsoft.web.webview2.core.corewebview2environment.createasync) to indicate the path to the Fixed Version binaries.
 
    * For WinUI, make sure the app has access to the folder by specifying the installed location and setting the environment variable for runtime path.  One way to do this is by adding the following C# code to your app:
-        
+       
       ```csharp
       StorageFolder localFolder = Windows.ApplicationModel.Package.Current.InstalledLocation;
       String fixedPath = Path.Combine(localFolder.Path, "FixedRuntime\\(version number)");
@@ -275,7 +275,7 @@ To use the Fixed Version distribution mode:
       Debug.WriteLine($"FixedRuntime path [{fixedPath}]");
       Environment.SetEnvironmentVariable("WEBVIEW2_BROWSER_EXECUTABLE_FOLDER", fixedPath);
       ```
-   
+  
 1. Package and ship the Fixed Version binaries with your app.  Update the binaries as appropriate.
 
    * For WinUI, this might include opening the project file (`.csproj`) in a code editor, and then add the following code within the project tags:
diff --git a/microsoft-edge/webview2/concepts/enterprise.md b/microsoft-edge/webview2/concepts/enterprise.md
index 4f33d5e009..72248a2e4f 100644
--- a/microsoft-edge/webview2/concepts/enterprise.md
+++ b/microsoft-edge/webview2/concepts/enterprise.md
@@ -77,7 +77,7 @@ See:
 <!-- ------------------------------ -->
 #### Browser policies
 
-[Microsoft Edge - Policies](/deployedge/microsoft-edge-policies) doesn't apply to WebView2 applications.  This is by design, because apps and browsers have different use cases, and IT admins might not be aware of what applications use WebView2.  
+[Microsoft Edge - Policies](/deployedge/microsoft-edge-policies) doesn't apply to WebView2 applications.  This is by design, because apps and browsers have different use cases, and IT admins might not be aware of what applications use WebView2. 
 
 Applying browser policies on WebView2 would have unintended consequences.  For example, IT admins can block JavaScript in the browser, and that would break WebView2 apps that use JavaScript.  To prevent that, browser policies are separate from WebView2 policies.
 
diff --git a/microsoft-edge/webview2/concepts/environment-controller-core.md b/microsoft-edge/webview2/concepts/environment-controller-core.md
index 90f4e8b324..5e96c497ab 100644
--- a/microsoft-edge/webview2/concepts/environment-controller-core.md
+++ b/microsoft-edge/webview2/concepts/environment-controller-core.md
@@ -78,7 +78,7 @@ From the `CoreWebView2Environment`, you create `CoreWebView2Controller` and `Cor
 <!-- ====================================================================== -->
 ## UI framework-specific WebView2 element class such as WPF, WinForms, or WinUI WebView2 classes
 
-It's different if you are using a UI framework-specific WebView2 element class such as the WPF, WinForms, or WinUI WebView2 classes. 
+It's different if you are using a UI framework-specific WebView2 element class such as the WPF, WinForms, or WinUI WebView2 classes.
 
 Then, the WebView2 class can optionally take a `CoreWebView2Environment` to use; otherwise, it creates a default `CoreWebView2Environment`.  Internally, the WebView2 class creates its `CoreWebView2Controller` and `CoreWebView2` from the `CoreWebView2Environment`.
 
diff --git a/microsoft-edge/webview2/concepts/evergreen-vs-fixed-version.md b/microsoft-edge/webview2/concepts/evergreen-vs-fixed-version.md
index 5a2eb6b6d2..0be41e96c8 100644
--- a/microsoft-edge/webview2/concepts/evergreen-vs-fixed-version.md
+++ b/microsoft-edge/webview2/concepts/evergreen-vs-fixed-version.md
@@ -110,5 +110,5 @@ The Evergreen distribution mode is recommended for most apps.
 
 External:
 * [Delivering Microsoft Edge WebView2 Runtime to managed Windows 10 devices](https://blogs.windows.com/msedgedev/2022/12/14/delivering-microsoft-edge-webview2-runtime-to-managed-windows-10-devices/)
-* [Download the WebView2 Runtime](https://developer.microsoft.com/microsoft-edge/webview2#download-the-webview2-runtime) section of the **Microsoft Edge WebView2** page 
+* [Download the WebView2 Runtime](https://developer.microsoft.com/microsoft-edge/webview2#download-the-webview2-runtime) section of the **Microsoft Edge WebView2** page
 * [Microsoft Edge release schedule](/deployedge/microsoft-edge-release-schedule)<!-- link not in article body -->
diff --git a/microsoft-edge/webview2/concepts/frames.md b/microsoft-edge/webview2/concepts/frames.md
index 59472e84ab..bf2f50e88f 100644
--- a/microsoft-edge/webview2/concepts/frames.md
+++ b/microsoft-edge/webview2/concepts/frames.md
@@ -10,7 +10,7 @@ ms.date: 11/16/2022
 ---
 # Using frames in WebView2 apps
 
-Frames allow you to embed other webpages into your own webpage.  A _frame_ is a sub-page or area within a webpage, like a webpage within a webpage.  
+Frames allow you to embed other webpages into your own webpage.  A _frame_ is a sub-page or area within a webpage, like a webpage within a webpage. 
 
 An iframe is one type of frame.  Other types of frames are `frameset`, `portal`, `embed`, `fencedFrame`, and `object`.  The main WebView2 type for frames is `CoreWebView2Frame`, which is currently enabled for top-level iframes.  Support for other types of frames is planned.
 
@@ -253,7 +253,7 @@ See also:
 * [Web messaging](./overview-features-apis.md#web-messaging) in _Overview of WebView2 APIs_.
 
 
-<!-- 
+<!--
 #### JavaScript API Reference
 
 TODO: link when exists.
@@ -338,7 +338,7 @@ See the latest prerelease APIs.  The following links contain `1.0.1466-prereleas
 * [ICoreWebView2Experimental16.RemoveWebResourceRequestedFilterWithRequestSourceKinds method](/microsoft-edge/webview2/reference/win32/icorewebview2experimental16#removewebresourcerequestedfilterwithrequestsourcekinds)
 * [ICoreWebView2ExperimentalWebResourceRequestedEventArgs interface](/microsoft-edge/webview2/reference/win32/icorewebview2experimentalwebresourcerequestedeventargs)
 
-<!-- 
+<!--
 todo: at next SDK release early Dec. 2022, update enum link when it changes to a Globals page section/anchor eg:
 https://learn.microsoft.com/microsoft-edge/webview2/reference/win32/webview2experimental-idl?view=webview2-1.0.1418.22
 https://learn.microsoft.com/microsoft-edge/webview2/reference/win32/webview2-idl?view=webview2-1.0.1418.22
@@ -388,7 +388,7 @@ This sample code is condensed from [MainWindow.xaml.cs](https://github.com/Micro
 ```csharp
         void DOMContentLoadedCmdExecuted(object target, ExecutedRoutedEventArgs e)
         {
-            // Subscribe to the FrameCreated event to obtain the frame object when 
+            // Subscribe to the FrameCreated event to obtain the frame object when
             // it's created.
             webView.CoreWebView2.FrameCreated += WebView_FrameCreatedDOMContentLoaded;
             webView.NavigateToString(@"<!DOCTYPE html>" +
@@ -399,8 +399,8 @@ This sample code is condensed from [MainWindow.xaml.cs](https://github.com/Micro
 
         void WebView_FrameCreatedDOMContentLoaded(object sender, CoreWebView2FrameCreatedEventArgs args)
         {
-            // In order for ExecuteScriptAsync to successfully run inside the iframe, 
-            // subscribe to the ContentLoading or DOMContentLoaded event.  Once these 
+            // In order for ExecuteScriptAsync to successfully run inside the iframe,
+            // subscribe to the ContentLoading or DOMContentLoaded event.  Once these
             // events are raised, you can call ExecuteScriptAsync.
             args.Frame.DOMContentLoaded += (frameSender, DOMContentLoadedArgs) =>
             {
diff --git a/microsoft-edge/webview2/concepts/measures.md b/microsoft-edge/webview2/concepts/measures.md
index aa0523b020..4eaa530c16 100644
--- a/microsoft-edge/webview2/concepts/measures.md
+++ b/microsoft-edge/webview2/concepts/measures.md
@@ -177,7 +177,7 @@ See:
 <!-- ====================================================================== -->
 ## Preserve Low Integrity Level (LowIL) on Runtime folders
 
-Don't modify the Low Integrity Level (LowIL) settings on WebView2 Runtime folders.  WebView2 runs renderer processes at a Low Integrity Level, to limit their access to system resources. 
+Don't modify the Low Integrity Level (LowIL) settings on WebView2 Runtime folders.  WebView2 runs renderer processes at a Low Integrity Level, to limit their access to system resources.
 
 A Low Integrity Level process (LowIL) must be able to Read and Execute the WebView2 Runtime binaries.
 
@@ -410,7 +410,7 @@ Symptoms:
 
 Align Transport Layer Security (TLS) inspection and proxy configuration with Chromium-based browser requirements.
 
-If your environment uses TLS inspection, ensure that the inspection certificates are trusted by the operating system's certificate store. 
+If your environment uses TLS inspection, ensure that the inspection certificates are trusted by the operating system's certificate store.
 
 
 <!-- ------------------------------ -->
@@ -498,7 +498,7 @@ The System32-based WebView2 Runtime's default Access Control Lists (ACLs) must b
 ## Don't apply Edge browser–only group policies
 
 Most group policies that apply to Microsoft Edge don't affect WebView2, and unsupported policies can break WebView2 features.
-    
+   
 Don't use Microsoft Edge–only group policies to affect WebView2.
 
 
diff --git a/microsoft-edge/webview2/concepts/performance.md b/microsoft-edge/webview2/concepts/performance.md
index 8064122f37..1882af25cd 100644
--- a/microsoft-edge/webview2/concepts/performance.md
+++ b/microsoft-edge/webview2/concepts/performance.md
@@ -323,7 +323,7 @@ See also:
 <!-- ------------------------------ -->
 #### Manage process priority
 
-* If the app has a heavy native workload, assign thread priorities carefully, to avoid starving WebView2 threads.  WebView2 creates separate renderer processes.  
+* If the app has a heavy native workload, assign thread priorities carefully, to avoid starving WebView2 threads.  WebView2 creates separate renderer processes. 
 
 See also:
 * [Process model for WebView2 apps](./process-model.md)
diff --git a/microsoft-edge/webview2/concepts/user-data-folder.md b/microsoft-edge/webview2/concepts/user-data-folder.md
index 671bdd745f..528cb8d27f 100644
--- a/microsoft-edge/webview2/concepts/user-data-folder.md
+++ b/microsoft-edge/webview2/concepts/user-data-folder.md
@@ -143,11 +143,11 @@ However, your host app might not be able to use that location to write data to.
 
 **Cleanup:**
 
-At the end of the session, ClickOnce automatically cleans up.  
+At the end of the session, ClickOnce automatically cleans up. 
 
 **Packaging:**
 
-ClickOnce is a deployment method for lightweight transient apps; it's a hybrid model.  It's possible to persist a ClickOnce app, but that's not standard, typical practice.  
+ClickOnce is a deployment method for lightweight transient apps; it's a hybrid model.  It's possible to persist a ClickOnce app, but that's not standard, typical practice. 
 
 **What type of platform app a ClickOnce app wraps:**
 
@@ -251,8 +251,8 @@ Use the [CoreWebView2Environment.CreateAsync method](/dotnet/api/microsoft.web.w
 ```csharp
 string UserDataFolder;
 UserDataFolder = "C:\\MyAppUserDataFolder";
-_task = CoreWebView2Environment.CreateAsync(BrowserExecutableFolder, 
-                                            UserDataFolder, 
+_task = CoreWebView2Environment.CreateAsync(BrowserExecutableFolder,
+                                            UserDataFolder,
                                             new CoreWebView2EnvironmentOptions(null, Language, null));
 ```
 
@@ -285,8 +285,8 @@ You should specify the same folder where all other app data is stored.
 ```csharp
 string UserDataFolder;
 UserDataFolder = "C:\\MyAppUserDataFolder";
-_task = CoreWebView2Environment.CreateAsync(BrowserExecutableFolder, 
-                                            UserDataFolder, 
+_task = CoreWebView2Environment.CreateAsync(BrowserExecutableFolder,
+                                            UserDataFolder,
                                             new CoreWebView2EnvironmentOptions(null, Language, null));
 ```
 
@@ -321,7 +321,7 @@ try {
     // dir (that is, /Program Files/) is protected.
     var userDataFolder = Path.Combine(
       Environment.GetFolderPath(Environment.SpecialFolder.LocalApplicationData),
-      "YOURAPPNAME", "WebView2"); // You need to decide if you want to keep this 
+      "YOURAPPNAME", "WebView2"); // You need to decide if you want to keep this
       // folder during uninstall, or add uninstall code that removes this folder.
     Log.Info($"WebView2 user data folder: {userDataFolder}");
     var env = await CoreWebView2Environment.CreateWithOptionsAsync(
@@ -479,12 +479,12 @@ If multiple users use your app repeatedly, you should create a new user data fol
 
 The WebView2 control creates a new UDF for each new user.  The WebView2 control creates one UDF per session.  If there are multiple WebView2 sessions, the WebView2 control creates multiple UDFs.  Usually if the host app has more than one WebView2 control instance, the host app should point all instances of WebView2 to the same UDF.
 
-Each host app that has a WebView2 control instance will have its own UDF.  Your host app can have each UDF point to the same place.  
+Each host app that has a WebView2 control instance will have its own UDF.  Your host app can have each UDF point to the same place. 
 
 If your host app is for multiple users, you should probably create one UDF per user.  If your app was installed per-user, this is how it works.
 <!-- in a more detailed article, cover this: how does your host app cause WebView2 to create one UDF per user vs. causing WebView2 to create one UDF per X or Y or Z instead? -->
 
-If you launch two copies of your host app, they will use the same UDF.  
+If you launch two copies of your host app, they will use the same UDF. 
 <!-- cover this in advanced whitepaper article -->
 
 * For Win32 host apps, the UDF is not automatically removed.
diff --git a/microsoft-edge/webview2/concepts/versioning.md b/microsoft-edge/webview2/concepts/versioning.md
index d5d7bd4646..45b22e1d06 100644
--- a/microsoft-edge/webview2/concepts/versioning.md
+++ b/microsoft-edge/webview2/concepts/versioning.md
@@ -229,6 +229,6 @@ Downloads:
 
 GitHub:
 * [WebView2Feedback](https://github.com/MicrosoftEdge/WebViewFeedback) repo.
-<!-- 
+<!--
 * [AppWindow.cpp](https://github.com/MicrosoftEdge/WebView2Samples/blob/8ec7de9d3e80a942bc7025cffad98eee75e11e64/SampleApps/WebView2APISample/AppWindow.cpp#L622)
 -->
diff --git a/microsoft-edge/webview2/concepts/win32-api-conventions.md b/microsoft-edge/webview2/concepts/win32-api-conventions.md
index 0119f2c5d6..81ed87c1eb 100644
--- a/microsoft-edge/webview2/concepts/win32-api-conventions.md
+++ b/microsoft-edge/webview2/concepts/win32-api-conventions.md
@@ -81,7 +81,7 @@ Events in the WebView2 Win32 C++ API use the `add_EventName` and `remove_EventNa
 <!-- ------------------------------ -->
 #### Event handler delegate interfaces
 
-Event handler delegate interfaces work similarly to the async method completed handler delegate interfaces.  You implement the event handler delegate interface and `CoreWebView2` sends a callback whenever the event runs.  
+Event handler delegate interfaces work similarly to the async method completed handler delegate interfaces.  You implement the event handler delegate interface and `CoreWebView2` sends a callback whenever the event runs. 
 
 Every event handler delegate interface has a single `Invoke` method that has a sender parameter followed by an event args parameter.  The sender is the instance of the object on which you subscribed for events.  The event args parameter is an interface that contains information about the currently firing event.
 
diff --git a/microsoft-edge/webview2/concepts/working-with-local-content.md b/microsoft-edge/webview2/concepts/working-with-local-content.md
index c8dc5b7dab..7cc05dd028 100644
--- a/microsoft-edge/webview2/concepts/working-with-local-content.md
+++ b/microsoft-edge/webview2/concepts/working-with-local-content.md
@@ -10,13 +10,57 @@ ms.date: 02/21/2025
 ---
 # Using local content in WebView2 apps
 
-In addition to loading remote content, content can also be loaded locally into WebView2.  There are several approaches that can be used to load local content into a WebView2 control, including: 
+In addition to loading remote content, content can also be loaded locally into WebView2.  There are several approaches that can be used to load local content into a WebView2 control, including:
 * Navigating to a file URL.
 * Navigating to an HTML string.
 * Virtual host name mapping.
 * Handling the `WebResourceRequested` event.
 
-These approaches are described below.
+**Detailed contents:**
+* [Selecting an approach](#selecting-an-approach)
+* [Loading local content by navigating to a file URL](#loading-local-content-by-navigating-to-a-file-url)
+   * [Considerations for loading local content by navigating to a file URL](#considerations-for-loading-local-content-by-navigating-to-a-file-url)
+      * [Cross-origin resources](#cross-origin-resources)
+      * [Origin-based DOM APIs](#origin-based-dom-apis)
+      * [DOM APIs requiring secure context](#dom-apis-requiring-secure-context)
+      * [Dynamic content](#dynamic-content)
+      * [Additional web resources](#additional-web-resources)
+      * [Additional web resources resolved in WebView2 process](#additional-web-resources-resolved-in-webview2-process)
+   * [APIs for loading local content by navigating to a file URL](#apis-for-loading-local-content-by-navigating-to-a-file-url)
+   * [Example of a file URL](#example-of-a-file-url)
+   * [Example of navigating to a file URL](#example-of-navigating-to-a-file-url)
+* [Loading local content by navigating to an HTML string](#loading-local-content-by-navigating-to-an-html-string)
+   * [Considerations for loading local content by navigating to an HTML string](#considerations-for-loading-local-content-by-navigating-to-an-html-string)
+      * [Origin-based DOM APIs](#origin-based-dom-apis-1)
+      * [DOM APIs requiring secure context](#dom-apis-requiring-secure-context-1)
+      * [Dynamic content](#dynamic-content-1)
+      * [Additional web resources](#additional-web-resources-1)
+      * [Additional web resources resolved in WebView2 process](#additional-web-resources-resolved-in-webview2-process-1)
+   * [APIs for loading local content by navigating to an HTML string](#apis-for-loading-local-content-by-navigating-to-an-html-string)
+   * [Example string representation of a webpage](#example-string-representation-of-a-webpage)
+   * [Example of navigating to an HTML string](#example-of-navigating-to-an-html-string)
+* [Loading local content by using virtual host name mapping](#loading-local-content-by-using-virtual-host-name-mapping)
+   * [Considerations for loading local content by using virtual host name mapping](#considerations-for-loading-local-content-by-using-virtual-host-name-mapping)
+      * [Origin-based DOM APIs](#origin-based-dom-apis-2)
+      * [DOM APIs requiring secure context](#dom-apis-requiring-secure-context-2)
+      * [Dynamic content](#dynamic-content-2)
+      * [Additional web resources](#additional-web-resources-2)
+      * [Additional web resources resolved in WebView2 process](#additional-web-resources-resolved-in-webview2-process-2)
+      * [Source maps with virtual host name mapping](#source-maps-with-virtual-host-name-mapping)
+   * [APIs for loading local content by using virtual host name mapping](#apis-for-loading-local-content-by-using-virtual-host-name-mapping)
+   * [Example of virtual host name mapping](#example-of-virtual-host-name-mapping)
+* [Loading local content by handling the WebResourceRequested event](#loading-local-content-by-handling-the-webresourcerequested-event)
+   * [Custom scheme registration](#custom-scheme-registration)
+   * [Considerations for loading local content by handling the WebResourceRequested event](#considerations-for-loading-local-content-by-handling-the-webresourcerequested-event)
+      * [Origin-based DOM APIs](#origin-based-dom-apis-3)
+      * [DOM APIs requiring secure context](#dom-apis-requiring-secure-context-3)
+      * [Dynamic content](#dynamic-content-3)
+      * [Additional web resources](#additional-web-resources-3)
+      * [Additional web resources resolved in WebView2 process](#additional-web-resources-resolved-in-webview2-process-3)
+      * [Source maps with the WebResourceRequested event](#source-maps-with-the-webresourcerequested-event)
+   * [APIs for loading local content by handling the WebResourceRequested event](#apis-for-loading-local-content-by-handling-the-webresourcerequested-event)
+   * [Example of handling the WebResourceRequested event](#example-of-handling-the-webresourcerequested-event)
+* [See also](#see-also)
 
 
 <!-- ====================================================================== -->
@@ -25,15 +69,14 @@ These approaches are described below.
 The various ways of loading local content into a WebView2 control support the following scenarios:
 
 | Scenario | By navigating to a file URL | By navigating to an HTML string | By using virtual host name mapping | By using `WebResourceRequested` |
-| --- |:---:|:---:|:---:|:---:|
+|---|:---:|:---:|:---:|:---:|
 | Origin-based DOM APIs | ✔️ | ❌ | ✔️ | ✔️ |
 | DOM APIs requiring secure context | ❌ | ❌ | ✔️ | ✔️ |
 | Dynamic content | ❌ | ✔️ | ❌ | ✔️ |
 | Additional web resources | ✔️ | ❌ | ✔️  | ✔️ |
 | Additional web resources resolved in WebView2 process | ✔️ | ❌ | ✔️ | ❌ |
 
-
-These scenarios are described in more detail below.
+These scenarios are described below.
 
 
 <!-- ====================================================================== -->
@@ -254,26 +297,26 @@ Loading local content by using the `NavigateToString` method doesn't make it pos
 The following is the string representation of the **Demo To Do** webpage.  The listing below has added line wrapping for readability.  In practice, these lines are concatenated into a single long line:
 
 ```html
-`<html lang="en"><head>\n    
-<meta charset="UTF-8">\n    
-<meta name="viewport" content="width=device-width, initial-scale=1.0">\n    
-<title>TODO app</title>\n    
-<link rel="stylesheet" href="styles/light-theme.css" media="(prefers-color-scheme: light), (prefers-color-scheme: no-preference)">\n    
-<link rel="stylesheet" href="styles/dark-theme.css" media="(prefers-color-scheme: dark)">\n    
-<link rel="stylesheet" href="styles/base.css">\n    
-<link rel="stylesheet" href="styles/to-do-styles.css">\n    
+`<html lang="en"><head>\n   
+<meta charset="UTF-8">\n   
+<meta name="viewport" content="width=device-width, initial-scale=1.0">\n   
+<title>TODO app</title>\n   
+<link rel="stylesheet" href="styles/light-theme.css" media="(prefers-color-scheme: light), (prefers-color-scheme: no-preference)">\n   
+<link rel="stylesheet" href="styles/dark-theme.css" media="(prefers-color-scheme: dark)">\n   
+<link rel="stylesheet" href="styles/base.css">\n   
+<link rel="stylesheet" href="styles/to-do-styles.css">\n   
 <link rel="icon" href="data:image/svg+xml,<svg xmlns=%22http://www.w3.org/2000/svg%22 viewBox=%220 0 100 100%22><text y=%22.9em%22 font-size=%2290%22>📋
-</text></svg>">\n  
-</head>\n\n  
-<body>\n    
-<h1>📋 My tasks</h1>\n    
-<form>\n      
-<div class="new-task-form" tabindex="0">\n        
-<label for="new-task">➕ Add a task</label>\n        
-<input id="new-task" autocomplete="off" type="text" placeholder="Try typing 'Buy milk'" title="Click to start adding a task">\n        
-<input type="submit" value="➡️">\n      
-</div>\n      
-<ul id="tasks"><li class="divider">No tasks defined</li></ul>\n    
+</text></svg>">\n 
+</head>\n\n 
+<body>\n   
+<h1>📋 My tasks</h1>\n   
+<form>\n     
+<div class="new-task-form" tabindex="0">\n       
+<label for="new-task">➕ Add a task</label>\n       
+<input id="new-task" autocomplete="off" type="text" placeholder="Try typing 'Buy milk'" title="Click to start adding a task">\n       
+<input type="submit" value="➡️">\n     
+</div>\n     
+<ul id="tasks"><li class="divider">No tasks defined</li></ul>\n   
 </form>\n\n    \x3Cscript src="to-do.js">\x3C/script>\n  \n\n
 </body>
 </html>`
@@ -321,7 +364,7 @@ webView->NavigateToString(htmlString);
 <!-- ====================================================================== -->
 ## Loading local content by using virtual host name mapping
 
-Another way to load local content in a WebView2 control is to use virtual host name mapping.  This involves mapping a local domain name to a local folder, so that when the WebView2 control attempts to load a resource for that domain, it will load the content from the specified local folder location instead. The origin of the document will also be the virtual host name. 
+Another way to load local content in a WebView2 control is to use virtual host name mapping.  This involves mapping a local domain name to a local folder, so that when the WebView2 control attempts to load a resource for that domain, it will load the content from the specified local folder location instead. The origin of the document will also be the virtual host name.
 
 This approach lets you specify the cross-origin access, by using the `CoreWebView2HostResourceAccessKind` enum.
 
@@ -369,7 +412,7 @@ Source maps are needed to debug the source code of compiled content, including:
 * Transpiled JavaScript, such as TypeScript or minified JavaScript.
 * Compiled CSS, such as SASS or SCSS.
 
-WebView2 doesn't load source maps that are referenced by content which was loaded by using virtual host name mapping.  
+WebView2 doesn't load source maps that are referenced by content which was loaded by using virtual host name mapping. 
 
 For example, suppose WebView2 loads `main.js` via virtual host name mapping.  If `main.js` references `main.js.map` as its source map, `main.js.map` will not be loaded automatically.
 
@@ -408,7 +451,7 @@ To use source maps along with virtual host name mapping, generate inline source
 ##### [.NET/C#](#tab/dotnetcsharp)
 
 ```csharp
-webView.CoreWebView2.SetVirtualHostNameToFolderMapping("demo", 
+webView.CoreWebView2.SetVirtualHostNameToFolderMapping("demo",
          "C:\Github\Demos\demo-to-do", CoreWebView2HostResourceAccessKind.DenyCors);
 webView.CoreWebView2.Navigate("https://demo/index.html");
 ```
@@ -416,10 +459,10 @@ webView.CoreWebView2.Navigate("https://demo/index.html");
 ##### [WinRT/C#](#tab/winrtcsharp)
 
 ```csharp
-Windows.Storage.StorageFolder storageFolder = 
+Windows.Storage.StorageFolder storageFolder =
                               Windows.Storage.ApplicationData.Current.LocalFolder;
 Windows.Storage.StorageFolder demo = await storageFolder.GetFolderAsync("Demo");
-webView.CoreWebView2.SetVirtualHostNameToFolderMapping("demo", demo.Path, 
+webView.CoreWebView2.SetVirtualHostNameToFolderMapping("demo", demo.Path,
                                      CoreWebView2HostResourceAccessKind.DenyCors);
 webView.CoreWebView2.Navigate("https://demo/index.html");
 ```
@@ -427,7 +470,7 @@ webView.CoreWebView2.Navigate("https://demo/index.html");
 ##### [Win32/C++](#tab/win32cpp)
 
 ```cpp
-webView->SetVirtualHostNameToFolderMapping(L"demo", L"C:\\Github\\Demos\\demo-to-do", 
+webView->SetVirtualHostNameToFolderMapping(L"demo", L"C:\\Github\\Demos\\demo-to-do",
                                   COREWEBVIEW2_HOST_RESOURCE_ACCESS_KIND_DENY_CORS);
 webView->Navigate(L"https://demo/index.html");
 ```
@@ -440,7 +483,7 @@ webView->Navigate(L"https://demo/index.html");
 
 Another way you can host local content in a WebView2 control is by relying on the `WebResourceRequested` event.  This event is triggered when the control attempts to load a resource.  You can use this event to intercept the request and provide the local content, as described in [Custom management of network requests](../how-to/webresourcerequested.md).
 
-`WebResourceRequested` allows you to customize the behavior of local content on a per-request basis. This means you can decide which requests to intercept and provide your own content for, and which requests to let the WebView2 control handle normally.  However, customizing the behavior requires more code, such as virtual host mapping, and requires knowledge of HTTP, to be able to construct a proper response. 
+`WebResourceRequested` allows you to customize the behavior of local content on a per-request basis. This means you can decide which requests to intercept and provide your own content for, and which requests to let the WebView2 control handle normally.  However, customizing the behavior requires more code, such as virtual host mapping, and requires knowledge of HTTP, to be able to construct a proper response.
 
 From WebView2's perspective, the resource will have come via the network, and WebView2 will adhere to the headers that are set by the app as part of the response. Using the `WebResourceRequested` event is also slower than other approaches, due to the cross-process communication and processing that's needed for each request.
 
@@ -543,7 +586,7 @@ To use source maps along with `WebResourceRequested`, use one of the following a
 ##### [.NET/C#](#tab/dotnetcsharp)
 
 ```csharp
-// Reading of response content stream happens asynchronously, and WebView2 does not 
+// Reading of response content stream happens asynchronously, and WebView2 does not
 // directly dispose the stream once it read.  Therefore, use the following stream
 // class, which properly disposes when WebView2 has read all data.  For details, see
 // [CoreWebView2 does not close stream content](https://github.com/MicrosoftEdge/WebView2Feedback/issues/2513).
@@ -588,7 +631,7 @@ class ManagedStream : Stream {
             {
                 s_.Dispose();
             }
-        } 
+        }
         catch
         {
             s_.Dispose();
@@ -604,12 +647,12 @@ class ManagedStream : Stream {
 
    private Stream s_;
 }
-webView.CoreWebView2.AddWebResourceRequestedFilter("https://demo/*", 
+webView.CoreWebView2.AddWebResourceRequestedFilter("https://demo/*",
                                                 CoreWebView2WebResourceContext.All);
-webView.CoreWebView2.WebResourceRequested += delegate (object sender, 
+webView.CoreWebView2.WebResourceRequested += delegate (object sender,
                                      CoreWebView2WebResourceRequestedEventArgs args)
 {
-    string assetsFilePath = "C:\\Demo\\" + 
+    string assetsFilePath = "C:\\Demo\\" +
                             args.Request.Uri.Substring("https://demo/*".Length - 1);
     try
     {
@@ -663,7 +706,7 @@ class ManagedStream : IRandomAccessStream
 
     public override bool CanWrite => s_.CanWrite;
 
-    ulong IRandomAccessStream.Position => 
+    ulong IRandomAccessStream.Position =>
                                  { get => s_.Position; set => s_.Position = value; }
 
     public ulong Size => s_.Size;
@@ -688,7 +731,7 @@ class ManagedStream : IRandomAccessStream
         throw new NotImplementedException();
     }
 
-    public IAsyncOperationWithProgress<IBuffer, uint> ReadAsync(IBuffer buffer, 
+    public IAsyncOperationWithProgress<IBuffer, uint> ReadAsync(IBuffer buffer,
                                              uint count, InputStreamOptions options)
     {
         IAsyncOperationWithProgress<IBuffer, uint> result;
@@ -698,7 +741,7 @@ class ManagedStream : IRandomAccessStream
             // Once read is complete if no data was read, dispose the underlying
             // stream.
             result.Completed += new AsyncOperationWithProgressCompletedHandler<IBuffer, uint>(
-                     delegate (IAsyncOperationWithProgress<IBuffer, uint> asyncInfo, 
+                     delegate (IAsyncOperationWithProgress<IBuffer, uint> asyncInfo,
                                AsyncStatus asyncStatus)
             {
                 if (asyncInfo.GetResults().Length == 0)
@@ -733,19 +776,19 @@ class ManagedStream : IRandomAccessStream
     private IRandomAccessStream s_;
 }
 
-WebView2.CoreWebView2.AddWebResourceRequestedFilter("https://demo/*", 
+WebView2.CoreWebView2.AddWebResourceRequestedFilter("https://demo/*",
                                                 CoreWebView2WebResourceContext.All);
-WebView2.CoreWebView2.WebResourceRequested += async delegate (CoreWebView2 sender, 
+WebView2.CoreWebView2.WebResourceRequested += async delegate (CoreWebView2 sender,
                                      CoreWebView2WebResourceRequestedEventArgs args)
 {
     string filename = args.Request.Uri.Substring("https://demo/*".Length - 1);
     try
     {
-        Windows.Storage.StorageFolder storageFolder = 
+        Windows.Storage.StorageFolder storageFolder =
                                 Windows.Storage.ApplicationData.Current.LocalFolder;
         Windows.Storage.StorageFolder demo = await storageFolder.GetFolderAsync("Demo");
         Windows.Storage.StorageFile asset = await demo.GetFileAsync(filename);
-        
+       
         ManagedStream ms = new ManagedStream(await asset.OpenReadAsync());
         string headers = "";
         if (filename.EndsWith(".html"))
@@ -769,12 +812,12 @@ WebView2.CoreWebView2.WebResourceRequested += async delegate (CoreWebView2 sende
             headers = "Content-Type: application/javascript";
         }
 
-        args.Response = WebView2.CoreWebView2.Environment.CreateWebResourceResponse(ms, 
+        args.Response = WebView2.CoreWebView2.Environment.CreateWebResourceResponse(ms,
                                                                 200, "OK", headers);
     }
     catch (Exception)
     {
-        args.Response = WebView2.CoreWebView2.Environment.CreateWebResourceResponse(null, 
+        args.Response = WebView2.CoreWebView2.Environment.CreateWebResourceResponse(null,
                                                               404, "Not found", "");
     }
 };
@@ -797,7 +840,7 @@ HRESULT AppWindow::WebResourceRequestedEventHandler(
     wil::com_ptr<ICoreWebView2WebResourceRequest> request;
     wil::com_ptr<ICoreWebView2WebResourceResponse> response;
     wil::com_ptr<IStream> stream;
-    
+   
     CHECK_FAILURE(args->get_Request(&request));
     wil::unique_cotaskmem_string uri;
     CHECK_FAILURE(request->get_Uri(&uri));
diff --git a/microsoft-edge/webview2/get-started/hololens2.md b/microsoft-edge/webview2/get-started/hololens2.md
index b48fea707a..e38fdd3195 100644
--- a/microsoft-edge/webview2/get-started/hololens2.md
+++ b/microsoft-edge/webview2/get-started/hololens2.md
@@ -17,7 +17,7 @@ This article is to learn to write your own WebView2 code.  If you want to run a
 > [!IMPORTANT]
 > WebView2 on Hololens 2 continues to be available.  However, support for WebView2 on Hololens 2 is discontinued; there are no planned bug fixes or content updates, and technical support has ended.  Applications that use WebView2 on Hololens 2 are not guaranteed to continue to work.
 
-WebView2 on HoloLens 2 and the WebView plugin for Unity are both in Preview and are subject to change before general availability.  
+WebView2 on HoloLens 2 and the WebView plugin for Unity are both in Preview and are subject to change before general availability. 
 
 WebView2 only works on HoloLens 2 devices running the Windows 11 update. For more information, see [Update HoloLens 2](/hololens/hololens-update-hololens).
 
@@ -109,11 +109,11 @@ Before you can start developing a HoloLens 2 app with WebView2, you will need to
 <!-- ====================================================================== -->
 ## Step 3 - Configure the Unity project for Mixed Reality development
 
-Once you have your tools installed, you're ready to create and configure your project.  The easiest way to get started with HoloLens 2 development is to use the Mixed Reality Toolkit in your project.  
+Once you have your tools installed, you're ready to create and configure your project.  The easiest way to get started with HoloLens 2 development is to use the Mixed Reality Toolkit in your project. 
 
 The Mixed Reality Feature Tool simplifies the process of discovering, installing, and managing mixed reality features, including the Mixed Reality Toolkit, and packages for your Unity project. For more guidance on installing the Mixed Reality Feature Tool, see [Welcome to the Mixed Reality Feature Tool](/windows/mixed-reality/develop/unity/welcome-to-mr-feature-tool).
 
-1. First, [Download the Mixed Reality Feature Tool](https://www.microsoft.com/download/details.aspx?id=102778) from the Microsoft Download Center.   
+1. First, [Download the Mixed Reality Feature Tool](https://www.microsoft.com/download/details.aspx?id=102778) from the Microsoft Download Center.  
 
 1. Run the downloaded Mixed Reality Feature Tool executable, and follow the prompts to install the Mixed Reality Toolkit and any additional required packages for HoloLens 2 development.
 
@@ -209,7 +209,7 @@ Then continue with the next steps below.
 <!-- ====================================================================== -->
 ## Step 7 - Extending WebView2 functionality
 
-Although the prefab exposes just a single property, there's additional functionality exposed on the `WebView` script. Let's take a look at exposing some of this functionality in our project.  First, inspect the `WebView` script to get an idea of what's available.  
+Although the prefab exposes just a single property, there's additional functionality exposed on the `WebView` script. Let's take a look at exposing some of this functionality in our project.  First, inspect the `WebView` script to get an idea of what's available. 
 
 > [!TIP]
 > To view the contents of a script in your default code editor, double-click the name of the script in the **Inspector** window.
@@ -372,9 +372,9 @@ Continue with the next steps below.
 <!-- ====================================================================== -->
 ## Step 8 - Learn about WebView2 events and interactions in Unity
 
-The Microsoft Mixed Reality WebView plugin for Unity provides events for working with the webview. 
+The Microsoft Mixed Reality WebView plugin for Unity provides events for working with the webview.
 
-One important event is `IWithPostMessage.MessageReceived`, which is raised when a message is sent from the webview to the Unity app. The `MessageReceived` event is defined in the `Microsoft.MixedReality.WebView.IWithPostMessage` interface. 
+One important event is `IWithPostMessage.MessageReceived`, which is raised when a message is sent from the webview to the Unity app. The `MessageReceived` event is defined in the `Microsoft.MixedReality.WebView.IWithPostMessage` interface.
 
 `IWithPostMessage` also defines the `PostMessage()` method, which can be used to send a message from the Unity app to the webview.
 
diff --git a/microsoft-edge/webview2/get-started/win32.md b/microsoft-edge/webview2/get-started/win32.md
index e9689917b4..1502b042e2 100644
--- a/microsoft-edge/webview2/get-started/win32.md
+++ b/microsoft-edge/webview2/get-started/win32.md
@@ -375,10 +375,10 @@ Now to do the above, in the callback, you'll:
 
    ```cpp
       UpdateWindow(hWnd);
-   
+  
       // <-- WebView2 sample code starts here -->
    ```
-   
+  
 1. If the following code isn't already present, paste the following code into `HelloWebView.cpp`.  Paste the code in between the lines `// <-- WebView2 sample code starts here -->` and `// <-- WebView2 sample code ends here -->`:
 
    ```cpp
diff --git a/microsoft-edge/webview2/get-started/winforms.md b/microsoft-edge/webview2/get-started/winforms.md
index 9601bcb2a0..624e3dedb4 100644
--- a/microsoft-edge/webview2/get-started/winforms.md
+++ b/microsoft-edge/webview2/get-started/winforms.md
@@ -14,7 +14,7 @@ This article is to learn to write your own WebView2 code.  If you want to run a
 
 <!--
 todo: errors experienced with vs2022 by following these instructions:
-* The addressbar text box & Go button shift to the right when alt+tab to the Form1 window. 
+* The addressbar text box & Go button shift to the right when alt+tab to the Form1 window.
 -->
 
 This tutorial helps you:
@@ -95,7 +95,7 @@ Start with a basic desktop project that contains a single main window.
 1. Select **Debug** > **Start Debugging** (**F5**).
 
    An empty **Form1** window opens, from the fresh WinForms project:
-   
+  
    <!-- used at end of 2 sections: -->
    ![The empty Form1 window from the fresh WinForms project](./winforms-images/form1-empty-window-fresh-winforms-project.png)
 
@@ -194,7 +194,7 @@ The starter project has a `Form1.cs` form already, but we'll add another, as `Fo
 
    ![Properties of the WebView2 control](./winforms-images/winforms-properties.png)
 
-1. In the **Properties** panel, in the **Misc** section, set the **Source** property to `https://www.microsoft.com`.  The **Source** property sets the initial URL that will be displayed in the WebView2 control.  
+1. In the **Properties** panel, in the **Misc** section, set the **Source** property to `https://www.microsoft.com`.  The **Source** property sets the initial URL that will be displayed in the WebView2 control. 
 
 1. Select **File** > **Save All** (**Ctrl+Shift+S**) to save the project.
 
@@ -268,7 +268,7 @@ Add more controls to your Windows Forms form from the toolbox, and then process
       InitializeComponent();
    }
    ```
-    
+   
 1. Paste this code in the same location:
 
    ```csharp
@@ -393,10 +393,10 @@ To demonstrate how to use the events, start by registering a handler for `Naviga
    {
       InitializeComponent();
       this.Resize += new System.EventHandler(this.Form_Resize);
-   
+  
       webView.NavigationStarting += EnsureHttps;
    }
-   
+  
    void EnsureHttps(object sender, CoreWebView2NavigationStartingEventArgs args)
    {
       String uri = args.Uri;
@@ -456,7 +456,7 @@ For example, add a script that sends an alert when a user navigates to a non-HTT
    ```javascript
    alert('{uri} is not safe, try an https link')
    ```
-   
+  
 1. Select **File** > **Save All (Ctrl+Shift+S)** to save the project.
 
 1. Press **F5** to build and run the project.
@@ -520,7 +520,7 @@ In your project, when the WebView2 control navigates to a URL, it displays the U
    ```
 
    Next, for WebView2 to send and respond to the web message, after `CoreWebView2` is initialized, the host will inject a script in the web content to:
- 
+
    * Send the URL to the host using `postMessage`.
 
    * Register an event handler to display a message sent from the host, in an alert box, before displaying webpage content.
diff --git a/microsoft-edge/webview2/get-started/winui.md b/microsoft-edge/webview2/get-started/winui.md
index cd92d2afec..dc9a411402 100644
--- a/microsoft-edge/webview2/get-started/winui.md
+++ b/microsoft-edge/webview2/get-started/winui.md
@@ -132,7 +132,7 @@ To create a WebView2 app for WinUI 3 (Windows App SDK):
 
     The project templates that were installed in the previous major step are listed.
 
-1.  Click the **Blank App, Packaged (WinUI 3 in Desktop)** card to select it, and then click the **Next** button.  
+1.  Click the **Blank App, Packaged (WinUI 3 in Desktop)** card to select it, and then click the **Next** button. 
 
     The **Configure your new project** dialog appears.
 
@@ -276,7 +276,7 @@ To add a WebView2 control that initially navigates to the Microsoft home page:
         </Grid.ColumnDefinitions>
 
         <controls:WebView2 x:Name="MyWebView"  Grid.Row="1" Grid.ColumnSpan="2"
-            Source="https://www.microsoft.com" HorizontalAlignment="Stretch" 
+            Source="https://www.microsoft.com" HorizontalAlignment="Stretch"
             VerticalAlignment="Stretch"/>
     </Grid>
     ```
@@ -335,11 +335,11 @@ To allow users to control which webpage is displayed in the WebView2 control, ad
         <Button x:Name="myButton" Grid.Column="1" Click="myButton_Click">Go</Button>
 
         <controls:WebView2 x:Name="MyWebView"  Grid.Row="1" Grid.ColumnSpan="2"
-            Source="https://www.microsoft.com" HorizontalAlignment="Stretch" 
+            Source="https://www.microsoft.com" HorizontalAlignment="Stretch"
             VerticalAlignment="Stretch"/>
     </Grid>
     ```
-    
+   
 1.  In `MainWindow.xaml.cs`, paste the following `try/catch` block into the body of the `myButton_Click` method:
 
     ```csharp
@@ -358,7 +358,7 @@ To allow users to control which webpage is displayed in the WebView2 control, ad
     ```
 
     This code navigates the WebView2 control to the URL that the user enters in the Address bar, when the user clicks the **Go** button, by re-setting the value of the `MyWebView.Source` property, which is equivalent to the `Source` attribute of the `<controls:WebView2 x:Name="MyWebView">` element.
-    
+   
 1.  Select **File** > **Save All** (**Ctrl+Shift+S**).
 
 1.  Press **F5**.
@@ -496,7 +496,7 @@ To display an alert when the user tries to navigate to a non-HTTPS site:
         }
     }
     ```
-    
+   
 1.  Select **File** > **Save All** (**Ctrl+Shift+S**).
 
 1.  Press **F5**.
diff --git a/microsoft-edge/webview2/get-started/wpf.md b/microsoft-edge/webview2/get-started/wpf.md
index 45ff8b5799..279c6c17a1 100644
--- a/microsoft-edge/webview2/get-started/wpf.md
+++ b/microsoft-edge/webview2/get-started/wpf.md
@@ -203,7 +203,7 @@ In Visual Studio, use NuGet Package Manager to add the WebView2 SDK to the proje
 1. In the upper left, click the **Browse** tab.  In the search bar, type `Microsoft.Web.WebView2`, then click the **Microsoft.Web.WebView2** package.
 
    The NuGet package manager dialog displays search results, including a **Microsoft.Web.WebView2** package.  The dialog has a version number and **Install** button.
-   
+  
    ![NuGet package manager dialog displays the Microsoft.Web.WebView2 package](./wpf-images/install-nuget.png)
 
 1. Accept the default version, and then click the **Install** button.
@@ -323,7 +323,7 @@ Enable users to change the URL that the WebView2 control displays, by adding an
    ```
 
 1. Paste the code directly after the `Public MainWIndow` declaration, as shown in the following code:
-    
+   
    ```csharp
    namespace WpfApp1
    {
@@ -426,7 +426,7 @@ To demonstrate how to use the events, register a handler for `NavigationStarting
         InitializeComponent();
         webView.NavigationStarting += EnsureHttps;
     }
-    
+   
     void EnsureHttps(object sender, CoreWebView2NavigationStartingEventArgs args)
     {
         String uri = args.Uri;
@@ -436,7 +436,7 @@ To demonstrate how to use the events, register a handler for `NavigationStarting
         }
     }
     ```
-    
+   
    In the constructor, `EnsureHttps` is registered as the event handler on the `NavigationStarting` event on the WebView2 control.
 
 1. Select **File** > **Save All** to save the project.
diff --git a/microsoft-edge/webview2/how-to/chromium-devtools-protocol.md b/microsoft-edge/webview2/how-to/chromium-devtools-protocol.md
index 01f6ab15a0..26063fb20e 100644
--- a/microsoft-edge/webview2/how-to/chromium-devtools-protocol.md
+++ b/microsoft-edge/webview2/how-to/chromium-devtools-protocol.md
@@ -52,20 +52,20 @@ To create an `HTML file` to find your geolocation, complete following the action
       <button id="display">Display Location</button>
       <div id="message"></div>
    </body>
-   
+  
    <script>
       const btn = document.getElementById('display');
       // Find the user location.
       btn.addEventListener('click', function () {
          navigator.geolocation.getCurrentPosition(onSuccess, onError);
       });
-   
+  
       // Update message to display the latitude and longitude coordinates.
       function onSuccess(position) {
          const {latitude, longitude} = position.coords;
          message.textContent = `Your location: (${latitude},${longitude})`;
       }
-   
+  
       function onError() {
          message.textContent = `Operation Failed`;
       }
diff --git a/microsoft-edge/webview2/how-to/communicate-btwn-web-native.md b/microsoft-edge/webview2/how-to/communicate-btwn-web-native.md
index 729aaf65ca..8ae90d4ddc 100644
--- a/microsoft-edge/webview2/how-to/communicate-btwn-web-native.md
+++ b/microsoft-edge/webview2/how-to/communicate-btwn-web-native.md
@@ -84,7 +84,7 @@ To see messaging in action:
    ```javascript
    window.chrome.webview.addEventListener('message', arg => {
       if ("SetColor" in arg.data) {
-         document.getElementById("colorable").style.color = 
+         document.getElementById("colorable").style.color =
          arg.data.SetColor;
       }
    });
@@ -96,15 +96,15 @@ To see messaging in action:
 
    ```html
    <h1>WebMessage sample page</h1>
-   <p>This page demonstrates basic interaction between the host app 
+   <p>This page demonstrates basic interaction between the host app
    and the webview by means of Web Messages.</p>
 
    <h2>Posting Messages</h2>
-   <p id="colorable">Messages can be posted from the host app to the 
+   <p id="colorable">Messages can be posted from the host app to the
    webview using the functions
    <code>ICoreWebView2::PostWebMessageAsJson</code> and
-   <code>ICoreWebView2::PostWebMessageAsString</code>. Try selecting 
-   the menu item "Script > Post Message JSON" to send the message 
+   <code>ICoreWebView2::PostWebMessageAsString</code>. Try selecting
+   the menu item "Script > Post Message JSON" to send the message
    <code>{"SetColor":"blue"}</code>.
    It should change the text color of this paragraph.</p>
    ```
@@ -146,9 +146,9 @@ The C++ file handles the title text and communicates it to the host app as a str
 
    ```html
    <h2>Receiving Messages</h2>
-   <p>The host app can receive messages by registering an event handler 
-   with <code>ICoreWebView2::add_WebMessageReceived</code>. If you 
-   enter text and click "Send", this page will send a message to the 
+   <p>The host app can receive messages by registering an event handler
+   with <code>ICoreWebView2::add_WebMessageReceived</code>. If you
+   enter text and click "Send", this page will send a message to the
    host app which will change the text of the title bar.</p>
    <input type="text" id="title-text"/>
    <button onclick="SetTitleText()">Send</button>
@@ -206,9 +206,9 @@ When requested by the host app, the C++ file gets the window bounds and sends th
 
    ```html
    <h2>Round trip</h2>
-   <p>The host app can send messages back in response to received 
-   messages. If you click the <b>Get window bounds</b> button, the 
-   host app reports back the bounds of its window, which are 
+   <p>The host app can send messages back in response to received
+   messages. If you click the <b>Get window bounds</b> button, the
+   host app reports back the bounds of its window, which are
    displayed in the text box.</p>
    <button onclick="GetWindowBounds()">Get window bounds</button><br>
    <textarea id="window-bounds" rows="4" readonly></textarea>
diff --git a/microsoft-edge/webview2/how-to/context-menus.md b/microsoft-edge/webview2/how-to/context-menus.md
index a790065460..ffbd7afeca 100644
--- a/microsoft-edge/webview2/how-to/context-menus.md
+++ b/microsoft-edge/webview2/how-to/context-menus.md
@@ -48,7 +48,7 @@ You can add default menu items and/or custom menu items to a custom context menu
 
 ##### [C#](#tab/csharp)
 
-To display a custom context menu that contains your desired menu items, use the data provided in the `CoreWebView2ContextMenuRequestedEventArgs` of the `CoreWebView2` [ContextMenuRequested Event](/dotnet/api/microsoft.web.webview2.core.corewebview2.contextmenurequested).  For this case, you specify `Handled` to be `true`, and request a deferral. 
+To display a custom context menu that contains your desired menu items, use the data provided in the `CoreWebView2ContextMenuRequestedEventArgs` of the `CoreWebView2` [ContextMenuRequested Event](/dotnet/api/microsoft.web.webview2.core.corewebview2.contextmenurequested).  For this case, you specify `Handled` to be `true`, and request a deferral.
 
 On a `CoreWebView2.ContextMenuRequested` event, add an event listener that has a `CoreWebView2ContextMenuRequestedEventArgs`.
 
@@ -91,7 +91,7 @@ The `MenuItems` property of `CoreWebView2ContextMenuRequestedEventArgs` provides
 
 ##### [C++](#tab/cpp)
 
-To display a custom context menu that contains your desired menu items, use the data provided in [ICoreWebView2ContextMenuRequestedEventArgs](/microsoft-edge/webview2/reference/win32/icorewebview2contextmenurequestedeventargs).  For this case, you specify `Handled` to be `true`, and request a deferral. 
+To display a custom context menu that contains your desired menu items, use the data provided in [ICoreWebView2ContextMenuRequestedEventArgs](/microsoft-edge/webview2/reference/win32/icorewebview2contextmenurequestedeventargs).  For this case, you specify `Handled` to be `true`, and request a deferral.
 
 On a `ContextMenuRequested` event, add an event listener that has an `ICoreWebView2ContextMenuRequestedEventArgs`.
 
@@ -128,7 +128,7 @@ Iterate through a list of `ICoreWebView2ContextMenuItem` items, adding an `ICore
 * [COREWEBVIEW2_CONTEXT_MENU_ITEM_KIND enum](/microsoft-edge/webview2/reference/win32/icorewebview2#corewebview2_context_menu_item_kind)
    * `COREWEBVIEW2_CONTEXT_MENU_ITEM_KIND_SEPARATOR`
    * `COREWEBVIEW2_CONTEXT_MENU_ITEM_KIND_SUBMENU`
-   
+  
 * [COREWEBVIEW2_CONTEXT_MENU_TARGET_KIND enum](/microsoft-edge/webview2/reference/win32/icorewebview2#corewebview2_context_menu_target_kind)
 
 ---
@@ -143,7 +143,7 @@ The following sample presents the WebView2 context menu in the Win32/WPF context
 ##### [C#](#tab/csharp)
 
 ```csharp
-webView.CoreWebView2.ContextMenuRequested += delegate (object sender, 
+webView.CoreWebView2.ContextMenuRequested += delegate (object sender,
                                     CoreWebView2ContextMenuRequestedEventArgs args)
 {
     IList<CoreWebView2ContextMenuItem> menuList = args.MenuItems;
@@ -154,7 +154,7 @@ webView.CoreWebView2.ContextMenuRequested += delegate (object sender,
     PopulateContextMenu(args, menuList, cm);
     cm.IsOpen = true;
 };
-void PopulateContextMenu(CoreWebView2ContextMenuRequestedEventArgs args, 
+void PopulateContextMenu(CoreWebView2ContextMenuRequestedEventArgs args,
 IList<CoreWebView2ContextMenuItem> menuList, ItemsControl cm)
 {
     for (int i = 0; i < menuList.Count; i++)
@@ -205,7 +205,7 @@ webview2_4->add_ContextMenuRequested(
             ICoreWebView2* sender,
             ICoreWebView2ContextMenuRequestedEventArgs* args)
         {
-            auto showMenu = [this, args = 
+            auto showMenu = [this, args =
             wil::com_ptr<ICoreWebView2ContextMenuRequestedEventArgs>(args)]
             {
                 wil::com_ptr<ICoreWebView2ContextMenuItemCollection> items;
@@ -219,17 +219,17 @@ webview2_4->add_ContextMenuRequested(
                 POINT locationInScreenCoordinates;
                 CHECK_FAILURE(args->get_Location(&locationInControlCoordinates));
                 // get_Location returns coordinates in relation to upper left Bounds
-                // of the WebView2.Controller. Will need to convert to Screen 
+                // of the WebView2.Controller. Will need to convert to Screen
                 // coordinates to display the popup menu in the correct location.
-                ConvertToScreenCoordinates(locationInControlCoordinates, 
+                ConvertToScreenCoordinates(locationInControlCoordinates,
                                            locationInScreenCoordinates);
                 UINT32 selectedCommandId = TrackPopupMenu(
-                                       hPopupMenu, 
+                                       hPopupMenu,
                                        TPM_TOPALIGN | TPM_LEFTALIGN | TPM_RETURNCMD,
-                                       locationInScreenCoordinates.x, 
-                                       locationInScreenCoordinates.y, 
-                                       0, 
-                                       hWnd, 
+                                       locationInScreenCoordinates.x,
+                                       locationInScreenCoordinates.y,
+                                       0,
+                                       hWnd,
                                        NULL);
                 if (selectedCommandId != 0) {
                     CHECK_FAILURE(args->put_SelectedCommandId(selectedCommandId));
@@ -288,15 +288,15 @@ void ContextMenu::AddMenuItems(
                 {
                     AddMenuItems(newMenu, submenuItems);
                     CHECK_BOOL(AppendMenu(hPopupMenu,
-                                          MF_POPUP, 
-                                          (UINT_PTR)newMenu, 
+                                          MF_POPUP,
+                                          (UINT_PTR)newMenu,
                                           labelString.c_str()));
                 }
                 else
                 {
-                    CHECK_BOOL(AppendMenu(hPopupMenu, 
-                                          MF_POPUP | MF_GRAYED, 
-                                          (UINT_PTR)newMenu, 
+                    CHECK_BOOL(AppendMenu(hPopupMenu,
+                                          MF_POPUP | MF_GRAYED,
+                                          (UINT_PTR)newMenu,
                                           labelString.c_str()));
                 }
             }
@@ -308,16 +308,16 @@ void ContextMenu::AddMenuItems(
                 {
                     if (isChecked)
                     {
-                        CHECK_BOOL(AppendMenu(hPopupMenu, 
-                                              MF_CHECKED | MF_STRING, 
-                                              commandId, 
+                        CHECK_BOOL(AppendMenu(hPopupMenu,
+                                              MF_CHECKED | MF_STRING,
+                                              commandId,
                                               labelString.c_str()));
                     }
                     else
                     {
-                        CHECK_BOOL(AppendMenu(hPopupMenu, 
+                        CHECK_BOOL(AppendMenu(hPopupMenu,
                                               MF_BYPOSITION | MF_STRING,
-                                              commandId, 
+                                              commandId,
                                               labelString.c_str()));
                     }
                 }
@@ -325,16 +325,16 @@ void ContextMenu::AddMenuItems(
                 {
                     if (isChecked)
                     {
-                        CHECK_BOOL(AppendMenu(hPopupMenu, 
-                                              MF_CHECKED | MF_GRAYED | MF_STRING, 
-                                              commandId, 
+                        CHECK_BOOL(AppendMenu(hPopupMenu,
+                                              MF_CHECKED | MF_GRAYED | MF_STRING,
+                                              commandId,
                                               labelString.c_str()));
                     }
                     else
                     {
-                        CHECK_BOOL(AppendMenu(hPopupMenu, 
-                                              MF_GRAYED | MF_STRING, 
-                                              commandId, 
+                        CHECK_BOOL(AppendMenu(hPopupMenu,
+                                              MF_GRAYED | MF_STRING,
+                                              commandId,
                                               labelString.c_str()));
                     }
                 }
@@ -344,15 +344,15 @@ void ContextMenu::AddMenuItems(
                 if (isEnabled)
                 {
                     CHECK_BOOL(AppendMenu(hPopupMenu,
-                                          MF_BYPOSITION | MF_STRING, 
-                                          commandId, 
+                                          MF_BYPOSITION | MF_STRING,
+                                          commandId,
                                           labelString.c_str()));
                 }
                 else
                 {
-                    CHECK_BOOL(AppendMenu(hPopupMenu, 
-                                          MF_GRAYED | MF_STRING, 
-                                          commandId, 
+                    CHECK_BOOL(AppendMenu(hPopupMenu,
+                                          MF_GRAYED | MF_STRING,
+                                          commandId,
                                           labelString.c_str()));
                 }
             }
@@ -435,11 +435,11 @@ The following example adds a **Display Page Uri** command to the WebView2 contex
 ##### [C#](#tab/csharp)
 
 ```csharp
-webView.CoreWebView2.ContextMenuRequested += delegate (object sender, 
+webView.CoreWebView2.ContextMenuRequested += delegate (object sender,
                                     CoreWebView2ContextMenuRequestedEventArgs args)
 {
     // add new item to end of collection
-    CoreWebView2ContextMenuItem newItem = 
+    CoreWebView2ContextMenuItem newItem =
                         webView.CoreWebView2.Environment.CreateContextMenuItem(
         "Display Page Uri", null, CoreWebView2ContextMenuItemKind.Command);
         newItem.CustomItemSelected += delegate (object send, Object ex)
@@ -452,7 +452,7 @@ webView.CoreWebView2.ContextMenuRequested += delegate (object sender,
         };
     menuList.Insert(menuList.Count, newItem);
 };
-``` 
+```
 
 
 ##### [C++](#tab/cpp)
@@ -475,8 +475,8 @@ webview2_4->add_ContextMenuRequested(
                 IID_PPV_ARGS(&webviewEnvironment)));
             wil::com_ptr<ICoreWebView2ContextMenuItem> newMenuItem;
             CHECK_FAILURE(webviewEnvironment->CreateContextMenuItem(
-                    L"Display page Uri", 
-                    nullptr, 
+                    L"Display page Uri",
+                    nullptr,
                     COREWEBVIEW2_CONTEXT_MENU_ITEM_KIND_COMMAND, &newMenuItem));
             newMenuItem->add_CustomItemSelected(
                         Callback<ICoreWebView2CustomItemSelectedEventHandler>(
@@ -565,7 +565,7 @@ The following example removes the **Save image as** command from the WebView2 co
 ##### [C#](#tab/csharp)
 
 ```csharp
-webView.CoreWebView2.ContextMenuRequested += delegate (object sender, 
+webView.CoreWebView2.ContextMenuRequested += delegate (object sender,
                                     CoreWebView2ContextMenuRequestedEventArgs args)
 {
     IList<CoreWebView2ContextMenuItem> menuList = args.MenuItems;
@@ -582,7 +582,7 @@ webView.CoreWebView2.ContextMenuRequested += delegate (object sender,
         }
     }
 };
-``` 
+```
 
 
 ##### [C++](#tab/cpp)
@@ -607,7 +607,7 @@ webview2_4->add_ContextMenuRequested(
             if (context_kind == COREWEBVIEW2_CONTEXT_MENU_TARGET_KIND_IMAGE)
             {
                 wil::com_ptr<ICoreWebView2ContextMenuItem> current;
-                for(UINT32 i = 0; i < itemsCount; i++) 
+                for(UINT32 i = 0; i < itemsCount; i++)
                 {
                     CHECK_FAILURE(items->GetValueAtIndex(i, &current));
                     wil::unique_cotaskmem_string name;
@@ -644,7 +644,7 @@ The WebView2 control raises this event to indicate that the user requested openi
 
 The WebView2 control only raises the `ContextMenuRequested` event if the current webpage allows the context menu to appear; that is, if the `AreDefaultContextMenusEnabled` property is `true`.
 
-The [CoreWebView2ContextMenuRequestedEventArgs](/dotnet/api/microsoft.web.webview2.core.corewebview2contextmenurequestedeventargs) contains the following information: 
+The [CoreWebView2ContextMenuRequestedEventArgs](/dotnet/api/microsoft.web.webview2.core.corewebview2contextmenurequestedeventargs) contains the following information:
 
 * An ordered list of `ContextMenuItem` objects to populate the custom context menu.  The ordered list includes the following:
    * The internal name of the menu item.
@@ -842,7 +842,7 @@ The `AreDefaultContextMenusEnabled` property controls whether any context menu c
    * [put_IsChecked](/microsoft-edge/webview2/reference/win32/icorewebview2contextmenuitem#put_ischecked)
    * [put_IsEnabled](/microsoft-edge/webview2/reference/win32/icorewebview2contextmenuitem#put_isenabled)
    * [remove_CustomItemSelected](/microsoft-edge/webview2/reference/win32/icorewebview2contextmenuitem#remove_customitemselected)
-   
+  
 * **[ICoreWebView2ContextMenuItemCollection](/microsoft-edge/webview2/reference/win32/icorewebview2contextmenuitemcollection)**
    * [get_Count](/microsoft-edge/webview2/reference/win32/icorewebview2contextmenuitemcollection#get_count)
    * [GetValueAtIndex](/microsoft-edge/webview2/reference/win32/icorewebview2contextmenuitemcollection#getvalueatindex)
@@ -876,7 +876,7 @@ The `AreDefaultContextMenusEnabled` property controls whether any context menu c
 * **[ICoreWebView2Settings](/microsoft-edge/webview2/reference/win32/icorewebview2settings)**
    * [get_AreDefaultContextMenusEnabled](/microsoft-edge/webview2/reference/win32/icorewebview2settings#get_aredefaultcontextmenusenabled)
    * [put_AreDefaultContextMenusEnabled](/microsoft-edge/webview2/reference/win32/icorewebview2settings#put_aredefaultcontextmenusenabled)
-   
+  
 * [COREWEBVIEW2_CONTEXT_MENU_ITEM_KIND enum](/microsoft-edge/webview2/reference/win32/icorewebview2#corewebview2_context_menu_item_kind)
    * `COREWEBVIEW2_CONTEXT_MENU_ITEM_KIND_COMMAND`
    * `COREWEBVIEW2_CONTEXT_MENU_ITEM_KIND_CHECK_BOX`
diff --git a/microsoft-edge/webview2/how-to/debug-visual-studio-code.md b/microsoft-edge/webview2/how-to/debug-visual-studio-code.md
index 5ebcec0cdb..43c85aa165 100644
--- a/microsoft-edge/webview2/how-to/debug-visual-studio-code.md
+++ b/microsoft-edge/webview2/how-to/debug-visual-studio-code.md
@@ -30,7 +30,7 @@ The following code demonstrates launching the app from Visual Studio Code (rathe
 "env": {
    // The following variable is needed when the "runtimeExecutable" property is set.
    // The port number below must match the value of the "port" property above.
-   "WEBVIEW2_ADDITIONAL_BROWSER_ARGUMENTS": "--remote-debugging-port=9222" 
+   "WEBVIEW2_ADDITIONAL_BROWSER_ARGUMENTS": "--remote-debugging-port=9222"
    // Customize for your app location.
    "Path": "%path%;e:/path/to/your/app/location; "
 },
@@ -181,7 +181,7 @@ To enable debug tracing, add the `trace` parameter to `launch.json` , as follows
 Saving debug output to a log file:
 
 ![ Save debug output to a log file](./debug-visual-studio-code-images/trace-log.png)
-      
+     
 ```json
 ,"trace": "verbose"  // Turn on verbose tracing in the Debug Output pane.
 ```
@@ -260,7 +260,7 @@ You might encounter these scenarios when using the debugger.
 <!-- ---------------------------------- -->
 #### Doesn't stop at breakpoint
 
-If the debugger doesn't stop at the breakpoint, and you have debug output: 
+If the debugger doesn't stop at the breakpoint, and you have debug output:
 
 To solve the issue, confirm that the file with the breakpoint is the same file that's used by the WebView2 control.  The debugger doesn't perform source path mapping.
 
diff --git a/microsoft-edge/webview2/how-to/debug-visual-studio.md b/microsoft-edge/webview2/how-to/debug-visual-studio.md
index e9fefe4d43..26f9a6f170 100644
--- a/microsoft-edge/webview2/how-to/debug-visual-studio.md
+++ b/microsoft-edge/webview2/how-to/debug-visual-studio.md
@@ -16,7 +16,7 @@ Microsoft Visual Studio provides various debugging tools for web and native code
 <!-- ------------------------------ -->
 #### Summary of high-level steps
 
-To debug JavaScript code in a WebView2 control: 
+To debug JavaScript code in a WebView2 control:
 
 1. Install the **JavaScript diagnostics** component in the **Desktop development with C++** workload of Visual Studio, or in another platform's workload.
 
@@ -110,18 +110,18 @@ After doing the above setup, debug your WebView2 app, as follows.
 
    ![Running the Local Windows Debugger in Visual Studio](./debug-visual-studio-images/run-local-windows-debugger.png)
 
-   When setting a breakpoint, you must open the file that's in the exact same path that's associated with your WebView2 control, because the JS/TS debug adapter doesn't perform source path mapping.  
+   When setting a breakpoint, you must open the file that's in the exact same path that's associated with your WebView2 control, because the JS/TS debug adapter doesn't perform source path mapping. 
 
    The breakpoint will be triggered when this section of the code is executed.  This breakpoint is triggered upon clicking the **Add a new item** button in the sample app, in a later step below.
 
 1. Select the bit size of the platform, such as **x64**.
 
-1. To run the debugger, do any of the following: 
+1. To run the debugger, do any of the following:
 
    * In the menu bar, select **Debug** > **Start Debugging (F5)**.
    * In Solution Explorer, right-click the project > **Debug** > **Start New Instance** or **Step Into New Instance**.
    * Click the green Play button to the left of **Local Windows Debugger**.
-    
+   
    The WebView2APISample app (or your own app) runs and opens, and the debugger connects to the first WebView2 process that's created.  In **Properties** > **Debugging** for the project, **Local Windows Debugger** was set to **JavaScript (WebView2)**.
 
 1. In Visual Studio, click the **Output** tab, in the lower right.
@@ -196,7 +196,7 @@ To open DevTools, press **Ctrl+Shift+I**.  Or, right-click the page in the runni
 
 If you use the WebView2 [SetVirtualHostNameToFolderMapping](/dotnet/api/microsoft.web.webview2.core.corewebview2.setvirtualhostnametofoldermapping) method, the debugger in Visual Studio 2019 doesn't understand the virtual source path mapping, so breakpoints don't work correctly.
 
-When setting a breakpoint, you must open the file that's in the exact same path that's associated with your WebView2 control, because the JS/TS debug adapter doesn't perform source path mapping.  
+When setting a breakpoint, you must open the file that's in the exact same path that's associated with your WebView2 control, because the JS/TS debug adapter doesn't perform source path mapping. 
 
 Virtual source path mapping is supported by the debugger in Visual Studio Code.
 
diff --git a/microsoft-edge/webview2/how-to/debug.md b/microsoft-edge/webview2/how-to/debug.md
index 6b1ba43b79..87aa83aacf 100644
--- a/microsoft-edge/webview2/how-to/debug.md
+++ b/microsoft-edge/webview2/how-to/debug.md
@@ -12,7 +12,7 @@ ms.date: 09/15/2021
 <!--
 previously contained a single, article-scoped tabset; converted the 3 tabs to 3 .md files/articles
 todo: delete .md & define a redirect?
-needed as a generic landing page to link to?  
+needed as a generic landing page to link to? 
 articles don't link to here
 -->
 
diff --git a/microsoft-edge/webview2/how-to/hostobject.md b/microsoft-edge/webview2/how-to/hostobject.md
index 852c8f1eed..18309f7805 100644
--- a/microsoft-edge/webview2/how-to/hostobject.md
+++ b/microsoft-edge/webview2/how-to/hostobject.md
@@ -37,7 +37,7 @@ This article mainly covers Win32/C++, and also covers some aspects of .NET/C# wi
 
 #### Why use `AddHostObjectToScript`?
 
-  * When developing a WebView2 app, you may encounter a native object whose methods or properties you find useful. You might want to trigger these native object methods from web-side code, as a result of user interaction on the web side of your app. In addition, you might not want to re-implement your native objects' methods in your web-side code.  The `AddHostObjectToScript` API enables re-use of native-side code by web-side code. 
+  * When developing a WebView2 app, you may encounter a native object whose methods or properties you find useful. You might want to trigger these native object methods from web-side code, as a result of user interaction on the web side of your app. In addition, you might not want to re-implement your native objects' methods in your web-side code.  The `AddHostObjectToScript` API enables re-use of native-side code by web-side code.
 
   * For example, there might be a native webcam API, which would require re-writing a large amount of code on the web side. Having the ability to call the native object's methods is quicker and more efficient than re-coding the object's methods on the web side of your app. In this case, your native-side code can pass the object to your app's web-side, JavaScript code, so that your JavaScript code can reuse the native API's methods.
 
@@ -76,7 +76,7 @@ First, use interface definition language (IDL) to define the host object's COM i
     ```csharp
     import "oaidl.idl";
     import "ocidl.idl";
-    
+   
     [uuid(0a7a4655-5660-47d0-8a37-98ae21399e57), version(0.1)]
     library HostObjectSampleLibrary
     {
@@ -85,24 +85,24 @@ First, use interface definition language (IDL) to define the host object's COM i
         {
             // Demonstrates a basic method call with some parameters and a return value.
             HRESULT MethodWithParametersAndReturnValue([in] BSTR stringParameter, [in] INT integerParameter, [out, retval] BSTR* stringResult);
-    
+   
             // Demonstrate getting and setting a property.
             [propget] HRESULT Property([out, retval] BSTR* stringResult);
             [propput] HRESULT Property([in] BSTR stringValue);
-    
+   
             [propget] HRESULT IndexedProperty(INT index, [out, retval] BSTR * stringResult);
             [propput] HRESULT IndexedProperty(INT index, [in] BSTR stringValue);
-    
+   
             // Demonstrate native calling back into JavaScript.
             HRESULT CallCallbackAsynchronously([in] IDispatch* callbackParameter);
-    
+   
             // Demonstrates a property which uses Date types.
             [propget] HRESULT DateProperty([out, retval] DATE * dateResult);
             [propput] HRESULT DateProperty([in] DATE dateValue);
-    
+   
             // Creates a date object on the native side and sets the DateProperty to it.
             HRESULT CreateNativeDate();
-    
+   
         };
     ```
 
@@ -141,7 +141,7 @@ Next, we examine two specific properties that were defined in the IDL, to show h
 1.  In Visual Studio **Solution Explorer**, expand **WebView2APISample** > **Source Files**, and then double-click **HostObjectSampleImpl.cpp** to open it.
 
 1.  Examine the property *declarations* in [HostObjectSample.idl](https://github.com/MicrosoftEdge/WebView2Samples/blob/main/SampleApps/WebView2APISample/HostObjectSample.idl):
- 
+
     ```csharp
     // Demonstrate getting and setting a property.
     [propget] HRESULT Property([out, retval] BSTR* stringResult);
@@ -163,7 +163,7 @@ Next, we examine two specific properties that were defined in the IDL, to show h
         *stringResult = SysAllocString(m_propertyValue.c_str());
         return S_OK;
     }
-    
+   
     STDMETHODIMP HostObjectSample::put_Property(BSTR stringValue)
     {
         m_propertyValue = stringValue;
@@ -176,7 +176,7 @@ Next, we examine two specific properties that were defined in the IDL, to show h
         *dateResult = m_date;
         return S_OK;
     }
-    
+   
     STDMETHODIMP HostObjectSample::put_DateProperty(DATE dateValue)
     {
         m_date = dateValue;
@@ -184,7 +184,7 @@ Next, we examine two specific properties that were defined in the IDL, to show h
         if (VariantTimeToSystemTime(dateValue, &systemTime))
     ...
     }
-    
+   
     STDMETHODIMP HostObjectSample::CreateNativeDate()
     {
         SYSTEMTIME systemTime;
@@ -212,12 +212,12 @@ The host object must implement `IDispatch` so that WebView2 can project the nati
 * `GetTypeInfoCount`
 * `Invoke`
 
-Implement `IDispatch` as described in [Type Libraries and the Object Description Language](/previous-versions/windows/desktop/automat/type-libraries-and-the-object-description-language).  For more information about `IDispatch` inheritance and methods, see [IDispatch interface (oaidl.h)](/windows/win32/api/oaidl/nn-oaidl-idispatch). 
+Implement `IDispatch` as described in [Type Libraries and the Object Description Language](/previous-versions/windows/desktop/automat/type-libraries-and-the-object-description-language).  For more information about `IDispatch` inheritance and methods, see [IDispatch interface (oaidl.h)](/windows/win32/api/oaidl/nn-oaidl-idispatch).
 
 If the object you want to add to JavaScript doesn't already implement `IDispatch`, you need to write an `IDispatch` class wrapper for the object that you want to expose.
 
 There might be libraries to do this automatically.  To learn more about the steps that are needed to write an `IDispatch` class wrapper for the object that you want to expose, see [Automation](/previous-versions/windows/desktop/automat/automation-programming-reference).
-    
+   
 1.  Next, save any changes you made in the project.
 
 1.  In Solution Explorer, right-click the **WebView2APISample** (which is the Win32 sample app), and then select **Build**.  This creates a COM type library `.tlb` file.  You need to reference the `.tlb` file from the C++ source code.  For more information, see [Type Library](/windows/win32/midl/com-dcom-and-type-libraries#type-library) in _COM, DCOM, and Type Libraries_.
@@ -250,7 +250,7 @@ So far, we've built our interface and implemented our native host object.  Now w
         : m_appWindow(appWindow), m_webView(appWindow->GetWebView())
     {
         std::wstring sampleUri = m_appWindow->GetLocalUri(L"ScenarioAddHostObject.html");
-    
+   
         m_hostObject = Microsoft::WRL::Make<HostObjectSample>(
             [appWindow = m_appWindow](std::function<void(void)> callback)
         {
@@ -272,10 +272,10 @@ So far, we've built our interface and implemented our native host object.  Now w
             std::wstring uriTarget(navigationTargetUri.get());
     ```
 
-1.  In the `NavigationStarting` event handler, the `query_to` line (below) casts the newly created COM object to an `IDispatch` type and then converts the object to a `VARIANT`. `VARIANT` types allow you to use data structures such as integers and arrays as well as more complex types such as `IDispatch`. 
+1.  In the `NavigationStarting` event handler, the `query_to` line (below) casts the newly created COM object to an `IDispatch` type and then converts the object to a `VARIANT`. `VARIANT` types allow you to use data structures such as integers and arrays as well as more complex types such as `IDispatch`.
 
     For a full list of supported data types, see [VARIANT structure (oaidl.h)](/windows/win32/api/oaidl/ns-oaidl-variant).  Not all types in the `VARIANT` union are supported by `AddHostObjectToScript`.  For details, see [ICoreWebView2::AddHostObjectToScript method](/microsoft-edge/webview2/reference/win32/icorewebview2#addhostobjecttoscript).
-    
+   
     ```cpp
             if (AreFileUrisEqual(sampleUri, uriTarget))
             {
@@ -344,7 +344,7 @@ To add the host object to an iframe, we'll use `ICoreWebView2Frame::AddHostObjec
 This Win32/C++ sample code is condensed from [ScenarioAddHostObject.cpp](https://github.com/MicrosoftEdge/WebView2Samples/blob/main/SampleApps/WebView2APISample/ScenarioAddHostObject.cpp#L83-L133) in the **WebView2APISample** project (which is the Win32 sample app).
 
 This sample code demonstrates these APIs:
-* `ICoreWebView2Frame::AddHostObjectToScriptWithOrigins` 
+* `ICoreWebView2Frame::AddHostObjectToScriptWithOrigins`
 * `ICoreWebView2FrameCreatedEventHandler`
    * `ICoreWebView2FrameCreatedEventArgs::get_Frame`
 
@@ -421,7 +421,7 @@ The web-side code of the Win32 sample app is now able to access the properties a
     ```
     sample.dateProperty: Tue Nov 01 2022 12:45:25 GMT-0700 (Pacific Daylight Time)
     ```
-    
+   
 1.  Explore properties and methods by clicking the buttons in the demo webpage and entering values, to see how the sample code behaves.  The buttons demonstrate accessing properties and methods of the host object from the app's web-side code.
 
 1.  To gain insight into what's happening in JavaScript, examine the following code in [ScenarioAddHostObject.html](https://github.com/MicrosoftEdge/WebView2Samples/blob/main/SampleApps/WebView2APISample/assets/ScenarioAddHostObject.html).
@@ -431,14 +431,14 @@ The web-side code of the Win32 sample app is now able to access the properties a
     ```javascript
     <h2>Date Objects</h2>
     <button id="setDateButton">Set Date to Now</button>
-    <label for="setDateButton">Sets <code>chrome.webview.hostObjects.options.shouldSerializeDates = true</code> 
+    <label for="setDateButton">Sets <code>chrome.webview.hostObjects.options.shouldSerializeDates = true</code>
         and then runs <code>chrome.webview.hostObjects.sample.dateProperty = new Date()</code></label>
     <br />
     <button id="createRemoteDateButton">Set Remote Date</button>
-    <label for="createRemoteDateButton">Calls <code>chrome.webview.hostObjects.sample.createNativeDate()</code> 
+    <label for="createRemoteDateButton">Calls <code>chrome.webview.hostObjects.sample.createNativeDate()</code>
         to have the native object create and set the current time to the DateProperty</label>
     <code><pre><span id="dateOutput"></span></pre></code>
-    
+   
     <div id="div_iframe" style="display: none;">
         <h2>IFrame</h2>
     </div>
@@ -450,17 +450,17 @@ The web-side code of the Win32 sample app is now able to access the properties a
     <!-- todo: relate to the above code, why do the buttons appear dup'd in frame -->
 
     ```javascript
-    // Date property 
-    document.getElementById("setDateButton").addEventListener("click", () => { 
-        chrome.webview.hostObjects.options.shouldSerializeDates = true; 
-        chrome.webview.hostObjects.sync.sample.dateProperty = new Date(); 
-        document.getElementById("dateOutput").textContent = 
+    // Date property
+    document.getElementById("setDateButton").addEventListener("click", () => {
+        chrome.webview.hostObjects.options.shouldSerializeDates = true;
+        chrome.webview.hostObjects.sync.sample.dateProperty = new Date();
+        document.getElementById("dateOutput").textContent =
+            "sample.dateProperty: " + chrome.webview.hostObjects.sync.sample.dateProperty;
+    });
+    document.getElementById("createRemoteDateButton").addEventListener("click", () => {
+        chrome.webview.hostObjects.sync.sample.createNativeDate();
+        document.getElementById("dateOutput").textContent =
             "sample.dateProperty: " + chrome.webview.hostObjects.sync.sample.dateProperty;
-    }); 
-    document.getElementById("createRemoteDateButton").addEventListener("click", () => { 
-        chrome.webview.hostObjects.sync.sample.createNativeDate(); 
-        document.getElementById("dateOutput").textContent = 
-            "sample.dateProperty: " + chrome.webview.hostObjects.sync.sample.dateProperty; 
     });
     ```
 
diff --git a/microsoft-edge/webview2/how-to/javascript.md b/microsoft-edge/webview2/how-to/javascript.md
index 3d2a30fe64..80a9cccd3c 100644
--- a/microsoft-edge/webview2/how-to/javascript.md
+++ b/microsoft-edge/webview2/how-to/javascript.md
@@ -58,7 +58,7 @@ When executing script via `ExecuteScriptAsync` that script is run in the global
 
 For example:
 
-* If you run the script `const example = 10;` more than once, the subsequent times you run the script will throw an exception, because `example` was defined the first time you ran it. 
+* If you run the script `const example = 10;` more than once, the subsequent times you run the script will throw an exception, because `example` was defined the first time you ran it.
 
 * If you instead run the script `(() => { const example = 10; })();` the `example` variable is defined in the context of that anonymous function.  That way, it's not polluting the global context, and can be run more than once.
 
diff --git a/microsoft-edge/webview2/how-to/print.md b/microsoft-edge/webview2/how-to/print.md
index c1456231d2..840b465cc6 100644
--- a/microsoft-edge/webview2/how-to/print.md
+++ b/microsoft-edge/webview2/how-to/print.md
@@ -337,7 +337,7 @@ string GetPrinterName()
 }
 
 // Gets the print settings for the selected printer.
-// You can also get the capabilities from the native printer API, and display them 
+// You can also get the capabilities from the native printer API, and display them
 // to the user to get the print settings for the current webpage and for the selected printer.
 CoreWebView2PrintSettings GetSelectedPrinterPrintSettings(string printerName)
 {
@@ -401,7 +401,7 @@ async void PrintToPrinter(object sender, RoutedEventArgs e)
   await dialog.ShowAsync();
 }
 
-// Gets the printer name by displaying the list of installed printers to the user, 
+// Gets the printer name by displaying the list of installed printers to the user,
 // and returns the user-selected printer.
 string GetPrinterName()
 {
@@ -412,7 +412,7 @@ string GetPrinterName()
 }
 
 // Gets print settings for the selected printer.
-// You can also get the capabilities from the printer APIs, and display them to the 
+// You can also get the capabilities from the printer APIs, and display them to the
 // user to get the print settings for the current webpage and for the selected printer.
 CoreWebView2PrintSettings GetSelectedPrinterPrintSettings(string printerName)
 {
@@ -457,7 +457,7 @@ struct SamplePrintSettings
   std::wstring FooterUri = L"";
 };
 
-// Gets the printer name by displaying the list of installed printers to the user, 
+// Gets the printer name by displaying the list of installed printers to the user,
 // and returns the user-selected printer.
 std::wstring AppWindow::GetPrinterName()
 {
@@ -467,8 +467,8 @@ std::wstring AppWindow::GetPrinterName()
 }
 
 // Gets the print settings for the selected printer.
-// You can also get the capabilities from the native printer API, and display them 
-// to the user to get the print settings for the current webpage and for the 
+// You can also get the capabilities from the native printer API, and display them
+// to the user to get the print settings for the current webpage and for the
 // selected printer.
 SamplePrintSettings AppWindow::GetSelectedPrinterPrintSettings(std::wstring printerName)
 {
diff --git a/microsoft-edge/webview2/how-to/publish-uwp-app-store.md b/microsoft-edge/webview2/how-to/publish-uwp-app-store.md
index 9ee1f9ded2..923f484ef0 100644
--- a/microsoft-edge/webview2/how-to/publish-uwp-app-store.md
+++ b/microsoft-edge/webview2/how-to/publish-uwp-app-store.md
@@ -55,7 +55,7 @@ The [Microsoft Store](https://apps.microsoft.com) requires submitting a packaged
 1. In the dialog, note where the package bundle was placed.  This information is also shown in the build window.
 
 1. Click the **Close** button.
- 
+
 
 <!-- ====================================================================== -->
 ## Step 4: Test the package
@@ -134,7 +134,7 @@ If your app failed the **Supported API** test, update the Windows SDK to version
 
    * Approach 1: In Windows App Certification Kit (WACK), select **Project** > **Publish** > **Upload App Packages**.
 
-   * Approach 2: Go to Partner Center and upload your app package to the Windows Store through Partner Center. 
+   * Approach 2: Go to Partner Center and upload your app package to the Windows Store through Partner Center.
 
 
 <!-- ====================================================================== -->
diff --git a/microsoft-edge/webview2/how-to/remote-debugging-desktop.md b/microsoft-edge/webview2/how-to/remote-debugging-desktop.md
index cc19d4405d..d570378a65 100644
--- a/microsoft-edge/webview2/how-to/remote-debugging-desktop.md
+++ b/microsoft-edge/webview2/how-to/remote-debugging-desktop.md
@@ -1,6 +1,6 @@
 ---
 title: Remote debugging desktop WebView2 WinUI 2 (UWP) apps
-description: How to remotely debug desktop WebView2 WinUI 2 (UWP) apps by using Remote Tools for Microsoft Edge. 
+description: How to remotely debug desktop WebView2 WinUI 2 (UWP) apps by using Remote Tools for Microsoft Edge.
 author: MSEdgeTeam
 ms.author: msedgedevrel
 ms.topic: article
@@ -65,9 +65,9 @@ Attach Microsoft Edge DevTools remotely to a desktop WebView2 WinUI 2 (UWP) app
     ```
     "WEBVIEW2_ADDITIONAL_BROWSER_ARGUMENTS", "--enable-features=msEdgeDevToolsWdpRemoteDebugging"
     ```
-    
+   
     For example, if you're using the [WebView2 Sample UWP app](https://github.com/MicrosoftEdge/WebView2Samples/tree/main/SampleApps/webview2_sample_uwp), you can set the environment variable by adding the following line in the `Browser.xaml.cs` file:
-    
+   
     ```csharp
     Environment.SetEnvironmentVariable("WEBVIEW2_ADDITIONAL_BROWSER_ARGUMENTS", "--enable-features=msEdgeDevToolsWdpRemoteDebugging");
     ```
diff --git a/microsoft-edge/webview2/how-to/remote-debugging-hololens.md b/microsoft-edge/webview2/how-to/remote-debugging-hololens.md
index 26d6014995..542a0364da 100644
--- a/microsoft-edge/webview2/how-to/remote-debugging-hololens.md
+++ b/microsoft-edge/webview2/how-to/remote-debugging-hololens.md
@@ -1,6 +1,6 @@
 ---
 title: Remote debugging HoloLens 2 WebView2 WinUI 2 (UWP) apps
-description: How to remotely debug HoloLens 2 WebView2 WinUI 2 (UWP) apps by using Remote Tools for Microsoft Edge. 
+description: How to remotely debug HoloLens 2 WebView2 WinUI 2 (UWP) apps by using Remote Tools for Microsoft Edge.
 author: MSEdgeTeam
 ms.author: msedgedevrel
 ms.topic: article
@@ -12,7 +12,7 @@ ms.date: 09/27/2023
 
 To use [Microsoft Edge DevTools](/microsoft-edge/devtools/landing/) to debug a WebView2 WinUI 2 (UWP) app, use remote debugging.  Remote debugging is necessary for WebView2 WinUI 2 (UWP) apps because currently, the built-in DevTools can't be launched inside a store-signed WebView2 WinUI 2 (UWP) app.
 
-WebView2 on HoloLens 2 and the WebView plugin for Unity are both in Preview and are subject to change before general availability.  
+WebView2 on HoloLens 2 and the WebView plugin for Unity are both in Preview and are subject to change before general availability. 
 
 WebView2 and the WebView2 plugin are only supported on HoloLens 2 devices running the Windows 11 update. For more information, see [Update HoloLens 2](/hololens/hololens-update-hololens).
 
@@ -57,9 +57,9 @@ Attach Microsoft Edge DevTools remotely to a HoloLens 2 WebView2 WinUI 2 (UWP) a
     ```
     "WEBVIEW2_ADDITIONAL_BROWSER_ARGUMENTS", "--enable-features=msEdgeDevToolsWdpRemoteDebugging"
     ```
-    
+   
     For example, if you're using the [WebView2 Sample UWP app](https://github.com/MicrosoftEdge/WebView2Samples/tree/main/SampleApps/webview2_sample_uwp), you can set the environment variable by adding the following line in the `Browser.xaml.cs` file:
-    
+   
     ```csharp
     Environment.SetEnvironmentVariable("WEBVIEW2_ADDITIONAL_BROWSER_ARGUMENTS", "--enable-features=msEdgeDevToolsWdpRemoteDebugging");
     ```
diff --git a/microsoft-edge/webview2/how-to/remote-debugging-xbox.md b/microsoft-edge/webview2/how-to/remote-debugging-xbox.md
index f3ebb4b709..39ce610db2 100644
--- a/microsoft-edge/webview2/how-to/remote-debugging-xbox.md
+++ b/microsoft-edge/webview2/how-to/remote-debugging-xbox.md
@@ -81,9 +81,9 @@ Attach Microsoft Edge DevTools remotely to an XBOX WebView2 WinUI 2 (UWP) app as
     ```
     "WEBVIEW2_ADDITIONAL_BROWSER_ARGUMENTS", "--enable-features=msEdgeDevToolsWdpRemoteDebugging"
     ```
-    
+   
     For example, if you're using the [WebView2 Sample UWP app](https://github.com/MicrosoftEdge/WebView2Samples/tree/main/SampleApps/webview2_sample_uwp), you can set the environment variable by adding the following line in the `Browser.xaml.cs` file:
-    
+   
     ```csharp
     Environment.SetEnvironmentVariable("WEBVIEW2_ADDITIONAL_BROWSER_ARGUMENTS", "--enable-features=msEdgeDevToolsWdpRemoteDebugging");
     ```
diff --git a/microsoft-edge/webview2/how-to/remote-debugging.md b/microsoft-edge/webview2/how-to/remote-debugging.md
index 307b4d37e3..e139312147 100644
--- a/microsoft-edge/webview2/how-to/remote-debugging.md
+++ b/microsoft-edge/webview2/how-to/remote-debugging.md
@@ -1,6 +1,6 @@
 ---
 title: Remote debugging WebView2 WinUI 2 (UWP) apps
-description: How to remotely debug WebView2 WinUI 2 (UWP) apps. 
+description: How to remotely debug WebView2 WinUI 2 (UWP) apps.
 author: MSEdgeTeam
 ms.author: msedgedevrel
 ms.topic: article
diff --git a/microsoft-edge/webview2/how-to/set-preview-channel.md b/microsoft-edge/webview2/how-to/set-preview-channel.md
index 1d5c9f73ee..3b5481888a 100644
--- a/microsoft-edge/webview2/how-to/set-preview-channel.md
+++ b/microsoft-edge/webview2/how-to/set-preview-channel.md
@@ -9,7 +9,7 @@ ms.subservice: webview
 ms.date: 04/22/2024
 ---
 # Test upcoming APIs and features
-<!-- old title: 
+<!-- old title:
 # Switch to a preview channel to test upcoming APIs and features
 -->
 
diff --git a/microsoft-edge/webview2/how-to/webdriver.md b/microsoft-edge/webview2/how-to/webdriver.md
index 8404d9d9ad..4b116c1e66 100644
--- a/microsoft-edge/webview2/how-to/webdriver.md
+++ b/microsoft-edge/webview2/how-to/webdriver.md
@@ -244,7 +244,7 @@ For more info about the `DebuggerAddress` property of the `EdgeOptions` object,
    This WebView2 feature is currently only supported in the Canary preview channel of Microsoft Edge.  Set the environment variable `WEBVIEW2_RELEASE_CHANNEL_PREFERENCE=1`, to ensure that the WebView2 version is Canary.  For more information, see [How to set an environment variable](./set-preview-channel.md#how-to-set-an-environment-variable) in _Test upcoming APIs and features_.
 
    ![Settings for UWP app](./webdriver-images/sample-uwp-settings.png)
- 
+
 1. After you've launched the UWP WebView2 app, go to `http://<Device Portal URL>/msedge`.  For example, the following screenshot shows `localhost:50080/msedge`:
 
    ![Process ID of a running UWP app](./webdriver-images/sample-process-id.png)
diff --git a/microsoft-edge/webview2/how-to/webresourcerequested.md b/microsoft-edge/webview2/how-to/webresourcerequested.md
index 19938ac09d..fdafdb0c9d 100644
--- a/microsoft-edge/webview2/how-to/webresourcerequested.md
+++ b/microsoft-edge/webview2/how-to/webresourcerequested.md
@@ -42,7 +42,7 @@ The `WebResourceRequested` event is a low-level API that gives more control, but
 
 Instead of using the WebResourceRequested APIs, it's preferable to use these other approaches when feasible:
 * [Basic Authentication](/microsoft-edge/webview2/concepts/basic-authentication?tabs=csharp)
-* [General navigation](/microsoft-edge/webview2/concepts/navigation-events) 
+* [General navigation](/microsoft-edge/webview2/concepts/navigation-events)
 * [Managing cookies in WebView2](/microsoft-edge/webview2/reference/win32/icorewebview2)
 * Setting the user agent string.  See [UserAgent Property](/microsoft-edge/webview2/reference/winrt/microsoft_web_webview2_core/corewebview2settings#useragent).
 
@@ -64,7 +64,7 @@ the host app
 <!-- ====================================================================== -->
 ## Intercepting a request, to monitor or modify it
 
-Your host app can _intercept_ a request that is sent from the WebView2 control to the HTTP server, read or modify the request, and then send the unchanged or modified request to the HTTP server (or to local code instead of the HTTP server). 
+Your host app can _intercept_ a request that is sent from the WebView2 control to the HTTP server, read or modify the request, and then send the unchanged or modified request to the HTTP server (or to local code instead of the HTTP server).
 
 Intercepting the request allows you to customize the header content, URL, or the GET/POST method.  The host app may want to intercept a request to provide optional POST content as part of the request.
 
@@ -84,7 +84,7 @@ The host app can change the properties of a request by using this API:
 <!-- ------------------------------ -->
 #### What you can do with headers
 
-A HTTP header provides important information and metadata about a request or response.  Changing [headers](https://developer.mozilla.org/docs/Glossary/HTTP_header) enables you to perform powerful actions on the network. 
+A HTTP header provides important information and metadata about a request or response.  Changing [headers](https://developer.mozilla.org/docs/Glossary/HTTP_header) enables you to perform powerful actions on the network.
 
 A [request header](https://developer.mozilla.org/docs/Glossary/Request_header) can be used to indicate the format of the response (such as the `Accept-*` headers), set authentication tokens, read and write cookies (sensitive information), modify the user agent, and so on.  A [response header](https://developer.mozilla.org/docs/Glossary/Response_header) can be used to provide more context of the response.
 
@@ -113,10 +113,10 @@ For details about how the URL filter works, see [CoreWebView2.AddWebResourceRequ
 
 
 <!-- ------------------------------ -->
-#### Why would you want to intercept requests that are sent from WebView2?  
+#### Why would you want to intercept requests that are sent from WebView2? 
 
 Intercepting requests sent from WebView2 enables you to further configure your request. The host app might want to provide optional content as part of the request that the WebView2 control won't know on its own. Some scenarios include:
-* You're logging into a page and the app has credentials so the app can provide authentication header without the user having to enter those credentials.  
+* You're logging into a page and the app has credentials so the app can provide authentication header without the user having to enter those credentials. 
 * You want offline functionality in the app so you redirect the URL to a local file path when no internet connection is detected.
 * You want to upload local file content to the request server via a POST request.
 
@@ -147,7 +147,7 @@ Intercepting requests sent from WebView2 enables you to further configure your r
 <!-- this example doesn't exist in the sample repo -->
 
 <!-- the below intro is based on copying the main h2's Sentence 1 from above: -->
-In the following example, the host app _intercepts_ the document request that is sent from the WebView2 control to the `http://www.example.com` HTTP server, adds a custom header value and sends the request.  
+In the following example, the host app _intercepts_ the document request that is sent from the WebView2 control to the `http://www.example.com` HTTP server, adds a custom header value and sends the request. 
 
 ##### [.NET](#tab/dotnet)
 
@@ -197,7 +197,7 @@ m_webView->add_WebResourceRequested(
          })
          .Get(),
       &m_webResourceRequestedToken);
-```  
+``` 
 
 ---
 
@@ -238,7 +238,7 @@ webView.CoreWebView2.AddWebResourceRequestedFilter(
       "*", CoreWebView2WebResourceContext.Image);
 webView.CoreWebView2.WebResourceRequested += delegate (
    object sender, CoreWebView2WebResourceRequestedEventArgs args) {
-    
+   
    // Replace the remote image resource with a local one specified at the path customImagePath.
    // If response is not set, the request will continue as it is.
    FileStream fs = File.Open(customImagePath, FileMode.Open);
@@ -321,7 +321,7 @@ from https://github.com/MicrosoftEdge/WebView2Feedback/blob/main/specs/NavigateW
 ```csharp
 // This code posts text input=Hello to the POST form page in W3Schools.
 
-// Need to convert post data to UTF-8 as required by the application/x-www-form-urlencoded Content-Type 
+// Need to convert post data to UTF-8 as required by the application/x-www-form-urlencoded Content-Type
 UTF8Encoding utfEncoding = new UTF8Encoding();
 byte[] postData = utfEncoding.GetBytes("input=Hello");
 
@@ -330,7 +330,7 @@ postDataStream.Write(postData, 0, postData.Length);
 postDataStream.Seek(0, SeekOrigin.Begin);
 
 // This acts as a HTML form submit to https://www.w3schools.com/action_page.php
-CoreWebView2WebResourceRequest webResourceRequest = 
+CoreWebView2WebResourceRequest webResourceRequest =
 environment.CreateWebResourceRequest("https://www.w3schools.com/action_page.php",
                                      "POST",
                                      postDataStream,
@@ -345,7 +345,7 @@ webView.CoreWebView2.NavigateWithWebResourceRequest(webResourceRequest);
 ```cpp
 // This code posts text input=Hello to the POST form page in W3Schools.
 
-// Need to convert post data to UTF-8 as required by the application/x-www-form-urlencoded Content-Type 
+// Need to convert post data to UTF-8 as required by the application/x-www-form-urlencoded Content-Type
 std::wstring postData = std::wstring(L"input=Hello");
 int sizeNeededForMultiByte = WideCharToMultiByte(
    CP_UTF8, 0, postData.c_str(), postData.size(), nullptr,
@@ -450,7 +450,7 @@ m_webView->add_WebResourceResponseReceived(
             // The response object as received
             wil::com_ptr<ICoreWebView2WebResourceResponseView> webResourceResponse;
             args->get_Response(&webResourceResponse);
-            
+           
             // Get body content for the response
             webResourceResponse->GetContent(
                 Callback<
@@ -463,7 +463,7 @@ m_webView->add_WebResourceResponseReceived(
                         if (content) {
                             DoSomethingWithContent(content);
                         }
-                        
+                       
                         return S_OK;
                     })
                     .Get());
@@ -534,7 +534,7 @@ m_webView->add_WebResourceResponseReceived(
    * `remove_WebResourceRequested`
    * `RemoveWebResourceRequestedFilter`
 * [ICoreWebView2Environment2](/microsoft-edge/webview2/reference/win32/icorewebview2environment2)
-   * `CreateWebResourceRequest`   
+   * `CreateWebResourceRequest`  
 * [ICoreWebView2WebResourceRequest](/microsoft-edge/webview2/reference/win32/icorewebview2webresourcerequest)
    * `get_Content`
    * `get_Headers`
@@ -590,6 +590,6 @@ m_webView->add_WebResourceResponseReceived(
 * [Call native-side code from web-side code](hostobject.md)
 * [Web/native interop](../concepts/overview-features-apis.md#webnative-interop) in _Overview of WebView2 APIs_.
 
-<!-- 
+<!--
 * [NavigateWithWebResourceRequest spec](https://github.com/MicrosoftEdge/WebView2Feedback/blob/main/specs/NavigateWithWebResourceRequest.md)
 * [WebResourceResponseReceived event spec](https://github.com/MicrosoftEdge/WebView2Feedback/blob/main/specs/WebResourceResponseReceived.md) -->
diff --git a/microsoft-edge/webview2/how-to/winrt-from-js.md b/microsoft-edge/webview2/how-to/winrt-from-js.md
index 55cdddfcf0..f74ea08c6a 100644
--- a/microsoft-edge/webview2/how-to/winrt-from-js.md
+++ b/microsoft-edge/webview2/how-to/winrt-from-js.md
@@ -172,7 +172,7 @@ Let's get started!
 
 ##### [WinUI 3 (Windows App SDK)](#tab/winui3)
 
-1. Use the Visual Studio project template to create a fresh new solution and project.  To do this, do the steps in [Get started with WebView2 in WinUI 3 (Windows App SDK) apps](../get-started/winui.md) and then continue below. 
+1. Use the Visual Studio project template to create a fresh new solution and project.  To do this, do the steps in [Get started with WebView2 in WinUI 3 (Windows App SDK) apps](../get-started/winui.md) and then continue below.
 
    Or, if you have your own app code base already, you can open that project in Visual Studio, and add a **WinRTAdapter** project as shown below.
 
@@ -567,7 +567,7 @@ This section is for WinUI 3 (Windows App SDK) only.
 
 
 <!-- edit .csproj: -->
-1. In Visual Studio, select **File** > **Open** > **File**.  The **Open File** dialog opens. 
+1. In Visual Studio, select **File** > **Open** > **File**.  The **Open File** dialog opens.
 
 1. Open the `.csproj` file, such as `MyWebView2WinUI3.csproj`.
 
@@ -575,7 +575,7 @@ This section is for WinUI 3 (Windows App SDK) only.
 
 1. In the `.csproj` file, update the version number in the line `<TargetFramework>net6.0-windows10.0.19041.0</TargetFramework>` to be the same as the WinRT Adapter version you obtained above.
 
-   For example, change the line from: 
+   For example, change the line from:
 
    ```xml
    <TargetFramework>net6.0-windows10.0.19041.0</TargetFramework>
@@ -599,11 +599,13 @@ This section is for WinUI 3 (Windows App SDK) only.
 
 Add the CsWinRT and WinRTAdapter packages in the project file:
 
-1. In Visual Studio, select **File** > **Open** > **File**.  The **Open File** dialog opens. 
+1. In Visual Studio, select **File** > **Open** > **File**.
+
+   The **Open File** dialog opens.
 
 1. Open the `.csproj` file, such as `MyWebView2WinUI3.csproj`.
 
-1. Add the following `<PackageReference>` element within the `<ItemGroup>` element that already contains some `<PackageReference>` elements.  You can add it below the other `<PackageReference>` elements:
+1. Within the `<ItemGroup>` element that already contains some `<PackageReference>` elements, add the following `<PackageReference>` element below the other `<PackageReference>` elements:
 
    ```xml
    <ItemGroup>
@@ -638,7 +640,7 @@ This section is for WinUI 3 (Windows App SDK) only.
 
 1. Select **View** > **Error List**.
 
-   You might get the following error: 
+   You might get the following error:
 
    "WinRTAdapter.winmd cannot be referenced.  Referencing a Windows Metadata NETSDK1component directly when targeting .NET 5 or higher is not supported."
 
@@ -784,7 +786,7 @@ The host app's web-side code (and the DevTools Console) can now call methods and
 <!-- ------------------------------ -->
 #### Access projected APIs via DevTools Console
 
-Next, use the DevTools Console to demonstrate that web-side code can call the host-side APIs that were specified in the **wv2winrt** tool (the WebView2 WinRT JS Projection tool): 
+Next, use the DevTools Console to demonstrate that web-side code can call the host-side APIs that were specified in the **wv2winrt** tool (the WebView2 WinRT JS Projection tool):
 * [Windows.System.UserProfile Namespace](/uwp/api/windows.system.userprofile)
 * [Windows.Globalization.Language Class](/uwp/api/windows.globalization.language)
 
@@ -916,7 +918,7 @@ For more information, see the `forceAsyncMethodMatches` row in [CoreWebView2.Add
 <!-- ====================================================================== -->
 ## Subscribing to WinRT events
 
-WinRT events are also exposed via the script proxies. You can add and remove event handlers of instance WinRT events and static WinRT events by using the `addEventListener(string eventName, function handler)` and `removeEventListener(string eventName, function handler)` methods. 
+WinRT events are also exposed via the script proxies. You can add and remove event handlers of instance WinRT events and static WinRT events by using the `addEventListener(string eventName, function handler)` and `removeEventListener(string eventName, function handler)` methods.
 
 These methods work similarly to the DOM methods of the same name. Call `addEventListener` with a string name of the WinRT event you want to subscribe as the first parameter, and a function callback to be called whenever the event is raised. Calling `removeEventListener` with the same parameters unsubscribes from that event. For example:
 
diff --git a/microsoft-edge/webview2/how-to/winrt-js-conversion.md b/microsoft-edge/webview2/how-to/winrt-js-conversion.md
index 4103b2a5f2..7a83122d20 100644
--- a/microsoft-edge/webview2/how-to/winrt-js-conversion.md
+++ b/microsoft-edge/webview2/how-to/winrt-js-conversion.md
@@ -96,7 +96,7 @@ If a WinRT method name is overloaded for more than one method, then calling that
 
 If there is more than one overload that has a matching number of parameters, the first overload that's found in the metadata will be called.
 
- 
+
 <!-- ====================================================================== -->
 ## Method out parameters
 
@@ -105,16 +105,16 @@ If a WinRT method has `out` parameters, when calling that method from JavaScript
 When calling a WinRT method that has `out` parameters, any `out` parameters are skipped in the parameter list in the method call (unless they are array type).  For example, suppose a WinRT method that has `out` parameters and a non-`void` return type is defined as follows, using MIDL3:
 
 ```cpp
-String MethodWithOutParams(String stringParam1, 
-                           out Int32 intParam2, 
-                           out Int32 intParam3, 
+String MethodWithOutParams(String stringParam1,
+                           out Int32 intParam2,
+                           out Int32 intParam3,
                            String stringParam4);
 ```
 
 When you call that method from JavaScript, omit the `out` arguments:
 
 ```javascript
-let result = object.MethodWithOutParams("stringParam1", 
+let result = object.MethodWithOutParams("stringParam1",
                                         "stringParam4");
 ```
 
@@ -152,7 +152,7 @@ console.assert(result2 == [0, 1, 2]);
 ```
 
 If passing typed arrays as array `out` parameters, `chrome.webview.hostObjects.options.shouldPassTypedArraysAsArrays` needs to be set to `true`.
- 
+
 See also:
 * [Issue #2788](https://github.com/MicrosoftEdge/WebView2Feedback/issues/2788) about WebView2 SDK and Windows App SDK (WinUI3) in C++ WinRT
 
diff --git a/microsoft-edge/webview2/platforms/hololens-2-unity.md b/microsoft-edge/webview2/platforms/hololens-2-unity.md
index 8aa4d88de6..c9ce76b1e3 100644
--- a/microsoft-edge/webview2/platforms/hololens-2-unity.md
+++ b/microsoft-edge/webview2/platforms/hololens-2-unity.md
@@ -15,7 +15,7 @@ This article is for developers using WebView2 in immersive HoloLens 2 Unity appl
 > [!IMPORTANT]
 > WebView2 on Hololens 2 continues to be available.  However, support for WebView2 on Hololens 2 is discontinued; there are no planned bug fixes or content updates, and technical support has ended.  Applications that use WebView2 on Hololens 2 are not guaranteed to continue to work.
 
-WebView2 on HoloLens 2 and the WebView plugin for Unity are both in Preview and are subject to change before general availability.  
+WebView2 on HoloLens 2 and the WebView plugin for Unity are both in Preview and are subject to change before general availability. 
 
 WebView2 only works on HoloLens 2 devices running the Windows 11 update.  For more information, see [Update HoloLens 2](/hololens/hololens-update-hololens).
 
diff --git a/microsoft-edge/webview2/platforms/winui2-uwp.md b/microsoft-edge/webview2/platforms/winui2-uwp.md
index f91f88b2ae..ef033aef70 100644
--- a/microsoft-edge/webview2/platforms/winui2-uwp.md
+++ b/microsoft-edge/webview2/platforms/winui2-uwp.md
@@ -9,9 +9,29 @@ ms.subservice: webview
 ms.date: 01/27/2025
 ---
 # WebView2 in WinUI 2 (UWP) apps
+<!-- https://learn.microsoft.com/en-us/microsoft-edge/webview2/platforms/winui2-uwp -->
 
 The following considerations apply to WebView2 in WinUI 2 (UWP) apps.  The WebView2 WinUI 2 (UWP) control is in development.
 
+**Detailed contents:**
+* [Autofill UI](#autofill-ui)
+* [Print to PDF](#print-to-pdf)
+* [Default printing](#default-printing)
+* [SmartScreen](#smartscreen)
+* [Downloading files](#downloading-files)
+   * [Save As](#save-as)
+   * [Which folder the files are downloaded to](#which-folder-the-files-are-downloaded-to)
+   * [Downloads Hub](#downloads-hub)
+* [XAML limitation](#xaml-limitation)
+* [Setting DefaultBackgroundColor](#setting-defaultbackgroundcolor)
+* [Setting transparency](#setting-transparency)
+* [CSS cursors](#css-cursors)
+   * [Image URLs](#image-urls)
+   * [Predefined CSS cursors](#predefined-css-cursors)
+* [Microsoft Edge Developer Tools](#microsoft-edge-developer-tools)
+* [API limitations](#api-limitations)
+* [See also](#see-also)
+
 
 <!-- ====================================================================== -->
 ## Autofill UI
@@ -131,52 +151,51 @@ On WinUI 2 (UWP), some of the predefined CSS cursors are not supported.  You can
 
 | Keyword | Supported? |
 |---|:---:|
-| **General** |  |
-| auto | ✔️ |
-| default | ✔️ |
-| none | ❌ |
-| **Links & status** |  |
-| context-menu | ✔️ |
-| help | ✔️ |
-| pointer | ✔️ |
-| progress | ❌ |
-| wait | ✔️ |
-| **Selection** |  |
-| cell | ❌ |
-| crosshair | ✔️ |
-| text | ✔️ |
-| vertical-text | ❌ |
-| **Drag & drop** |  |
-| alias | ❌ |
-| copy | ❌ |
-| move | ✔️ |
-| no-drop | ✔️ |
-| not-allowed | ✔️ |
-| grab | ❌ |
-| grabbing | ❌ |
-| **Resizing & scrolling** |  |
-| all-scroll | ✔️ |
-| col-resize | ❌ |
-| row-resize | ❌ |
-| n-resize | ✔️ |
-| e-resize | ✔️ |
-| s-resize | ✔️ |
-| w-resize | ✔️ |
-| ne-resize | ✔️ |
-| nw-resize | ✔️ |
-| se-resize | ✔️ |
-| sw-resize | ✔️ |
-| ew-resize | ✔️ |
-| ns-resize | ✔️ |
-| nesw-resize | ✔️ |
-| nwse-resize | ✔️ |
-| **Zooming** |  |
-| zoom-in | ❌ |
-| zoom-out | ❌ |
+| **General:** | |
+| `auto` | ✔️ |
+| `default` | ✔️ |
+| `none` | ❌ |
+| **Links and status:** | |
+| `context-menu` | ✔️ |
+| `help` | ✔️ |
+| `pointer` | ✔️ |
+| `progress` | ❌ |
+| `wait` | ✔️ |
+| **Selection:** | |
+| `cell` | ❌ |
+| `crosshair` | ✔️ |
+| `text` | ✔️ |
+| `vertical-text` | ❌ |
+| **Drag and drop:** | |
+| `alias` | ❌ |
+| `copy` | ❌ |
+| `move` | ✔️ |
+| `no-drop` | ✔️ |
+| `not-allowed` | ✔️ |
+| `grab` | ❌ |
+| `grabbing` | ❌ |
+| **Resizing and scrolling:** | |
+| `all-scroll` | ✔️ |
+| `col-resize` | ❌ |
+| `row-resize` | ❌ |
+| `n-resize` | ✔️ |
+| `e-resize` | ✔️ |
+| `s-resize` | ✔️ |
+| `w-resize` | ✔️ |
+| `ne-resize` | ✔️ |
+| `nw-resize` | ✔️ |
+| `se-resize` | ✔️ |
+| `sw-resize` | ✔️ |
+| `ew-resize` | ✔️ |
+| `ns-resize` | ✔️ |
+| `nesw-resize` | ✔️ |
+| `nwse-resize` | ✔️ |
+| **Zooming:** | |
+| `zoom-in` | ❌ |
+| `zoom-out` | ❌ |
 
 See also:
-* [CSS cursors](https://developer.mozilla.org/docs/Web/CSS/cursor#values) - the **Values** section describes the above keyword values.
-<!-- known limitation: destination page doesn't scroll to anchor -->
+* [CSS cursors](https://developer.mozilla.org/docs/Web/CSS/cursor#values) - The **Values** section describes the above keyword values.
 
 
 <!-- ====================================================================== -->
diff --git a/microsoft-edge/webview2/platforms/winui3-windows-app-sdk.md b/microsoft-edge/webview2/platforms/winui3-windows-app-sdk.md
index 7cca4d4002..2929edb44a 100644
--- a/microsoft-edge/webview2/platforms/winui3-windows-app-sdk.md
+++ b/microsoft-edge/webview2/platforms/winui3-windows-app-sdk.md
@@ -98,7 +98,7 @@ Windows apps docs:
 Windows App SDK Reference:
 * [WebView2.EnsureCoreWebView2Async](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.webview2.ensurecorewebview2async)
 * [WebView2.Source property](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.webview2.source#microsoft-ui-xaml-controls-webview2-source)
-* [WebView2.EnsureCoreWebView2Async method](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.webview2.ensurecorewebview2async#microsoft-ui-xaml-controls-webview2-ensurecorewebview2async) 
+* [WebView2.EnsureCoreWebView2Async method](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.webview2.ensurecorewebview2async#microsoft-ui-xaml-controls-webview2-ensurecorewebview2async)
 
 WebView2 Reference:
 * [CoreWebView2ControllerOptions](/microsoft-edge/webview2/reference/winrt/microsoft_web_webview2_core/corewebview2controlleroptions)
@@ -106,4 +106,4 @@ WebView2 Reference:
 * [CoreWebView2EnvironmentOptions](/microsoft-edge/webview2/reference/winrt/microsoft_web_webview2_core/corewebview2environmentoptions)
 
 Windows Security docs:
-* [SmartScreen](/windows/security/threat-protection/microsoft-defender-smartscreen/microsoft-defender-smartscreen-overview) 
+* [SmartScreen](/windows/security/threat-protection/microsoft-defender-smartscreen/microsoft-defender-smartscreen-overview)
diff --git a/microsoft-edge/webview2/reference/javascript/sharedbufferreceivedevent.yml b/microsoft-edge/webview2/reference/javascript/sharedbufferreceivedevent.yml
index ddd2071efc..8339348f35 100644
--- a/microsoft-edge/webview2/reference/javascript/sharedbufferreceivedevent.yml
+++ b/microsoft-edge/webview2/reference/javascript/sharedbufferreceivedevent.yml
@@ -43,7 +43,7 @@ remarks: |-
   ```
 
   In the HTML document, subscribe to and handle sharedbufferreceived event.
-  
+ 
   Next, in the HTML document, subscribe to and then handle the `sharedbufferreceived` event:
 
   ```html
diff --git a/microsoft-edge/webview2/release-notes/includes/runtime-preview-template.md b/microsoft-edge/webview2/release-notes/includes/runtime-preview-template.md
index 542567a15b..facbe1b07e 100644
--- a/microsoft-edge/webview2/release-notes/includes/runtime-preview-template.md
+++ b/microsoft-edge/webview2/release-notes/includes/runtime-preview-template.md
@@ -20,13 +20,13 @@ This is a Preview Runtime, for early testing.  Prerelease testing of WebView2 SD
 <!-- ====================================================================== -->
 #### Bug fixes
 
-* Fixed behavior.  ([Issue #]())
+* Fixed behavior.  ([Issue #] ())
 
 
 <!-- ====================================================================== -->
 ## See also
 
-* [SDK n.n.nnnn-prerelease, for Runtime nnn (Mmm. dd, yyyy)](../sdk/n-n-nnnn-prerelease.md)
+* [SDK n.n.nnnn-prerelease, for Runtime nnn (Mmm. dd, yyyy)] (../sdk/n-n-nnnn-prerelease.md)
 * [Release notes for WebView2](../index.md)
    * [Release notes for the WebView2 Runtime](./index.md)
    * [Release notes for WebView2 SDKs](../sdk/index.md)
diff --git a/microsoft-edge/webview2/release-notes/includes/runtime-template.md b/microsoft-edge/webview2/release-notes/includes/runtime-template.md
index 4ce2a174ac..253d85972b 100644
--- a/microsoft-edge/webview2/release-notes/includes/runtime-template.md
+++ b/microsoft-edge/webview2/release-notes/includes/runtime-template.md
@@ -16,14 +16,14 @@ Release notes for Microsoft Edge WebView2 Runtime, release date: Mmm. dd, yyyy.
 <!-- ====================================================================== -->
 ## Bug fixes
 
-* Fixed behavior.  ([Issue #]())
+* Fixed behavior.  ([Issue #] ())
 
 
 <!-- ====================================================================== -->
 ## See also
 
-* [SDK n.n.nnnn.nn, for Runtime nnn (Mmm. dd, yyyy)](../sdk/n-n-nnnn-nn.md)
-* [SDK n.n.nnnn-prerelease, for Runtime nnn (Mmm. dd, yyyy)](../sdk/n-n-nnnn-prerelease.md)
+* [SDK n.n.nnnn.nn, for Runtime nnn (Mmm. dd, yyyy)] (../sdk/n-n-nnnn-nn.md)
+* [SDK n.n.nnnn-prerelease, for Runtime nnn (Mmm. dd, yyyy)] (../sdk/n-n-nnnn-prerelease.md)
 * [Release notes for WebView2](../index.md)
    * [Release notes for the WebView2 Runtime](./index.md)
    * [Release notes for WebView2 SDKs](../sdk/index.md)
diff --git a/microsoft-edge/webview2/release-notes/includes/sdk-prerelease-template.md b/microsoft-edge/webview2/release-notes/includes/sdk-prerelease-template.md
index 61a0871715..d6dfdb2f33 100644
--- a/microsoft-edge/webview2/release-notes/includes/sdk-prerelease-template.md
+++ b/microsoft-edge/webview2/release-notes/includes/sdk-prerelease-template.md
@@ -12,7 +12,7 @@ ms.date: 01/01/2026
 
 Release notes for Microsoft Edge WebView2 Prerelease SDK, release date: Mmm. dd, yyyy.
 
-[NuGet package for WebView2 SDK 1.0.####-prerelease](https://www.nuget.org/packages/Microsoft.Web.WebView2/n.n.nnnn-prerelease)
+[NuGet package for WebView2 SDK n.n.nnnn-prerelease] (https://www.nuget.org/packages/Microsoft.Web.WebView2/n.n.nnnn-prerelease)
 
 For full API compatibility, this Prerelease version of the WebView2 SDK requires the WebView2 Runtime that ships with Microsoft Edge version nnn.n.nnnn.n or later.
 
@@ -67,7 +67,7 @@ The following APIs skipped Phase 1: Experimental in Prerelease, and have been di
 
 description
 
-Previous phase: [~](./~.md#~) in _~_.
+Previous phase: [~] (./~.md#~) in _~_.
 
 ##### [.NET/C#](#tab/dotnetcsharp)
 
@@ -81,10 +81,13 @@ Previous phase: [~](./~.md#~) in _~_.
 <!-- ====================================================================== -->
 ## Bug fixes
 
-* Fixed behavior.  ([Issue #]())
+* Fixed behavior.  ([Issue #] ())
 
 
 <!-- ====================================================================== -->
 ## See also
 
-* [Release notes for WebView2](./index.md)
+* [Runtime nnn.n.nnnn.nn (Mmm. dd, yyyy)] (../runtime/nnn.md)
+* [Release notes for WebView2](../index.md)
+   * [Release notes for the WebView2 Runtime](../runtime/index.md)
+   * [Release notes for WebView2 SDKs](./index.md)
diff --git a/microsoft-edge/webview2/release-notes/includes/sdk-release-template.md b/microsoft-edge/webview2/release-notes/includes/sdk-release-template.md
index 49a7204135..b72d8f1e78 100644
--- a/microsoft-edge/webview2/release-notes/includes/sdk-release-template.md
+++ b/microsoft-edge/webview2/release-notes/includes/sdk-release-template.md
@@ -8,11 +8,11 @@ ms.service: microsoft-edge
 ms.subservice: webview
 ms.date: 01/01/2026
 ---
-# SDK 1.0.nnnn.nn, for Runtime nnn (Mmm. dd, yyyy)
+# SDK n.n.nnnn.nn, for Runtime nnn (Mmm. dd, yyyy)
 
 Release notes for Microsoft Edge WebView2 SDK, release date: Mmm. dd, yyyy.
 
-[NuGet package for WebView2 SDK 1.0.####.##](https://www.nuget.org/packages/Microsoft.Web.WebView2/n.n.nnnn.nn)
+[NuGet package for WebView2 SDK n.n.nnnn.nn] (https://www.nuget.org/packages/Microsoft.Web.WebView2/n.n.nnnn.nn)
 
 For full API compatibility, this Release version of the WebView2 SDK requires WebView2 Runtime version nnn.n.nnnn.nn or later.
 
@@ -46,7 +46,7 @@ The following APIs have been promoted from Phase 2: Stable in Prerelease, to Pha
 
 description
 
-Previous phase: [~](./~.md#~) in _~_.
+Previous phase: [~] (./~.md#~) in _~_.
 
 ##### [.NET/C#](#tab/dotnetcsharp)
 
@@ -60,10 +60,13 @@ Previous phase: [~](./~.md#~) in _~_.
 <!-- ====================================================================== -->
 ## Bug fixes
 
-* Fixed behavior.  ([Issue #]())
+* Fixed behavior.  ([Issue #] ())
 
 
 <!-- ====================================================================== -->
 ## See also
 
-* [Release notes for WebView2](./index.md)
+* [Runtime nnn.n.nnnn.nn (Mmm. dd, yyyy)] (../runtime/nnn.md)
+* [Release notes for WebView2](../index.md)
+   * [Release notes for the WebView2 Runtime](../runtime/index.md)
+   * [Release notes for WebView2 SDKs](./index.md)
diff --git a/microsoft-edge/webview2/release-notes/index.md b/microsoft-edge/webview2/release-notes/index.md
index 90aa6993e4..ae3adf6769 100644
--- a/microsoft-edge/webview2/release-notes/index.md
+++ b/microsoft-edge/webview2/release-notes/index.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 08/05/2026
+ms.date: 08/24/2026
 ---
 # Release notes for WebView2
 
@@ -22,9 +22,3 @@ Release notes for the WebView2 Runtime and for WebView2 SDKs.
 * [Contact the WebView2 team](../contact.md)<!-- toc bucket: bottom -->
 * [Release notes for Microsoft Edge web platform](../../web-platform/release-notes/index.md)
 * [Microsoft Edge release schedule](/deployedge/microsoft-edge-release-schedule)
-
-API Reference:
-* [WebView2 API Reference](../webview2-api-reference.md)
-   * .NET: [Microsoft.Web.WebView2.Core Namespace](/dotnet/api/microsoft.web.webview2.core)<!-- https://learn.microsoft.com/dotnet/api/microsoft.web.webview2.core -->
-   * WinRT: [Microsoft.Web.WebView2.Core Namespace](/microsoft-edge/webview2/reference/winrt/microsoft_web_webview2_core/)<!-- https://learn.microsoft.com/microsoft-edge/webview2/reference/winrt/microsoft_web_webview2_core/ -->
-   * Win32: [Reference (WebView2 Win32 C++)](/microsoft-edge/webview2/reference/win32/)<!-- https://learn.microsoft.com/microsoft-edge/webview2/reference/win32/ -->
diff --git a/microsoft-edge/webview2/release-notes/runtime/100.md b/microsoft-edge/webview2/release-notes/runtime/100.md
index 1ca5c05095..4372581f30 100644
--- a/microsoft-edge/webview2/release-notes/runtime/100.md
+++ b/microsoft-edge/webview2/release-notes/runtime/100.md
@@ -6,7 +6,8 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 01/01/2025
+ms.date: 04/12/2022
+
 ---
 # Runtime 100.0.1185.39 (Apr. 12, 2022)
 
diff --git a/microsoft-edge/webview2/release-notes/runtime/101.md b/microsoft-edge/webview2/release-notes/runtime/101.md
index ef9db7d5fb..1d1df85ae4 100644
--- a/microsoft-edge/webview2/release-notes/runtime/101.md
+++ b/microsoft-edge/webview2/release-notes/runtime/101.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 01/01/2025
+ms.date: 05/09/2022
 ---
 # Runtime 101.0.1210.39 (May 9, 2022)
 
diff --git a/microsoft-edge/webview2/release-notes/runtime/102.md b/microsoft-edge/webview2/release-notes/runtime/102.md
index 227b32a8b8..002e3eb793 100644
--- a/microsoft-edge/webview2/release-notes/runtime/102.md
+++ b/microsoft-edge/webview2/release-notes/runtime/102.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 01/01/2025
+ms.date: 06/14/2022
 ---
 # Runtime 102.0.1245.22 (Jun. 14, 2022)
 
diff --git a/microsoft-edge/webview2/release-notes/runtime/103.md b/microsoft-edge/webview2/release-notes/runtime/103.md
index c8a888defe..9abdef1493 100644
--- a/microsoft-edge/webview2/release-notes/runtime/103.md
+++ b/microsoft-edge/webview2/release-notes/runtime/103.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 01/01/2025
+ms.date: 07/04/2022
 ---
 # Runtime 103.0.1264.42 (Jul. 4, 2022)
 
diff --git a/microsoft-edge/webview2/release-notes/runtime/104.md b/microsoft-edge/webview2/release-notes/runtime/104.md
index 4a3c22af43..736a506bd3 100644
--- a/microsoft-edge/webview2/release-notes/runtime/104.md
+++ b/microsoft-edge/webview2/release-notes/runtime/104.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 01/01/2025
+ms.date: 08/08/2022
 ---
 # Runtime 104.0.1293.44 (Aug. 8, 2022)
 
diff --git a/microsoft-edge/webview2/release-notes/runtime/105.md b/microsoft-edge/webview2/release-notes/runtime/105.md
index d9ff4df28b..6ee70e366b 100644
--- a/microsoft-edge/webview2/release-notes/runtime/105.md
+++ b/microsoft-edge/webview2/release-notes/runtime/105.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 01/01/2025
+ms.date: 09/06/2022
 ---
 # Runtime 105.0.1343.22 (Sep. 6, 2022)
 
diff --git a/microsoft-edge/webview2/release-notes/runtime/106.md b/microsoft-edge/webview2/release-notes/runtime/106.md
index e155bb7473..9fd3828cc9 100644
--- a/microsoft-edge/webview2/release-notes/runtime/106.md
+++ b/microsoft-edge/webview2/release-notes/runtime/106.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 01/01/2025
+ms.date: 10/11/2022
 ---
 # Runtime 106.0.1370.28 (Oct. 11, 2022)
 
diff --git a/microsoft-edge/webview2/release-notes/runtime/107.md b/microsoft-edge/webview2/release-notes/runtime/107.md
index a769729c89..a0b23ca670 100644
--- a/microsoft-edge/webview2/release-notes/runtime/107.md
+++ b/microsoft-edge/webview2/release-notes/runtime/107.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 01/01/2025
+ms.date: 10/31/2022
 ---
 # Runtime 107.0.1418.22 (Oct. 31, 2022)
 
diff --git a/microsoft-edge/webview2/release-notes/runtime/108.md b/microsoft-edge/webview2/release-notes/runtime/108.md
index 40cc8258e5..a67ad031bb 100644
--- a/microsoft-edge/webview2/release-notes/runtime/108.md
+++ b/microsoft-edge/webview2/release-notes/runtime/108.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 01/01/2025
+ms.date: 12/12/2022
 ---
 # Runtime 108.0.1462.37 (Dec. 12, 2022)
 
diff --git a/microsoft-edge/webview2/release-notes/runtime/109.md b/microsoft-edge/webview2/release-notes/runtime/109.md
index 12eff52213..b9c934f7a1 100644
--- a/microsoft-edge/webview2/release-notes/runtime/109.md
+++ b/microsoft-edge/webview2/release-notes/runtime/109.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 01/01/2025
+ms.date: 01/17/2023
 ---
 # Runtime 109.0.1518.46 (Jan. 17, 2023)
 
diff --git a/microsoft-edge/webview2/release-notes/runtime/110.md b/microsoft-edge/webview2/release-notes/runtime/110.md
index 60072df612..71ca9476a4 100644
--- a/microsoft-edge/webview2/release-notes/runtime/110.md
+++ b/microsoft-edge/webview2/release-notes/runtime/110.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 01/01/2025
+ms.date: 02/15/2023
 ---
 # Runtime 110.0.1587.40 (Feb. 15, 2023)
 
diff --git a/microsoft-edge/webview2/release-notes/runtime/111.md b/microsoft-edge/webview2/release-notes/runtime/111.md
index e69083d764..e38d2fab4d 100644
--- a/microsoft-edge/webview2/release-notes/runtime/111.md
+++ b/microsoft-edge/webview2/release-notes/runtime/111.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 01/01/2025
+ms.date: 03/20/2023
 ---
 # Runtime 111.0.1661.34 (Mar. 20, 2023)
 
diff --git a/microsoft-edge/webview2/release-notes/runtime/112.md b/microsoft-edge/webview2/release-notes/runtime/112.md
index e879ad38f1..65fce3e3a7 100644
--- a/microsoft-edge/webview2/release-notes/runtime/112.md
+++ b/microsoft-edge/webview2/release-notes/runtime/112.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 01/01/2025
+ms.date: 04/13/2023
 ---
 # Runtime 112.0.1722.45 (Apr. 13, 2023)
 
diff --git a/microsoft-edge/webview2/release-notes/runtime/113.md b/microsoft-edge/webview2/release-notes/runtime/113.md
index 6dafe04edb..8d93484eb8 100644
--- a/microsoft-edge/webview2/release-notes/runtime/113.md
+++ b/microsoft-edge/webview2/release-notes/runtime/113.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 01/01/2025
+ms.date: 05/08/2023
 ---
 # Runtime 113.0.1774.30 (May 8, 2023)
 
diff --git a/microsoft-edge/webview2/release-notes/runtime/114.md b/microsoft-edge/webview2/release-notes/runtime/114.md
index c2532af883..9e46e89d5e 100644
--- a/microsoft-edge/webview2/release-notes/runtime/114.md
+++ b/microsoft-edge/webview2/release-notes/runtime/114.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 01/01/2025
+ms.date: 06/05/2023
 ---
 # Runtime 114.0.1823.32 (Jun. 5, 2023)
 
diff --git a/microsoft-edge/webview2/release-notes/runtime/115.md b/microsoft-edge/webview2/release-notes/runtime/115.md
index 6586bc5052..7469973128 100644
--- a/microsoft-edge/webview2/release-notes/runtime/115.md
+++ b/microsoft-edge/webview2/release-notes/runtime/115.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 01/01/2025
+ms.date: 07/24/2023
 ---
 # Runtime 115.0.1901.177 (Jul. 24, 2023)
 
diff --git a/microsoft-edge/webview2/release-notes/runtime/116.md b/microsoft-edge/webview2/release-notes/runtime/116.md
index dabbc5db31..8a03f32618 100644
--- a/microsoft-edge/webview2/release-notes/runtime/116.md
+++ b/microsoft-edge/webview2/release-notes/runtime/116.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 01/01/2025
+ms.date: 08/28/2023
 ---
 # Runtime 116.0.1938.49 (Aug. 28, 2023)
 
diff --git a/microsoft-edge/webview2/release-notes/runtime/117.md b/microsoft-edge/webview2/release-notes/runtime/117.md
index 1962319a5d..404aa1eeb7 100644
--- a/microsoft-edge/webview2/release-notes/runtime/117.md
+++ b/microsoft-edge/webview2/release-notes/runtime/117.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 01/01/2025
+ms.date: 09/18/2023
 ---
 # Runtime 117.0.2045.28 (Sep. 18, 2023)
 
diff --git a/microsoft-edge/webview2/release-notes/runtime/118.md b/microsoft-edge/webview2/release-notes/runtime/118.md
index 117ea07033..7a37f37806 100644
--- a/microsoft-edge/webview2/release-notes/runtime/118.md
+++ b/microsoft-edge/webview2/release-notes/runtime/118.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 01/01/2025
+ms.date: 10/16/2023
 ---
 # Runtime 118.0.2088.41 (Oct. 16, 2023)
 
diff --git a/microsoft-edge/webview2/release-notes/runtime/119.md b/microsoft-edge/webview2/release-notes/runtime/119.md
index fd4718d25a..0b0e67b543 100644
--- a/microsoft-edge/webview2/release-notes/runtime/119.md
+++ b/microsoft-edge/webview2/release-notes/runtime/119.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 01/01/2025
+ms.date: 11/06/2023
 ---
 # Runtime 119.0.2151.40 (Nov. 6, 2023)
 
diff --git a/microsoft-edge/webview2/release-notes/runtime/120.md b/microsoft-edge/webview2/release-notes/runtime/120.md
index 8305a9242a..f892b72729 100644
--- a/microsoft-edge/webview2/release-notes/runtime/120.md
+++ b/microsoft-edge/webview2/release-notes/runtime/120.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 01/01/2025
+ms.date: 12/11/2023
 ---
 # Runtime 120.0.2210.55 (Dec. 11, 2023)
 
diff --git a/microsoft-edge/webview2/release-notes/runtime/121.md b/microsoft-edge/webview2/release-notes/runtime/121.md
index d2ece1e118..a5f77a99de 100644
--- a/microsoft-edge/webview2/release-notes/runtime/121.md
+++ b/microsoft-edge/webview2/release-notes/runtime/121.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 01/01/2025
+ms.date: 02/05/2024
 ---
 # Runtime 121.0.2277.86 (Feb. 5, 2024)
 
diff --git a/microsoft-edge/webview2/release-notes/runtime/122.md b/microsoft-edge/webview2/release-notes/runtime/122.md
index a4ec199994..305f52c65e 100644
--- a/microsoft-edge/webview2/release-notes/runtime/122.md
+++ b/microsoft-edge/webview2/release-notes/runtime/122.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 01/01/2025
+ms.date: 02/26/2024
 ---
 # Runtime 122.0.2365.46 (Feb. 26, 2024)
 
diff --git a/microsoft-edge/webview2/release-notes/runtime/123.md b/microsoft-edge/webview2/release-notes/runtime/123.md
index 438fe82824..bfe0cc1be6 100644
--- a/microsoft-edge/webview2/release-notes/runtime/123.md
+++ b/microsoft-edge/webview2/release-notes/runtime/123.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 01/01/2025
+ms.date: 03/25/2024
 ---
 # Runtime 123.0.2420.47 (Mar. 25, 2024)
 
diff --git a/microsoft-edge/webview2/release-notes/runtime/124.md b/microsoft-edge/webview2/release-notes/runtime/124.md
index 22112d8692..a8b1e1eea1 100644
--- a/microsoft-edge/webview2/release-notes/runtime/124.md
+++ b/microsoft-edge/webview2/release-notes/runtime/124.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 01/01/2025
+ms.date: 04/22/2024
 ---
 # Runtime 124.0.2478.35 (Apr. 22, 2024)
 
diff --git a/microsoft-edge/webview2/release-notes/runtime/125.md b/microsoft-edge/webview2/release-notes/runtime/125.md
index 7edb931d5d..04a5e37bf9 100644
--- a/microsoft-edge/webview2/release-notes/runtime/125.md
+++ b/microsoft-edge/webview2/release-notes/runtime/125.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 01/01/2025
+ms.date: 05/28/2024
 ---
 # Runtime 125.0.2535.41 (May 28, 2024)
 
diff --git a/microsoft-edge/webview2/release-notes/runtime/126.md b/microsoft-edge/webview2/release-notes/runtime/126.md
index 8a909cc743..a2755dfc2c 100644
--- a/microsoft-edge/webview2/release-notes/runtime/126.md
+++ b/microsoft-edge/webview2/release-notes/runtime/126.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 01/01/2025
+ms.date: 06/19/2024
 ---
 # Runtime 126.0.2592.51 (Jun. 19, 2024)
 
diff --git a/microsoft-edge/webview2/release-notes/runtime/127.md b/microsoft-edge/webview2/release-notes/runtime/127.md
index b76f7d1431..fd2f990b60 100644
--- a/microsoft-edge/webview2/release-notes/runtime/127.md
+++ b/microsoft-edge/webview2/release-notes/runtime/127.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 01/01/2025
+ms.date: 08/13/2024
 ---
 # Runtime 127.0.2651.64 (Aug. 13, 2024)
 
diff --git a/microsoft-edge/webview2/release-notes/runtime/128.md b/microsoft-edge/webview2/release-notes/runtime/128.md
index c221c2108f..0efd755f32 100644
--- a/microsoft-edge/webview2/release-notes/runtime/128.md
+++ b/microsoft-edge/webview2/release-notes/runtime/128.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 01/01/2025
+ms.date: 08/26/2024
 ---
 # Runtime 128.0.2739.15 (Aug. 26, 2024)
 
diff --git a/microsoft-edge/webview2/release-notes/runtime/129.md b/microsoft-edge/webview2/release-notes/runtime/129.md
index 9bd83440ec..9b9e9e43d9 100644
--- a/microsoft-edge/webview2/release-notes/runtime/129.md
+++ b/microsoft-edge/webview2/release-notes/runtime/129.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 01/01/2025
+ms.date: 09/23/2024
 ---
 # Runtime 129.0.2792.45 (Sep. 23, 2024)
 
diff --git a/microsoft-edge/webview2/release-notes/runtime/130.md b/microsoft-edge/webview2/release-notes/runtime/130.md
index 03adf7e601..efd77c9914 100644
--- a/microsoft-edge/webview2/release-notes/runtime/130.md
+++ b/microsoft-edge/webview2/release-notes/runtime/130.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 01/01/2025
+ms.date: 10/21/2024
 ---
 # Runtime 130.0.2849.39 (Oct. 21, 2024)
 
diff --git a/microsoft-edge/webview2/release-notes/runtime/131.md b/microsoft-edge/webview2/release-notes/runtime/131.md
index 14267e6af7..fb4ac1cc2c 100644
--- a/microsoft-edge/webview2/release-notes/runtime/131.md
+++ b/microsoft-edge/webview2/release-notes/runtime/131.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 01/01/2025
+ms.date: 11/18/2024
 ---
 # Runtime 131.0.2903.40 (Nov. 18, 2024)
 
diff --git a/microsoft-edge/webview2/release-notes/runtime/132.md b/microsoft-edge/webview2/release-notes/runtime/132.md
index de464e01e0..387d8b70fd 100644
--- a/microsoft-edge/webview2/release-notes/runtime/132.md
+++ b/microsoft-edge/webview2/release-notes/runtime/132.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 01/01/2025
+ms.date: 01/20/2025
 ---
 # Runtime 132.0.2957.106 (Jan. 20, 2025)
 
diff --git a/microsoft-edge/webview2/release-notes/runtime/133.md b/microsoft-edge/webview2/release-notes/runtime/133.md
index 7b18a7acb8..58ac4e5efe 100644
--- a/microsoft-edge/webview2/release-notes/runtime/133.md
+++ b/microsoft-edge/webview2/release-notes/runtime/133.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 01/01/2025
+ms.date: 02/10/2025
 ---
 # Runtime 133.0.3065.39 (Feb. 10, 2025)
 
diff --git a/microsoft-edge/webview2/release-notes/runtime/134.md b/microsoft-edge/webview2/release-notes/runtime/134.md
index a42789abd5..f2593c92c0 100644
--- a/microsoft-edge/webview2/release-notes/runtime/134.md
+++ b/microsoft-edge/webview2/release-notes/runtime/134.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 01/01/2025
+ms.date: 03/10/2025
 ---
 # Runtime 134.0.3124.44 (Mar. 10, 2025)
 
diff --git a/microsoft-edge/webview2/release-notes/runtime/152.md b/microsoft-edge/webview2/release-notes/runtime/152.md
index 1f428e077e..5d0b8379fa 100644
--- a/microsoft-edge/webview2/release-notes/runtime/152.md
+++ b/microsoft-edge/webview2/release-notes/runtime/152.md
@@ -1,20 +1,16 @@
 ---
-title: Preview Runtime 152.0.4181.0 (Aug. 3, 2026)
-description: Release notes for Microsoft Edge WebView2 Preview Runtime 152.0.4181.0.
+title: Runtime 152.n.nnnn.nn (Mmm. dd, yyyy)
+description: Release notes for Microsoft Edge WebView2 Preview Runtime.
 author: MSEdgeTeam
 ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 08/03/2026
+ms.date: 08/24/2026
 ---
-# Preview Runtime 152.0.4181.0 (Aug. 3, 2026)
-<!-- todo: when this runtime gets released as a stable runtime, remove "preview" from title, update version number, update date, update lead-in sentence; same format as regular sibling .md -->
+# Runtime 152.n.nnnn.nn (Mmm. dd, yyyy)
 
-Release notes for Microsoft Edge WebView2 Preview Runtime, release date: Aug. 3, 2026.
-
-<!-- todo: remove paragraph when this runtime gets released as a stable runtime -->
-This is a Preview Runtime, for early testing.  Prerelease testing of WebView2 SDKs uses a preview channel of Microsoft Edge (Beta, Dev, or Canary), which includes the WebView2 Preview Runtime.  See [Prerelease testing using preview channels](../../how-to/prerelease-testing.md).
+Release notes for Microsoft Edge WebView2 Runtime, release date: Mmm. dd, yyyy.
 
 
 <!-- ====================================================================== -->
@@ -40,6 +36,7 @@ This is a Preview Runtime, for early testing.  Prerelease testing of WebView2 SD
 <!-- ====================================================================== -->
 ## See also
 
+* [SDK n.n.nnnn.nn, for Runtime 152 (Mmm. dd, yyyy)](../sdk/1-0-nnnn-nn.md)
 * [SDK 1.0.4181-prerelease, for Runtime 152 (Aug. 3, 2026)](../sdk/1-0-4181-prerelease.md)
 * [Release notes for WebView2](../index.md)
    * [Release notes for the WebView2 Runtime](./index.md)
diff --git a/microsoft-edge/webview2/release-notes/runtime/153.md b/microsoft-edge/webview2/release-notes/runtime/153.md
new file mode 100644
index 0000000000..499a2fbf3c
--- /dev/null
+++ b/microsoft-edge/webview2/release-notes/runtime/153.md
@@ -0,0 +1,32 @@
+---
+title: Preview Runtime 153.n.nnnn.nn (Mmm. dd, yyyy)
+description: Release notes for Microsoft Edge WebView2 Preview Runtime 153.0.nnnn.nn.
+author: MSEdgeTeam
+ms.author: msedgedevrel
+ms.topic: article
+ms.service: microsoft-edge
+ms.subservice: webview
+ms.date: 08/24/2026
+---
+# Preview Runtime 153.n.nnnn.nn (Mmm. dd, yyyy)
+<!-- todo: when this runtime gets released as a stable runtime, remove "preview" from title, update version number, update date, update lead-in sentence; same format as regular sibling .md -->
+
+Release notes for Microsoft Edge WebView2 Preview Runtime, release date: Mmm. dd, yyyy.
+
+<!-- todo: remove paragraph when this runtime gets released as a stable runtime -->
+This is a Preview Runtime, for early testing.  Prerelease testing of WebView2 SDKs uses a preview channel of Microsoft Edge (Beta, Dev, or Canary), which includes the WebView2 Preview Runtime.  See [Prerelease testing using preview channels](../../how-to/prerelease-testing.md).
+
+
+<!-- ====================================================================== -->
+#### Bug fixes
+
+* Fixed behavior.  ([Issue #] ())
+
+
+<!-- ====================================================================== -->
+## See also
+
+* [SDK n.n.nnnn-prerelease, for Runtime nnn (Mmm. dd, yyyy)] (../sdk/n-n-nnnn-prerelease.md)
+* [Release notes for WebView2](../index.md)
+   * [Release notes for the WebView2 Runtime](./index.md)
+   * [Release notes for WebView2 SDKs](../sdk/index.md)
diff --git a/microsoft-edge/webview2/release-notes/runtime/76.md b/microsoft-edge/webview2/release-notes/runtime/76.md
index 7a6799bf35..d8960de4ad 100644
--- a/microsoft-edge/webview2/release-notes/runtime/76.md
+++ b/microsoft-edge/webview2/release-notes/runtime/76.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 01/01/2025
+ms.date: 05/06/2019
 ---
 # Runtime 76.8.149 (May 6, 2019)
 
diff --git a/microsoft-edge/webview2/release-notes/runtime/77.md b/microsoft-edge/webview2/release-notes/runtime/77.md
index d6d0401139..29572d3143 100644
--- a/microsoft-edge/webview2/release-notes/runtime/77.md
+++ b/microsoft-edge/webview2/release-notes/runtime/77.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 01/01/2025
+ms.date: 07/29/2019
 ---
 # Runtime 77.8.230 (Jul. 29, 2019)
 
diff --git a/microsoft-edge/webview2/release-notes/runtime/78.md b/microsoft-edge/webview2/release-notes/runtime/78.md
index 9b8d6489d6..3843fbce8c 100644
--- a/microsoft-edge/webview2/release-notes/runtime/78.md
+++ b/microsoft-edge/webview2/release-notes/runtime/78.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 01/01/2025
+ms.date: 09/10/2019
 ---
 # Runtime 78.8.270 (Sep. 10, 2019)
 
diff --git a/microsoft-edge/webview2/release-notes/runtime/80.md b/microsoft-edge/webview2/release-notes/runtime/80.md
index 1e742af9fd..6eefa76927 100644
--- a/microsoft-edge/webview2/release-notes/runtime/80.md
+++ b/microsoft-edge/webview2/release-notes/runtime/80.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 01/01/2025
+ms.date: 12/09/2019
 ---
 # Runtime 80.8.355 (Dec. 9, 2019)
 
diff --git a/microsoft-edge/webview2/release-notes/runtime/82.md b/microsoft-edge/webview2/release-notes/runtime/82.md
index 48b2aee04f..6c9e64a91e 100644
--- a/microsoft-edge/webview2/release-notes/runtime/82.md
+++ b/microsoft-edge/webview2/release-notes/runtime/82.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 01/01/2025
+ms.date: 02/24/2020
 ---
 # Runtime 82.9.430 (Feb. 24, 2020)
 
diff --git a/microsoft-edge/webview2/release-notes/runtime/83.md b/microsoft-edge/webview2/release-notes/runtime/83.md
index 3ebbb99c67..d33b9fc3ce 100644
--- a/microsoft-edge/webview2/release-notes/runtime/83.md
+++ b/microsoft-edge/webview2/release-notes/runtime/83.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 01/01/2025
+ms.date: 04/20/2020
 ---
 # Runtime 83.9.488.0 (Apr. 20, 2020)
 
diff --git a/microsoft-edge/webview2/release-notes/runtime/84.md b/microsoft-edge/webview2/release-notes/runtime/84.md
index 42e1cd8e74..b5f9db417b 100644
--- a/microsoft-edge/webview2/release-notes/runtime/84.md
+++ b/microsoft-edge/webview2/release-notes/runtime/84.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 01/01/2025
+ms.date: 04/20/2020
 ---
 # Runtime 84.9.488 (Apr. 20, 2020)
 
diff --git a/microsoft-edge/webview2/release-notes/runtime/85.md b/microsoft-edge/webview2/release-notes/runtime/85.md
index 0b071a6f43..0b6938baad 100644
--- a/microsoft-edge/webview2/release-notes/runtime/85.md
+++ b/microsoft-edge/webview2/release-notes/runtime/85.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 01/01/2025
+ms.date: 06/08/2020
 ---
 # Runtime 85.9.538 (Jun. 8, 2020)
 
diff --git a/microsoft-edge/webview2/release-notes/runtime/86.md b/microsoft-edge/webview2/release-notes/runtime/86.md
index 9b37487d41..f76a79377e 100644
--- a/microsoft-edge/webview2/release-notes/runtime/86.md
+++ b/microsoft-edge/webview2/release-notes/runtime/86.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 01/01/2025
+ms.date: 01/25/2021
 ---
 # Runtime 86.0.705.50 (Jan. 25, 2021)
 
diff --git a/microsoft-edge/webview2/release-notes/runtime/89.md b/microsoft-edge/webview2/release-notes/runtime/89.md
index 7fade4d25c..f445455ab6 100644
--- a/microsoft-edge/webview2/release-notes/runtime/89.md
+++ b/microsoft-edge/webview2/release-notes/runtime/89.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 01/01/2025
+ms.date: 03/08/2021
 ---
 # Runtime 89.0.774.44 (Mar. 8, 2021)
 
diff --git a/microsoft-edge/webview2/release-notes/runtime/90.md b/microsoft-edge/webview2/release-notes/runtime/90.md
index 4c32edfd91..d49bd74547 100644
--- a/microsoft-edge/webview2/release-notes/runtime/90.md
+++ b/microsoft-edge/webview2/release-notes/runtime/90.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 01/01/2025
+ms.date: 04/21/2021
 ---
 # Runtime 90.0.818.41 (Apr. 21, 2021)
 
diff --git a/microsoft-edge/webview2/release-notes/runtime/91.md b/microsoft-edge/webview2/release-notes/runtime/91.md
index f87819653b..0782995358 100644
--- a/microsoft-edge/webview2/release-notes/runtime/91.md
+++ b/microsoft-edge/webview2/release-notes/runtime/91.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 01/01/2025
+ms.date: 05/31/2021
 ---
 # Runtime 91.0.864.35 (May 31, 2021)
 
diff --git a/microsoft-edge/webview2/release-notes/runtime/92.md b/microsoft-edge/webview2/release-notes/runtime/92.md
index 737573a6b6..6941650c4c 100644
--- a/microsoft-edge/webview2/release-notes/runtime/92.md
+++ b/microsoft-edge/webview2/release-notes/runtime/92.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 01/01/2025
+ms.date: 07/26/2021
 ---
 # Runtime 92.0.902.49 (Jul. 26, 2021)
 
diff --git a/microsoft-edge/webview2/release-notes/runtime/93.md b/microsoft-edge/webview2/release-notes/runtime/93.md
index 590b0e2db2..c62566c7bc 100644
--- a/microsoft-edge/webview2/release-notes/runtime/93.md
+++ b/microsoft-edge/webview2/release-notes/runtime/93.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 01/01/2025
+ms.date: 09/08/2021
 ---
 # Runtime 93.0.961.33 (Sep. 8, 2021)
 
diff --git a/microsoft-edge/webview2/release-notes/runtime/94.md b/microsoft-edge/webview2/release-notes/runtime/94.md
index e1e2fa4896..1020e71221 100644
--- a/microsoft-edge/webview2/release-notes/runtime/94.md
+++ b/microsoft-edge/webview2/release-notes/runtime/94.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 01/01/2025
+ms.date: 09/27/2021
 ---
 # Runtime 94.0.992.28 (Sep. 27, 2021)
 
diff --git a/microsoft-edge/webview2/release-notes/runtime/95.md b/microsoft-edge/webview2/release-notes/runtime/95.md
index 4eb4805aa6..0fdae983f9 100644
--- a/microsoft-edge/webview2/release-notes/runtime/95.md
+++ b/microsoft-edge/webview2/release-notes/runtime/95.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 01/01/2025
+ms.date: 10/25/2021
 ---
 # Runtime 95.0.1020.30 (Oct. 25, 2021)
 
diff --git a/microsoft-edge/webview2/release-notes/runtime/96.md b/microsoft-edge/webview2/release-notes/runtime/96.md
index 20fdb6c5f5..eb2ec735ad 100644
--- a/microsoft-edge/webview2/release-notes/runtime/96.md
+++ b/microsoft-edge/webview2/release-notes/runtime/96.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 01/01/2025
+ms.date: 11/29/2021
 ---
 # Runtime 96.0.1054.31 (Nov. 29, 2021)
 
diff --git a/microsoft-edge/webview2/release-notes/runtime/97.md b/microsoft-edge/webview2/release-notes/runtime/97.md
index 9ad98a7d5a..b269267cf4 100644
--- a/microsoft-edge/webview2/release-notes/runtime/97.md
+++ b/microsoft-edge/webview2/release-notes/runtime/97.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 01/01/2025
+ms.date: 01/13/2022
 ---
 # Runtime 97.0.1072.54 (Jan. 13, 2022)
 
diff --git a/microsoft-edge/webview2/release-notes/runtime/98.md b/microsoft-edge/webview2/release-notes/runtime/98.md
index ec9d6200b0..08486b0c09 100644
--- a/microsoft-edge/webview2/release-notes/runtime/98.md
+++ b/microsoft-edge/webview2/release-notes/runtime/98.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 01/01/2025
+ms.date: 02/06/2022
 ---
 # Runtime 98.0.1108.44 (Feb. 6, 2022)
 
diff --git a/microsoft-edge/webview2/release-notes/runtime/99.md b/microsoft-edge/webview2/release-notes/runtime/99.md
index 992cbaf01d..4efd49c7cb 100644
--- a/microsoft-edge/webview2/release-notes/runtime/99.md
+++ b/microsoft-edge/webview2/release-notes/runtime/99.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 01/01/2025
+ms.date: 03/10/2022
 ---
 # Runtime 99.0.1150.38 (Mar. 10, 2022)
 
diff --git a/microsoft-edge/webview2/release-notes/runtime/index.md b/microsoft-edge/webview2/release-notes/runtime/index.md
index f9c2ec31a1..6ca293ab49 100644
--- a/microsoft-edge/webview2/release-notes/runtime/index.md
+++ b/microsoft-edge/webview2/release-notes/runtime/index.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 08/12/2026
+ms.date: 08/24/2026
 ---
 # Release notes for the WebView2 Runtime
 
@@ -15,7 +15,9 @@ list past 10 releases (runtimes)
 in toc.yml, add new relnotes pages, move relnotes pages to archive
 in /webview2/release-notes/runtime/index.md, add new relnotes link, remove earliest relnotes link -->
 Release notes for recent Runtimes:
-* [Preview Runtime 152.0.4181.0 (Aug. 3, 2026)](./152.md)
+
+* [Preview Runtime 153.n.nnnn.nn (Mmm. dd, yyyy)](./153.md)
+* [Runtime 152.n.nnnn.nn (Mmm. dd, yyyy)](./152.md)
 * [Runtime 151.0.4129.50 (Aug. 3, 2026)](./151.md)
 * [Runtime 150.0.4078.44 (Jul. 7, 2026)](./150.md)
 * [Runtime 149.0.4022.49 (Jun. 11, 2026)](./149.md)
@@ -24,7 +26,6 @@ Release notes for recent Runtimes:
 * [Runtime 146.0.3856.49 (Mar. 16, 2026)](./146.md)
 * [Runtime 145.0.3800.47 (Feb. 16, 2026)](./145.md)
 * [Runtime 144.0.3719.77 (Jan. 27, 2026)](./144.md)
-* [Runtime 143.0.3650.58 (Dec. 8, 2025)](./143.md)
 
 For earlier release notes, see **Archive** in the table of contents.
 
@@ -51,7 +52,7 @@ Make sure to re-compile your WebView2 app after updating the WebView2 SDK NuGet
 
 * Use the Canary preview channel of Microsoft Edge (which includes the WebView2 Preview Runtime) when you do early testing and development using a Prerelease version of the WebView2 SDK package.
 
-  Canary is the recommended preview channel, because it ships at the fastest cadence and has the newest APIs.  
+  Canary is the recommended preview channel, because it ships at the fastest cadence and has the newest APIs. 
 
   Prerelease testing of WebView2 SDKs uses a preview channel of Microsoft Edge (Beta, Dev, or Canary), which includes the WebView2 Preview Runtime.  See [Prerelease testing using preview channels](../../how-to/prerelease-testing.md).
 
@@ -61,10 +62,30 @@ See also:
 * [Matching the Runtime version with the SDK version](../../concepts/versioning.md#matching-the-runtime-version-with-the-sdk-version) in _Prerelease and Release SDKs for WebView2_.
 
 
+<!-- ====================================================================== -->
+## Updating the Runtime
+
+WebView2 changes may require an update to the WebView2 Runtime, the WebView2 SDK, or both.  Most new APIs require both Runtime and SDK updates.
+
+WebView2 shares code and binaries with the Microsoft Edge browser, and is released around the same time.  As a result, WebView2 Runtime releases generally also include Microsoft Edge updates.
+
+* For Microsoft Edge updates, see [Release notes for Microsoft Edge Stable Channel](/deployedge/microsoft-edge-relnote-stable-channel) and [Release notes for Microsoft Edge Beta Channel](/deployedge/microsoft-edge-relnote-beta-channel).
+
+* To update the WebView2 Runtime on your development machine and on user machines, see [Distribute your app and the WebView2 Runtime](../../concepts/distribution.md).  To view or get the latest WebView2 Runtime versions, see [Download the WebView2 Runtime](https://developer.microsoft.com/microsoft-edge/webview2#download-the-webview2-runtime) in the _Microsoft Edge WebView2_ page at developer.microsoft.com.
+
+To obtain a WebView2 Preview Runtime, use the following combination:
+* A Prerelease version of the WebView2 SDK.
+* A preview channel of Microsoft Edge (containing the WebView2 Preview Runtime) on your development client.
+
+See also:
+* [Prerelease and Release SDKs for WebView2](../../concepts/versioning.md)
+* [Updating the SDK](../sdk/index.md#updating-the-sdk) in _Release notes for WebView2 SDKs_.
+
+
 <!-- ====================================================================== -->
 ## Minimum version of the browser or Runtime to load WebView2
 
-To load WebView2, the minimum version of Microsoft Edge or the WebView2 Runtime is 86.0.616.0.  The minimum version to load WebView2 only changes when a breaking change occurs in the web platform.
+To load WebView2, the minimum version of Microsoft Edge or the WebView2 Runtime is 86.0.616.0; see [Runtime 86.0.705.50 (Jan. 25, 2021)](./86.md).  The minimum version to load WebView2 only changes when a breaking change occurs in the web platform.
 
 To use a Prerelease SDK along with a Microsoft Edge preview channel (containing the WebView2 Preview Runtime), see [Test upcoming APIs and features](../../how-to/set-preview-channel.md).
 
@@ -85,26 +106,6 @@ Async methods:
 Release notes entries correspond to historical releases of WebView2, and are not updated over time.  References to "new features" and "experimental APIs" might become outdated as new versions of WebView2 are released.
 
 
-<!-- ====================================================================== -->
-## Updating the Runtime
-
-WebView2 changes may require an update to the WebView2 Runtime, the WebView2 SDK, or both.  Most new APIs require both Runtime and SDK updates.
-
-WebView2 shares code and binaries with the Microsoft Edge browser, and is released around the same time.  As a result, WebView2 Runtime releases generally also include Microsoft Edge updates.
-
-* For Microsoft Edge updates, see [Release notes for Microsoft Edge Stable Channel](/deployedge/microsoft-edge-relnote-stable-channel) and [Release notes for Microsoft Edge Beta Channel](/deployedge/microsoft-edge-relnote-beta-channel).
-
-* To update the WebView2 Runtime on your development machine and on user machines, see [Distribute your app and the WebView2 Runtime](../../concepts/distribution.md).  To view or get the latest WebView2 Runtime versions, see [Download the WebView2 Runtime](https://developer.microsoft.com/microsoft-edge/webview2#download-the-webview2-runtime) in the _Microsoft Edge WebView2_ page at developer.microsoft.com.
-
-To obtain a WebView2 Preview Runtime, use the following combination:
-* A Prerelease version of the WebView2 SDK.
-* A preview channel of Microsoft Edge (containing the WebView2 Preview Runtime) on your development client.
-
-See also:
-* [Prerelease and Release SDKs for WebView2](../../concepts/versioning.md)
-* [Updating the SDK](../sdk/index.md#updating-the-sdk) in _Release notes for WebView2 SDKs_.
-
-
 <!-- ====================================================================== -->
 ## See also
 
@@ -114,9 +115,3 @@ See also:
 * [Contact the WebView2 team](../../contact.md)<!-- toc bucket: bottom -->
 * [Release notes for Microsoft Edge web platform](../../../web-platform/release-notes/index.md)
 * [Microsoft Edge release schedule](/deployedge/microsoft-edge-release-schedule)
-
-API Reference:
-* [WebView2 API Reference](../../webview2-api-reference.md)
-   * .NET: [Microsoft.Web.WebView2.Core Namespace](/dotnet/api/microsoft.web.webview2.core)<!-- https://learn.microsoft.com/dotnet/api/microsoft.web.webview2.core -->
-   * WinRT: [Microsoft.Web.WebView2.Core Namespace](/microsoft-edge/webview2/reference/winrt/microsoft_web_webview2_core/)<!-- https://learn.microsoft.com/microsoft-edge/webview2/reference/winrt/microsoft_web_webview2_core/ -->
-   * Win32: [Reference (WebView2 Win32 C++)](/microsoft-edge/webview2/reference/win32/)<!-- https://learn.microsoft.com/microsoft-edge/webview2/reference/win32/ -->
diff --git a/microsoft-edge/webview2/release-notes/sdk/0-8-149.md b/microsoft-edge/webview2/release-notes/sdk/0-8-149.md
index 26535bf49d..41992f06d1 100644
--- a/microsoft-edge/webview2/release-notes/sdk/0-8-149.md
+++ b/microsoft-edge/webview2/release-notes/sdk/0-8-149.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 06/11/2026
+ms.date: 05/06/2019
 ---
 # Release SDK 0.8.149, for Runtime 76 (May 6, 2019)
 
diff --git a/microsoft-edge/webview2/release-notes/sdk/0-8-190.md b/microsoft-edge/webview2/release-notes/sdk/0-8-190.md
index c4641487df..0a5d949e22 100644
--- a/microsoft-edge/webview2/release-notes/sdk/0-8-190.md
+++ b/microsoft-edge/webview2/release-notes/sdk/0-8-190.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 06/11/2026
+ms.date: 06/17/2019
 ---
 # Release SDK 0.8.190, for Runtime 77 (Jun. 17, 2019)
 
diff --git a/microsoft-edge/webview2/release-notes/sdk/0-8-230.md b/microsoft-edge/webview2/release-notes/sdk/0-8-230.md
index a22d9bb14a..fd3514eed5 100644
--- a/microsoft-edge/webview2/release-notes/sdk/0-8-230.md
+++ b/microsoft-edge/webview2/release-notes/sdk/0-8-230.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 06/11/2026
+ms.date: 07/29/2019
 ---
 # Release SDK 0.8.230, for Runtime 77 (Jul. 29, 2019)
 
diff --git a/microsoft-edge/webview2/release-notes/sdk/0-8-270.md b/microsoft-edge/webview2/release-notes/sdk/0-8-270.md
index f35d556879..2766dc9842 100644
--- a/microsoft-edge/webview2/release-notes/sdk/0-8-270.md
+++ b/microsoft-edge/webview2/release-notes/sdk/0-8-270.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 06/11/2026
+ms.date: 09/10/2019
 ---
 # Release SDK 0.8.270, for Runtime 78 (Sep. 10, 2019)
 
diff --git a/microsoft-edge/webview2/release-notes/sdk/0-8-314.md b/microsoft-edge/webview2/release-notes/sdk/0-8-314.md
index c72e4254bf..67a37fad2b 100644
--- a/microsoft-edge/webview2/release-notes/sdk/0-8-314.md
+++ b/microsoft-edge/webview2/release-notes/sdk/0-8-314.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 06/11/2026
+ms.date: 10/28/2019
 ---
 # Release SDK 0.8.314, for Runtime 80 (Oct. 28, 2019)
 
diff --git a/microsoft-edge/webview2/release-notes/sdk/0-8-355.md b/microsoft-edge/webview2/release-notes/sdk/0-8-355.md
index 3f2d93ffed..5f782f0194 100644
--- a/microsoft-edge/webview2/release-notes/sdk/0-8-355.md
+++ b/microsoft-edge/webview2/release-notes/sdk/0-8-355.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 06/11/2026
+ms.date: 12/09/2019
 ---
 # Release SDK 0.8.355, for Runtime 80 (Dec. 9, 2019)
 
diff --git a/microsoft-edge/webview2/release-notes/sdk/0-9-430.md b/microsoft-edge/webview2/release-notes/sdk/0-9-430.md
index 23c9b736c7..1311cce2a8 100644
--- a/microsoft-edge/webview2/release-notes/sdk/0-9-430.md
+++ b/microsoft-edge/webview2/release-notes/sdk/0-9-430.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 06/11/2026
+ms.date: 02/24/2020
 ---
 # Release SDK 0.9.430, for Runtime 82 (Feb. 24, 2020)
 
diff --git a/microsoft-edge/webview2/release-notes/sdk/0-9-488-prerelease.md b/microsoft-edge/webview2/release-notes/sdk/0-9-488-prerelease.md
index 7efed82802..b64c130bf0 100644
--- a/microsoft-edge/webview2/release-notes/sdk/0-9-488-prerelease.md
+++ b/microsoft-edge/webview2/release-notes/sdk/0-9-488-prerelease.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 06/11/2026
+ms.date: 04/20/2020
 ---
 # Prerelease SDK 0.9.488-prerelease, for Runtime 83 (Apr. 20, 2020)
 <!--
diff --git a/microsoft-edge/webview2/release-notes/sdk/0-9-488.md b/microsoft-edge/webview2/release-notes/sdk/0-9-488.md
index 9210947c1e..6ffa551aea 100644
--- a/microsoft-edge/webview2/release-notes/sdk/0-9-488.md
+++ b/microsoft-edge/webview2/release-notes/sdk/0-9-488.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 06/11/2026
+ms.date: 04/20/2020
 ---
 # Release SDK 0.9.488, for Runtime 84 (Apr. 20, 2020)
 
diff --git a/microsoft-edge/webview2/release-notes/sdk/0-9-515-prerelease.md b/microsoft-edge/webview2/release-notes/sdk/0-9-515-prerelease.md
index e7c5aed10d..801d5542a7 100644
--- a/microsoft-edge/webview2/release-notes/sdk/0-9-515-prerelease.md
+++ b/microsoft-edge/webview2/release-notes/sdk/0-9-515-prerelease.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 06/11/2026
+ms.date: 05/14/2020
 ---
 # Prerelease SDK 0.9.515-prerelease, for Runtime 84 (May 14, 2020)
 
diff --git a/microsoft-edge/webview2/release-notes/sdk/0-9-538-prerelease.md b/microsoft-edge/webview2/release-notes/sdk/0-9-538-prerelease.md
index 3a07cf8905..d99767825f 100644
--- a/microsoft-edge/webview2/release-notes/sdk/0-9-538-prerelease.md
+++ b/microsoft-edge/webview2/release-notes/sdk/0-9-538-prerelease.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 06/11/2026
+ms.date: 06/08/2020
 ---
 # Prerelease SDK 0.9.538-prerelease, for Runtime 85 (Jun. 8, 2020)
 <!--
diff --git a/microsoft-edge/webview2/release-notes/sdk/0-9-538.md b/microsoft-edge/webview2/release-notes/sdk/0-9-538.md
index e91cd17165..7dafe3a207 100644
--- a/microsoft-edge/webview2/release-notes/sdk/0-9-538.md
+++ b/microsoft-edge/webview2/release-notes/sdk/0-9-538.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 06/11/2026
+ms.date: 06/08/2020
 ---
 # Release SDK 0.9.538, for Runtime 85 (Jun. 8, 2020)
 
diff --git a/microsoft-edge/webview2/release-notes/sdk/0-9-579-prerelease.md b/microsoft-edge/webview2/release-notes/sdk/0-9-579-prerelease.md
index b310bee452..d08e7fdc2d 100644
--- a/microsoft-edge/webview2/release-notes/sdk/0-9-579-prerelease.md
+++ b/microsoft-edge/webview2/release-notes/sdk/0-9-579-prerelease.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 06/11/2026
+ms.date: 07/20/2020
 ---
 # Prerelease SDK 0.9.579-prerelease, for Runtime 85 (Jul. 20, 2020)
 <!--
diff --git a/microsoft-edge/webview2/release-notes/sdk/0-9-579.md b/microsoft-edge/webview2/release-notes/sdk/0-9-579.md
index 64d5b692f5..8c231c8910 100644
--- a/microsoft-edge/webview2/release-notes/sdk/0-9-579.md
+++ b/microsoft-edge/webview2/release-notes/sdk/0-9-579.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 06/11/2026
+ms.date: 07/20/2020
 ---
 # Release SDK 0.9.579, for Runtime 86 (Jul. 20, 2020)
 
diff --git a/microsoft-edge/webview2/release-notes/sdk/0-9-622-11.md b/microsoft-edge/webview2/release-notes/sdk/0-9-622-11.md
index 8a9a4b15d9..521c370b69 100644
--- a/microsoft-edge/webview2/release-notes/sdk/0-9-622-11.md
+++ b/microsoft-edge/webview2/release-notes/sdk/0-9-622-11.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 06/11/2026
+ms.date: 09/10/2020
 ---
 # Release SDK 0.9.622.11, for Runtime 86 (Sep. 10, 2020)
 
diff --git a/microsoft-edge/webview2/release-notes/sdk/1-0-1010-prerelease.md b/microsoft-edge/webview2/release-notes/sdk/1-0-1010-prerelease.md
index ca4b5d7bfe..6cb9ae0470 100644
--- a/microsoft-edge/webview2/release-notes/sdk/1-0-1010-prerelease.md
+++ b/microsoft-edge/webview2/release-notes/sdk/1-0-1010-prerelease.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 06/11/2026
+ms.date: 09/14/2021
 ---
 # Prerelease SDK 1.0.1010-prerelease, for Runtime 95 (Sep. 14, 2021)
 
diff --git a/microsoft-edge/webview2/release-notes/sdk/1-0-1018-prerelease.md b/microsoft-edge/webview2/release-notes/sdk/1-0-1018-prerelease.md
index 3d59bc79f6..488d1673b7 100644
--- a/microsoft-edge/webview2/release-notes/sdk/1-0-1018-prerelease.md
+++ b/microsoft-edge/webview2/release-notes/sdk/1-0-1018-prerelease.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 06/11/2026
+ms.date: 09/20/2021
 ---
 # Prerelease SDK 1.0.1018-prerelease, for Runtime 95 (Sep. 20, 2021)
 
diff --git a/microsoft-edge/webview2/release-notes/sdk/1-0-1020-30.md b/microsoft-edge/webview2/release-notes/sdk/1-0-1020-30.md
index 1c127229eb..93066ad0a0 100644
--- a/microsoft-edge/webview2/release-notes/sdk/1-0-1020-30.md
+++ b/microsoft-edge/webview2/release-notes/sdk/1-0-1020-30.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 06/11/2026
+ms.date: 10/25/2021
 ---
 # Release SDK 1.0.1020.30, for Runtime 95 (Oct. 25, 2021)
 
diff --git a/microsoft-edge/webview2/release-notes/sdk/1-0-1054-31.md b/microsoft-edge/webview2/release-notes/sdk/1-0-1054-31.md
index d84f8d4e11..a92b8ebc70 100644
--- a/microsoft-edge/webview2/release-notes/sdk/1-0-1054-31.md
+++ b/microsoft-edge/webview2/release-notes/sdk/1-0-1054-31.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 06/11/2026
+ms.date: 11/29/2021
 ---
 # Release SDK 1.0.1054.31, for Runtime 96 (Nov. 29, 2021)
 
diff --git a/microsoft-edge/webview2/release-notes/sdk/1-0-1056-prerelease.md b/microsoft-edge/webview2/release-notes/sdk/1-0-1056-prerelease.md
index 78c72766ac..76a3355bb8 100644
--- a/microsoft-edge/webview2/release-notes/sdk/1-0-1056-prerelease.md
+++ b/microsoft-edge/webview2/release-notes/sdk/1-0-1056-prerelease.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 06/11/2026
+ms.date: 10/29/2021
 ---
 # Prerelease SDK 1.0.1056-prerelease, for Runtime 97 (Oct. 29, 2021)
 
diff --git a/microsoft-edge/webview2/release-notes/sdk/1-0-1072-54.md b/microsoft-edge/webview2/release-notes/sdk/1-0-1072-54.md
index b8e3a3d87b..f79fd35e61 100644
--- a/microsoft-edge/webview2/release-notes/sdk/1-0-1072-54.md
+++ b/microsoft-edge/webview2/release-notes/sdk/1-0-1072-54.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 06/11/2026
+ms.date: 01/13/2022
 ---
 # Release SDK 1.0.1072.54, for Runtime 97 (Jan. 13, 2022)
 
diff --git a/microsoft-edge/webview2/release-notes/sdk/1-0-1083-prerelease.md b/microsoft-edge/webview2/release-notes/sdk/1-0-1083-prerelease.md
index 7c01c49bee..f1eaad87e8 100644
--- a/microsoft-edge/webview2/release-notes/sdk/1-0-1083-prerelease.md
+++ b/microsoft-edge/webview2/release-notes/sdk/1-0-1083-prerelease.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 06/11/2026
+ms.date: 11/29/2021
 ---
 # Prerelease SDK 1.0.1083-prerelease, for Runtime 97 (Nov. 29, 2021)
 
diff --git a/microsoft-edge/webview2/release-notes/sdk/1-0-1108-44.md b/microsoft-edge/webview2/release-notes/sdk/1-0-1108-44.md
index 52f256dcdd..e83ba24eb3 100644
--- a/microsoft-edge/webview2/release-notes/sdk/1-0-1108-44.md
+++ b/microsoft-edge/webview2/release-notes/sdk/1-0-1108-44.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 06/11/2026
+ms.date: 02/06/2022
 ---
 # Release SDK 1.0.1108.44, for Runtime 98 (Feb. 6, 2022)
 
diff --git a/microsoft-edge/webview2/release-notes/sdk/1-0-1133-prerelease.md b/microsoft-edge/webview2/release-notes/sdk/1-0-1133-prerelease.md
index 1f97c0ad46..25cbde9d07 100644
--- a/microsoft-edge/webview2/release-notes/sdk/1-0-1133-prerelease.md
+++ b/microsoft-edge/webview2/release-notes/sdk/1-0-1133-prerelease.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 06/11/2026
+ms.date: 01/13/2022
 ---
 # Prerelease SDK 1.0.1133-prerelease, for Runtime 99 (Jan. 13, 2022)
 
diff --git a/microsoft-edge/webview2/release-notes/sdk/1-0-1150-38.md b/microsoft-edge/webview2/release-notes/sdk/1-0-1150-38.md
index 060d3a4884..875eef913b 100644
--- a/microsoft-edge/webview2/release-notes/sdk/1-0-1150-38.md
+++ b/microsoft-edge/webview2/release-notes/sdk/1-0-1150-38.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 06/11/2026
+ms.date: 03/10/2022
 ---
 # Release SDK 1.0.1150.38, for Runtime 99 (Mar. 10, 2022)
 
diff --git a/microsoft-edge/webview2/release-notes/sdk/1-0-1158-prerelease.md b/microsoft-edge/webview2/release-notes/sdk/1-0-1158-prerelease.md
index daba458d07..4c52eadde9 100644
--- a/microsoft-edge/webview2/release-notes/sdk/1-0-1158-prerelease.md
+++ b/microsoft-edge/webview2/release-notes/sdk/1-0-1158-prerelease.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 06/11/2026
+ms.date: 02/06/2022
 ---
 # Prerelease SDK 1.0.1158-prerelease, for Runtime 100 (Feb. 6, 2022)
 
diff --git a/microsoft-edge/webview2/release-notes/sdk/1-0-1185-39.md b/microsoft-edge/webview2/release-notes/sdk/1-0-1185-39.md
index 5f50ac168e..01b1007093 100644
--- a/microsoft-edge/webview2/release-notes/sdk/1-0-1185-39.md
+++ b/microsoft-edge/webview2/release-notes/sdk/1-0-1185-39.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 06/11/2026
+ms.date: 04/12/2022
 ---
 # Release SDK 1.0.1185.39, for Runtime 100 (Apr. 12, 2022)
 
diff --git a/microsoft-edge/webview2/release-notes/sdk/1-0-1189-prerelease.md b/microsoft-edge/webview2/release-notes/sdk/1-0-1189-prerelease.md
index 6774823294..aef82d8f17 100644
--- a/microsoft-edge/webview2/release-notes/sdk/1-0-1189-prerelease.md
+++ b/microsoft-edge/webview2/release-notes/sdk/1-0-1189-prerelease.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 06/11/2026
+ms.date: 03/10/2022
 ---
 # Prerelease SDK 1.0.1189-prerelease, for Runtime 100 (Mar. 10, 2022)
 
diff --git a/microsoft-edge/webview2/release-notes/sdk/1-0-1210-30.md b/microsoft-edge/webview2/release-notes/sdk/1-0-1210-30.md
index 185f48be2a..9fc6bf73a5 100644
--- a/microsoft-edge/webview2/release-notes/sdk/1-0-1210-30.md
+++ b/microsoft-edge/webview2/release-notes/sdk/1-0-1210-30.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 06/11/2026
+ms.date: 05/05/2022
 ---
 # Release SDK 1.0.1210.30, for Runtime 101 (May 5, 2022)
 <!--
diff --git a/microsoft-edge/webview2/release-notes/sdk/1-0-1210-39.md b/microsoft-edge/webview2/release-notes/sdk/1-0-1210-39.md
index d951b2d5c2..22af5bc50a 100644
--- a/microsoft-edge/webview2/release-notes/sdk/1-0-1210-39.md
+++ b/microsoft-edge/webview2/release-notes/sdk/1-0-1210-39.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 06/11/2026
+ms.date: 05/09/2022
 ---
 # Release SDK 1.0.1210.39, for Runtime 101 (May 9, 2022)
 
diff --git a/microsoft-edge/webview2/release-notes/sdk/1-0-1222-prerelease.md b/microsoft-edge/webview2/release-notes/sdk/1-0-1222-prerelease.md
index efb49b9008..438da38d23 100644
--- a/microsoft-edge/webview2/release-notes/sdk/1-0-1222-prerelease.md
+++ b/microsoft-edge/webview2/release-notes/sdk/1-0-1222-prerelease.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 06/11/2026
+ms.date: 04/12/2022
 ---
 # Prerelease SDK 1.0.1222-prerelease, for Runtime 102 (Apr. 12, 2022)
 
diff --git a/microsoft-edge/webview2/release-notes/sdk/1-0-1243-prerelease.md b/microsoft-edge/webview2/release-notes/sdk/1-0-1243-prerelease.md
index 912d17219f..1db0b8efca 100644
--- a/microsoft-edge/webview2/release-notes/sdk/1-0-1243-prerelease.md
+++ b/microsoft-edge/webview2/release-notes/sdk/1-0-1243-prerelease.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 06/11/2026
+ms.date: 05/02/2022
 ---
 # Prerelease SDK 1.0.1243-prerelease, for Runtime 102 (May 2, 2022)
 <!--
diff --git a/microsoft-edge/webview2/release-notes/sdk/1-0-1245-22.md b/microsoft-edge/webview2/release-notes/sdk/1-0-1245-22.md
index 8bdd5b9635..898115350a 100644
--- a/microsoft-edge/webview2/release-notes/sdk/1-0-1245-22.md
+++ b/microsoft-edge/webview2/release-notes/sdk/1-0-1245-22.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 06/11/2026
+ms.date: 06/14/2022
 ---
 # Release SDK 1.0.1245.22, for Runtime 102 (Jun. 14, 2022)
 
diff --git a/microsoft-edge/webview2/release-notes/sdk/1-0-1248-prerelease.md b/microsoft-edge/webview2/release-notes/sdk/1-0-1248-prerelease.md
index 5aeaac515c..b16e52d02e 100644
--- a/microsoft-edge/webview2/release-notes/sdk/1-0-1248-prerelease.md
+++ b/microsoft-edge/webview2/release-notes/sdk/1-0-1248-prerelease.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 06/11/2026
+ms.date: 05/09/2022
 ---
 # Prerelease SDK 1.0.1248-prerelease, for Runtime 102 (May 9, 2022)
 
diff --git a/microsoft-edge/webview2/release-notes/sdk/1-0-1264-42.md b/microsoft-edge/webview2/release-notes/sdk/1-0-1264-42.md
index 38d0048a86..0cf871f719 100644
--- a/microsoft-edge/webview2/release-notes/sdk/1-0-1264-42.md
+++ b/microsoft-edge/webview2/release-notes/sdk/1-0-1264-42.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 06/11/2026
+ms.date: 07/04/2022
 ---
 # Release SDK 1.0.1264.42, for Runtime 103 (Jul. 4, 2022)
 
diff --git a/microsoft-edge/webview2/release-notes/sdk/1-0-1293-44.md b/microsoft-edge/webview2/release-notes/sdk/1-0-1293-44.md
index c95084c8e1..380fe7de6a 100644
--- a/microsoft-edge/webview2/release-notes/sdk/1-0-1293-44.md
+++ b/microsoft-edge/webview2/release-notes/sdk/1-0-1293-44.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 06/11/2026
+ms.date: 08/08/2022
 ---
 # Release SDK 1.0.1293.44, for Runtime 104 (Aug. 8, 2022)
 
diff --git a/microsoft-edge/webview2/release-notes/sdk/1-0-1305-prerelease.md b/microsoft-edge/webview2/release-notes/sdk/1-0-1305-prerelease.md
index 118355a1f5..0de3eebf8e 100644
--- a/microsoft-edge/webview2/release-notes/sdk/1-0-1305-prerelease.md
+++ b/microsoft-edge/webview2/release-notes/sdk/1-0-1305-prerelease.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 06/11/2026
+ms.date: 07/04/2022
 ---
 # Prerelease SDK 1.0.1305-prerelease, for Runtime 105 (Jul. 4, 2022)
 
diff --git a/microsoft-edge/webview2/release-notes/sdk/1-0-1340-prerelease.md b/microsoft-edge/webview2/release-notes/sdk/1-0-1340-prerelease.md
index 51d7f37b66..bda6a09226 100644
--- a/microsoft-edge/webview2/release-notes/sdk/1-0-1340-prerelease.md
+++ b/microsoft-edge/webview2/release-notes/sdk/1-0-1340-prerelease.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 06/11/2026
+ms.date: 08/08/2022
 ---
 # Prerelease SDK 1.0.1340-prerelease, for Runtime 105 (Aug. 8, 2022)
 
diff --git a/microsoft-edge/webview2/release-notes/sdk/1-0-1343-22.md b/microsoft-edge/webview2/release-notes/sdk/1-0-1343-22.md
index c88c8bdf95..b91dc7f15e 100644
--- a/microsoft-edge/webview2/release-notes/sdk/1-0-1343-22.md
+++ b/microsoft-edge/webview2/release-notes/sdk/1-0-1343-22.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 06/11/2026
+ms.date: 09/06/2022
 ---
 # Release SDK 1.0.1343.22, for Runtime 105 (Sep. 6, 2022)
 
diff --git a/microsoft-edge/webview2/release-notes/sdk/1-0-1369-prerelease.md b/microsoft-edge/webview2/release-notes/sdk/1-0-1369-prerelease.md
index aec0d9c7a5..7ad444a6c4 100644
--- a/microsoft-edge/webview2/release-notes/sdk/1-0-1369-prerelease.md
+++ b/microsoft-edge/webview2/release-notes/sdk/1-0-1369-prerelease.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 06/11/2026
+ms.date: 09/06/2022
 ---
 # Prerelease SDK 1.0.1369-prerelease, for Runtime 106 (Sep. 6, 2022)
 
diff --git a/microsoft-edge/webview2/release-notes/sdk/1-0-1370-28.md b/microsoft-edge/webview2/release-notes/sdk/1-0-1370-28.md
index ff567849f2..852b3318ef 100644
--- a/microsoft-edge/webview2/release-notes/sdk/1-0-1370-28.md
+++ b/microsoft-edge/webview2/release-notes/sdk/1-0-1370-28.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 06/11/2026
+ms.date: 10/11/2022
 ---
 # Release SDK 1.0.1370.28, for Runtime 106 (Oct. 11, 2022)
 
diff --git a/microsoft-edge/webview2/release-notes/sdk/1-0-1414-prerelease.md b/microsoft-edge/webview2/release-notes/sdk/1-0-1414-prerelease.md
index e80bc53db9..3635d84c09 100644
--- a/microsoft-edge/webview2/release-notes/sdk/1-0-1414-prerelease.md
+++ b/microsoft-edge/webview2/release-notes/sdk/1-0-1414-prerelease.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 06/11/2026
+ms.date: 10/11/2022
 ---
 # Prerelease SDK 1.0.1414-prerelease, for Runtime 107 (Oct. 11, 2022)
 
diff --git a/microsoft-edge/webview2/release-notes/sdk/1-0-1418-22.md b/microsoft-edge/webview2/release-notes/sdk/1-0-1418-22.md
index 1a917dd4f8..b63b135d26 100644
--- a/microsoft-edge/webview2/release-notes/sdk/1-0-1418-22.md
+++ b/microsoft-edge/webview2/release-notes/sdk/1-0-1418-22.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 06/11/2026
+ms.date: 10/31/2022
 ---
 # Release SDK 1.0.1418.22, for Runtime 107 (Oct. 31, 2022)
 
diff --git a/microsoft-edge/webview2/release-notes/sdk/1-0-1462-37.md b/microsoft-edge/webview2/release-notes/sdk/1-0-1462-37.md
index fd8cee3793..5a812fbdc4 100644
--- a/microsoft-edge/webview2/release-notes/sdk/1-0-1462-37.md
+++ b/microsoft-edge/webview2/release-notes/sdk/1-0-1462-37.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 06/11/2026
+ms.date: 12/12/2022
 ---
 # Release SDK 1.0.1462.37, for Runtime 108 (Dec. 12, 2022)
 
diff --git a/microsoft-edge/webview2/release-notes/sdk/1-0-1466-prerelease.md b/microsoft-edge/webview2/release-notes/sdk/1-0-1466-prerelease.md
index d829dedb91..4b596e4f37 100644
--- a/microsoft-edge/webview2/release-notes/sdk/1-0-1466-prerelease.md
+++ b/microsoft-edge/webview2/release-notes/sdk/1-0-1466-prerelease.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 06/11/2026
+ms.date: 10/31/2022
 ---
 # Prerelease SDK 1.0.1466-prerelease, for Runtime 109 (Oct. 31, 2022)
 
diff --git a/microsoft-edge/webview2/release-notes/sdk/1-0-1518-46.md b/microsoft-edge/webview2/release-notes/sdk/1-0-1518-46.md
index f5b2db3115..99fab265a5 100644
--- a/microsoft-edge/webview2/release-notes/sdk/1-0-1518-46.md
+++ b/microsoft-edge/webview2/release-notes/sdk/1-0-1518-46.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 06/11/2026
+ms.date: 01/17/2023
 ---
 # Release SDK 1.0.1518.46, for Runtime 109 (Jan. 17, 2023)
 
diff --git a/microsoft-edge/webview2/release-notes/sdk/1-0-1549-prerelease.md b/microsoft-edge/webview2/release-notes/sdk/1-0-1549-prerelease.md
index 5cfdc78116..48f5c3c111 100644
--- a/microsoft-edge/webview2/release-notes/sdk/1-0-1549-prerelease.md
+++ b/microsoft-edge/webview2/release-notes/sdk/1-0-1549-prerelease.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 06/11/2026
+ms.date: 12/12/2022
 ---
 # Prerelease SDK 1.0.1549-prerelease, for Runtime 110 (Dec. 12, 2022)
 
diff --git a/microsoft-edge/webview2/release-notes/sdk/1-0-1587-40.md b/microsoft-edge/webview2/release-notes/sdk/1-0-1587-40.md
index 235424859e..9d4937bffb 100644
--- a/microsoft-edge/webview2/release-notes/sdk/1-0-1587-40.md
+++ b/microsoft-edge/webview2/release-notes/sdk/1-0-1587-40.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 06/11/2026
+ms.date: 02/15/2023
 ---
 # Release SDK 1.0.1587.40, for Runtime 110 (Feb. 15, 2023)
 
diff --git a/microsoft-edge/webview2/release-notes/sdk/1-0-1619-prerelease.md b/microsoft-edge/webview2/release-notes/sdk/1-0-1619-prerelease.md
index fc38343977..b65c045812 100644
--- a/microsoft-edge/webview2/release-notes/sdk/1-0-1619-prerelease.md
+++ b/microsoft-edge/webview2/release-notes/sdk/1-0-1619-prerelease.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 06/11/2026
+ms.date: 01/19/2023
 ---
 # Prerelease SDK 1.0.1619-prerelease, for Runtime 111 (Jan. 19, 2023)
 
diff --git a/microsoft-edge/webview2/release-notes/sdk/1-0-1661-34.md b/microsoft-edge/webview2/release-notes/sdk/1-0-1661-34.md
index 34ca9137bb..df2040071e 100644
--- a/microsoft-edge/webview2/release-notes/sdk/1-0-1661-34.md
+++ b/microsoft-edge/webview2/release-notes/sdk/1-0-1661-34.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 06/11/2026
+ms.date: 03/20/2023
 ---
 # Release SDK 1.0.1661.34, for Runtime 111 (Mar. 20, 2023)
 
diff --git a/microsoft-edge/webview2/release-notes/sdk/1-0-1671-prerelease.md b/microsoft-edge/webview2/release-notes/sdk/1-0-1671-prerelease.md
index 9ffd9ec5e6..a3121d79c7 100644
--- a/microsoft-edge/webview2/release-notes/sdk/1-0-1671-prerelease.md
+++ b/microsoft-edge/webview2/release-notes/sdk/1-0-1671-prerelease.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 06/11/2026
+ms.date: 02/15/2023
 ---
 # Prerelease SDK 1.0.1671-prerelease, for Runtime 112 (Feb. 15, 2023)
 
diff --git a/microsoft-edge/webview2/release-notes/sdk/1-0-1722-45.md b/microsoft-edge/webview2/release-notes/sdk/1-0-1722-45.md
index ee88424b80..ec0f4c2693 100644
--- a/microsoft-edge/webview2/release-notes/sdk/1-0-1722-45.md
+++ b/microsoft-edge/webview2/release-notes/sdk/1-0-1722-45.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 06/11/2026
+ms.date: 04/13/2023
 ---
 # Release SDK 1.0.1722.45, for Runtime 112 (Apr. 13, 2023)
 
diff --git a/microsoft-edge/webview2/release-notes/sdk/1-0-1724-prerelease.md b/microsoft-edge/webview2/release-notes/sdk/1-0-1724-prerelease.md
index 5ac0bee4cf..2a8ec1a403 100644
--- a/microsoft-edge/webview2/release-notes/sdk/1-0-1724-prerelease.md
+++ b/microsoft-edge/webview2/release-notes/sdk/1-0-1724-prerelease.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 06/11/2026
+ms.date: 03/20/2023
 ---
 # Prerelease SDK 1.0.1724-prerelease, for Runtime 113 (Mar. 20, 2023)
 
diff --git a/microsoft-edge/webview2/release-notes/sdk/1-0-1774-30.md b/microsoft-edge/webview2/release-notes/sdk/1-0-1774-30.md
index a08cbc4d85..e383e7e152 100644
--- a/microsoft-edge/webview2/release-notes/sdk/1-0-1774-30.md
+++ b/microsoft-edge/webview2/release-notes/sdk/1-0-1774-30.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 06/11/2026
+ms.date: 05/08/2023
 ---
 # Release SDK 1.0.1774.30, for Runtime 113 (May 8, 2023)
 
diff --git a/microsoft-edge/webview2/release-notes/sdk/1-0-1777-prerelease.md b/microsoft-edge/webview2/release-notes/sdk/1-0-1777-prerelease.md
index d390b4290a..7588f01749 100644
--- a/microsoft-edge/webview2/release-notes/sdk/1-0-1777-prerelease.md
+++ b/microsoft-edge/webview2/release-notes/sdk/1-0-1777-prerelease.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 06/11/2026
+ms.date: 04/10/2023
 ---
 # Prerelease SDK 1.0.1777-prerelease, for Runtime 114 (Apr. 10, 2023)
 
diff --git a/microsoft-edge/webview2/release-notes/sdk/1-0-1823-32.md b/microsoft-edge/webview2/release-notes/sdk/1-0-1823-32.md
index cbda45d55b..d025d97706 100644
--- a/microsoft-edge/webview2/release-notes/sdk/1-0-1823-32.md
+++ b/microsoft-edge/webview2/release-notes/sdk/1-0-1823-32.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 06/11/2026
+ms.date: 06/05/2023
 ---
 # Release SDK 1.0.1823.32, for Runtime 114 (Jun. 5, 2023)
 
diff --git a/microsoft-edge/webview2/release-notes/sdk/1-0-1829-prerelease.md b/microsoft-edge/webview2/release-notes/sdk/1-0-1829-prerelease.md
index 346eb96831..a9ab4fef1d 100644
--- a/microsoft-edge/webview2/release-notes/sdk/1-0-1829-prerelease.md
+++ b/microsoft-edge/webview2/release-notes/sdk/1-0-1829-prerelease.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 06/11/2026
+ms.date: 05/08/2023
 ---
 # Prerelease SDK 1.0.1829-prerelease, for Runtime 115 (May 8, 2023)
 
diff --git a/microsoft-edge/webview2/release-notes/sdk/1-0-1901-177.md b/microsoft-edge/webview2/release-notes/sdk/1-0-1901-177.md
index 4f5296a587..5af22b8c8d 100644
--- a/microsoft-edge/webview2/release-notes/sdk/1-0-1901-177.md
+++ b/microsoft-edge/webview2/release-notes/sdk/1-0-1901-177.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 06/11/2026
+ms.date: 07/24/2023
 ---
 # Release SDK 1.0.1901.177, for Runtime 115 (Jul. 24, 2023)
 
diff --git a/microsoft-edge/webview2/release-notes/sdk/1-0-1905-prerelease.md b/microsoft-edge/webview2/release-notes/sdk/1-0-1905-prerelease.md
index 7aa558a59d..25afab81c2 100644
--- a/microsoft-edge/webview2/release-notes/sdk/1-0-1905-prerelease.md
+++ b/microsoft-edge/webview2/release-notes/sdk/1-0-1905-prerelease.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 06/11/2026
+ms.date: 06/12/2023
 ---
 # Prerelease SDK 1.0.1905-prerelease, for Runtime 116 (Jun. 12, 2023)
 
diff --git a/microsoft-edge/webview2/release-notes/sdk/1-0-1938-49.md b/microsoft-edge/webview2/release-notes/sdk/1-0-1938-49.md
index 746e7b57ff..825987e6bf 100644
--- a/microsoft-edge/webview2/release-notes/sdk/1-0-1938-49.md
+++ b/microsoft-edge/webview2/release-notes/sdk/1-0-1938-49.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 06/11/2026
+ms.date: 08/28/2023
 ---
 # Release SDK 1.0.1938.49, for Runtime 116 (Aug. 28, 2023)
 
diff --git a/microsoft-edge/webview2/release-notes/sdk/1-0-1988-prerelease.md b/microsoft-edge/webview2/release-notes/sdk/1-0-1988-prerelease.md
index ca6170bee5..fa9c7bcabb 100644
--- a/microsoft-edge/webview2/release-notes/sdk/1-0-1988-prerelease.md
+++ b/microsoft-edge/webview2/release-notes/sdk/1-0-1988-prerelease.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 06/11/2026
+ms.date: 07/24/2023
 ---
 # Prerelease SDK 1.0.1988-prerelease, for Runtime 117 (Jul. 24, 2023)
 
diff --git a/microsoft-edge/webview2/release-notes/sdk/1-0-2045-28.md b/microsoft-edge/webview2/release-notes/sdk/1-0-2045-28.md
index 96a67c4e5d..a097816c3f 100644
--- a/microsoft-edge/webview2/release-notes/sdk/1-0-2045-28.md
+++ b/microsoft-edge/webview2/release-notes/sdk/1-0-2045-28.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 06/11/2026
+ms.date: 09/18/2023
 ---
 # Release SDK 1.0.2045.28, for Runtime 117 (Sep. 18, 2023)
 
diff --git a/microsoft-edge/webview2/release-notes/sdk/1-0-2065-prerelease.md b/microsoft-edge/webview2/release-notes/sdk/1-0-2065-prerelease.md
index 5adda01339..190684544d 100644
--- a/microsoft-edge/webview2/release-notes/sdk/1-0-2065-prerelease.md
+++ b/microsoft-edge/webview2/release-notes/sdk/1-0-2065-prerelease.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 06/11/2026
+ms.date: 08/30/2023
 ---
 # Prerelease SDK 1.0.2065-prerelease, for Runtime 118 (Aug. 30, 2023)
 
diff --git a/microsoft-edge/webview2/release-notes/sdk/1-0-4181-prerelease.md b/microsoft-edge/webview2/release-notes/sdk/1-0-4181-prerelease.md
index 3fa23d6343..0896253339 100644
--- a/microsoft-edge/webview2/release-notes/sdk/1-0-4181-prerelease.md
+++ b/microsoft-edge/webview2/release-notes/sdk/1-0-4181-prerelease.md
@@ -14,7 +14,7 @@ Release notes for Microsoft Edge WebView2 Prerelease SDK, release date: Aug. 3,
 
 [NuGet package for WebView2 SDK 1.0.4181-prerelease](https://www.nuget.org/packages/Microsoft.Web.WebView2/1.0.4181-prerelease)
 
-For full API compatibility, this Prerelease version of the WebView2 SDK requires the WebView2 Runtime that ships with Microsoft Edge version 152.0.4181.0 or later; see [Preview Runtime 152.0.4181.0 (Aug. 3, 2026)](../runtime/152.md).
+For full API compatibility, this Prerelease version of the WebView2 SDK requires the WebView2 Runtime that ships with Microsoft Edge version 152.0.4181.0 or later; see [Runtime 152.n.nnnn.nn (Mmm. dd, yyyy)](../runtime/152.md).
 
 
 <!-- ====================================================================== -->
@@ -130,7 +130,7 @@ Releasing or closing the monitor stops all events and clears all filters.
 <!-- ====================================================================== -->
 ## See also
 
-* [Preview Runtime 152.0.4181.0 (Aug. 3, 2026)](../runtime/152.md)
+* [Runtime 152.n.nnnn.nn (Mmm. dd, yyyy)](../runtime/152.md)
 * [Release notes for WebView2](../index.md)
    * [Release notes for the WebView2 Runtime](../runtime/index.md)
    * [Release notes for WebView2 SDKs](./index.md)
diff --git a/microsoft-edge/webview2/release-notes/sdk/1-0-622-22.md b/microsoft-edge/webview2/release-notes/sdk/1-0-622-22.md
index 87db3b39a4..2cdec77c70 100644
--- a/microsoft-edge/webview2/release-notes/sdk/1-0-622-22.md
+++ b/microsoft-edge/webview2/release-notes/sdk/1-0-622-22.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 06/11/2026
+ms.date: 10/19/2020
 ---
 # Release SDK 1.0.622.22, for Runtime 86 (Oct. 19, 2020)
 
diff --git a/microsoft-edge/webview2/release-notes/sdk/1-0-664-37.md b/microsoft-edge/webview2/release-notes/sdk/1-0-664-37.md
index 4106ebfb48..3c0c912fba 100644
--- a/microsoft-edge/webview2/release-notes/sdk/1-0-664-37.md
+++ b/microsoft-edge/webview2/release-notes/sdk/1-0-664-37.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 06/11/2026
+ms.date: 11/20/2020
 ---
 # Release SDK 1.0.664.37, for Runtime 86 (Nov. 20, 2020)
 
diff --git a/microsoft-edge/webview2/release-notes/sdk/1-0-674-prerelease.md b/microsoft-edge/webview2/release-notes/sdk/1-0-674-prerelease.md
index 43f3b4c3de..c7e4fdf395 100644
--- a/microsoft-edge/webview2/release-notes/sdk/1-0-674-prerelease.md
+++ b/microsoft-edge/webview2/release-notes/sdk/1-0-674-prerelease.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 06/11/2026
+ms.date: 10/19/2020
 ---
 # Prerelease SDK 1.0.674-prerelease, for Runtime 86 (Oct. 19, 2020)
 
diff --git a/microsoft-edge/webview2/release-notes/sdk/1-0-705-50.md b/microsoft-edge/webview2/release-notes/sdk/1-0-705-50.md
index ceba6be1c7..f16fb5900a 100644
--- a/microsoft-edge/webview2/release-notes/sdk/1-0-705-50.md
+++ b/microsoft-edge/webview2/release-notes/sdk/1-0-705-50.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 06/11/2026
+ms.date: 01/25/2021
 ---
 # Release SDK 1.0.705.50, for Runtime 86 (Jan. 25, 2021)
 
diff --git a/microsoft-edge/webview2/release-notes/sdk/1-0-721-prerelease.md b/microsoft-edge/webview2/release-notes/sdk/1-0-721-prerelease.md
index dcb55cce80..cc084e3331 100644
--- a/microsoft-edge/webview2/release-notes/sdk/1-0-721-prerelease.md
+++ b/microsoft-edge/webview2/release-notes/sdk/1-0-721-prerelease.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 06/11/2026
+ms.date: 12/08/2020
 ---
 # Prerelease SDK 1.0.721-prerelease, for Runtime 86 (Dec. 8, 2020)
 
diff --git a/microsoft-edge/webview2/release-notes/sdk/1-0-774-44.md b/microsoft-edge/webview2/release-notes/sdk/1-0-774-44.md
index 10ed04f4eb..9340ab29a9 100644
--- a/microsoft-edge/webview2/release-notes/sdk/1-0-774-44.md
+++ b/microsoft-edge/webview2/release-notes/sdk/1-0-774-44.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 06/11/2026
+ms.date: 03/08/2021
 ---
 # Release SDK 1.0.774.44, for Runtime 89 (Mar. 8, 2021)
 
diff --git a/microsoft-edge/webview2/release-notes/sdk/1-0-790-prerelease.md b/microsoft-edge/webview2/release-notes/sdk/1-0-790-prerelease.md
index f3a8e16a16..cba0e287eb 100644
--- a/microsoft-edge/webview2/release-notes/sdk/1-0-790-prerelease.md
+++ b/microsoft-edge/webview2/release-notes/sdk/1-0-790-prerelease.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 06/11/2026
+ms.date: 02/10/2021
 ---
 # Prerelease SDK 1.0.790-prerelease, for Runtime 86 (Feb. 10, 2021)
 
diff --git a/microsoft-edge/webview2/release-notes/sdk/1-0-818-41.md b/microsoft-edge/webview2/release-notes/sdk/1-0-818-41.md
index 968f24e2b3..6b1b2695f7 100644
--- a/microsoft-edge/webview2/release-notes/sdk/1-0-818-41.md
+++ b/microsoft-edge/webview2/release-notes/sdk/1-0-818-41.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 06/11/2026
+ms.date: 04/21/2021
 ---
 # Release SDK 1.0.818.41, for Runtime 90 (Apr. 21, 2021)
 
diff --git a/microsoft-edge/webview2/release-notes/sdk/1-0-824-prerelease.md b/microsoft-edge/webview2/release-notes/sdk/1-0-824-prerelease.md
index e6709f36f3..95e3b5b1ab 100644
--- a/microsoft-edge/webview2/release-notes/sdk/1-0-824-prerelease.md
+++ b/microsoft-edge/webview2/release-notes/sdk/1-0-824-prerelease.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 06/11/2026
+ms.date: 03/08/2021
 ---
 # Prerelease SDK 1.0.824-prerelease, for Runtime 91 (Mar. 8, 2021)
 
diff --git a/microsoft-edge/webview2/release-notes/sdk/1-0-864-35.md b/microsoft-edge/webview2/release-notes/sdk/1-0-864-35.md
index 942d8a09c8..94e38ab74f 100644
--- a/microsoft-edge/webview2/release-notes/sdk/1-0-864-35.md
+++ b/microsoft-edge/webview2/release-notes/sdk/1-0-864-35.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 06/11/2026
+ms.date: 05/31/2021
 ---
 # Release SDK 1.0.864.35, for Runtime 91 (May 31, 2021)
 
diff --git a/microsoft-edge/webview2/release-notes/sdk/1-0-865-prerelease.md b/microsoft-edge/webview2/release-notes/sdk/1-0-865-prerelease.md
index 1df63b1ca7..73e89e7157 100644
--- a/microsoft-edge/webview2/release-notes/sdk/1-0-865-prerelease.md
+++ b/microsoft-edge/webview2/release-notes/sdk/1-0-865-prerelease.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 06/11/2026
+ms.date: 04/26/2021
 ---
 # Prerelease SDK 1.0.865-prerelease, for Runtime 91 (Apr. 26, 2021)
 
diff --git a/microsoft-edge/webview2/release-notes/sdk/1-0-902-49.md b/microsoft-edge/webview2/release-notes/sdk/1-0-902-49.md
index 1bfa606b36..aad44149e4 100644
--- a/microsoft-edge/webview2/release-notes/sdk/1-0-902-49.md
+++ b/microsoft-edge/webview2/release-notes/sdk/1-0-902-49.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 06/11/2026
+ms.date: 07/26/2021
 ---
 # Release SDK 1.0.902.49, for Runtime 92 (Jul. 26, 2021)
 
diff --git a/microsoft-edge/webview2/release-notes/sdk/1-0-902-prerelease.md b/microsoft-edge/webview2/release-notes/sdk/1-0-902-prerelease.md
index dd31ec0079..83e045af50 100644
--- a/microsoft-edge/webview2/release-notes/sdk/1-0-902-prerelease.md
+++ b/microsoft-edge/webview2/release-notes/sdk/1-0-902-prerelease.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 06/11/2026
+ms.date: 06/01/2021
 ---
 # Prerelease SDK 1.0.902-prerelease, for Runtime 92 (Jun. 1, 2021)
 
diff --git a/microsoft-edge/webview2/release-notes/sdk/1-0-955-prerelease.md b/microsoft-edge/webview2/release-notes/sdk/1-0-955-prerelease.md
index 6c724d9a92..43c9654281 100644
--- a/microsoft-edge/webview2/release-notes/sdk/1-0-955-prerelease.md
+++ b/microsoft-edge/webview2/release-notes/sdk/1-0-955-prerelease.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 06/11/2026
+ms.date: 07/26/2021
 ---
 # Prerelease SDK 1.0.955-prerelease, for Runtime 93 (Jul. 26, 2021)
 
diff --git a/microsoft-edge/webview2/release-notes/sdk/1-0-961-33.md b/microsoft-edge/webview2/release-notes/sdk/1-0-961-33.md
index 91ab198a86..cb52f6fcb8 100644
--- a/microsoft-edge/webview2/release-notes/sdk/1-0-961-33.md
+++ b/microsoft-edge/webview2/release-notes/sdk/1-0-961-33.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 06/11/2026
+ms.date: 08/08/2021
 ---
 # Release SDK 1.0.961.33, for Runtime 93 (Sep. 8, 2021)
 
diff --git a/microsoft-edge/webview2/release-notes/sdk/1-0-992-28.md b/microsoft-edge/webview2/release-notes/sdk/1-0-992-28.md
index 2c953ea1ad..e2b974fc98 100644
--- a/microsoft-edge/webview2/release-notes/sdk/1-0-992-28.md
+++ b/microsoft-edge/webview2/release-notes/sdk/1-0-992-28.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 06/11/2026
+ms.date: 09/27/2021
 ---
 # Release SDK 1.0.992.28, for Runtime 94 (Sep. 27, 2021)
 
diff --git a/microsoft-edge/webview2/release-notes/sdk/1-0-nnnn-nn.md b/microsoft-edge/webview2/release-notes/sdk/1-0-nnnn-nn.md
new file mode 100644
index 0000000000..e1134af0ec
--- /dev/null
+++ b/microsoft-edge/webview2/release-notes/sdk/1-0-nnnn-nn.md
@@ -0,0 +1,72 @@
+---
+title: SDK n.n.nnnn.nn, for Runtime 152 (Mmm. dd, yyyy)
+description: Release notes for Microsoft Edge WebView2, for Release SDK n.n.nnnn.nn.
+author: MSEdgeTeam
+ms.author: msedgedevrel
+ms.topic: article
+ms.service: microsoft-edge
+ms.subservice: webview
+ms.date: 01/01/2026
+---
+# SDK n.n.nnnn.nn, for Runtime 152 (Mmm. dd, yyyy)
+
+Release notes for Microsoft Edge WebView2 SDK, release date: Mmm. dd, yyyy.
+
+[NuGet package for WebView2 SDK n.n.nnnn.nn] (https://www.nuget.org/packages/Microsoft.Web.WebView2/n.n.nnnn.nn)
+
+For full API compatibility, this Release version of the WebView2 SDK requires WebView2 Runtime version nnn.n.nnnn.nn or later.
+
+<!-- if a section is empty, omit the section heading -->
+
+
+<!-- ====================================================================== -->
+## Breaking changes
+
+
+<!-- ------------------------------ -->
+#### heading
+
+
+<!-- ====================================================================== -->
+## General changes
+
+
+<!-- ------------------------------ -->
+#### heading
+
+
+<!-- ====================================================================== -->
+## Promotions to Phase 3 (Stable in Release)
+
+The following APIs have been promoted from Phase 2: Stable in Prerelease, to Phase 3: Stable in Release, and are now included in this Release SDK.
+
+
+<!-- ------------------------------ -->
+#### heading
+
+description
+
+Previous phase: [~] (./~.md#~) in _~_.
+
+##### [.NET/C#](#tab/dotnetcsharp)
+
+##### [WinRT/C#](#tab/winrtcsharp)
+
+##### [Win32/C++](#tab/win32cpp)
+
+---
+
+
+<!-- ====================================================================== -->
+## Bug fixes
+
+* Fixed behavior.  ([Issue #] ())
+
+
+<!-- ====================================================================== -->
+## See also
+
+* [Runtime 152.n.nnnn.nn (Mmm. dd, yyyy)](../runtime/152.md)
+* [Release notes for WebView2](../index.md)
+   * [Release notes for the WebView2 Runtime](../runtime/index.md)
+   * [Release notes for WebView2 SDKs](./index.md)
diff --git a/microsoft-edge/webview2/release-notes/sdk/index.md b/microsoft-edge/webview2/release-notes/sdk/index.md
index 73060ebc2a..73c3e71b4b 100644
--- a/microsoft-edge/webview2/release-notes/sdk/index.md
+++ b/microsoft-edge/webview2/release-notes/sdk/index.md
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 08/05/2026
+ms.date: 08/24/2026
 ---
 # Release notes for WebView2 SDKs
 
@@ -15,6 +15,8 @@ list past 10 releases
 in toc.yml, add new relnotes pages, move relnotes pages to archive
 in /webview2/release-notes/sdk/index.md, add new relnotes links, remove earliest relnotes links -->
 Release notes for recent SDKs:
+
+* [SDK n.n.nnnn.nn, for Runtime 152 (Mmm. dd, yyyy)](./1-0-nnnn-nn.md)
 * [SDK 1.0.4181-prerelease, for Runtime 152 (Aug. 3, 2026)](./1-0-4181-prerelease.md)
 * [SDK 1.0.4129.50, for Runtime 151 (Aug. 3, 2026)](./1-0-4129-50.md)
 * [SDK 1.0.4126-prerelease, for Runtime 151 (Jul. 7, 2026)](./1-0-4126-prerelease.md)
@@ -97,17 +99,6 @@ SDKs/packages are Prerelease or Release
 -->
 
 
-<!-- ====================================================================== -->
-## Updating the SDK
-
-WebView2 changes may require an update to the Runtime, SDK, or both.  Most new APIs require both Runtime and SDK updates.
-
-To install or update the WebView2 SDK, see [Install or update the WebView2 SDK](../../how-to/machine-setup.md#install-or-update-the-webview2-sdk) in _Set up your Dev environment for WebView2_.
-
-See also:
-* [Updating the Runtime](../runtime/index.md#updating-the-runtime) in _Release notes for the WebView2 Runtime_.
-
-
 <!-- ====================================================================== -->
 ## Recommended browser channel and Runtime
 
@@ -120,10 +111,21 @@ Make sure to re-compile your WebView2 app after updating the WebView2 SDK NuGet
 For more information, see [Matching the Runtime version with the SDK version](../../concepts/versioning.md#matching-the-runtime-version-with-the-sdk-version) in _Prerelease and Release SDKs for WebView2_.
 
 
+<!-- ====================================================================== -->
+## Updating the SDK
+
+WebView2 changes may require an update to the Runtime, SDK, or both.  Most new APIs require both Runtime and SDK updates.
+
+To install or update the WebView2 SDK, see [Install or update the WebView2 SDK](../../how-to/machine-setup.md#install-or-update-the-webview2-sdk) in _Set up your Dev environment for WebView2_.
+
+See also:
+* [Updating the Runtime](../runtime/index.md#updating-the-runtime) in _Release notes for the WebView2 Runtime_.
+
+
 <!-- ====================================================================== -->
 ## Minimum version of the browser or Runtime to load WebView2
 
-To load WebView2, the minimum version of Microsoft Edge or the WebView2 Runtime is 86.0.616.0.  The minimum version to load WebView2 only changes when a breaking change occurs in the web platform.
+To load WebView2, the minimum version of Microsoft Edge or the WebView2 Runtime is 86.0.616.0; see [Runtime 86.0.705.50 (Jan. 25, 2021)](../runtime/86.md).  The minimum version to load WebView2 only changes when a breaking change occurs in the web platform.
 
 To use a Prerelease SDK along with a Microsoft Edge preview channel, see [Test upcoming APIs and features](../../how-to/set-preview-channel.md).
 
@@ -151,9 +153,4 @@ Async methods:
 * [Contact the WebView2 team](../../contact.md)<!-- toc bucket: bottom -->
 * [Release notes for Microsoft Edge web platform](../../../web-platform/release-notes/index.md)
 * [Microsoft Edge release schedule](/deployedge/microsoft-edge-release-schedule)
-
-API Reference:
 * [WebView2 API Reference](../../webview2-api-reference.md)
-   * .NET: [Microsoft.Web.WebView2.Core Namespace](/dotnet/api/microsoft.web.webview2.core)<!-- https://learn.microsoft.com/dotnet/api/microsoft.web.webview2.core -->
-   * WinRT: [Microsoft.Web.WebView2.Core Namespace](/microsoft-edge/webview2/reference/winrt/microsoft_web_webview2_core/)<!-- https://learn.microsoft.com/microsoft-edge/webview2/reference/winrt/microsoft_web_webview2_core/ -->
-   * Win32: [Reference (WebView2 Win32 C++)](/microsoft-edge/webview2/reference/win32/)<!-- https://learn.microsoft.com/microsoft-edge/webview2/reference/win32/ -->
diff --git a/microsoft-edge/webview2/samples/webview2-winui3-sample.md b/microsoft-edge/webview2/samples/webview2-winui3-sample.md
index f7fbf794d9..927e8a15e9 100644
--- a/microsoft-edge/webview2/samples/webview2-winui3-sample.md
+++ b/microsoft-edge/webview2/samples/webview2-winui3-sample.md
@@ -216,7 +216,7 @@ To install the **Windows 10 SDK** component of the **Windows application develop
    ![Sample app](./webview2-winui3-sample-images/sample-app.png)
 
    The message "Navigation complete" is displayed at the bottom.
- 
+
 1. In the Address bar (a text box), enter `https://bing.com` (a complete HTTPS URL), and then press **Enter** (equivalent to clicking the **Go** button).
 
    The WebView2 control navigates to Bing and then displays "Navigation complete" at the bottom.
@@ -424,7 +424,7 @@ public MainWindow()
         if (WebView2 != null)
         {
             // Ensure that WebView2 resources are released when
-            // the MainWindow is closed. 
+            // the MainWindow is closed.
             // WebView2 lifecycle in WinUI3 and the Close() method:
             // https://github.com/microsoft/microsoft-ui-xaml/issues/4752#issuecomment-819687363
             WebView2.Close();
diff --git a/microsoft-edge/webview2/samples/webview2apissample.md b/microsoft-edge/webview2/samples/webview2apissample.md
index 4a2f7264d7..3d5b087fce 100644
--- a/microsoft-edge/webview2/samples/webview2apissample.md
+++ b/microsoft-edge/webview2/samples/webview2apissample.md
@@ -74,7 +74,7 @@ This sample was created with Visual Studio 2019, as a Visual Studio 2019 project
 <!-- ---------- -->
 ###### Visual Studio 2017
 
-If you want to open this sample by using Visual Studio 2017: 
+If you want to open this sample by using Visual Studio 2017:
 
 1. Open the solution in Visual Studio 2017.
 
@@ -284,7 +284,7 @@ At the top of Visual Studio, set the build target, as follows:
 
    This builds the project file `SampleApps/WebView2APISample/WebView2APISample.vcxproj`.
 
-1. Select **Debug** > **Start Debugging** (**F5**).  
+1. Select **Debug** > **Start Debugging** (**F5**). 
 
    The **WebView2APISample** app window opens:
 
@@ -346,7 +346,7 @@ Assuming you updated the Prerelease version of the WebView2 SDK, build and run t
 
 1. In **Solution Explorer**, right-click the **WebView2APISample** project, and then select **Build**.
 
-1. Select **Debug** > **Start Debugging** (**F5**).  
+1. Select **Debug** > **Start Debugging** (**F5**). 
 
    The **WebView2APISample** app window opens:
 
@@ -702,7 +702,7 @@ The following steps show how the WebView can modify the Win32 Host App by changi
    {
       wil::unique_cotaskmem_string uri;
       CHECK_FAILURE(args->get_Source(&uri));
-   
+  
       // Always validate that the origin of the message is what you expect.
       if (uri.get() != m_sampleUri)
       {
@@ -711,7 +711,7 @@ The following steps show how the WebView can modify the Win32 Host App by changi
       wil::unique_cotaskmem_string messageRaw;
       CHECK_FAILURE(args->TryGetWebMessageAsString(&messageRaw));
       std::wstring message = messageRaw.get();
-   
+  
       if (message.compare(0, 13, L"SetTitleText ") == 0)
       {
          m_appWindow->SetTitleText(message.substr(13).c_str());
diff --git a/microsoft-edge/webview2/samples/webview2browser.md b/microsoft-edge/webview2/samples/webview2browser.md
index 5ffc1bfedf..6a7c5e49df 100644
--- a/microsoft-edge/webview2/samples/webview2browser.md
+++ b/microsoft-edge/webview2/samples/webview2browser.md
@@ -1,6 +1,6 @@
 ---
 title: Win32 sample WebView2Browser
-description: "A web browser built with the Microsoft Edge WebView2 control."
+description: A web browser built with the Microsoft Edge WebView2 control.
 author: MSEdgeTeam
 ms.author: msedgedevrel
 ms.topic: article
@@ -129,7 +129,7 @@ WebView2Browser has a multi-WebView approach to integrate web content and applic
 The multi-WebView approach involves using two separate WebView environments (each with its own user data directory): one for the UI WebViews and the other for all content WebViews. UI WebViews (controls and options dropdown list) use the UI environment, while web content WebViews (one per tab) use the content environment.
 
 ![Browser layout](./webview2browser-images/layout.png)
-<!-- todo: remove png from other repo, in PR 140: 
+<!-- todo: remove png from other repo, in PR 140:
 ![Browser layout](https://raw.githubusercontent.com/MicrosoftEdge/WebView2Browser/master/screenshots/layout.png)
 -->
 
@@ -156,36 +156,36 @@ The **WebView2Browser** sample implements the following features:
 
 WebView2Browser makes use of a handful of the APIs available in WebView2. For the APIs not used here, you can find more about them in the [Microsoft Edge WebView2 Reference](/microsoft-edge/webview2/reference/win32). The following is a list of the most interesting APIs WebView2Browser uses and the features they enable.
 
-API | Features
-:--- | :---
-`CreateCoreWebView2EnvironmentWithOptions` | Used to create the environments for UI and content WebViews. Different user data directories are passed to isolate UI from web content. |
-`ICoreWebView2` | There are several WebViews in WebView2Browser and most features make use of members in this interface, the table below shows how they're used.
-`ICoreWebView2DevToolsProtocolEventReceivedEventHandler` | Used along with add_DevToolsProtocolEventReceived to listen for CDP security events to update the lock icon in the browser UI. |
-`ICoreWebView2DevToolsProtocolEventReceiver` | Used along with `add_DevToolsProtocolEventReceived` to listen for CDP security events to update the lock icon in the browser UI. |
-`ICoreWebView2ExecuteScriptCompletedHandler` | Used along with `ExecuteScript` to get the title and favicon from the visited page. |
-`ICoreWebView2FocusChangedEventHandler` | Used along with `add_LostFocus` to hide the browser options dropdown list when it loses focus.
-`ICoreWebView2HistoryChangedEventHandler` | Used along with `add_HistoryChanged` to update the navigation buttons in the browser UI. |
-`ICoreWebView2Controller` | There are several WebViewControllers in WebView2Browser and we fetch the associated WebViews from them.
-`ICoreWebView2NavigationCompletedEventHandler` | Used along with `add_NavigationCompleted` to update the reload button in the browser UI.
-`ICoreWebView2Settings` | Used to disable DevTools in the browser UI.
-`ICoreWebView2SourceChangedEventHandler` | Used along with `add_SourceChanged` to update the Address bar in the browser UI. |
-`ICoreWebView2WebMessageReceivedEventHandler` | This is one of the most important APIs to WebView2Browser. Most functionalities involving communication across WebViews use this.
-
-ICoreWebView2 API | Features
-:--- | :---
-`add_NavigationStarting` | Used to display the cancel navigation button in the controls WebView.
-`add_SourceChanged` | Used to update the Address bar.
-`add_HistoryChanged` | Used to update go back/forward buttons.
-`add_NavigationCompleted` | Used to display the reload button once a navigation completes.
-`ExecuteScript` | Used to get the title and favicon of a visited page.
-`PostWebMessageAsJson` | Used to communicate WebViews. All messages use JSON to pass parameters needed.
-`add_WebMessageReceived` | Used to handle web messages posted to the WebView.
-`CallDevToolsProtocolMethod` | Used to enable listening for security events, which will notify of security status changes in a document.
-
-ICoreWebView2Controller API | Feature(s)
-:--- | :---
-`get_CoreWebView2` | Used to get the CoreWebView2 associated with this CoreWebView2Controller.
-`add_LostFocus` | Used to hide the options dropdown list when the user clicks away from it.
+| API | Features |
+|---|---|
+| `CreateCoreWebView2EnvironmentWithOptions` | Used to create the environments for UI and content WebViews. Different user data directories are passed to isolate UI from web content. |
+| `ICoreWebView2` | There are several WebViews in WebView2Browser and most features make use of members in this interface, the table below shows how they're used. |
+| `ICoreWebView2DevToolsProtocolEventReceivedEventHandler` | Used along with add_DevToolsProtocolEventReceived to listen for CDP security events to update the lock icon in the browser UI. |
+| `ICoreWebView2DevToolsProtocolEventReceiver` | Used along with `add_DevToolsProtocolEventReceived` to listen for CDP security events to update the lock icon in the browser UI. |
+| `ICoreWebView2ExecuteScriptCompletedHandler` | Used along with `ExecuteScript` to get the title and favicon from the visited page. |
+| `ICoreWebView2FocusChangedEventHandler` | Used along with `add_LostFocus` to hide the browser options dropdown list when it loses focus. |
+| `ICoreWebView2HistoryChangedEventHandler` | Used along with `add_HistoryChanged` to update the navigation buttons in the browser UI. |
+| `ICoreWebView2Controller` | There are several WebViewControllers in WebView2Browser and we fetch the associated WebViews from them. |
+| `ICoreWebView2NavigationCompletedEventHandler` | Used along with `add_NavigationCompleted` to update the reload button in the browser UI. |
+| `ICoreWebView2Settings` | Used to disable DevTools in the browser UI. |
+| `ICoreWebView2SourceChangedEventHandler` | Used along with `add_SourceChanged` to update the Address bar in the browser UI. |
+| `ICoreWebView2WebMessageReceivedEventHandler` | This is one of the most important APIs to WebView2Browser. Most functionalities involving communication across WebViews use this. |
+
+| `ICoreWebView2` API | Features |
+|---|---|
+| `add_NavigationStarting` | Used to display the cancel navigation button in the controls WebView. |
+| `add_SourceChanged` | Used to update the Address bar. |
+| `add_HistoryChanged` | Used to update go back/forward buttons. |
+| `add_NavigationCompleted` | Used to display the reload button once a navigation completes. |
+| `ExecuteScript` | Used to get the title and favicon of a visited page. |
+| `PostWebMessageAsJson` | Used to communicate WebViews. All messages use JSON to pass parameters needed. |
+| `add_WebMessageReceived` | Used to handle web messages posted to the WebView. |
+| `CallDevToolsProtocolMethod` | Used to enable listening for security events, which will notify of security status changes in a document. |
+
+| `ICoreWebView2Controller` API | Features |
+|---|---|
+| `get_CoreWebView2` | Used to get the CoreWebView2 associated with this `CoreWebView2Controller`. |
+| `add_LostFocus` | Used to hide the options dropdown list when the user clicks away from it. |
 
 
 <!-- ====================================================================== -->
diff --git a/microsoft-edge/webview2/samples/webview2samplewincomp.md b/microsoft-edge/webview2/samples/webview2samplewincomp.md
index dc54675e3c..e8db22aeb1 100644
--- a/microsoft-edge/webview2/samples/webview2samplewincomp.md
+++ b/microsoft-edge/webview2/samples/webview2samplewincomp.md
@@ -77,7 +77,7 @@ If the solution is already open, you can change the target as follows:
 <!-- ====================================================================== -->
 ## Step 4 - Install the Windows SDK
 
-By default, this sample app uses the latest Window 10 SDK version you have installed.  There's an issue with Windows 10 SDK, version 2004 (10.0.**19041**.0) that will stop this sample app from building.  If you run into this issue, either install (and retarget this project to use) a later version, such as Windows 10 SDK version 2104 (10.0.**20348**.0), or an earlier version, such as 10.0.**18362**.1.  
+By default, this sample app uses the latest Window 10 SDK version you have installed.  There's an issue with Windows 10 SDK, version 2004 (10.0.**19041**.0) that will stop this sample app from building.  If you run into this issue, either install (and retarget this project to use) a later version, such as Windows 10 SDK version 2104 (10.0.**20348**.0), or an earlier version, such as 10.0.**18362**.1. 
 
 To install a Windows 10 SDK:
 
diff --git a/microsoft-edge/webview2/samples/webview2wpfbrowser.md b/microsoft-edge/webview2/samples/webview2wpfbrowser.md
index 04ef373bc4..8050e6a1cf 100644
--- a/microsoft-edge/webview2/samples/webview2wpfbrowser.md
+++ b/microsoft-edge/webview2/samples/webview2wpfbrowser.md
@@ -110,7 +110,7 @@ At the top of Visual Studio, set the build target, as follows:
    * **View**
    * **Settings**
    * **Scenario**
-   
+  
 1. In the Visual Studio code editor, inspect the code:
 
    ![WebView2WpfBrowser project's code in Visual Studio](./webview2wpfbrowser-images/webview2wpfbrowser-code.png)
diff --git a/microsoft-edge/webview2/samples/wv2deploymentwixcustomactionsample.md b/microsoft-edge/webview2/samples/wv2deploymentwixcustomactionsample.md
index 7d1f5c1d1c..eb58dd943d 100644
--- a/microsoft-edge/webview2/samples/wv2deploymentwixcustomactionsample.md
+++ b/microsoft-edge/webview2/samples/wv2deploymentwixcustomactionsample.md
@@ -119,7 +119,7 @@ If not done yet, install WiX Toolset Visual Studio 2019 Extension:
 <!-- ====================================================================== -->
 ## Step 6 - Edit Product.wxs to configure how to distribute the WebView2 Runtime
 
-1. Open `Product.wxs` under the `WV2DeploymentWiXCustomActionSample` project. 
+1. Open `Product.wxs` under the `WV2DeploymentWiXCustomActionSample` project.
 
 1. Edit `Product.wxs` depending on which approach you want to use:
 
@@ -144,7 +144,7 @@ If you want to package the Evergreen WebView2 Runtime Bootstrapper (`MicrosoftEd
 1. Under `<!-- Step 4: Config Custom Action to download/install Bootstrapper -->`, uncomment the `<Binary Id="MicrosoftEdgeWebview2Setup.exe" ...>` and `<CustomAction Id='InvokeBootstrapper' ...>` elements below `<!-- [Package Bootstrapper] ... -->`.
 
 1. Comment out other `<Binary>` and `<CustomAction>` elements under `Step 4`.
-        
+       
 1. Under `<!-- Step 5: Config execute sequence of custom action -->`, uncomment the `<Custom Action='InvokeBootstrapper' ...>` element below `<!-- [Package Bootstrapper] ...-->`.
 
 1. Comment out other `<Custom>` elements under `Step 5`.
@@ -154,7 +154,7 @@ If you want to package the Evergreen WebView2 Runtime Bootstrapper (`MicrosoftEd
 
 If you want to package the Evergreen WebView2 Runtime Standalone Installer with the app:
 
-1. Under `<!-- Step 4: Config Custom Action to download/install Bootstrapper -->`, uncomment the `<Binary Id="MicrosoftEdgeWebView2RuntimeInstallerX64.exe" ...>` and `<CustomAction Id='InvokeStandalone' ...>` elements below `<!-- [Package Standalone Installer] ... -->`. 
+1. Under `<!-- Step 4: Config Custom Action to download/install Bootstrapper -->`, uncomment the `<Binary Id="MicrosoftEdgeWebView2RuntimeInstallerX64.exe" ...>` and `<CustomAction Id='InvokeStandalone' ...>` elements below `<!-- [Package Standalone Installer] ... -->`.
 
 1. Comment out other `<Binary>` and `<CustomAction>` elements under `Step 4`.
 
diff --git a/scripts/beta-release-notes-template.njk b/scripts/beta-release-notes-template.njk
index 532c2ad070..6e22c47f0e 100644
--- a/scripts/beta-release-notes-template.njk
+++ b/scripts/beta-release-notes-template.njk
@@ -50,10 +50,6 @@ See [What's new in DevTools (Microsoft Edge {{ data.nextBetaVersion }})](../../d
 
 See [Release notes for WebView2](../../webview2/release-notes/index.md).
 <!-- todo: when exists, use instead:
-See [Release SDK 1.0.nnnn.nn, for Runtime nnn](../../webview2/release-notes/index.md#10nnnnnn) ({% monthYear data.nextBetaReleaseDate %}) in _Release notes for the WebView2 SDK_.
--->
-<!-- todo: revise the above per new format: -->
-<!-- todo: when exists, use instead:
 See:
 * [Runtime nnn.n.nnnn.nn (Mmm. dd, yyyy)](../../webview2/release-notes/runtime/nnn.md)
 * [Release SDK n.n.nnnn.nn, for Runtime nnn (Mmm. dd, yyyy)](../../webview2/release-notes/sdk/n-n-nnnn-nn.md)