MicrosoftDocs · mikehoffms · Oct 24, 2025 · Oct 28, 2025 · Oct 28, 2025 · Oct 28, 2025
diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md
@@ -4,6 +4,6 @@ This project has adopted the [Microsoft Open Source Code of Conduct](https://ope
 
 Resources:
 
-*   [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct)
-*   [Microsoft Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq)
-*   Contact [opencode@microsoft.com](mailto:opencode@microsoft.com) with questions or concerns
+* [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct)
+* [Microsoft Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq)
+* Contact [opencode@microsoft.com](mailto:opencode@microsoft.com) with questions or concerns
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
@@ -124,6 +124,6 @@ Be sure to include the topic title and the URL for the page.
 <!-- ====================================================================== -->
 ## See also
 
-*  [Getting started with writing and formatting on GitHub](https://help.github.com/github/writing-on-github/getting-started-with-writing-and-formatting-on-github)
-*  [Docs Contributor Guide](https://learn.microsoft.com/contribute/)
-*  [README](README.md)
+* [Getting started with writing and formatting on GitHub](https://help.github.com/github/writing-on-github/getting-started-with-writing-and-formatting-on-github)
+* [Docs Contributor Guide](https://learn.microsoft.com/contribute/)
+* [README](README.md)
diff --git a/README.md b/README.md
@@ -31,11 +31,11 @@ For the latest implementation status and future plans for web platform features
 
 ### File names and directories
 
-*  When adding a webpage (an article implemented as a .md file), you must add an entry for the new webpage in [toc.yml](microsoft-edge/toc.yml), for the article to appear in the Table of Contents.
+* When adding a webpage (an article implemented as a .md file), you must add an entry for the new webpage in [toc.yml](microsoft-edge/toc.yml), for the article to appear in the Table of Contents.
 
-*  A directory can contain more directories or `readme.md` files.
+* A directory can contain more directories or `readme.md` files.
 
-*  Folder/directory names are dash-separated (for example, `f12-tools`) and lowercase.  Directories are used in URLs on the `learn.microsoft.com` site.  Avoid using underscores, PascalCase, or camelCase.
+* Folder/directory names are dash-separated (for example, `f12-tools`) and lowercase.  Directories are used in URLs on the `learn.microsoft.com` site.  Avoid using underscores, PascalCase, or camelCase.
 
 
 <!-- ====================================================================== -->

diff --git a/microsoft-edge/accessibility/build/index.md b/microsoft-edge/accessibility/build/index.md
@@ -24,8 +24,8 @@ Visit [HTML5Accessibility](https://html5accessibility.com) for information on wh
 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).
-*  An application-specific object model such as the Document Object Model (DOM) in Microsoft Edge.
+* Microsoft [UI Automation](/windows/win32/winauto/uiauto-specandcommunitypromise).
+* An application-specific object model such as the Document Object Model (DOM) in Microsoft Edge.
 
 For web developers, certain HTML elements are mapped to UI Automation objects, so in selecting those HTML elements, the developer can use the accessibility properties and events built in to those elements.  While developing your website, you usually only need to make sure that the API is correctly written to, or that the appropriate element is specified, for the application to be accessible.
 
@@ -77,8 +77,8 @@ Verifying that the website you are building works with real assistive technologi
 
 Once you are confident that your website works well with a keyboard, try it with other assistive technologies, such as screen readers.  This testing can uncover issues in the following:
 
-*   Your HTML, ARIA, and CSS.
-*   The level of support of an assistive technology for a feature or technique.
+* Your HTML, ARIA, and CSS.
+* The level of support of an assistive technology for a feature or technique.
 
 Different browsers might map elements to the platform accessibility APIs differently than Microsoft Edge maps them.  While building your interface, it's important to consider each difference.
 
@@ -116,7 +116,7 @@ Under macOS, if you want to test with an assistive technology only available for
 
 If an assistive technology isn't available on your OS or you not possible to install one on a virtual machine or emulator, cloud-based assistive technology testing tools are the next best thing.
 
-*  [Assistiv Labs](https://assistivlabs.com) (a commercial product) enables you to manually test with assistive technologies through any modern web browser.  Select an assistive technology and browser and it connects you with a virtual machine, emulator, or real device that you can interact with.
+* [Assistiv Labs](https://assistivlabs.com) (a commercial product) enables you to manually test with assistive technologies through any modern web browser.  Select an assistive technology and browser and it connects you with a virtual machine, emulator, or real device that you can interact with.
 
 See also [Cloud-based emulators and simulators](../../devtools/device-mode/testing-other-browsers.md#cloud-based-emulators-and-simulators).
 

diff --git a/microsoft-edge/accessibility/design.md b/microsoft-edge/accessibility/design.md
@@ -30,13 +30,13 @@ Users who are blind or who have low vision rely on screen readers to interpret a
 
 Many accessibility users rely on the keyboard to navigate and operate the UI by:
 
-*  Moving focus among elements by pressing the **Tab** key or **Shift+Tab** keys.
+* Moving focus among elements by pressing the **Tab** key or **Shift+Tab** keys.
 
-*  Navigating in container elements such as lists, grids, and tree views by using the arrow keys.
+* Navigating in container elements such as lists, grids, and tree views by using the arrow keys.
 
-*  Invoking actions by pressing the **Enter** key or **Spacebar**.
+* Invoking actions by pressing the **Enter** key or **Spacebar**.
 
-*  Using shortcut keys to efficiently access other app functionality.
+* Using shortcut keys to efficiently access other app functionality.
 
 
 <!-- ====================================================================== -->
@@ -50,10 +50,10 @@ Many common accessibility issues on the web can be solved through good coding pr
 <!-- ====================================================================== -->
 ## Resources
 
-*  [Designing for Inclusion](https://w3.org/WAI/users/Overview.html) - Designing for Inclusion by the W3C Web Accessibility Initiative provides resources to help you better understand users with disabilities and how to design your website with them in mind.
+* [Designing for Inclusion](https://w3.org/WAI/users/Overview.html) - Designing for Inclusion by the W3C Web Accessibility Initiative provides resources to help you better understand users with disabilities and how to design your website with them in mind.
 
-*  [Designing inclusive software](https://msdn.microsoft.com/windows/uwp/accessibility/designing-inclusive-software) - Designing inclusive software discusses Microsoft design principles and practices for the Universal Windows Platform (UWP).
+* [Designing inclusive software](https://msdn.microsoft.com/windows/uwp/accessibility/designing-inclusive-software) - Designing inclusive software discusses Microsoft design principles and practices for the Universal Windows Platform (UWP).
 
-*  [How People with Disabilities Use the Web](https://www.w3.org/WAI/intro/people-use-web/Overview.html) - This resource by the W3C introduces how people with disabilities, including people with age-related impairments, use the Web.
+* [How People with Disabilities Use the Web](https://www.w3.org/WAI/intro/people-use-web/Overview.html) - This resource by the W3C introduces how people with disabilities, including people with age-related impairments, use the Web.
 
-*  [Inclusive Design Toolkit](https://www.microsoft.com/design/practice#howwemake-section) - Microsoft developed the Inclusive Design Toolkit to show how human diversity can create better design constraints and how to connect seemingly niche solutions to broader markets.
+* [Inclusive Design Toolkit](https://www.microsoft.com/design/practice#howwemake-section) - Microsoft developed the Inclusive Design Toolkit to show how human diversity can create better design constraints and how to connect seemingly niche solutions to broader markets.
diff --git a/microsoft-edge/accessibility/index.md b/microsoft-edge/accessibility/index.md
@@ -26,11 +26,11 @@ The articles in this Accessibility section present some best practices, code sam
 
 Microsoft Edge DevTools is built into the Microsoft Edge browser, and includes many accessibility-testing features, to test aspects of webpages including:
 
-*  Alt-text for images, and screen reader support.
-*  Keyboard support.
-*  Text contrast.
-*  Usability with vision deficiencies.
-*  Usability when the browser is narrow.
+* Alt-text for images, and screen reader support.
+* Keyboard support.
+* Text contrast.
+* Usability with vision deficiencies.
+* Usability when the browser is narrow.
 
 See:
 

diff --git a/microsoft-edge/accessibility/test.md b/microsoft-edge/accessibility/test.md
@@ -58,20 +58,20 @@ You can also use the assessment feature of [Accessibility Insights](https://acce
 <!-- ====================================================================== -->
 ## External articles and websites
 
-*  [Assistive technology compatibility tests](http://www.powermapper.com/tests) - Test results showing how different content types and standards behave in assistive technologies (AT) such as screen readers.
+* [Assistive technology compatibility tests](http://www.powermapper.com/tests) - Test results showing how different content types and standards behave in assistive technologies (AT) such as screen readers.
 
-*  [HTML5Accessibility](https://html5accessibility.com) - This site tests which new HTML5 features are accessibly supported by major browsers.
+* [HTML5Accessibility](https://html5accessibility.com) - This site tests which new HTML5 features are accessibly supported by major browsers.
 
-*  [webhint](https://webhint.io) - Use webhint to check for out-of-date libraries, security improvements, performance problems, and accessibility issues.
+* [webhint](https://webhint.io) - Use webhint to check for out-of-date libraries, security improvements, performance problems, and accessibility issues.
 
-*  [Web Accessibility Evaluation Tools List](https://www.w3.org/WAI/ER/tools/index.html) - A list of web accessibility evaluation tools to help determine if websites meet accessibility guidelines.
+* [Web Accessibility Evaluation Tools List](https://www.w3.org/WAI/ER/tools/index.html) - A list of web accessibility evaluation tools to help determine if websites meet accessibility guidelines.
 
 
 <!-- ====================================================================== -->
 ## The Web Accessibility Initiative (WAI)
 
-*  [Accessibility Evaluation Resources](https://www.w3.org/WAI/eval/Overview.html) - Approaches for evaluating websites for accessibility.
+* [Accessibility Evaluation Resources](https://www.w3.org/WAI/eval/Overview.html) - Approaches for evaluating websites for accessibility.
 
-*  [Easy Checks – A First Review of Web Accessibility](https://www.w3.org/WAI/eval/preliminary.html) - Quick checks that help you assess the accessibility of a webpage.
+* [Easy Checks – A First Review of Web Accessibility](https://www.w3.org/WAI/eval/preliminary.html) - Quick checks that help you assess the accessibility of a webpage.
 
-*  [How to Meet WCAG 2.0](https://www.w3.org/WAI/WCAG20/quickref) - A quick reference to Web Content Accessibility Guidelines (WCAG), requirements, success criteria, and techniques.
+* [How to Meet WCAG 2.0](https://www.w3.org/WAI/WCAG20/quickref) - A quick reference to Web Content Accessibility Guidelines (WCAG), requirements, success criteria, and techniques.
diff --git a/microsoft-edge/develop-web-microsoft-edge.md b/microsoft-edge/develop-web-microsoft-edge.md
@@ -46,15 +46,15 @@ The Microsoft Edge browser comes with built-in web development tools, called Mic
 
 With DevTools, you can do the following:
 
-*  Inspect, tweak, and change the styles of elements in the webpage using live tools with a visual interface.  Inspect where the browser stored content to construct the webpage, including `.html`, `.css`, `.js`, and `.png` file formats.
+* Inspect, tweak, and change the styles of elements in the webpage using live tools with a visual interface.  Inspect where the browser stored content to construct the webpage, including `.html`, `.css`, `.js`, and `.png` file formats.
 
-*  Emulate how your webpage behaves on different devices and simulate a mobile environment, complete with different network conditions.  Inspect the network traffic and see the location of the problems.
+* Emulate how your webpage behaves on different devices and simulate a mobile environment, complete with different network conditions.  Inspect the network traffic and see the location of the problems.
 
-*  Debug your JavaScript using breakpoint debugging and with the live console.  Find memory problems and rendering issues with your web apps.
+* Debug your JavaScript using breakpoint debugging and with the live console.  Find memory problems and rendering issues with your web apps.
 
-*  Find accessibility, performance, compatibility, and security issues in your products, and use DevTools to fix the accessibility issues that are found.
+* Find accessibility, performance, compatibility, and security issues in your products, and use DevTools to fix the accessibility issues that are found.
 
-*  Use a development environment to sync changes in DevTools with the file system and from the web.
+* Use a development environment to sync changes in DevTools with the file system and from the web.
 
 <!-- /keep sync'd -->
 
@@ -70,9 +70,9 @@ You can create a Microsoft Edge extension if you have an idea or product that is
 
 A Microsoft Edge extension is structured similarly to a regular web app, and usually includes:
 
-*  An app manifest JSON file that contains basic platform information.
-*  A JavaScript file that defines the behavior of the browser extension.
-*  HTML and CSS files that define the user interface.
+* An app manifest JSON file that contains basic platform information.
+* A JavaScript file that defines the behavior of the browser extension.
+* HTML and CSS files that define the user interface.
 
 See [Overview of Microsoft Edge extensions](./extensions/index.md).
 
@@ -111,12 +111,12 @@ See [Introduction to Microsoft Edge WebView2](./webview2/index.md).
 
 The following are tools to automate testing in Microsoft Edge:
 
-*  **DevTools Protocol** is used to instrument, inspect, debug, and profile browsers.
-*  Use **origin trials** to try experimental APIs.
-*  **Playwright** provides cross-browser automation through a single API.
-*  **Puppeteer**'s API controls Microsoft Edge via DevTools Protocol.
-*  **WebDriver** simulates user interaction with Microsoft Edge.
-*  **webhint** linting checks code for errors and best practices.
+* **DevTools Protocol** is used to instrument, inspect, debug, and profile browsers.
+* Use **origin trials** to try experimental APIs.
+* **Playwright** provides cross-browser automation through a single API.
+* **Puppeteer**'s API controls Microsoft Edge via DevTools Protocol.
+* **WebDriver** simulates user interaction with Microsoft Edge.
+* **webhint** linting checks code for errors and best practices.
 
 See [Test and automation in Microsoft Edge](./test-and-automation/test-and-automation.md).
 

diff --git a/microsoft-edge/developer/index.yml b/microsoft-edge/developer/index.yml
@@ -114,9 +114,12 @@ landingContent:
           - text: Overview of Microsoft Edge extensions
             url: ../extensions/index.md
 
-          - text: Extension concepts and architecture
+          - text: Get started developing an extension
             url: ../extensions/getting-started/index.md
 
+          - text: Extension concepts and architecture
+            url: ../extensions/getting-started/architecture.md
+
       - linkListType: sample
         links:
           - text: "Sample: Picture viewer pop-up webpage"

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
@@ -65,21 +65,21 @@ See also:
 
 To delete a specific network blocking request pattern:
 
-*  In the **Network request blocking** table, hover over a network blocking request pattern, and then click the **Remove** (![Remove blocked request icon](./network-request-blocking-tool-images/remove-blocked-request-icon.png)) button:
+* In the **Network request blocking** table, hover over a network blocking request pattern, and then click the **Remove** (![Remove blocked request icon](./network-request-blocking-tool-images/remove-blocked-request-icon.png)) button:
 
    ![Removing a blocked request](./network-request-blocking-tool-images/remove-blocked-request.png)
 
 To delete all network blocking requests at once:
 
-*  In the toolbar, click the **Remove all patterns** (![Remove all blocked requests icon](./network-request-blocking-tool-images/remove-all-blocked-requests-icon.png)) button.
+* In the toolbar, click the **Remove all patterns** (![Remove all blocked requests icon](./network-request-blocking-tool-images/remove-all-blocked-requests-icon.png)) button.
 
 
 <!-- ====================================================================== -->
 ## Modify a blocked network request
 
 To change an existing blocked network request:
 
-*  In the **Network request blocking** table, hover over a blocked network request, and then click **Edit** (![edit blocked request icon](./network-request-blocking-tool-images/edit-blocked-request-icon.png)):
+* In the **Network request blocking** table, hover over a blocked network request, and then click **Edit** (![edit blocked request icon](./network-request-blocking-tool-images/edit-blocked-request-icon.png)):
 
    ![Editing a blocked request](./network-request-blocking-tool-images/edit-blocked-request.png)
 
@@ -89,7 +89,7 @@ To change an existing blocked network request:
 
 To toggle network request blocking without having to delete and re-create all of the blocked network requests:
 
-*  In the toolbar, select or clear the **Enable network request blocking** checkbox:
+* In the toolbar, select or clear the **Enable network request blocking** checkbox:
 
    ![Toggling network request blocking](./network-request-blocking-tool-images/toggle-request-blocking.png)