Fixed some 404 error links, which recently happened on the changes in…

… branch name (#346)

[Note: master branch restored to prevent other 404 issues; however, redirecting these official links to 'main' will be good for long-term health as that is the primary default branch now.]

* Updated error link and removed the same link which is used over the article

* Updated link with main branch name

* Updated links with new branch name "main"

* Updated branch name

* Update link with change in branch name

* Update link on i2i.md with main branch name

* Fixed error links

* Fixed link

* Fixed 404 erro with the change in branch name

* Fixed 404 error with new branch name

* Updated link with the new branch name

Accessibility/CaretBrowsing/designDoc.md

@@ -6,7 +6,7 @@ [email protected], [email protected], [email protected]
 
 ## Introduction
 
-This document provides an overview of the proposed changes in Chromium to support native caret browsing. For a high-level description of native caret browsing and the motivation for introducing the feature, see the associated [explainer doc](https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/master/Accessibility/CaretBrowsing/explainer.md).
+This document provides an overview of the proposed changes in Chromium to support native caret browsing. For a high-level description of native caret browsing and the motivation for introducing the feature, see the associated [explainer doc](https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/Accessibility/CaretBrowsing/explainer.md).
 
 
 ## Changes in the Renderer Process
@@ -89,4 +89,4 @@ Unit test coverage to verify that toggling the caret browsing preference works w
 
 
 ## Implementation and Shipping Plan
-The feature will initially be behind a runtime flag and disabled by default. We will follow the standard Chromium guidelines to determine when to enable the feature by default.
+The feature will initially be behind a runtime flag and disabled by default. We will follow the standard Chromium guidelines to determine when to enable the feature by default.

Accessibility/CaretBrowsing/i2i.md

@@ -6,7 +6,7 @@ [email protected], [email protected], [email protected]
 
 ## Explainer
 
-[Native Caret Browsing Explainer](https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/master/CaretBrowsing/explainer.md)
+[Native Caret Browsing Explainer](https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/CaretBrowsing/explainer.md)
 
 
 ## Design Doc

Accessibility/UIA/i2i.md

@@ -6,7 +6,7 @@ [email protected], [email protected]
 
 ## Explainer
 
-[UI Automation Explainer](https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/master/UIA/explainer.md)
+[UI Automation Explainer](https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/UIA/explainer.md)
 
 ## Design doc/Spec
 
@@ -35,7 +35,7 @@ With UIA, ATs can enhance web browsing for their users in Chromium-based browser
 * Spend less time writing to different accessibility APIs, and more time on core capabilities.
 * Take advantage of a continually-evolving platform, and the performance gains and extended capabilities that come along with it.
 
-For extended background on motivations, please refer to the [explainer](https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/master/UIA/explainer.md).
+For extended background on motivations, please refer to the [explainer](https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/UIA/explainer.md).
 
 ## Risks
 

CSSModules/v1Explainer.md

@@ -60,7 +60,7 @@ One of the main differences between options 2 and 3 is that 3 implies that if a
 
 However, as @tabatkins discussed [here](https://github.com/w3c/webcomponents/issues/759#issuecomment-490685490), option 3 is a significant departure from the current `@import` behavior in a way that can't be reproduced dynamically: the CSS object model can't be used to make multiple sheets depend on a single child stylesheet.  The `.parentStyleSheet` and `.ownerRule` references also pose a problem here as these currently reference only a single sheet and become ambiguous if a sheet were to have multiple importers.
 
-The discussion following [this comment](https://github.com/w3c/webcomponents/issues/759#issuecomment-490256626) contains more extensive discussion of this issue.  Given the lack of consensus on far, we're moving forward with a V1 that sidesteps the question by going with option 1.  This is forward-compatible given that any use of `@import` in a CSS module will prevent the module from loading.  Making progress on this now rather than waiting for a final option 2 vs 3 decision is advantageous given that we can get earlier developer feedback on the feature and a better perspective of how it is used in practice, both of which may help us in making these design decisions.  Additionally, completing a V1 of CSS modules unblocks progress on [HTML modules](https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/master/HTMLModules/designDoc.md).
+The discussion following [this comment](https://github.com/w3c/webcomponents/issues/759#issuecomment-490256626) contains more extensive discussion of this issue.  Given the lack of consensus on far, we're moving forward with a V1 that sidesteps the question by going with option 1.  This is forward-compatible given that any use of `@import` in a CSS module will prevent the module from loading.  Making progress on this now rather than waiting for a final option 2 vs 3 decision is advantageous given that we can get earlier developer feedback on the feature and a better perspective of how it is used in practice, both of which may help us in making these design decisions.  Additionally, completing a V1 of CSS modules unblocks progress on [HTML modules](https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/HTMLModules/designDoc.md).
 
 ## Example: Custom Element Definition using CSS Modules
 

InstallTimePermissionsPrompt/Explainer.md

@@ -69,7 +69,7 @@ As the document that governs the installation and presentation of PWAs within an
 ]
 ```
 
-This example would request five permissions: [Camera access](https://w3c.github.io/permissions/#dom-permissionname-camera), [Microphone access](https://w3c.github.io/permissions/#dom-permissionname-camera), the ability to [send notifications](https://w3c.github.io/permissions/#dom-permissionname-notifications) and [push notifications](https://w3c.github.io/permissions/#dom-permissionname-push), and [the ability to run when a user is logging in to their OS](https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/master/RunOnLogin/Explainer.md).
+This example would request five permissions: [Camera access](https://w3c.github.io/permissions/#dom-permissionname-camera), [Microphone access](https://w3c.github.io/permissions/#dom-permissionname-camera), the ability to [send notifications](https://w3c.github.io/permissions/#dom-permissionname-notifications) and [push notifications](https://w3c.github.io/permissions/#dom-permissionname-push), and [the ability to run when a user is logging in to their OS](https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/RunOnLogin/Explainer.md).
 
 ## User Interface
 

PenAction/explainer.md

@@ -36,7 +36,7 @@ Note with this proposal that there is no mode enabling some manipulations with a
 ## Sample Code
 This sample renders one highlight for each range selected by a pen.  Panning and zooming is still possible using touch, but a separate property (pen-action) is used to disable all the manipulations that could be initiated by using the pen.
 
-To simplify the code that draws the highlight, the example leverages the proposed [Highlights API](https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/master/highlight/explainer.md).
+To simplify the code that draws the highlight, the example leverages the proposed [Highlights API](https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/highlight/explainer.md).
 ```html
 <style>
     :root::highlight(yellow-highlighter) {

RunOnLogin/Explainer.md

@@ -124,7 +124,7 @@ promise.then(function(status) {
 The `navigator.runOnOsLogin.get()` API will not prompt the permission but rather resolve with the status as `"none"` if the permission has not been granted yet or is denied. 
 
 ### Enabling it During Install
-We propose an additional way to enable the capability during the installation process of an installable web app. This option is designed based on a separate work called the [Install Time Permissions Prompt](https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/master/InstallTimePermissionsPrompt/Explainer.md) which uses the Web App Manifest to declare a set of permissions to ask for user consent during the installation of an installable web app.
+We propose an additional way to enable the capability during the installation process of an installable web app. This option is designed based on a separate work called the [Install Time Permissions Prompt](https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/InstallTimePermissionsPrompt/Explainer.md) which uses the Web App Manifest to declare a set of permissions to ask for user consent during the installation of an installable web app.
 
 The *Install Time Permissions Prompt* defines a new member of the Web App Manifest, `request_on_install`. Developers can request a user permission with the following directive in the Web App Manifest:
 

URLProtocolHandler/SecuritySelfReview.md

@@ -59,8 +59,7 @@ This has been created by cut-and-paste from https://w3ctag.github.io/security-qu
 15. Does this specification have a "Security Considerations" and "Privacy Considerations" section?
 
     Yes.
-    https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/master/URLProtocolHandler/explainer.md#security-considerations
-    https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/master/URLProtocolHandler/explainer.md#security-considerations
+    https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/URLProtocolHandler/explainer.md#security-considerations
 
 16. Does this specification allow downgrading default security characteristics?
 

VirtualKeyboardPolicy/explainer.md

@@ -1,6 +1,6 @@
 # Virtual Keyboard Control
 
-**Note - this proposal extends the scope of [VirtualKeyboard Interface](https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/master/VirtualKeyboardAPI/explainer.md)**
+**Note - this proposal extends the scope of [VirtualKeyboard Interface](https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/VirtualKeyboardAPI/explainer.md)**
 
 ## Status of this Document
 This document is intended as a starting point for engaging the community and standards bodies in developing collaborative solutions fit for standardization. As the solutions to problems described in this document progress along the standards-track, we will retain this document as an archive and use this section to keep the community up-to-date with the most current standards venue and content location of future work and discussions.
@@ -81,7 +81,7 @@ Revisiting the earlier table:
 | editable, `inputmode="text", virtualkeyboardpolicy="auto"` | read-only, `virtualkeyboardpolicy="manual"`                | A VK was shown, but then is hidden (the `virtualkeyboardpolicy` is only applicable to editable elements) |
 
 
-Additionally, two new methods will be added to the VirtualKeyboard interface: ```show``` and ```hide``` (the ```VirtualKeyboard``` interface is introduced in this [separate explainer](https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/master/VirtualKeyboardAPI/explainer.md)). ```show``` will request that the OS show the VK, while ```hide``` requests that the VK be hidden.  Note that the OS has its own heuristics and may not honor the request.
+Additionally, two new methods will be added to the VirtualKeyboard interface: ```show``` and ```hide``` (the ```VirtualKeyboard``` interface is introduced in this [separate explainer](https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/VirtualKeyboardAPI/explainer.md)). ```show``` will request that the OS show the VK, while ```hide``` requests that the VK be hidden.  Note that the OS has its own heuristics and may not honor the request.
 
 ## Examples
 

WebPrivacyAuditing/explainer.md

@@ -56,7 +56,7 @@ A certification program would also allow for the validation of standardized tran
 * Clear browsing data experiences whereby users could clear both client-side browser data in addition to data that's been collected on them by various first and third parties as they browse the web
 
 ### Reducing User Permission Prompts
-Several of the future looking web standard proposals for preserving user privacy—such as the current iterations of the [Storage Access API](https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/master/StorageAccessAPI/explainer.md) and [Privacy Budget](https://github.com/bslassey/privacy-budget)—touch on the use of permission prompts to inform users when some information that could be used to track them is to be shared on the web. Such prompts may be shown when certain technological heuristics say that they should be, disrupting a user's experience while browsing the web.
+Several of the future looking web standard proposals for preserving user privacy—such as the current iterations of the [Storage Access API](https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/StorageAccessAPI/explainer.md) and [Privacy Budget](https://github.com/bslassey/privacy-budget)—touch on the use of permission prompts to inform users when some information that could be used to track them is to be shared on the web. Such prompts may be shown when certain technological heuristics say that they should be, disrupting a user's experience while browsing the web.
 
 An auditing program for privacy on the web could again be used to augment such technological solutions by suppressing user permission prompts on sites that are known to give users control over their privacy.
 

highlight/events-explainer.md

@@ -7,7 +7,7 @@ This document is intended as a starting point for engaging the community and sta
 * Current version: this document
 
 ## Introduction
-[Highlights](https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/master/highlight/explainer.md) give ranges an appearance. Use cases include rendering background colors to denote comments or annotations in a document, powering find-on-page for virtualized content, adding squiggles for spelling and grammar checking, and more.
+[Highlights](https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/highlight/explainer.md) give ranges an appearance. Use cases include rendering background colors to denote comments or annotations in a document, powering find-on-page for virtualized content, adding squiggles for spelling and grammar checking, and more.
 
 These use cases require that the users not only be able to see the highlighted portion of the document, but also interact with it.
 
@@ -72,7 +72,7 @@ Ranges can overlap and each range may belong to more than one HighlightRangeGrou
 
 #### Option 1
 
-Only fire one event on one HighlightRangeGroup. HighlightRangeGroups have a priority order as defined in the [Highlight API explainer](https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/master/highlight/explainer.md). To find the group that will receive the event, sort the HighlightRangeGroup objects in descending priority order and dispatch the event to the first HighlightRangeGroup. The priority order establishes a layering of highlights, so firing the event based on this ordering ensures the higlight "nearest to the user" receives the event.
+Only fire one event on one HighlightRangeGroup. HighlightRangeGroups have a priority order as defined in the [Highlight API explainer](https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/highlight/explainer.md). To find the group that will receive the event, sort the HighlightRangeGroup objects in descending priority order and dispatch the event to the first HighlightRangeGroup. The priority order establishes a layering of highlights, so firing the event based on this ordering ensures the higlight "nearest to the user" receives the event.
 
 It is also possible that there are multiple hit ranges within the target HighlightRangeGroup. To handle this, we also define a priority order for ranges within a HighlightRangeGroup, where the range that was added to the group first has the highest priority and the range added last has the lowest priority. Using this ordering, we take the range with the highest priority to be the HighlightRangePointerEvent's range.