Clean up some URLs for default branch main

api/extension-guides/notebook.md

@@ -141,7 +141,7 @@ If a kernel has been directly registered to a `NotebookContentProvider` via the
 
 Samples:
 
-* [GitHub Issues Notebook](https://github.com/microsoft/vscode-github-issue-notebooks/blob/master/src/extension/notebookProvider.ts): Kernel to execute queries for GitHub Issues
+* [GitHub Issues Notebook](https://github.com/microsoft/vscode-github-issue-notebooks/blob/main/src/extension/notebookProvider.ts): Kernel to execute queries for GitHub Issues
 
 <!-- - [HTTP Request Notebook](): Kernel to issue HTTP requests (TODO: PR against https://github.com/Huachao/vscode-restclient to add notebooks) -->
 

blogs/2016/10/31/js_roundup_2.md

@@ -65,9 +65,9 @@ There are two extensions in this section, one for [Atom](https://marketplace.vis
 
 These extensions are in preview because we want your feedback. There are still many shortcuts to include and it is easy for you to add any we may have missed.
 
-1. Go to the extension's GitHub repository ([Atom](https://github.com/waderyan/vscode-atom-keybindings) and [Sublime Text](https://github.com/microsoft/vscode-sublime-keybindings)).
-2. Open the `package.json` file ([Atom](https://github.com/waderyan/vscode-atom-keybindings/blob/master/package.json) and [Sublime Text](https://github.com/microsoft/vscode-sublime-keybindings/blob/master/package.json)).
-3. Add a JSON object to `contributes.keybindings` section of `package.json` as seen below ([Atom](https://github.com/waderyan/vscode-atom-keybindings/blob/master/package.json#L25) and [Sublime Text](https://github.com/microsoft/vscode-sublime-keybindings/blob/master/package.json#L25)).
+1. Go to the extension's GitHub repository ([Atom](https://github.com/microsoft/vscode-atom-keybindings) and [Sublime Text](https://github.com/microsoft/vscode-sublime-keybindings)).
+2. Open the `package.json` file ([Atom](https://github.com/microsoft/vscode-atom-keybindings/blob/master/package.json) and [Sublime Text](https://github.com/microsoft/vscode-sublime-keybindings/blob/master/package.json)).
+3. Add a JSON object to `contributes.keybindings` section of `package.json` as seen below ([Atom](https://github.com/microsoft/vscode-atom-keybindings/blob/master/package.json#L25) and [Sublime Text](https://github.com/microsoft/vscode-sublime-keybindings/blob/master/package.json#L25)).
 4. Open a pull request.
 
 ```json

blogs/2020/02/24/custom-data-format.md

@@ -58,7 +58,7 @@ You then get language features for the defined entities:
 
 ![Custom Data helloworld](custom-data-helloworld.png)
 
-You can try this feature by opening the preconfigured [Custom Data hello world sample](https://github.com/microsoft/vscode-custom-data/tree/master/samples/helloworld) with VS Code. You can edit the HTML/CSS custom data files in order to add, remove, or refine the definitions of custom entities and fine-tune the language features.
+You can try this feature by opening the preconfigured [Custom Data hello world sample](https://github.com/microsoft/vscode-custom-data/tree/main/samples/helloworld) with VS Code. You can edit the HTML/CSS custom data files in order to add, remove, or refine the definitions of custom entities and fine-tune the language features.
 
 The `html.customData` and `css.customData` settings serve as a good starting point for using Custom Data. However, there are other ways to take advantage of Custom Data as well. In the following sections, we describe how extension authors can share curated sets of Custom Data or leverage Custom Data to build language support.
 
@@ -95,7 +95,7 @@ Our built-in [HTML language server](https://github.com/microsoft/vscode/tree/mai
 - Mozilla's [mdn-data](https://github.com/mdn/data) and [mdn-browser-compat-data](https://github.com/mdn/browser-compat-data) packages
 - Chrome's ranking of CSS properties usage
 
-We have published this set of data to [NPM](https://www.npmjs.com/package/vscode-web-custom-data). You can find the data [on GitHub](https://github.com/microsoft/vscode-custom-data/tree/master/web-data) as well. Language server authors might use this dataset in combination with our HTML/CSS language services to implement support for their languages that extend or embed HTML/CSS, or they could use this data to implement support for languages that transpile to HTML/CSS, such as Pug or Stylus. Finally, we will continue to curate this dataset to provide up-to-date language support for HTML/CSS in VS Code.
+We have published this set of data to [NPM](https://www.npmjs.com/package/vscode-web-custom-data). You can find the data [on GitHub](https://github.com/microsoft/vscode-custom-data/tree/main/web-data) as well. Language server authors might use this dataset in combination with our HTML/CSS language services to implement support for their languages that extend or embed HTML/CSS, or they could use this data to implement support for languages that transpile to HTML/CSS, such as Pug or Stylus. Finally, we will continue to curate this dataset to provide up-to-date language support for HTML/CSS in VS Code.
 
 ## Summary
 

docs/languages/css.md

@@ -100,7 +100,7 @@ There is jump to definition for `@import` and `url()` links in CSS, SCSS and Les
 
 ## CSS custom data
 
-You can extend VS Code's CSS support through a declarative [custom data format](https://github.com/microsoft/vscode-css-languageservice/blob/master/docs/customData.md). By setting `css.customData` to a list of JSON files following the custom data format, you can enhance VS Code's understanding of new CSS properties, at-directives, pseudo-classes and pesudo-elements. VS Code will then offer language support such as completion & hover information for the provided properties, at-directives, pseudo-classes and pesudo-elements.
+You can extend VS Code's CSS support through a declarative [custom data format](https://github.com/microsoft/vscode-css-languageservice/blob/main/docs/customData.md). By setting `css.customData` to a list of JSON files following the custom data format, you can enhance VS Code's understanding of new CSS properties, at-directives, pseudo-classes and pesudo-elements. VS Code will then offer language support such as completion & hover information for the provided properties, at-directives, pseudo-classes and pesudo-elements.
 
 You can read more about using custom data in the [vscode-custom-data](https://github.com/microsoft/vscode-custom-data) repository.
 

docs/languages/html.md

@@ -158,7 +158,7 @@ We also support [User Defined Snippets](/docs/editor/userdefinedsnippets.md).
 
 ## HTML custom data
 
-You can extend VS Code's HTML support through a declarative [custom data format](https://github.com/microsoft/vscode-html-languageservice/blob/master/docs/customData.md). By setting `html.customData` to a list of JSON files following the custom data format, you can enhance VS Code's understanding of new HTML tags, attributes and attribute values. VS Code will then offer language support such as completion & hover information for the provided tags, attributes and attribute values.
+You can extend VS Code's HTML support through a declarative [custom data format](https://github.com/microsoft/vscode-html-languageservice/blob/main/docs/customData.md). By setting `html.customData` to a list of JSON files following the custom data format, you can enhance VS Code's understanding of new HTML tags, attributes and attribute values. VS Code will then offer language support such as completion & hover information for the provided tags, attributes and attribute values.
 
 You can read more about using custom data in the [vscode-custom-data](https://github.com/microsoft/vscode-custom-data) repository.
 

release-notes/July_2016.md

@@ -160,7 +160,7 @@ VS Code has a built in link detector that finds `http`, `https`, and `file` link
 
 ### Debug Extension Authoring: Additions to the Debug Protocol
 
-The [debug protocol](https://github.com/microsoft/vscode-debugadapter-node/blob/master/protocol/src/debugProtocol.ts) has been extended in the following areas (and VS Code already provides the corresponding UI):
+The [debug protocol](https://github.com/microsoft/vscode-debugadapter-node/blob/main/protocol/src/debugProtocol.ts) has been extended in the following areas (and VS Code already provides the corresponding UI):
 
 * **Restart Frame**: If a debug adapter returns the capability `supportsRestartFrame`, VS Code shows a **Restart Frame** action in the context menu of the **CALL STACK** view and calls the new `restartFrame` request upon execution of the **Restart Frame** action. The `restartFrame` request must result in a `StoppedEvent` so that the UI can be updated for the new location.
 * **Variable Paging**: 'Variables paging' adds support for paging variables and their children. The debugger UI in VS Code 1.4 uses this to present variables with many children with a better scalable (paged) UI and fetches the children in a piecemeal way. A debug adapter can find out whether the client supports variable paging by checking the value of the `supportsVariablePaging` client capability passed as an argument to the `initializeRequest`.<br>

release-notes/June_2016.md

@@ -425,9 +425,9 @@ Introducing a new command variable is simple:
 
 The debug protocol has been extended in three areas (and VS Code already provides the corresponding UI):
 
-* **Editing variables**: If a debug adapter returns the [capability `supportsSetVariable`](https://github.com/microsoft/vscode-debugadapter-node/blob/master/protocol/src/debugProtocol.ts#L594), VS Code supports setting the value of unstructured (leaf) variables in the Variables view by calling the [`setVariable` request](https://github.com/microsoft/vscode-debugadapter-node/blob/master/protocol/src/debugProtocol.ts#L476).
-* **Stepping backward**: If a debug adapter returns the [capability `supportsStepBack`](https://github.com/microsoft/vscode-debugadapter-node/blob/master/protocol/src/debugProtocol.ts#L592), VS Code enables the UI for stepping back and will call the [`stepBack` request](https://github.com/microsoft/vscode-debugadapter-node/blob/master/protocol/src/debugProtocol.ts#L476).
-* **Show variable type on hover**: If a debug adapter returns the optional `type` attribute for the [`variable` type](https://github.com/microsoft/vscode-debugadapter-node/blob/master/protocol/src/debugProtocol.ts#L741), VS Code will show  the value of this attribute when hovering over the variable's name.
+* **Editing variables**: If a debug adapter returns the [capability `supportsSetVariable`](https://github.com/microsoft/vscode-debugadapter-node/blob/main/protocol/src/debugProtocol.ts#L594), VS Code supports setting the value of unstructured (leaf) variables in the Variables view by calling the [`setVariable` request](https://github.com/microsoft/vscode-debugadapter-node/blob/main/protocol/src/debugProtocol.ts#L476).
+* **Stepping backward**: If a debug adapter returns the [capability `supportsStepBack`](https://github.com/microsoft/vscode-debugadapter-node/blob/main/protocol/src/debugProtocol.ts#L592), VS Code enables the UI for stepping back and will call the [`stepBack` request](https://github.com/microsoft/vscode-debugadapter-node/blob/main/protocol/src/debugProtocol.ts#L476).
+* **Show variable type on hover**: If a debug adapter returns the optional `type` attribute for the [`variable` type](https://github.com/microsoft/vscode-debugadapter-node/blob/main/protocol/src/debugProtocol.ts#L741), VS Code will show  the value of this attribute when hovering over the variable's name.
 
 ### Creating Errors/Warnings from an Extension (Diagnostics)
 
@@ -445,7 +445,7 @@ documents.onDidClose((event) => {
 
 The Monaco Editor is now on [npm](https://www.npmjs.com/package/monaco-editor-core)! It is the VS Code source code editor extracted and packaged as a library that can be integrated in any web application to work in any modern browser. We have created a [playground](https://microsoft.github.io/monaco-editor/index.html) showcasing some of the APIs. You can get it via `npm install monaco-editor`.
 
-All further Monaco Editor specific release notes will be available at its distribution [repository](https://github.com/microsoft/monaco-editor/blob/master/CHANGELOG.md).
+All further Monaco Editor specific release notes will be available at its distribution [repository](https://github.com/microsoft/monaco-editor/blob/main/CHANGELOG.md).
 
 ![Monaco Editor Playground](images/June_2016/monaco-editor-playground.png)
 

release-notes/v1_15.md

@@ -279,7 +279,7 @@ In this release, we've added an Explorer to the Debug view that provides direct
 
 In contrast to the limited Quick Pick UI, the Explorer supports concurrent debug sessions and the scripts are grouped according to folders if used in a multi-root workspace.
 
-A second advantage of the Loaded Scripts Explorer is that it was implemented as an extension and shows a real world example of the new debug API and how to contribute to a tree view. You can find the implementation [here](https://github.com/microsoft/vscode-node-debug/blob/master/src/node/extension/loadedScripts.ts).
+A second advantage of the Loaded Scripts Explorer is that it was implemented as an extension and shows a real world example of the new debug API and how to contribute to a tree view.
 
 ## Languages
 

release-notes/v1_31.md

@@ -422,8 +422,8 @@ The above sample is available at [octref/simple-customdata](https://github.com/o
 
 These guides explain the data format and how to use them through settings and extension Contribution Points.
 
-* [Guide](https://github.com/microsoft/vscode-html-languageservice/blob/master/docs/customData.md) for using HTML Custom Data
-* [Guide](https://github.com/microsoft/vscode-css-languageservice/blob/master/docs/customData.md) for using CSS Custom Data
+* [Guide](https://github.com/microsoft/vscode-html-languageservice/blob/main/docs/customData.md) for using HTML Custom Data
+* [Guide](https://github.com/microsoft/vscode-css-languageservice/blob/main/docs/customData.md) for using CSS Custom Data
 
 ## Extension authoring
 

release-notes/v1_44.md

@@ -441,7 +441,7 @@ More semantic token types are returned by the Typescript Language Server. Color
 * All symbols from the JavaScript default library get a `defaultLibrary` modifier.
 * Function parameters that are callbacks are classified as `function`.
 
-Read the [TypeScript Semantic Highlighting plugin README](https://github.com/aeschli/typescript-vscode-sh-plugin/blob/master/README.md) for an overview of all semantic token types and modifiers returned by the TypeScript language server.
+Read the [TypeScript Semantic Highlighting plugin README](https://github.com/aeschli/typescript-vscode-sh-plugin/blob/main/README.md) for an overview of all semantic token types and modifiers returned by the TypeScript language server.
 
 ### File system error code
 

release-notes/v1_46.md

@@ -447,7 +447,7 @@ Work continues on the [GitHub Pull Requests and Issues](https://marketplace.visu
 * Issue and user suggestions now only trigger in comments and plaintext.
 * The new issue editor enables you to set assignees and labels.
 
-To learn about all the new features and updates, you can see the full [changelog for the 0.17.0](https://github.com/microsoft/vscode-pull-request-github/blob/master/CHANGELOG.md) release of the extension.
+To learn about all the new features and updates, you can see the full [changelog for the 0.17.0](https://github.com/microsoft/vscode-pull-request-github/blob/main/CHANGELOG.md) release of the extension.
 
 ### Remote Development
 

release-notes/v1_47.md

@@ -317,7 +317,7 @@ We've also added the following color tokens for Notebooks:
 
 **Two new samples show how to support debugging in Notebooks**
 
-* [Debugging in a JavaScript Notebook](https://github.com/microsoft/vscode-nodebook/blob/master/README.md) sample
+* [Debugging in a JavaScript Notebook](https://github.com/microsoft/vscode-nodebook/blob/main/README.md) sample
 
   This sample shows how to implement Notebook debugging functionality based on the existing VS Code debugger extensions.
 
@@ -363,7 +363,7 @@ Work continues on the [GitHub Pull Requests and Issues](https://marketplace.visu
 * Label suggestions in the new issue editor.
 * Hover support for issues formatted as GH-123.
 
-To learn about all the new features and updates, you can see the full [changelog for the 0.18.0](https://github.com/microsoft/vscode-pull-request-github/blob/master/CHANGELOG.md) release of the extension.
+To learn about all the new features and updates, you can see the full [changelog for the 0.18.0](https://github.com/microsoft/vscode-pull-request-github/blob/main/CHANGELOG.md) release of the extension.
 
 ### Hex Editor
 
@@ -371,7 +371,7 @@ The [HexEditor](https://marketplace.visualstudio.com/items?itemName=ms-vscode.he
 
 ![Editing in the HexEditor extension](images/1_47/hex-editor-editing.gif)
 
-A full list of notable changes can be found in the [CHANGELOG](https://github.com/microsoft/vscode-hexeditor/blob/master/CHANGELOG.md). Any feedback or issues experienced can be filed against the [vscode-hexeditor repository](https://github.com/microsoft/vscode-hexeditor).
+A full list of notable changes can be found in the [CHANGELOG](https://github.com/microsoft/vscode-hexeditor/blob/main/CHANGELOG.md). Any feedback or issues experienced can be filed against the [vscode-hexeditor repository](https://github.com/microsoft/vscode-hexeditor).
 
 ## Extension authoring
 

release-notes/v1_48.md

@@ -167,7 +167,7 @@ You can try out these features today by installing the [TypeScript 4.0-rc](https
 
 ### Hex Editor
 
-The [HexEditor extension](https://marketplace.visualstudio.com/items?itemName=ms-vscode.hexeditor) sees further improvements this iteration with support for copy and paste, file watching, and find and replace. A full list of notable changes can be found in the [CHANGELOG](https://github.com/microsoft/vscode-hexeditor/blob/master/CHANGELOG.md). Any feedback or issues experienced can be filed against the [vscode-hexeditor repository](https://github.com/microsoft/vscode-hexeditor/issues).
+The [HexEditor extension](https://marketplace.visualstudio.com/items?itemName=ms-vscode.hexeditor) sees further improvements this iteration with support for copy and paste, file watching, and find and replace. A full list of notable changes can be found in the [CHANGELOG](https://github.com/microsoft/vscode-hexeditor/blob/main/CHANGELOG.md). Any feedback or issues experienced can be filed against the [vscode-hexeditor repository](https://github.com/microsoft/vscode-hexeditor/issues).
 
 **Copy and Paste Support**
 
@@ -237,7 +237,7 @@ Work continues on the [GitHub Pull Requests and Issues](https://marketplace.visu
 * Offer to fork a repository when you don't have permissions, when you want to push a commit or **Start Working on an  Issue**.
 * Upgraded the version of the GitHub rest API we use for better performance.
 
-To learn about all the new features and updates, you can see the full [changelog for the 0.19.0](https://github.com/microsoft/vscode-pull-request-github/blob/master/CHANGELOG.md#0190) release of the extension.
+To learn about all the new features and updates, you can see the full [changelog for the 0.19.0](https://github.com/microsoft/vscode-pull-request-github/blob/main/CHANGELOG.md#0190) release of the extension.
 
 ## Extension authoring
 

release-notes/v1_49.md

@@ -286,7 +286,7 @@ You can learn about new extension features and bug fixes in the [Remote Developm
 
 Work continues on the [GitHub Pull Requests and Issues](https://marketplace.visualstudio.com/items?itemName=GitHub.vscode-pull-request-github) extension, which allows you to work on, create, and manage pull requests and issues. One useful update in this release is being able to track multiple repositories, similar to how the build-in Git extension works.
 
-To learn about all the new features and updates, you can see the full [changelog for the 0.20.0](https://github.com/microsoft/vscode-pull-request-github/blob/master/CHANGELOG.md#0200) release of the extension.
+To learn about all the new features and updates, you can see the full [changelog for the 0.20.0](https://github.com/microsoft/vscode-pull-request-github/blob/main/CHANGELOG.md#0200) release of the extension.
 
 ## Extension authoring
 

release-notes/v1_5.md

@@ -332,7 +332,7 @@ An API has been added that provides extensions with some basic control over the
 
 ### Additions to the Debug Protocol
 
-The [debug protocol](https://github.com/microsoft/vscode-debugadapter-node/blob/master/protocol/src/debugProtocol.ts) has been extended in the following areas (and VS Code already provides the corresponding UI):
+The [debug protocol](https://github.com/microsoft/vscode-debugadapter-node/blob/main/protocol/src/debugProtocol.ts) has been extended in the following areas (and VS Code already provides the corresponding UI):
 
 * **IntelliSense Support for the Debug Console**: Debug adapters can now implement the `completions` request to provide suggestion proposals for IntelliSense in the **Debug Console**. To enable this feature in VS Code, a debug adapter has to set the `supportsCompletionsRequest` capability to true.
 
@@ -363,7 +363,7 @@ These are the [closed bugs](https://github.com/microsoft/vscode/issues?q=is%3Ais
 
 ## Monaco Editor 0.6.0
 
-We will create monthly releases of the "Monaco" Editor, in the same rhythm with VS Code. You can see the change log [here](https://github.com/microsoft/monaco-editor/blob/master/CHANGELOG.md).
+We will create monthly releases of the "Monaco" Editor, in the same rhythm with VS Code. You can see the change log [here](https://github.com/microsoft/monaco-editor/blob/main/CHANGELOG.md).
 
 ## Downloads
 

release-notes/v1_50.md

@@ -237,7 +237,7 @@ To start using the TypeScript 4.1 nightly builds, just install the [TypeScript N
 
 Work continues on the [GitHub Pull Requests and Issues](https://marketplace.visualstudio.com/items?itemName=GitHub.vscode-pull-request-github) extension, which allows you to work on, create, and manage pull requests and issues.
 
-To learn about all the new features and updates, you can see the full [changelog for the 0.21.0](https://github.com/microsoft/vscode-pull-request-github/blob/master/CHANGELOG.md#0210) release of the extension.
+To learn about all the new features and updates, you can see the full [changelog for the 0.21.0](https://github.com/microsoft/vscode-pull-request-github/blob/main/CHANGELOG.md#0210) release of the extension.
 
 ### Remote Development
 
@@ -307,7 +307,7 @@ For code action providers, we have added an optional function ([`CodeActionProvi
 
 ### References Viewlet API
 
-The references viewlet now [exports an API](https://github.com/microsoft/vscode-references-view/blob/master/src/references-view.d.ts) that allows its content to be defined by other extensions.
+The references viewlet now [exports an API](https://github.com/microsoft/vscode-references-view/blob/main/src/references-view.d.ts) that allows its content to be defined by other extensions.
 
 ### New theme colors
 

release-notes/v1_51.md

@@ -206,7 +206,7 @@ Possible values are:
 
 Work continues on the [GitHub Pull Requests and Issues](https://marketplace.visualstudio.com/items?itemName=GitHub.vscode-pull-request-github) extension, which allows you to work on, create, and manage pull requests and issues.
 
-To learn about all the new features and updates, you can see the full [changelog for the 0.21.0](https://github.com/microsoft/vscode-pull-request-github/blob/master/CHANGELOG.md#0210) release of the extension.
+To learn about all the new features and updates, you can see the full [changelog for the 0.21.0](https://github.com/microsoft/vscode-pull-request-github/blob/main/CHANGELOG.md#0210) release of the extension.
 
 ### Remote Development
 

release-notes/v1_6.md

@@ -425,7 +425,7 @@ As mentioned in the API documentation, the `window.createTerminal` and `Terminal
 
 ### VS Code Debug Protocol
 
-The VS Code debug protocol specification is now maintained as a [language neutral JSON schema](https://github.com/microsoft/vscode-debugadapter-node/blob/master/debugProtocol.json) instead of a TypeScript definition file. This schema can be used to generate client or server libraries for a specific language automatically. The project [vscode-debugadapter-node](https://github.com/microsoft/vscode-debugadapter-node) contains a [simple program](https://github.com/microsoft/vscode-debugadapter-node/blob/master/src/generator.ts) to generate the TypeScript `d.ts` from the schema. This program can be used as a starting point for other languages.
+The VS Code debug protocol specification is now maintained as a [language neutral JSON schema](https://github.com/microsoft/vscode-debugadapter-node/blob/main/debugProtocol.json) instead of a TypeScript definition file. This schema can be used to generate client or server libraries for a specific language automatically. The project [vscode-debugadapter-node](https://github.com/microsoft/vscode-debugadapter-node) contains a [simple program](https://github.com/microsoft/vscode-debugadapter-node/blob/main/src/generator.ts) to generate the TypeScript `d.ts` from the schema. This program can be used as a starting point for other languages.
 
 ### External Terminal support for 'runInTerminal' request
 
@@ -433,7 +433,7 @@ Debug adapters can now easily run the debug target in an **External Terminal** v
 
 ### Initial Configurations contributed by a command
 
-It is now possible for a debug adapter to specify a command name as a value for `initialConfigurations` attribute of the `debuggers` contribution in the `package.json` file. The debug adapter extension can then register the specified command which will get called once the `launch.json` file is generated for the first time. The command needs to return the initial content of the `launch.json` file - this way debug adapters have more flexibility on customizing `launch.json`. Our example mock debug illustrates this: ['initialConfigurations' contribution](https://github.com/microsoft/vscode-mock-debug/blob/master/package.json#L83) and [command registration](https://github.com/microsoft/vscode-mock-debug/blob/master/src/extension.ts#L29).
+It is now possible for a debug adapter to specify a command name as a value for `initialConfigurations` attribute of the `debuggers` contribution in the `package.json` file. The debug adapter extension can then register the specified command which will get called once the `launch.json` file is generated for the first time. The command needs to return the initial content of the `launch.json` file - this way debug adapters have more flexibility on customizing `launch.json`. Our example mock debug illustrates this: ['initialConfigurations' contribution](https://github.com/microsoft/vscode-mock-debug/blob/main/package.json#L83) and [command registration](https://github.com/microsoft/vscode-mock-debug/blob/main/src/extension.ts#L29).
 
 ### Debug Protocol Additions
 

release-notes/v1_8.md

@@ -286,7 +286,7 @@ Controls the font family, size and line height used in the Markdown preview.
 
 #### vscode-tslint
 
-The `vscode-tslint` extension now supports [TSLint 4.0](https://palantir.github.io/tslint/2016/11/17/new-for-4.0.html). This version of TSLint provides additional quick fixes for warnings. In addition, `vscode-tslint` adds a quick fix to disable a TSLint rule on the next line. The new TSLint version also adds support for linting JavaScript files. See the [CHANGELOG](https://github.com/microsoft/vscode-tslint/blob/master/tslint/CHANGELOG.md) for more details.
+The `vscode-tslint` extension now supports [TSLint 4.0](https://palantir.github.io/tslint/2016/11/17/new-for-4.0.html). This version of TSLint provides additional quick fixes for warnings. In addition, `vscode-tslint` adds a quick fix to disable a TSLint rule on the next line. The new TSLint version also adds support for linting JavaScript files. See the [CHANGELOG](https://github.com/microsoft/vscode-tslint/blob/main/tslint/CHANGELOG.md) for more details.
 
 #### vscode-eslint
 
@@ -473,7 +473,7 @@ Ever since the text document allows to ask for a [word-range](https://github.com
 
 In the `launch.json`, the top level `debugServer` attribute has been deprecated (and support for it will be removed in the February milestone). Instead the `debugServer` attribute has to be specified per launch configuration. More details can be found [here](https://github.com/microsoft/vscode/issues/13783).
 
-Debugger extensions can now contribute launch configuration snippets which will get surfaced in `launch.json` as explained in section "Adding Individual Launch Configurations". This can be done using the regular syntax for contributing snippets to VS Code, but as a `configurationSnippets` attribute inside the `debuggers` section of the `package.json`. An example of how Mock Debug is contributing debug configuration snippets can be found [here](https://github.com/microsoft/vscode-mock-debug/blob/master/package.json#L71).
+Debugger extensions can now contribute launch configuration snippets which will get surfaced in `launch.json` as explained in section "Adding Individual Launch Configurations". This can be done using the regular syntax for contributing snippets to VS Code, but as a `configurationSnippets` attribute inside the `debuggers` section of the `package.json`. An example of how Mock Debug is contributing debug configuration snippets can be found [here](https://github.com/microsoft/vscode-mock-debug/blob/main/package.json#L71).
 
 ### VS Code Debug Protocol
 

release-notes/vApril.md

@@ -158,9 +158,9 @@ The source for this module lives in the GitHub repository [vscode-debugadapter-n
 
 You can find examples of how to use the module here:
 
-* [Node Debug](https://github.com/microsoft/vscode-node-debug/blob/master/src/tests/adapter.test.ts)
+* [Node Debug](https://github.com/microsoft/vscode-node-debug/blob/main/src/tests/adapter.test.ts)
 * [Mono Debug](https://github.com/microsoft/vscode-mono-debug/blob/master/tests/adapter.test.ts)
-* [Mock Debug](https://github.com/microsoft/vscode-mock-debug/blob/master/src/tests/adapter.test.ts)
+* [Mock Debug](https://github.com/microsoft/vscode-mock-debug/blob/main/src/tests/adapter.test.ts)
 
 ## Electron Shell
 

release-notes/vJanuary.md

@@ -362,7 +362,7 @@ More examples can be found in these debug adapter projects on GitHub:
 * [Microsoft/vscode-mock-debug](https://github.com/microsoft/vscode-mock-debug)
 * [Microsoft/vscode-mono-debug](https://github.com/microsoft/vscode-mono-debug)
 
-You can see the Promise-based API in [DebugClient.ts](https://github.com/microsoft/vscode-node-debug/blob/master/src/tests/DebugClient.ts) and an initial set of tests in [adapter.test.ts](https://github.com/microsoft/vscode-node-debug/blob/master/src/tests/adapter.test.ts). We plan to make this API available as an npm module in February.
+You can see an initial set of tests in [adapter.test.ts](https://github.com/microsoft/vscode-node-debug/blob/main/src/tests/adapter.test.ts). We plan to make this API available as an npm module in February.
 
 ### JSON mode is now an extension