Merge pull request #6901 from dotnet/mkArtakMSFT-patch-1

Updated ASP.NET 6.0 known issues

.github/ISSUE_TEMPLATE/01_bug_report.md

@@ -0,0 +1,42 @@
+---
+name: General bug report
+about: If you're not sure where to create the .NET issue, click here
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+<!--This is just a template - feel free to delete any and all of it and replace as appropriate. If you're not sure of an answer, just skip it. We'll help you! -->
+
+### Description
+
+<!--
+* Please share a clear and concise description of the problem.
+* Include minimal steps to reproduce the problem if possible. E.g.: the smallest possible code snippet; or a small repo to clone, with steps to run it.
+* What behavior are you seeing, and what behavior would you expect?
+  -->
+
+### Configuration
+
+<!--
+* Which version of .NET is the code running on?
+* What OS and version, and for Linux, what distro?
+* What is the architecture (x64, x86, ARM, ARM64)?
+* Do you know whether it is specific to that configuration?
+* If you're using Blazor, which web browser(s) do you see this issue in?
+  -->
+
+### Regression?
+
+<!--
+* Did this work in a previous build or release of .NET Core, or from .NET Framework? If you can try a previous release or build to find out, that can help us narrow down the problem. If you don't know, that's OK.
+  -->
+
+### Other information
+
+<!--
+* Please include any relevant stack traces or error messages. If possible please include text as text rather than images (so it shows up in searches).
+* If you have an idea where the problem might lie, let us know that here. Please include any pointers to code, relevant changes, or related issues you know of.
+* Do you know of any workarounds?
+  -->

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,26 @@
+blank_issues_enabled: true
+contact_links:
+  - name: Issue with ASP.NET Core
+    url:  https://github.com/dotnet/aspnetcore/issues/new/choose
+    about: Please open issues relating to ASP.NET Core in dotnet/aspnetcore.
+  - name: Issue with .NET runtime or core .NET libraries
+    url:  https://github.com/dotnet/runtime/issues/new/choose
+    about: Please open issues with the .NET runtime or core .NET libraries in dotnet/runtime.
+  - name: Issue with .NET SDK
+    url:  https://github.com/dotnet/sdk/issues/new/choose
+    about: Please open issues relating to the .NET SDK in dotnet/sdk.
+  - name: Issue with Entity Framework
+    url:  https://github.com/dotnet/efcore/issues/new/choose
+    about: Please open issues relating to Entity Framework in dotnet/efcore.
+  - name: Issue with Roslyn compiler
+    url:  https://github.com/dotnet/roslyn/issues/new/choose
+    about: Please open issues relating to the Roslyn .NET compiler in dotnet/roslyn.
+  - name: Issue with Windows Forms
+    url:  https://github.com/dotnet/winforms/issues/new/choose
+    about: Please open issues relating to Windows Forms in dotnet/winforms.
+  - name: Issue with WPF
+    url:  https://github.com/dotnet/wpf/issues/new/choose
+    about: Please open issues relating to WPF in dotnet/wpf.
+  - name: Issue with .NET Framework
+    url:  https://developercommunity.visualstudio.com/spaces/61/index.html
+    about: Please open issues relating to the .NET Framework (rather than .NET Core or .NET 5+) in Developer Community

.github/ISSUE_TEMPLATES/epic.md

@@ -0,0 +1,21 @@
+---
+name: Epic
+about: Use this template for creating Epics
+labels: Epic
+---
+
+<!--This is  a template - feel free to delete any and all of it and replace as appropriate-->
+
+### Summary
+
+Describe a specific and tangible customer Epic that is delivered over the course of the product release.
+
+
+<!--We will include a markdown list of all User Stories under this Epic-->
+
+
+### User Stories
+
+User Stories under this Epic:
+
+- [ ] [Title of the linked User Story](hyperlink to the User Story issue).

.github/ISSUE_TEMPLATES/theme.md

@@ -0,0 +1,23 @@
+---
+name: Theme
+about: Use this template for creating Themes
+title: ''
+labels: theme
+assignees: ''
+
+---
+
+<!--This is  a template - feel free to delete any and all of it and replace as appropriate-->
+
+### Summary
+
+Describe a Theme that will be delivered over the release.
+
+
+<!--We will include a markdown list of all Epics under this Theme-->
+
+### Epics
+
+Epics under this Theme:
+
+- [ ] [Title of the linked Epic](hyperlink to the Epic issue).

.github/ISSUE_TEMPLATES/user_story.md

@@ -0,0 +1,18 @@
+---
+name: User Story
+about: Use this template for creating user stories
+labels: User Story
+---
+
+<!--This is  a template - feel free to delete any and all of it and replace as appropriate-->
+
+### Summary
+
+Describe a specific user story experience. Use the format:
+
+As a [__**user type**__], I want to [__**task**__] so that [__**goal**__].”
+
+
+For example:
+
+As a [__**customer**__], I want to [__**create an account**__] so that [__**I can make purchases**__].

.github/dependabot.yml

@@ -1,27 +0,0 @@
-version: 2
-updates:
-- package-ecosystem: nuget
-  directory: "/samples/dotnetbot"
-  schedule:
-    interval: daily
-  open-pull-requests-limit: 10
-- package-ecosystem: nuget
-  directory: "/samples/helloworld"
-  schedule:
-    interval: daily
-  open-pull-requests-limit: 10
-- package-ecosystem: nuget
-  directory: "/samples/qotd"
-  schedule:
-    interval: daily
-  open-pull-requests-limit: 10
-- package-ecosystem: nuget
-  directory: "/samples/helloworldasync"
-  schedule:
-    interval: daily
-  open-pull-requests-limit: 10
-- package-ecosystem: nuget
-  directory: "/samples/dotnetsay"
-  schedule:
-    interval: daily
-  open-pull-requests-limit: 10

.github/no-response.yml

@@ -1,7 +1,7 @@
 # Configuration for probot-no-response - https://github.com/probot/no-response
 
 # Number of days of inactivity before an Issue is closed for lack of response
-daysUntilClose: 10
+daysUntilClose: 7
 # Label requiring a response
 responseRequiredLabel: needs-more-info
 # Comment to post when closing an Issue for lack of response. Set to `false` to disable

CONTRIBUTING.md

@@ -1,6 +1,6 @@
 # Contributing
 
-See [Contributing](https://github.com/dotnet/coreclr/blob/master/Documentation/project-docs/contributing.md) for information about coding styles, source structure, making pull requests, and more.
+See [Contributing](https://github.com/dotnet/runtime/blob/main/CONTRIBUTING.md) for information about coding styles, source structure, making pull requests, and more.
 
 # Repos
 

Documentation/build-and-install-rhel6-prerequisites.md

@@ -1,8 +1,8 @@
 # How to use .NET Core on RHEL 6 / CentOS 6
 This document describes the prerequisites required to run .NET Core applications on RHEL / CentOS 6. Since this version is quite old, there are two runtime libraries that are not available as standard  installation packages in versions that .NET Core can use, so they need to be obtained in different ways described in the sections below.
 ## Required packages
-.NET Core requires the following packages to be installed on RHEL 6: 
-* epel-release 
+.NET Core requires the following packages to be installed on RHEL 6:
+* epel-release
 * libunwind
 * openssl
 * libnghttp2
@@ -22,7 +22,7 @@ This document describes the prerequisites required to run .NET Core applications
     }
 }
 ```
-For more information about enabling or disabling the Globalization, you may refer to the [Globalization Invariant Mode Doc](https://github.com/dotnet/corefx/blob/master/Documentation/architecture/globalization-invariant-mode.md)
+For more information about enabling or disabling the Globalization, you may refer to the [Globalization Invariant Mode Doc](https://github.com/dotnet/runtime/blob/main/docs/design/features/globalization-invariant-mode.md)
 
 ## Getting the libraries that are not available as packages.
 ### ICU
@@ -35,13 +35,13 @@ First install the prerequisites:
 ```sh
 yum install -y \
     wget \
-    epel-release 
+    epel-release
 
 yum install -y \
     openssl-devel \
     libnghttp2-devel \
     libidn-devel \
-    gcc 
+    gcc
 ```
 Now untar the source code
 ```sh
@@ -83,11 +83,11 @@ make install
 ```
 Now pack the compiled CURL:
 ```sh
-cd install 
+cd install
 tar -czf curl-7_45_0-RHEL6-x64.tgz *
 ```
 ## Making the libraries available for a .NET Core application
-There are several ways to do this. The following paragraphs describe them. 
+There are several ways to do this. The following paragraphs describe them.
 ### Install the libraries into /usr/local
 First untar the .tgz files as follows:
 ```sh
@@ -109,7 +109,7 @@ tar -xf /your/path/to/icu4c-57_1-RHEL6-x64.tgz --strip-components=3 usr/local/li
 ### For the app developers – pack the libraries with your application
 The steps are the same as for the previous option, but they are done by the app developer. The app is then packaged including the libraries.
 ## Troubleshooting
-**Q1:** I try to run a .NET Core application on RHEL 6 / CentOS 6 and I get the following exception: 
+**Q1:** I try to run a .NET Core application on RHEL 6 / CentOS 6 and I get the following exception:
 ```
 FailFast: Couldn't find a valid ICU package installed on the system. Set the configuration flag System.Globalization.Invariant to true if you want to run with no globalization support.
 
@@ -128,7 +128,7 @@ FailFast: Couldn't find a valid ICU package installed on the system. Set the con
 Aborted (core dumped)
 ```
 **A1:** The ICU libraries were not extracted from `icu4c-57_1-RHEL6-x64.tgz` to the right place, or `LD_LIBRARY_PATH` was not set to `/usr/local/lib`. See the [Making the libraries available for a .NET Core application](#making-the-libraries-available-for-a-net-core-application) section.
- 
+
 
 **Q2:** I try to run a .NET Core application on RHEL 6 / CentOS 6 and I get the exception similar to the following one:
 ```

Documentation/core-repos.md

@@ -4,28 +4,28 @@
 
 ## .NET Core
 
-|Repository                                                        |Description |
-|------------------------------------------------------------------|------------|
-|[dotnet/core](https://github.com/dotnet/core)                     |.NET Core home repository|
-|[dotnet/runtime](https://github.com/dotnet/runtime)               |.NET Core runtime, runtime installers, application model, & Base Class Library (BCL)|
-|[dotnet/docs](https://github.com/dotnet/docs)                     |.NET documentation|
+|Repository                                                          |Description |
+|--------------------------------------------------------------------|------------|
+|[dotnet/core](https://github.com/dotnet/core)                       |.NET Core home repository|
+|[dotnet/runtime](https://github.com/dotnet/runtime)                 |.NET Core runtime, runtime installers, application model, & Base Class Library (BCL)|
+|[dotnet/docs](https://github.com/dotnet/docs)                       |.NET documentation|
 |[dotnet/dotnet-api-docs](https://github.com/dotnet/dotnet-api-docs) |.NET API documentation|
-|[dotnet/project-system](https://github.com/dotnet/project-system) |Visual Studio project system for C#, F#, & VB|
-|[dotnet/sdk](https://github.com/dotnet/sdk)                       |.NET Core SDK (used by Visual Studio & .NET Core CLI)|
-|[dotnet/installer](https://github.com/dotnet/installer)           |.NET Core installer (produces zips, tarballs, and installers for the .NET SDK)
-|[dotnet/extensions](https://github.com/dotnet/extensions)         |.NET extension APIs (DI, logging, configuration, etc.)|
-|[dotnet/dotnet-docker](https://github.com/dotnet/dotnet-docker)   |.NET Core Docker images|
-|[dotnet/templating](https://github.com/dotnet/templating)         |Templating engine used by `dotnet new`|
-|[dotnet/test-templates](https://github.com/dotnet/test-templates) |.NET Core unit testing project templates|
-|[dotnet/winforms](https://github.com/dotnet/winforms)             |Windows Forms|
-|[dotnet/wpf](https://github.com/dotnet/wpf)                       |Windows Presentation Foundation (WPF)|
-|[dotnet/maui](https://github.com/dotnet/maui)                     |.NET Multi-platform App UI|
+|[dotnet/project-system](https://github.com/dotnet/project-system)   |Visual Studio project system for C#, F#, & VB|
+|[dotnet/sdk](https://github.com/dotnet/sdk)                         |.NET Core SDK (used by Visual Studio & .NET Core CLI)|
+|[dotnet/installer](https://github.com/dotnet/installer)             |.NET Core installer (produces zips, tarballs, and installers for the .NET SDK)
+|[dotnet/extensions](https://github.com/dotnet/extensions)           |.NET extension APIs (DI, logging, configuration, etc.)|
+|[dotnet/dotnet-docker](https://github.com/dotnet/dotnet-docker)     |.NET Core Docker images|
+|[dotnet/templating](https://github.com/dotnet/templating)           |Templating engine used by `dotnet new`|
+|[dotnet/test-templates](https://github.com/dotnet/test-templates)   |.NET Core unit testing project templates|
+|[dotnet/winforms](https://github.com/dotnet/winforms)               |Windows Forms|
+|[dotnet/wpf](https://github.com/dotnet/wpf)                         |Windows Presentation Foundation (WPF)|
+|[dotnet/maui](https://github.com/dotnet/maui)                       |.NET Multi-platform App UI|
 
 ## .NET Framework
 
-|Repository                                                        |Description |
-|------------------------------------------------------------------|------------|
-|[microsoft/dotnet](https://github.com/microsoft/dotnet) |Catch-all repository for .NET (where most .NET Framework issues are filed)|
+|Repository                                                                                |Description |
+|------------------------------------------------------------------------------------------|------------|
+|[Dev Community](https://developercommunity.visualstudio.com/spaces/61/index.html)         |Report issues to .NET Framework Developer Community|
 |[microsoft/dotnet-framework-docker](https://github.com/microsoft/dotnet-framework-docker) |.NET Framework Docker images|
 
 ## .NET Standard
@@ -59,6 +59,15 @@
 |[dotnet/EntityFramework.Docs](https://github.com/dotnet/EntityFramework.Docs)|EF Core & EF 6 documentation          |
 |[dotnet/sqlclient](https://github.com/dotnet/sqlclient)                      |SqlClient data provider for SQL Server|
 
+## Machine Learning and AI
+
+|Repository                                                                                    |Description              |
+|----------------------------------------------------------------------------------------------|-------------------------|
+|[dotnet/machinelearning](https://github.com/dotnet/machinelearning)                           |ML.NET                   |
+|[dotnet/machinelearning-modelbuilder](https://github.com/dotnet/machinelearning-modelbuilder) |ML.NET Tooling           |
+|[dotnet/ml-api-docs](https://github.com/dotnet/ml-api-docs)                                   |ML.NET API documentation |
+|[dotnet/spark](https://github.com/dotnet/spark)                                               |.NET for Apache® Spark™  |
+
 ## Languages
 
 |Repository                                                               |Description                                            |

Documentation/diagnostics/portable_pdb.md

@@ -9,7 +9,7 @@ The Windows PDB format has been around a long time now (~25 years), and it evolv
 ## Why a new format? ##
 While the Windows PDB format has worked okay over the years, with .NET Core the [Roslyn](https://github.com/dotnet/roslyn/wiki/Roslyn%20Overview) team decided it was time to go back to the drawing board and come up with a new format. A few of the reasons:
 
-* The Windows PDB format is complex, and not well documented. This complexity is important for some of the native code scenarios that the format was designed for, but it is unnecessary for the .NET scenarios. The portable format is [open source](https://github.com/dotnet/symreader-portable) and [documented](https://github.com/dotnet/runtime/blob/master/docs/design/specs/PortablePdb-Metadata.md).
+* The Windows PDB format is complex, and not well documented. This complexity is important for some of the native code scenarios that the format was designed for, but it is unnecessary for the .NET scenarios. The portable format is [open source](https://github.com/dotnet/symreader-portable) and [documented](https://github.com/dotnet/runtime/blob/main/docs/design/specs/PortablePdb-Metadata.md).
 * At the time the effort was begun there wasn't a cross-platform library that could read or write the original windows PDB format.
 * The Windows PDB format is not a compact representation for managed code. Significant size reductions can be obtained with a new format without losing any information.
 
@@ -25,7 +25,7 @@ Portable PDBs can be read on any operating system, but there are a number of pla
 * Some symbol servers (ex: SymbolSource.org [does not](https://github.com/SymbolSource/SymbolSource/issues/7#issuecomment-399747015), nuget.org [does](https://blog.nuget.org/20181116/Improved-debugging-experience-with-the-NuGet-org-symbol-server-and-snupkg.html))
 * Running post-compilation build step that consumes or modifies the PDB using older versions of tools such as CCI, CodeContracts.
 * Using .NET decompilers such as ildasm or .Net reflector and expecting to see source line mappings or local parameter names
-* [MS DIA](https://msdn.microsoft.com/en-us/library/ee8x173s.aspx)-based tools such as WinDBG.
+* [MS DIA](https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2015/debugger/debug-interface-access/debug-interface-access-sdk-reference)-based tools such as WinDBG.
 
 Over time we plan to shrink this list of non-supported scenarios so that portable PDB can become the default choice for most usage needs.
 

Documentation/diagnostics/source_link.md

@@ -1 +1 @@
-This document has moved to https://github.com/dotnet/designs/blob/master/accepted/2020/diagnostics/source-link.md
+This document has moved to https://github.com/dotnet/designs/blob/main/accepted/2020/diagnostics/source-link.md

Documentation/linux-setup.md

@@ -8,8 +8,8 @@ There are a few options available for installing .NET Core on Linux systems and
 
 Other useful references
 
-* [OS lifecycle support policy](https://github.com/dotnet/core/blob/master/os-lifecycle-policy.md)
-* [Linux System Prerequisites](https://github.com/dotnet/core/blob/master/Documentation/linux-prereqs.md)
+* [OS lifecycle support policy](https://github.com/dotnet/core/blob/main/os-lifecycle-policy.md)
+* [Linux System Prerequisites](https://github.com/dotnet/core/blob/main/Documentation/linux-prereqs.md)
 
 ### Installation using a package manager
 
@@ -83,11 +83,11 @@ sudo zypper install libunwind libicu
 
 ## Ready to install
 
-Your system is now ready to install .NET Core. See the [Release Notes index](https://github.com/dotnet/core/tree/master/release-notes#net-core-release-notes) for the latest available updates.
+Your system is now ready to install .NET Core. See the [Release Notes index](https://github.com/dotnet/core/tree/main/release-notes#net-core-release-notes) for the latest available updates.
 
 ## Installation from a binary archive
 
-Installing from the packages detailed above is recommended or you can install from binary archive, if that better suits your needs. When using binary archives to install, the contents must be extracted to a user location such as `$HOME/dotnet`, a symbolic link created for `dotnet` and a few dependencies installed. Dependency requirements for each distro can be seen in the [Linux System Prerequisites](https://github.com/dotnet/core/blob/master/Documentation/linux-prereqs.md) document.
+Installing from the packages detailed above is recommended or you can install from binary archive, if that better suits your needs. When using binary archives to install, the contents must be extracted to a user location such as `$HOME/dotnet`, a symbolic link created for `dotnet` and a few dependencies installed. Dependency requirements for each distro can be seen in the [Linux System Prerequisites](https://github.com/dotnet/core/blob/main/Documentation/linux-prereqs.md) document.
 
 ```bash
 mkdir -p $HOME/dotnet && tar zxf dotnet.tar.gz -C $HOME/dotnet

Documentation/microsoft-team.md

@@ -10,55 +10,55 @@ You need to link your GitHub and @microsoft.com accounts. Click the link:
 
 You need to join teams in two organizations. Click the two links:
 
-* [dotnet org](https://repos.opensource.microsoft.com/dotnet/teams/microsoft/join/)
-* [Microsoft org](https://repos.opensource.microsoft.com/microsoft/teams/dotnet/join/)
+1. [Join the Microsoft org](https://repos.opensource.microsoft.com/orgs/microsoft/join)
+2. [Join the dotnet team](https://repos.opensource.microsoft.com/Microsoft/teams/dotnet/join/)
+3. [Join the dotnet org](https://repos.opensource.microsoft.com/orgs/dotnet/join)
+4. [Join the microsoft team](https://repos.opensource.microsoft.com/dotnet/teams/microsoft/join/)
 
-After you join the teams: 
+After you join the teams:
 
-* Users will be able to @mention you on [.NET Core Repos](https://github.com/dotnet/core/blob/master/Documentation/core-repos.md)
+* Users will be able to @mention you on [.NET Core Repos](https://github.com/dotnet/core/blob/main/Documentation/core-repos.md)
 * You will be able to access to private repos we maintain
 * You will get write access to a subset of repos
 
 ## Configure your GitHub account as a Microsoft employee (recommended)
 
 * Publicly associate yourself with dotnet and Microsoft orgs
-    * For Microsoft, go to https://github.com/orgs/Microsoft/people
-    * For dotnet, go to https://github.com/orgs/dotnet/people
-    * Search for your GitHub handle in the list
-    * Choose `Public` from the drop-down list of organization visibility
-    * Note: Everyone will now see an org badge on your GH profile in the Organizations section
+  * For Microsoft, go to <https://github.com/orgs/Microsoft/people>.
+  * For dotnet, go to <https://github.com/orgs/dotnet/people>.
+  * Search for your GitHub handle in the list.
+  * Choose `Public` from the drop-down list of organization visibility.
+  * Note: Everyone will now see an org badge on your GH profile in the Organizations section.
 * Update your profile
-    * Go to https://github.com/settings/profile
-    * Match your **Name** on GitHub with full name in address book (so other employees can find you and contact you internally when needed)
-    * Set `@Microsoft` as your **Company**
-    * Upload your **picture**, ideally showing your face
-        * Hint: You can grab your GAL picture from https://microsoft-my.sharepoint.com
+  * Go to <https://github.com/settings/profile>.
+  * Match your **Name** on GitHub with full name in address book (so other employees can find you and contact you internally when needed).
+  * Set `@Microsoft` as your **Company**,
+  * Upload your **picture**, ideally showing your face.
+    * Hint: You can grab your GAL picture from <https://microsoft-my.sharepoint.com>.
 
 ## Install Microsoft open source tools (recommended)
 
-The tools make it easier to use open source and participate in open source projects:
+The following tool makes it easier to use open source and participate in open-source projects:
 
 * [Browser Extension](https://docs.opensource.microsoft.com/tools/browser.html) -- Identifies Microsoft employees on GitHub.
-* [VS Code Extension](https://docs.opensource.microsoft.com/tools/vscode.html) --  Provides information about known vulnerabilities.
-
-The browser extension is recommended. The VS code extension is optional.
 
 ## Get write permissions to repos (optional)
 
 Join teams to gain write access to repos:
- * Request team membership via https://repos.opensource.microsoft.com/teams
- * Ask someone if you don't know which team(s) to join.
- * Select `Request to join this team` on the right side - it will send email request to maintainers of the team
+
+* Request team membership via <https://repos.opensource.microsoft.com/teams>.
+* Ask someone if you don't know which team(s) to join.
+* Select `Request to join this team` on the right side - it will send email request to maintainers of the team.
 
 ## Security best practices
 
 Enabling 2FA doesn't necessarily mean your account is secure. SMS (phone texts) is [not secure](https://en.wikipedia.org/wiki/SIM_swap_scam) as a 2FA method and should be avoided if possible. You can see [failed login attempts](https://github.com/settings/security-log?q=action%3Auser.failed_login) on your account to get some sense of the risk you have.
 
-The following best practices are required for org owners, and recommended for repo admins. 
+The following best practices are required for org owners, and recommended for repo admins.
 
 * Do register a [security key(s)](https://www.yubico.com/works-with-yubikey/catalog/github/) as a two factor method.
 * Do register an authenticator app -- registering a one-time-password with an app like 1Password is recommended (not tied to your phone).
-* Do store recorvery codes in a safe place, like [OneDrive Vault](https://www.microsoft.com/en-us/microsoft-365/onedrive/personal-vault), 2FA-protected OneNote or in a password vault like 1Password.
+* Do store recovery codes in a safe place, like [OneDrive Vault](https://www.microsoft.com/microsoft-365/onedrive/personal-vault), 2FA-protected OneNote or in a password vault like 1Password.
 * Do register your GitHub account with your 2FA-protected Facebook account for GitHub account recovery. This is the absolute last recovery option and is considered secure (even if your Facebook account is breached).
 * Do not use SMS for 2FA or as a recovery fallback.
 
@@ -69,7 +69,7 @@ A few more notes on hardware keys:
 * You should have at least one hardware key that does not travel with you, but is stored in a secure location (like at home) as a last resort in case you lose access to other factors.
 * If you have a FIDO2 key, it can be used with [mysignins](https://mysignins.microsoft.com/).
 * If you have USB-C and USB-A only devices, and want to use hardware keys for them, then you need [separate keys](https://www.yubico.com/works-with-yubikey/catalog/github/). This explains why the example below has three keys registered (one securely stored at home, and two keys for daily use for USB-C and USB-A only devices).
-* You can use Windows Hello to signin as a hardware key. This is fine to use, but doesn't replace the need for hardware key that you store in a secure location.Your Windows Hello key is not tied to you, but the machine. It won't survive hardware failures or re-installing Windows.
+* You can use Windows Hello to sign in as a hardware key. This is fine to use, but it doesn't replace the need for hardware key that you store in a secure location. Your Windows Hello key is not tied to you, but the machine. It won't survive hardware failures or re-installing Windows.
 
 A correctly configured account should look similar to the following:
 
@@ -89,5 +89,5 @@ Service accounts should also be linked. For more details, see [Service accounts
 
 ## Guidelines
 
-* [Contributing to .NET Core](https://github.com/dotnet/runtime/blob/master/CONTRIBUTING.md)
-* [What you can expect from Maintainers](https://github.com/dotnet/core/blob/master/Documentation/contributing/maintainers.md)
+* [Contributing to .NET Core](https://github.com/dotnet/runtime/blob/main/CONTRIBUTING.md)
+* [What you can expect from Maintainers](https://github.com/dotnet/core/blob/main/Documentation/contributing/maintainers.md)

Documentation/prereqs.md

@@ -1,7 +1,7 @@
 .NET Core native prerequisites
 ==============================
 
-* [Windows Prerequisites](https://docs.microsoft.com/dotnet/core/install/dependencies?pivots=os-windows)
-* [macOS Prerequisites](https://docs.microsoft.com/dotnet/core/install/dependencies?pivots=os-macos)
-* [Linux Prerequisites](https://docs.microsoft.com/dotnet/core/install/dependencies?pivots=os-linux)
-* [.NET Core Supported OS Lifecycle Policy](https://github.com/dotnet/core/blob/master/os-lifecycle-policy.md)
+* [Windows Prerequisites](https://docs.microsoft.com/dotnet/core/install/windows)
+* [macOS Prerequisites](https://docs.microsoft.com/dotnet/core/install/macos)
+* [Linux Prerequisites](https://docs.microsoft.com/dotnet/core/install/linux)
+* [.NET Core Supported OS Lifecycle Policy](https://github.com/dotnet/core/blob/main/os-lifecycle-policy.md)

ISSUE_TEMPLATE

@@ -1,11 +0,0 @@
-# Issue Title
-
-Be as descriptive as you can with your title.
-
-# General
-
-Provide details on the problem you are experiencing including the .NET Core version, operating system version and anything else that is relevant.
-
-Please provide a code sample for your issue if it is relevant, either inline, link to a gist (or similar) or add it as a zipped attachment.
-
-For some issues, you will get a quicker and better response if you file it at a more specific [.NET repo](https://github.com/dotnet/core/blob/master/Documentation/core-repos.md). For example, if the problem is with ASP.NET Core, you are encouraged to use the [aspnet/home repo](https://github.com/aspnet/home/issues).

README.md

@@ -2,23 +2,20 @@
 
 The dotnet/core repository is a good starting point for .NET Core.
 
-The latest major release is [.NET Core 3.1](release-notes/3.1). The latest patch updates are listed in [.NET Core release notes](release-notes/README.md).
+The latest major release is [.NET 6.0](release-notes/6.0/README.md). The latest patch updates are listed in [.NET Core release notes](release-notes/README.md).
 
-## Download the latest .NET Core SDK
+## .NET Core Releases
 
-* [.NET Core 3.1 SDK](release-notes/3.1/README.md)
-
-## .NET Core Releases and Daily Builds
-
-* [.NET Core released builds](release-notes/README.md)
+* [Download the latest .NET Core SDK](https://dotnet.microsoft.com/download/dotnet/5.0)
+* [.NET Core releases](releases.md)
 * [.NET Core daily builds](daily-builds.md)
 
 ## Learn about .NET Core
 
 * [Learn about .NET Core](https://docs.microsoft.com/dotnet/core)
-* [.NET Core Roadmap](https://github.com/dotnet/core/blob/master/roadmap.md)
+* [.NET Core Roadmap](https://github.com/dotnet/core/blob/main/roadmap.md)
 * [Learn about the .NET platform](https://docs.microsoft.com/dotnet/standard/)
-* [.NET Core release notes](https://github.com/dotnet/core/blob/master/release-notes/README.md)
+* [.NET Core release notes](https://github.com/dotnet/core/blob/main/release-notes/README.md)
 * [.NET Core Announcements](https://github.com/dotnet/announcements)
 * [.NET Core blog](https://blogs.msdn.microsoft.com/dotnet/tag/net-core/)
 
@@ -31,7 +28,7 @@ The latest major release is [.NET Core 3.1](release-notes/3.1). The latest patch
 
 ## How to Engage, Contribute and Provide Feedback
 
-The .NET Core team encourages [contributions](https://github.com/dotnet/runtime/blob/master/CONTRIBUTING.md), both issues and PRs. The first step is finding the [.NET Core repository](Documentation/core-repos.md) that you want to contribute to.
+The .NET Core team encourages [contributions](https://github.com/dotnet/runtime/blob/main/CONTRIBUTING.md), both issues and PRs. The first step is finding the [.NET Core repository](Documentation/core-repos.md) that you want to contribute to.
 
 Check the [product roadmap](https://aka.ms/dotnet-product-roadmap) to see what the team is focusing on.
 
@@ -42,13 +39,13 @@ Instances of abusive, harassing, or otherwise unacceptable behavior may be repor
 
 ## .NET Foundation
 
-The .NET Core platform is part of the [.NET Foundation](http://www.dotnetfoundation.org).
+The .NET Core platform is part of the [.NET Foundation](https://www.dotnetfoundation.org).
 
 ## Licenses
 
 .NET Core repos typically use either the [MIT](LICENSE.TXT) or
-[Apache 2](http://www.apache.org/licenses/LICENSE-2.0) licenses for code.
+[Apache 2](https://www.apache.org/licenses/LICENSE-2.0) licenses for code.
 Some projects license documentation and other forms of content under
-[Creative Commons Attribution 4.0](http://creativecommons.org/licenses/by/4.0/).
+[Creative Commons Attribution 4.0](https://creativecommons.org/licenses/by/4.0/).
 
 See specific [repos](Documentation/core-repos.md) to understand the license used.

SECURITY.md

@@ -6,9 +6,9 @@ The .NET Core and ASP.NET Core support policy, including supported versions can
 
 ## Reporting a Vulnerability
 
-Security issues and bugs should be reported privately to the Microsoft Security Response Center (MSRC), either by emailing secure@microsoft.com or via the portal at https://msrc.microsoft.com. 
-You should receive a response within 24 hours. If for some reason you do not, please follow up via email to ensure we received your 
-original message. Further information, including the MSRC PGP key, can be found in the [MSRC Report an Issue FAQ](https://www.microsoft.com/en-us/msrc/faqs-report-an-issue).
+Security issues and bugs should be reported privately to the Microsoft Security Response Center (MSRC), either by emailing secure@microsoft.com or via the portal at https://msrc.microsoft.com.
+You should receive a response within 24 hours. If for some reason you do not, please follow up via email to ensure we received your
+original message. Further information, including the MSRC PGP key, can be found in the [MSRC Report an Issue FAQ](https://www.microsoft.com/msrc/faqs-report-an-issue).
 
 Reports via MSRC may qualify for the .NET Core Bug Bounty. Details of the .NET Core Bug Bounty including terms and conditions are at [https://aka.ms/corebounty](https://aka.ms/corebounty).
 

daily-builds.md

@@ -1,23 +1,25 @@
-# .NET Core Daily Builds -- Servicing and future releases
+# .NET Daily Builds -- Servicing and future releases
 
-The .NET Core team builds many branches of the product daily. You can install these builds to try out functionality prior to release.
+The .NET team builds many branches of the product daily. You can install these builds to try out functionality prior to release.
+
+Daily builds, for both future and servicing branches, are available as Docker container images from the [Microsoft Container Registry](https://hub.docker.com/_/microsoft-dotnet-nightly/).
 
 ## Future Releases
 
-Preview branches are for new major/minor versions of .NET Core that have not yet been released and are not yet supported.
+Preview branches are for new versions of .NET that have not yet been released and are not yet supported.
 
-|Component|*.NET 5.0*
+|Component|*.NET 6.0*
 |:------:|:------:|
-|SDK|[.NET Core SDK 5.0.xxx  (Master)](https://github.com/dotnet/core-sdk/blob/master/README.md#installers-and-binaries)
-|ASP.NET Core|[ASP.NET Core Shared Framework 5.0 (Master)](https://github.com/aspnet/AspNetCore/blob/master/docs/DailyBuilds.md)
-|Runtime|[.NET Core Runtime 5.0 (Master)](https://github.com/dotnet/core-setup/blob/master/README.md#daily-builds)
+|SDK|[.NET SDK 6.0.xxx](https://github.com/dotnet/installer/blob/main/README.md#installers-and-binaries)
+|ASP.NET Core|[ASP.NET Core 6.0](https://github.com/dotnet/aspnetcore/blob/main/docs/DailyBuilds.md)
+|Runtime|[.NET Runtime 6.0](https://github.com/dotnet/installer/blob/master/README.md#daily-builds)
 
 ## Servicing Releases
 
-Servicing branches are for new patch versions of .NET Core that have not yet been released and are not yet supported. These patch versions are for previously released major/minor versions.
+Servicing branches are for new patch versions of .NET that have not yet been released and are not yet supported.
 
-|Component|*.NET Core 3.1*|*.NET Core 2.1*
+|Component|*.NET 5.0*|*.NET Core 3.1*|
 |:------:|:------:|:------:|
-|SDK|[.NET Core SDK 3.1](https://github.com/dotnet/core-sdk/blob/master/README.md#installers-and-binaries)|[.NET Core SDK 2.1.xxx](https://github.com/dotnet/cli/blob/release/2.1/README.md#installers-and-binaries)|
-|ASP.NET Core|[ASP.NET Core Shared Framework 3.1](https://github.com/aspnet/AspNetCore/blob/master/docs/DailyBuilds.md)|[ASP.NET Core Shared Framework 2.1](https://github.com/aspnet/AspNetCore/blob/master/docs/DailyBuilds.md)|
-|Runtime|[.NET Core Runtime 3.1](https://github.com/dotnet/core-setup/blob/master/README.md#daily-builds)|[.NET Core Runtime 2.1](https://github.com/dotnet/core-setup/blob/master/README.md#daily-builds)|
+|SDK|[.NET SDK 5.0.xxx](https://github.com/dotnet/installer/blob/main/README.md#installers-and-binaries)|[.NET Core SDK 3.1.xxx](https://github.com/dotnet/core-sdk/blob/main/README.md#installers-and-binaries)
+|ASP.NET Core|[ASP.NET Core 5.0](https://github.com/dotnet/aspnetcore/blob/main/docs/DailyBuilds.md)|[ASP.NET Core 3.1](https://github.com/dotnet/aspnetcore/blob/main/docs/DailyBuilds.md)|
+|Runtime|[.NET Core Runtime 5.0](https://github.com/dotnet/installer/blob/master/README.md#daily-builds)|[.NET Core Runtime 3.1](https://github.com/dotnet/core-setup/blob/master/README.md#daily-builds)

license-information-windows.md

@@ -1,32 +1,31 @@
-# License information for .NET
+# License information for .NET on Windows
 
-The Windows distribution of .NET 5.0 contains files that are provided under 
-multiple licenses. 
-This information is provided to help you to understand if the files, and their
-associated licenses terms, apply to your use.  
-By using any or all of these files you agree to their associated license terms.
+The Windows distribution of .NET 5.0 and later releases contains files that are provided under 
+multiple licenses.
+This information is provided to help you understand the license terms that 
+apply to your use. By using any or all of these files you agree to their associated license terms.
 
 The following binaries are licensed with the 
-[.NET Library License](https://dotnet.microsoft.com/en/dotnet_library_license.htm)
+[Windows SDK License](https://docs.microsoft.com/legal/windows-sdk/license):
 
-* WPF: PresentationNative_cor3.dll
-* WPF: wpfgfx_cor3.dll
+* api-ms-\*.\* (used by .NET runtime)
+* ucrtbase.dll (used by .NET runtime)
+* D3DCompiler_47_cor3.dll (used by WPF)
+
+The following binaries are licensed with the 
+[.NET Library License](https://dotnet.microsoft.com/dotnet_library_license.htm)
+
+* PresentationNative_cor3.dll (used by WPF)
+* wpfgfx_cor3.dll (used by WPF)
 
 The following binaries are licensed with the 
 [Visual Studio 2019 License](https://visualstudio.microsoft.com/license-terms/mlt031619/) 
 (not as a "trial"):
 
-* WPF: vcruntime140_cor3.dll 
-* SDK Tools: Microsoft.DiaSymReader.Native.{x86|amd64|arm|arm64}.dll 
-
-The following binaries are licensed with the 
-[Windows SDK License](https://docs.microsoft.com/legal/windows-sdk/license):
-
-* .NET Core: api-ms-*.* 
-* .NET Core: ucrtbase.dll 
-* WPF: D3DCompiler_47_cor3.dll
+* vcruntime140_cor3.dll (used by WPF)
+* Microsoft.DiaSymReader.Native.{x86|amd64|arm|arm64}.dll (used by .NET SDK)
 
 All other binaries and files are licensed with the 
-[MIT license](https://github.com/dotnet/core/blob/master/LICENSE.TXT)
+[MIT license](https://github.com/dotnet/core/blob/main/LICENSE.TXT)
 
 This document is provided for informative purposes only, and is not itself a license.

microsoft-support.md

@@ -1,61 +1,21 @@
-# Microsoft .NET Core support lifecycle
+# Microsoft support for .NET
 
-Every Microsoft product has a lifecycle, including .NET Core. The lifecycle begins when a product is released and ends when it's no longer supported. Knowing key dates in this lifecycle helps you make informed decisions about when to upgrade or make other changes to your software. This product is governed by the [Microsoft Modern Lifecycle](https://support.microsoft.com/help/30881/modern-lifecycle-policy).
+[Microsoft supports .NET](https://dotnet.microsoft.com/platform/support/policy) on multiple operating systems, per the [Microsoft Modern Lifecycle](https://support.microsoft.com/help/30881/modern-lifecycle-policy).
 
-This document describes the support lifecycle for: .NET Core, ASP.NET Core and EF Core.
+Support is provided for: .NET SDK, .NET runtime, ASP.NET Core, and EF Core.
 
-The [.NET Core OS Lifecycle Policy](https://github.com/dotnet/core/blob/master/os-lifecycle-policy.md) describes support for various operating systems.
+Support has two key benefits:
 
-## .NET Core Releases
+* Patches are provided (for free) as required for functional or security issues, typically monthly.
+* You can [contact Microsoft support to request help](https://support.serviceshub.microsoft.com/supportforbusiness/onboarding) (potentially at a cost).
 
-This table describes support type, supported patch version and end of support date for .NET Core releases.
+You can also request community support on GitHub (for free), but there is no guarantee on a quick reply.
 
-|  Version  |  Release Date | Support Level | Supported Patch Version | End of Support |
-| -- | -- | -- | -- | -- |
-| [.NET Core 3.1](https://devblogs.microsoft.com/dotnet/announcing-net-core-3-1/) | December 3, 2019 | LTS | [3.1.5](https://dotnet.microsoft.com/download/dotnet-core/3.1) | December 3, 2022 |
-| [.NET Core 2.1](https://blogs.msdn.microsoft.com/dotnet/2018/05/30/announcing-net-core-2-1) | May 30, 2018 | LTS | [2.1.19](https://dotnet.microsoft.com/download/dotnet-core/2.1) | August 21, 2021 |
+Support is conditional on using the latest .NET patch update and a supported operating system, as defined by:
 
-For previous versions, [see here](https://dotnet.microsoft.com/platform/support/policy/dotnet-core).
+* [Microsoft support policy](https://dotnet.microsoft.com/platform/support/policy)
+* [.NET releases](releases.md)
+* [.NET release policies](release-policies.md)
+* [.NET supported operating system lifecycle](os-lifecycle-policy.md).
 
-## Release Types
-
-Microsoft produces **Long Term Support (LTS)** and **Current** releases, which are defined as:
-
-* **LTS** releases are designed for long-term support. They included features and components that have been stabilized, requiring few updates over a longer support release lifetime. These releases are a good choice for hosting applications that you do not intend to update.
-* **Current** releases include new features that may undergo future change based on feedback. These releases are a good choice for applications in active development, giving you access to the latest features and improvements. You need to upgrade to later .NET Core releases more often to stay in support.
-
-Both types of releases receive critical fixes throughout their lifecycle, for security, reliability, or to add support for new operating system versions. You must stay up-to-date with the latest patches to qualify for support.
-
-## Release Support Policies
-
-.NET Core releases are supported according to the following policies.
-
-### Long Term Support (LTS) releases
-
-LTS releases are supported for three years after the initial release.
-
-Note: .NET Core 1.x was released under an earlier definition of LTS. See: [.NET Core 1.x "shorter" LTS definition](https://github.com/dotnet/core/blob/e2f22a7106860c0e5dc98bb36dc648a779944ad5/microsoft-support.md#long-term-support-lts-releases).
-
-### Current releases
-
-Current releases are supported for three months after a subsequent Current or LTS release.
-
-### Maintenance releases
-
-Maintenance releases are in the last stage of the lifecycle . During Maintenance, a release will receive security updates. The length of Maintenance time is 3 months for Current and 1 year for LTS.
-
-### End of support
-
-End of support refers to the date when Microsoft no longer provides fixes, updates, or online technical assistance. As this date nears, make sure you have the latest available update\* installed. Without Microsoft support, you will no longer receive security updates that can help protect your machine from harmful viruses, spyware, and other malicious software that can steal your personal information.
-
-\* Updates are cumulative, with each update built upon all of the updates that preceded it. A device needs to install the latest update to remain supported. Updates may include new features, fixes (security and/or non-security), or a combination of both. Not all features in an update will work on all devices. Update availability may vary, for example by country, region, network connectivity, or hardware capabilities (including, for example, free disk space).
-
-### Out of support .NET Core releases
-
-|  Version  |  End of Support |
-| -- | -- |
-| [.NET Core 3.0](https://devblogs.microsoft.com/dotnet/announcing-net-core-3-0/) | [March 3, 2020](https://devblogs.microsoft.com/dotnet/net-core-3-0-end-of-life/) |
-| [.NET Core 2.2](https://devblogs.microsoft.com/dotnet/announcing-net-core-2-2/) | [December 23, 2019](https://devblogs.microsoft.com/dotnet/net-core-2-2-will-reach-end-of-life-on-december-23-2019/)
-| [.NET Core 2.0](https://blogs.msdn.microsoft.com/dotnet/2017/08/14/announcing-net-core-2-0/) | [October 1, 2018](https://devblogs.microsoft.com/dotnet/net-core-2-0-will-reach-end-of-life-on-september-1-2018/)
-| [.NET Core 1.1](https://blogs.msdn.microsoft.com/dotnet/2016/11/16/announcing-net-core-1-1/) | [June 27, 2019](https://devblogs.microsoft.com/dotnet/net-core-1-0-and-1-1-will-reach-end-of-life-on-june-27-2019/)
-| [.NET Core 1.0](https://blogs.msdn.microsoft.com/dotnet/2016/06/27/announcing-net-core-1-0/) | [June 27, 2019](https://devblogs.microsoft.com/dotnet/net-core-1-0-and-1-1-will-reach-end-of-life-on-june-27-2019/)
+Knowing key dates for a product lifecycle helps you make informed decisions about when to upgrade or make other changes to your software and computing environment.

os-lifecycle-policy.md

@@ -1,31 +1,37 @@
-# .NET Core Supported OS Lifecycle Policy
+# .NET Supported OS Policy
 
-.NET Core is [supported by Microsoft](microsoft-support.md) on a range of operating systems. 
+.NET is [supported by Microsoft](microsoft-support.md) on multiple operating systems.
 
-Each supported operating system has a lifecycle defined by its sponsor organization (for example, Microsoft, Red Hat, or Apple). The .NET Core team applies each of those lifecycle schedules to inform adding and removing support for operating system versions.
+A more restrictive policy is used for [.NET container images](https://github.com/dotnet/dotnet-docker/blob/main/documentation/supported-platforms.md).
 
-The following support documents list currently supported operating system versions for supported .NET Core versions:
+## Supported .NET versions
 
+The following documents describe supported operating systems:
+
+* [.NET 6 supported OS versions](release-notes/6.0/supported-os.md)
 * [.NET 5 supported OS versions](release-notes/5.0/5.0-supported-os.md)
 * [.NET Core 3.1 supported OS versions](release-notes/3.1/3.1-supported-os.md)
-* [.NET Core 2.1 supported OS versions](release-notes/2.1/2.1-supported-os.md)
 
-## Out-of-Support .NET Core versions
+## Out-of-support .NET versions
 
-When an operating system version goes out of support, we stop testing that version and providing support for that version. This means that users will need to move forward to a supported operating system version to get support. Previously released packages will remain available for users needing access.
-
-The following support documents list historical operating system support for out-of-support .NET Core versions:
+The following documents describe (historical) supported operating systems:
 
 * [.NET Core 3.0 supported OS versions](release-notes/3.0/3.0-supported-os.md)
 * [.NET Core 2.2 supported OS versions](release-notes/2.2/2.2-supported-os.md)
+* [.NET Core 2.1 supported OS versions](release-notes/2.1/2.1-supported-os.md)
 * [.NET Core 2.0 supported OS versions](release-notes/2.0/2.0-supported-os.md)
 * [.NET Core 1.x supported OS versions](release-notes/1.0/1.0-supported-os.md)
 
 ## Change Process
 
-Operating system versions are added and go out of support on a regular basis. We record these changes in two places:
+Operating system versions are added and go out of support on a regular basis. We record these changes in three places:
 
 * The support documents listed above
 * [Monthly Update Announcements](https://github.com/dotnet/announcements/labels/Monthly-Update)
+* [OS support tracking issues](https://github.com/dotnet/core/labels/os-support)
 
-When a new operating system version is made available, we will typically support it on a subset of supported .NET Core versions, potentially only with the latest .NET Core version.
+## Lifecycle Policy
+
+Each supported operating system has a lifecycle defined by its sponsor organization (for example, Microsoft, Red Hat, Debian, or Apple). The .NET team applies each of those lifecycle schedules to inform adding and removing support for operating system versions. Support is typically removed when an operating system goes out of mainline support, at which point we stop testing and supporting it, and support documents are updated to match.
+
+Operating system policies and schedules do not always align well with the annual .NET schedule. We have sometimes supported both [Windows](https://docs.microsoft.com/troubleshoot/windows-client/windows-7-eos-faq/windows-7-extended-security-updates-faq) and Linux versions after mainline (and possibly free) support has lapsed as a service to users to provide more time to transition to newer releases. The previous support documents are kept up to date and provide accurate information you can use to make your own support decisions.

product-roadmap/current.md

@@ -7,9 +7,9 @@ The .NET product roadmap communicates project priorities for evolving and extend
 These are some of the high level themes for the .NET 5.0 release. A more comprehensive list of the work we’re doing organized by technology can be found further below in this document.
 - Developers can build great cloud infrastructure components with .NET.
 - Developers can build great mobile apps for new devices with .NET 5 – we will support not only the latest in iOS and Android, but unify the platform and deliver first-class support for delivering cross-platform applications.
-- .NET 5.0 has excellent fundamentals - continue to deliver on reliability, performance, diagnosability, compliance, security, acquisition and deployment.  
+- .NET 5.0 has excellent fundamentals - continue to deliver on reliability, performance, diagnosability, compliance, security, acquisition and deployment.
 
-These are some key moments in our .NET 5.0 roadmap. 
+These are some key moments in our .NET 5.0 roadmap.
 
 | Date      | Moment/Rally Point | Key Message     |
 | :-------- | :----------------- | :-------------- |
@@ -25,16 +25,16 @@ Items in each section include the following icons:
 
 ## ASP.NET
 
-- ![In Progress](media/status-in-progress.png "In Progress icon") [Blazor](https://github.com/dotnet/aspnetcore/issues/21514)
+- ![Completed](media/status-completed.png "Completed icon") [Blazor](https://github.com/dotnet/aspnetcore/issues/21514)
   - ![Completed](media/status-completed.png "Completed icon") [Move Blazor to .NET 5](https://github.com/dotnet/aspnetcore/issues/20519)
   - ![Completed](media/status-completed.png "Completed icon") [CSS Isolation](https://github.com/dotnet/aspnetcore/issues/10170)
   - ![Completed](media/status-completed.png "Completed icon") [Support IAsyncDisposable](https://github.com/dotnet/aspnetcore/issues/9960)
   - ![Completed](media/status-completed.png "Completed icon") [Lazy loading of application areas](https://github.com/dotnet/aspnetcore/issues/5465)
   - ![Completed](media/status-completed.png "Completed icon") [Add focus support to BrowserRenderer](https://github.com/dotnet/aspnetcore/issues/17472)
   - ![Completed](media/status-completed.png "Completed icon") [Protected Browser Storage](https://github.com/dotnet/aspnetcore/issues/18755)
-  - ![In Progress](media/status-in-progress.png "In Progress icon") [Build performance improvements for Blazor](https://github.com/dotnet/aspnetcore/issues/22566)
+  - ![Completed](media/status-completed.png "Completed icon") [Build performance improvements for Blazor](https://github.com/dotnet/aspnetcore/issues/22566)
   - ![Completed](media/status-completed.png "Completed icon") [Blazor performance optimizations](https://github.com/dotnet/aspnetcore/issues/22432)
-  - ![In Progress](media/status-in-progress.png "In Progress icon") [How to upload files in Blazor App](https://github.com/dotnet/aspnetcore/issues/12205)
+  - ![Completed](media/status-completed.png "Completed icon") [How to upload files in Blazor App](https://github.com/dotnet/aspnetcore/issues/12205)
 
 ## gRPC
 
@@ -45,8 +45,8 @@ Items in each section include the following icons:
 - ![Completed](media/status-completed.png "Completed icon") Configurable HTTP/2 PING frames
 - ![Completed](media/status-completed.png "Completed icon") Instrument gRPC for use with OpenTelemetry
 - ![Completed](media/status-completed.png "Completed icon") Add support for HttpSysServer
-- ![In Progress](media/status-in-progress.png "In Progress icon") Add support for IIS
-- ![In Progress](media/status-in-progress.png "In Progress icon") Introduce additional transports (e.g., Unix-domain sockets, Windows Named Pipes)
+- ![Completed](media/status-completed.png "Completed icon") Add support for IIS
+- ![Completed](media/status-completed.png "Completed icon") Introduce additional transports (e.g., Unix-domain sockets, Windows Named Pipes)
 
 ## Tye
 
@@ -59,7 +59,7 @@ Items in each section include the following icons:
 - ![Completed](media/status-completed.png "Completed icon") Using the same conventions as development to keep it consistent
 - ![Completed](media/status-completed.png "Completed icon") Support Azure Functions in development
 - ![In Progress](media/status-in-progress.png "In Progress icon") VS Code tooling
- 
+
 ## EF
 
 [EF Core 5.0 plan](https://docs.microsoft.com/ef/core/what-is-new/ef-core-5.0/plan)
@@ -77,16 +77,16 @@ Items in each section include the following icons:
 - ![Completed](media/status-completed.png "Completed icon") Performance improvements
 
 ## ML.NET
- 
+
 - ![Completed](media/status-completed.png "Completed icon") Local GPU training for Image Classification in Model Builder
 - ![Completed](media/status-completed.png "Completed icon") Add Ranking scenario to local ML.NET AutoML API
 - ![Completed](media/status-completed.png "Completed icon") Add new algorithm and root cause detection for anomaly detection
 - ![Completed](media/status-completed.png "Completed icon") Add time series seasonality and de-seasonality
 - ![In Progress](media/status-in-progress.png "In Progress icon") GA Model Builder in Visual Studio
-- ![In Progress](media/status-in-progress.png "In Progress icon") Add Azure Object Detection training to Model Builder
-- ![In Progress](media/status-in-progress.png "In Progress icon") Add local Image Classification training scenario to ML.NET CLI
-- ![In Progress](media/status-in-progress.png "In Progress icon") Add advanced options for data loading in Model Builder
-- ![In Progress](media/status-in-progress.png "In Progress icon") Improve Azure training from Model Builder (better errors, multi-GPU multi-machine, reduced overhead)
+- ![Completed](media/status-completed.png "Completed icon") Add Azure Object Detection training to Model Builder
+- ![Completed](media/status-completed.png "Completed icon") Add local Image Classification training scenario to ML.NET CLI
+- ![Completed](media/status-completed.png "Completed icon") Add advanced options for data loading in Model Builder
+- ![Completed](media/status-completed.png "Completed icon") Improve Azure training from Model Builder (better errors, multi-GPU multi-machine, reduced overhead)
 - ![In Planning](media/status-in-planning.png "In Planning icon") Add local Ranking scenario to tooling
 - ![In Progress](media/status-in-progress.png "In Progress icon") Add support for re-opening Model Builder and adding multiple models to a project
 - ![In Planning](media/status-in-planning.png "In Planning icon") Add integration with MLOps
@@ -95,8 +95,8 @@ Items in each section include the following icons:
 ## Spark
 
 - ![Completed](media/status-completed.png "Completed icon") Improve debugging experience
-- ![In Progress](media/status-in-progress.png "In Progress icon") Spark 2.4 API compatibility
-- ![In Progress](media/status-in-progress.png "In Progress icon") Spark 3.0 API compatibility
+- ![Completed](media/status-completed.png "Completed icon") Spark 2.4 API compatibility
+- ![Completed](media/status-completed.png "Completed icon") Spark 3.0 API compatibility
 - ![In Planning](media/status-in-planning.png "In Planning icon") .NET Core project templates for .NET for Spark
 - ![In Planning](media/status-in-planning.png "In Planning icon") VS deploy for .NET for Spark jobs
 
@@ -113,8 +113,10 @@ Items in each section include the following icons:
 
 [Details](https://github.com/dotnet/interactive/issues/392)
 
-- ![Completed](media/status-completed.png "Completed icon") Multi Language support for Jupyter Notebooks (C#, F#, PowerShell)
-- ![In Progress](media/status-in-progress.png "In Progress icon") .NET Notebooks support in VS code Support
+- ![Completed](media/status-completed.png "Completed icon") Multi Language support for Jupyter Notebooks (C#, F#, PowerShell)[Post](https://devblogs.microsoft.com/dotnet/net-interactive-is-here-net-notebooks-preview-2/)
+- ![Completed](media/status-completed.png "Completed icon") [.NET Notebooks support - Available in VS Code Insiders.](https://marketplace.visualstudio.com/items?itemName=ms-dotnettools.dotnet-interactive-vscode)
+- ![In Progress](media/status-in-progress.png "In Progress icon") VS Code
+- ![In Progress](media/status-in-progress.png "In Progress icon") Adding SQL to .NET Interactive
 - ![In Progress](media/status-in-progress.png "In Progress icon") Improve Productivity
 - ![In Progress](media/status-in-progress.png "In Progress icon") .NET Interactive for makers
 - ![Completed](media/status-completed.png "Completed icon") [Documentation](https://github.com/dotnet/interactive/tree/main/docs) - done but always improving
@@ -127,11 +129,11 @@ Please see the following links to view work items and themes across:
 
 ## Languages
 
-[Language Feature Status](https://github.com/dotnet/roslyn/blob/master/docs/Language%20Feature%20Status.md)
+[Language Feature Status](https://github.com/dotnet/roslyn/blob/main/docs/Language%20Feature%20Status.md)
 
 ### C# 9
 
-- ![Completed](media/status-completed.png "Completed icon") [Target-typed new](https://github.com/dotnet/csharplang/issues/100)  
+- ![Completed](media/status-completed.png "Completed icon") [Target-typed new](https://github.com/dotnet/csharplang/issues/100)
 - ![In Progress](media/status-in-progress.png "In Progress icon") [Relax ordering of `ref` and `partial` modifiers](https://github.com/dotnet/csharplang/issues/946)
 - ![In Progress](media/status-in-progress.png "In Progress icon") [Parameter null-checking](https://github.com/dotnet/csharplang/issues/2145)
 - ![Completed](media/status-completed.png "Completed icon") [Skip locals init](https://github.com/dotnet/csharplang/issues/1738)
@@ -145,9 +147,9 @@ Please see the following links to view work items and themes across:
 - ![Completed](media/status-completed.png "Completed icon") [Target-typed conditional](https://github.com/dotnet/csharplang/issues/2460)
 - ![In Progress](media/status-in-progress.png "In Progress icon") [Covariant](https://github.com/dotnet/csharplang/issues/49) [Returns](https://github.com/dotnet/csharplang/issues/2844)
 - ![Completed](media/status-completed.png "Completed icon") [Extension GetEnumerator](https://github.com/dotnet/csharplang/issues/3194)
-- ![Completed](media/status-completed.png "Completed icon") [Module initializers](https://github.com/dotnet/csharplang/blob/master/proposals/csharp-9.0/module-initializers.md)
-- ![Completed](media/status-completed.png "Completed icon") [Extending Partial](https://github.com/dotnet/csharplang/blob/master/proposals/csharp-9.0/extending-partial-methods.md)
-- ![Completed](media/status-completed.png "Completed icon") [Top-level statements](https://github.com/dotnet/csharplang/blob/master/proposals/csharp-9.0/top-level-statements.md)
+- ![Completed](media/status-completed.png "Completed icon") [Module initializers](https://github.com/dotnet/csharplang/blob/main/proposals/csharp-9.0/module-initializers.md)
+- ![Completed](media/status-completed.png "Completed icon") [Extending Partial](https://github.com/dotnet/csharplang/blob/main/proposals/csharp-9.0/extending-partial-methods.md)
+- ![Completed](media/status-completed.png "Completed icon") [Top-level statements](https://github.com/dotnet/csharplang/blob/main/proposals/csharp-9.0/top-level-statements.md)
 
 ### C# Next
 
@@ -183,7 +185,7 @@ Please see the following links to view work items and themes across:
 ## CLI/SDK and MSBuild
 
 
-- ![Completed](media/status-completed.png "Completed icon") [Changes to Target Framework Moniker - TFM](https://github.com/dotnet/designs/blob/master/accepted/2020/net5/net5.md)
+- ![Completed](media/status-completed.png "Completed icon") [Changes to Target Framework Moniker - TFM](https://github.com/dotnet/designs/blob/main/accepted/2020/net5/net5.md)
 - ![In Planning](media/status-in-planning.png "In Planning icon") Xamarin runs on .NET and via the CLI
 - ![In Progress](media/status-in-progress.png "In Progress icon") [Optional Workload infrastructure](https://github.com/dotnet/designs/blob/107b50feec105b7c2b67b37acb322054e2255df5/accepted/2020/workloads/workloads.md)
 - ![In Planning](media/status-in-planning.png "In Planning icon") Acquisition improvements
@@ -193,13 +195,15 @@ Please see the following links to view work items and themes across:
 - ![Completed](media/status-completed.png "Completed icon") [Solution filter support in MSBuild](https://github.com/dotnet/msbuild/issues/4097)
 - ![Completed](media/status-completed.png "Completed icon") [Low priority builds for MSBuild](https://github.com/dotnet/msbuild/pull/4162)
 - ![In Progress](media/status-in-progress.png "In Progress icon") [Resolve Assembly References (RAR) pre-built cache](https://github.com/dotnet/msbuild/issues/5247)
-- ![In Progress](media/status-in-progress.png "In Progress icon") [Share RAR cache between projects](https://github.com/dotnet/msbuild/blob/master/documentation/specs/rar-as-service.md)
+- ![In Progress](media/status-in-progress.png "In Progress icon") [Share RAR cache between projects](https://github.com/dotnet/msbuild/blob/main/documentation/specs/rar-as-service.md)
 
 ## Desktop
 
 ### WPF
 
-- ![In Progress](media/status-in-progress.png "In Progress icon") WPF Integration with .NET 5
+[Details](https://github.com/dotnet/wpf/blob/main/roadmap.md)
+
+- ![Completed](media/status-completed.png "Completed icon") WPF Integration with .NET 5
 - ![In Progress](media/status-in-progress.png "In Progress icon") Accessibility updates on app sample bugs
 
 ### WinForms
@@ -210,8 +214,8 @@ Please see the following links to view work items and themes across:
 -	![In Progress](media/status-in-progress.png "In Progress icon") Keep pace with changes in the underlying OS to ensure compatibility with the latest changes in Win10.
 
 ## Xamarin
-- ![Completed](media/status-completed.png "Completed icon") [Android 11 / API 30 Support](https://docs.microsoft.com/en-us/xamarin/android/release-notes/11/11.0)
-- ![Completed](media/status-completed.png "Completed icon") [Android smaller APK sizes](https://docs.microsoft.com/en-us/xamarin/android/release-notes/11/11.0#smaller-app-package-sizes)
+- ![Completed](media/status-completed.png "Completed icon") [Android 11 / API 30 Support](https://docs.microsoft.com/xamarin/android/release-notes/11/11.0)
+- ![Completed](media/status-completed.png "Completed icon") [Android smaller APK sizes](https://docs.microsoft.com/xamarin/android/release-notes/11/11.0#smaller-app-package-sizes)
 - ![In Progress](media/status-in-progress.png "In Progress icon") [Xcode 12 and iOS 14 Support](https://github.com/xamarin/xamarin-macios/issues/8931)
 - ![In Progress](media/status-in-progress.png "In Progress icon") Hot Restart for Android
 - ![In Progress](media/status-in-progress.png "In Progress icon") AndroidX and Google Play Services Bindings Updates
@@ -219,13 +223,13 @@ Please see the following links to view work items and themes across:
 - ![In Planning](media/status-in-planning.png "In Planning icon") Xamarin.Essentials integration to .NET 6 BCL (System namespace)
 
 ### Xamarin.Forms 5
-- ![Completed](media/status-completed.png "Completed icon") [AppTheme aka Dark Mode support](https://docs.microsoft.com/en-us/xamarin/xamarin-forms/user-interface/theming/system-theme-changes)
-- ![In Progress](media/status-in-progress.png "In Progress icon") [CarouselView](https://docs.microsoft.com/en-us/xamarin/xamarin-forms/user-interface/carouselview/)
-- ![In Progress](media/status-in-progress.png "In Progress icon") [Drag-and-drop Gestures](https://docs.microsoft.com/en-us/xamarin/xamarin-forms/app-fundamentals/gestures/drag-and-drop)
-- ![In Progress](media/status-in-progress.png "In Progress icon") [Gradient and Solid Brushes](https://docs.microsoft.com/en-us/xamarin/xamarin-forms/user-interface/brushes/)
-- ![In Progress](media/status-in-progress.png "In Progress icon") [Shapes and Paths](https://docs.microsoft.com/en-us/xamarin/xamarin-forms/user-interface/shapes/)
-- ![In Progress](media/status-in-progress.png "In Progress icon") [SwipeView](https://docs.microsoft.com/en-us/xamarin/xamarin-forms/user-interface/swipeview)
+- ![Completed](media/status-completed.png "Completed icon") [AppTheme aka Dark Mode support](https://docs.microsoft.com/xamarin/xamarin-forms/user-interface/theming/system-theme-changes)
+- ![In Progress](media/status-in-progress.png "In Progress icon") [CarouselView](https://docs.microsoft.com/xamarin/xamarin-forms/user-interface/carouselview/)
+- ![In Progress](media/status-in-progress.png "In Progress icon") [Drag-and-drop Gestures](https://docs.microsoft.com/xamarin/xamarin-forms/app-fundamentals/gestures/drag-and-drop)
+- ![In Progress](media/status-in-progress.png "In Progress icon") [Gradient and Solid Brushes](https://docs.microsoft.com/xamarin/xamarin-forms/user-interface/brushes/)
+- ![In Progress](media/status-in-progress.png "In Progress icon") [Shapes and Paths](https://docs.microsoft.com/xamarin/xamarin-forms/user-interface/shapes/)
+- ![In Progress](media/status-in-progress.png "In Progress icon") [SwipeView](https://docs.microsoft.com/xamarin/xamarin-forms/user-interface/swipeview)
 
 ### Xamarin.Forms vNext (.NET MAUI)
-- ![In Progress](media/status-in-progress.png "In Progress icon") [Slim Renderers](https://github.com/dotnet/maui/issues/28) - performance improvements, decouple from bindable, and introduce interfaces 
+- ![In Progress](media/status-in-progress.png "In Progress icon") [Slim Renderers](https://github.com/dotnet/maui/issues/28) - performance improvements, decouple from bindable, and introduce interfaces
 - ![In Planning](media/status-in-planning.png "In Planning icon") WinUI 3 Support - [testing integration](https://github.com/xamarin/Xamarin.Forms/pull/11955)

release-notes/1.0/1.0-supported-os.md

@@ -15,7 +15,7 @@ Windows Server                | 2008 R2 SP1 - 2016*            | x64, x86     |
 
 \* Supported by latest patch release of .NET Core 1.1
 
-See the [Windows Lifecycle Fact Sheet](https://support.microsoft.com/en-us/help/13853/windows-lifecycle-fact-sheet) for details regarding each Windows release lifecycle.
+See the [Windows Lifecycle Fact Sheet](https://support.microsoft.com/help/13853/windows-lifecycle-fact-sheet) for details regarding each Windows release lifecycle.
 
 ## macOS
 
@@ -29,7 +29,7 @@ Mac OS X                      | 10.11, 10.12*                  | x64          |
 
 OS                            | Version                        | Architectures| Notes
 ------------------------------|--------------------------------|--------------|-----
-Red Hat Enterprise Linux <br> CentOS <br> Oracle Linux | 7     | x64          | [Red Hat support policy](https://access.redhat.com/support/policy/updates/errata/) <br> [CentOS lifecycle](https://wiki.centos.org/FAQ/General#head-fe8a0be91ee3e7dea812e8694491e1dde5b75e6d) <br> [Oracle Linux lifecycle](http://www.oracle.com/us/support/library/elsp-lifetime-069338.pdf)
+Red Hat Enterprise Linux <br> CentOS <br> Oracle Linux | 7     | x64          | [Red Hat support policy](https://access.redhat.com/support/policy/updates/errata/) <br> [CentOS lifecycle](https://wiki.centos.org/FAQ/General#head-fe8a0be91ee3e7dea812e8694491e1dde5b75e6d) <br> [Oracle Linux lifecycle](https://www.oracle.com/a/ocom/docs/elsp-lifetime-069338.pdf)
 Fedora                        | 27, 28 (1.1)                   | x64          | [Fedora lifecycle](https://fedoraproject.org/wiki/End_of_life)
 Debian                        | 8.2+                           | x64          | [Debian lifecycle](https://wiki.debian.org/DebianReleases)
 Ubuntu <br> Linux Mint        | 16.04, 18.04 (1.1) <br> 17     | x64    | [Ubuntu lifecycle](https://wiki.ubuntu.com/Releases) <br> [Linux Mint end of life announcements](https://forums.linuxmint.com/search.php?keywords=%22end+of+life%22&terms=all&author=&sc=1&sf=titleonly&sr=posts&sk=t&sd=d&st=0&ch=300&t=0&submit=Search)
@@ -41,7 +41,7 @@ openSUSE                      | 42.3+ (1.1)                    | x64          |
 
 ## Out of support OS versions
 
-Support for the following versions was ended by the distribution owners and are [not supported by .NET Core 1.x](https://github.com/dotnet/core/blob/master/os-lifecycle-policy.md).
+Support for the following versions was ended by the distribution owners and are [not supported by .NET Core 1.x](https://github.com/dotnet/core/blob/main/os-lifecycle-policy.md).
 
 OS         | Version  | End of Life
 -----------|----------|-------------

release-notes/1.0/1.0.0-known-issues.md

@@ -4,12 +4,12 @@ This document lists known issues for *.NET Core 1.0.0* and *.NET Core SDK 1.0.0
 
 ## .NET Core native prerequisites
 
-See the [.NET Core prequisites document](https://github.com/dotnet/core/blob/master/Documentation/prereqs.md) to understand any installation or setup requirements for your OS which are not handled by the .NET Core 1.0.0 installers.
+See the [.NET Core prequisites document](https://github.com/dotnet/core/blob/main/Documentation/prereqs.md) to understand any installation or setup requirements for your OS which are not handled by the .NET Core 1.0.0 installers.
 
 ## NegotiateStream's functionality relies on gssapi implementation
 
 ```NegotiateStream``` relies on the gssapi implementation available on the platform:
-* On Linux, the default gssapi implementation typically provided is [MIT's krb5 library](http://web.mit.edu/kerberos/), which is available on all the linux platforms.
+* On Linux, the default gssapi implementation typically provided is [MIT's krb5 library](https://web.mit.edu/kerberos/), which is available on all the linux platforms.
 * On OS X, the default implementation is the heimdal-based GSS.framework.
 
 On both Linux and OS X, NegotiateStream uses SPNEGO and relies on the underlying implementation for supporting Kerberos and NTLM as the underlying security protocol:
@@ -130,7 +130,7 @@ With 1.0.0 of .NET Core, all applications that target .NET Core and run on Windo
 
 If the dependency is not present, applications will fail to run and errors will be thrown, e.g.
 ```The program can't start because api-ms-win-crt-runtime-1-1-0.dll is missing from your computer. Try reinstalling the program to fix this problem.```
-The UCRT dependency can be installed via Windows Update (name: "Update for Universal C Runtime in Windows", per <https://support.microsoft.com/en-us/kb/2999226>) and, as a recommended update, it will be installed automatically if the user uses the default settings for Windows Update. It can also be downloaded from [Microsoft Download Center](https://www.microsoft.com/en-us/download/details.aspx?id=48234).
+The UCRT dependency can be installed via Windows Update (name: "Update for Universal C Runtime in Windows", per <https://support.microsoft.com/kb/2999226>) and, as a recommended update, it will be installed automatically if the user uses the default settings for Windows Update. It can also be downloaded from [Microsoft Download Center](https://www.microsoft.com/download/details.aspx?id=48234).
 
 - https://github.com/dotnet/corefx/issues/9083
 - https://github.com/dotnet/corefx/issues/9389
@@ -221,8 +221,8 @@ This process will ensure that that the dotnet host finds the appropriate APIs it
 Some libraries that P/Invoke into api-set's and target .NET Framework in our nuget packages might fail to run on Windows 7.
 
 **Workarounds:**
-Some of the api-sets are installed by the UCRT update: <https://support.microsoft.com/en-us/kb/2999226>
-and <https://support.microsoft.com/en-us/kb/2790113> but these installations may not be a comprehensive fix.
+Some of the api-sets are installed by the UCRT update: <https://support.microsoft.com/kb/2999226>
+and <https://support.microsoft.com/kb/2790113> but these installations may not be a comprehensive fix.
 
 - If you're using project.json you can just reference the Microsoft.NETCore.Windows.ApiSets package from your app and be sure to deploy for runtime win7-x86 or win7-x64, as appropriate.
 
@@ -232,6 +232,6 @@ and <https://support.microsoft.com/en-us/kb/2790113> but these installations ma
 
 ## Bash on Ubuntu on Windows
 
-[Bash on Windows (WSL)](https://msdn.microsoft.com/en-us/commandline/wsl/about) is not yet supported by .NET Core. Attempting to run applications in the environment can experience intermittent crashes.
+[Bash on Windows (WSL)](https://docs.microsoft.com/windows/wsl/about) is not yet supported by .NET Core. Attempting to run applications in the environment can experience intermittent crashes.
 
 - https://github.com/Microsoft/BashOnWindows/issues/520

release-notes/1.0/1.0.0-manifest.md

@@ -1,4 +1,4 @@
-# .NET Core 1.0 mainfest
+# .NET Core 1.0 manifest
 
 The following is a comprehensive manifest of packages released for .NET Core 1.0.
 

release-notes/1.0/1.0.0.md

@@ -3,7 +3,7 @@
 ## .NET Core 1.0.0 released 6/27/2016
 
 Details on this release can be read about on the 
-[.NET Blog](https://blogs.msdn.microsoft.com/dotnet/2016/06/27/announcing-net-core-1-0) and if you haven't already discovered the updated [.NET Portal](http://go.microsoft.com/fwlink/?LinkID=798306), make that your next destination for getting started with .NET Core.
+[.NET Blog](https://blogs.msdn.microsoft.com/dotnet/2016/06/27/announcing-net-core-1-0) and if you haven't already discovered the updated [.NET Portal](https://go.microsoft.com/fwlink/?LinkID=798306), make that your next destination for getting started with .NET Core.
 
 There are a few issues to be aware of, which are described in the [.NET Core 1.0.0 Known Issues](1.0.0-known-issues.md) document.
 

release-notes/1.0/1.0.1-manifest.md

@@ -1,4 +1,4 @@
-# .NET Core September 2016 Update for .NET Core 1.0 mainfest
+# .NET Core September 2016 Update for .NET Core 1.0 manifest
 
 The following is a comprehensive manifest of packages released with September 2016 Update for .NET Core 1.0.
 

release-notes/1.0/1.0.1-release-notes.md

@@ -2,11 +2,11 @@
 
 ## .NET Core September 2016 Update - 1.0.1 released 9/13/2016
 
-A few highlights on this release can be read about on the [.NET Blog](https://blogs.msdn.microsoft.com/dotnet/) and if you haven't already discovered the updated [.NET Portal](http://go.microsoft.com/fwlink/?LinkID=798306), make that your next destination for getting started with .NET Core.
+A few highlights on this release can be read about on the [.NET Blog](https://blogs.msdn.microsoft.com/dotnet/) and if you haven't already discovered the updated [.NET Portal](https://go.microsoft.com/fwlink/?LinkID=798306), make that your next destination for getting started with .NET Core.
 
 This release coincides with a security advisory for MVC. See the following for additional details.
 
-* [Advisory](https://technet.microsoft.com/en-us/en-us/library/3181759.aspx)
+* [Advisory](https://docs.microsoft.com/security-updates/SecurityAdvisories/2016/3181759)
 * [Announcement](https://github.com/aspnet/Announcements/issues/203)
 * [Discussion](https://github.com/aspnet/Mvc/issues/5271)
 
@@ -31,4 +31,4 @@ The fix list below includes a number of components under the .NET Core umbrella
 
 ### ASP.NET Core
 
-* Please see the [ASP.NET Core release page](https://github.com/aspnet/home/releases/1.0.1) for details on fixes for ASP.NET Core, MVC, Entity Framework Core and other components. 
+* Please see the [ASP.NET Core release page](https://github.com/aspnet/home/releases/1.0.1) for details on fixes for ASP.NET Core, MVC, Entity Framework Core and other components.

release-notes/1.0/1.0.1-sdk-release-notes.md

@@ -3,10 +3,10 @@
 ## .NET Core March 2017 Update - Released 3/7/2017
 
 * .NET Core SDK 1.0.0 and 1.0.1
-* [.NET Core 1.0.4](https://github.com/dotnet/core/blob/master/release-notes/1.0/1.0.4.md)
-* [.NET Core 1.1.1](https://github.com/dotnet/core/blob/master/release-notes/1.1/1.1.1.md)
+* [.NET Core 1.0.4](https://github.com/dotnet/core/blob/main/release-notes/1.0/1.0.4.md)
+* [.NET Core 1.1.1](https://github.com/dotnet/core/blob/main/release-notes/1.1/1.1.1.md)
 
-[.NET Core 1.0.4](https://github.com/dotnet/core/blob/master/release-notes/1.0/1.0.4.md) was released today. Both releases include reliability updates to improve the quality of .NET Core. You can download the .NET Core Runtime releases via our [.NET Core Runtimes download page](https://www.microsoft.com/net/download/core#/runtime). If you are looking for the .NET Core SDK, to get the latest tools, try the [.NET Core SDK download page](https://www.microsoft.com/net/download/core#/sdk).
+[.NET Core 1.0.4](https://github.com/dotnet/core/blob/main/release-notes/1.0/1.0.4.md) was released today. Both releases include reliability updates to improve the quality of .NET Core. You can download the .NET Core Runtime releases via our [.NET Core Runtimes download page](https://dotnet.microsoft.com/download/dotnet/current/runtime). If you are looking for the .NET Core SDK, to get the latest tools, try the [.NET Core SDK download page](https://dotnet.microsoft.com/download).
 
 Have a look at the [.NET announcement blog post](https://blogs.msdn.microsoft.com/dotnet/2017/03/07/announcing-net-core-tools-1-0/) for details and great context around the release. Visual Studio 2017 is also releasing today and you can read about it in their [announcement](https://blogs.msdn.microsoft.com/visualstudio/).
 
@@ -14,7 +14,7 @@ Have a look at the [.NET announcement blog post](https://blogs.msdn.microsoft.co
 
 **.NET Core SDK 1.0.0** is releasing with Visual Studio 2017. The [announcement blog](https://blogs.msdn.microsoft.com/dotnet/2017/03/07/announcing-net-core-tools-1-0/) as well as the [RC4 blog post](https://blogs.msdn.microsoft.com/dotnet/2017/02/07/announcing-net-core-tools-updates-in-vs-2017-rc) have great details on what is available in this final release.
 
-**.NET Core SDK 1.0.1**, available for download from the [.NET Core download page](https://www.microsoft.com/net/core), also includes support for Fedora 24, OpenSUSE 42.1 and Ubuntu 16.10.
+**.NET Core SDK 1.0.1**, available for download from the [.NET Core download page](https://dotnet.microsoft.com/download), also includes support for Fedora 24, OpenSUSE 42.1 and Ubuntu 16.10.
 
 ### project.json tools
 

release-notes/1.0/1.0.10.md

@@ -4,8 +4,8 @@ Microsoft is releasing security advisories for .NET Core and ASP.NET Core. Issue
 
 .NET Core 1.0.10 and SDK 1.1.8 are available for download and usage in your environment.
 
-* [Getting Started](https://www.microsoft.com/net/core/)
-* [Downloads](https://github.com/dotnet/core/blob/master/release-notes/download-archives/1.0.10-download.md)
+* [Getting Started](https://dotnet.microsoft.com/download)
+* [Downloads](https://github.com/dotnet/core/blob/main/release-notes/download-archives/1.0.10-download.md)
 
 The .NET Core SDK 1.1.8 includes .NET Core 1.0.10 Runtime so downloading the runtime packages separately is not needed when installing the SDK. After installing the .NET Core SDK 1.1.8, the following command will show that you're running version `1.1.8` of the tools.
 

release-notes/1.0/1.0.11.md

@@ -4,8 +4,8 @@ Microsoft is releasing updates for .NET Core and ASP.NET Core. Issues addressed
 
 .NET Core 1.0.11 and SDK 1.1.8 are available for download and usage in your environment.
 
-* [Getting Started](https://www.microsoft.com/net/core/)
-* [Downloads](https://github.com/dotnet/core/blob/master/release-notes/download-archives/1.0.11-download.md)
+* [Getting Started](https://dotnet.microsoft.com/download)
+* [Downloads](https://github.com/dotnet/core/blob/main/release-notes/download-archives/1.0.11-download.md)
 
 The .NET Core SDK 1.1.9 includes .NET Core 1.0.11 Runtime so downloading the runtime packages separately is not needed when installing the SDK. After installing the .NET Core SDK 1.1.8, the following command will show that you're running version `1.1.9` of the tools.
 
@@ -19,7 +19,7 @@ The [.NET Core Docker images](https://hub.docker.com/r/microsoft/dotnet/) have b
 
 ## Azure AppServices
 
-Deployment of this update to Azure AppServices is in process. Because AppServices is a high availability service, the deployment is carfully staged across regions over a period of time. Deployment will begin in the West US 2 and North Central US regions with remaining regions following over a few days.
+Deployment of this update to Azure AppServices is in process. Because AppServices is a high availability service, the deployment is carefully staged across regions over a period of time. Deployment will begin in the West US 2 and North Central US regions with remaining regions following over a few days.
 
 ## Known Issues
 

release-notes/1.0/1.0.12.md

@@ -2,7 +2,7 @@
 
 .NET Core 1.0.12 is available for download and usage in your environment.
 
-* [Download .NET Core](https://github.com/dotnet/core/blob/master/release-notes/download-archives/1.0.12-download.md)
+* [Download .NET Core](https://github.com/dotnet/core/blob/main/release-notes/download-archives/1.0.12-download.md)
 
 ## Blog Round up
 
@@ -22,7 +22,7 @@ The [.NET Core Docker images](https://hub.docker.com/r/microsoft/dotnet/) have b
 
 ## .NET Core Lifecycle News
 
-See [.NET Core Supported OS Lifecycle Policy](https://github.com/dotnet/core/blob/master/os-lifecycle-policy.md) to learn about Windows, macOS and Linux versions that are supported for each .NET Core release.
+See [.NET Core Supported OS Lifecycle Policy](https://github.com/dotnet/core/blob/main/os-lifecycle-policy.md) to learn about Windows, macOS and Linux versions that are supported for each .NET Core release.
 
 .NET Core 2.1 is expected to be declared LTS in the next few months. It is recommended that 2.1 be the default target for projects. .NET Core 2.0 will go out of support October 2018.
 

release-notes/1.0/1.0.13.md

@@ -2,7 +2,7 @@
 
 .NET Core 1.0.13 is available for download and usage in your environment.
 
-* [Download .NET Core](https://github.com/dotnet/core/blob/master/release-notes/download-archives/1.0.13-download.md)
+* [Download .NET Core](https://github.com/dotnet/core/blob/main/release-notes/download-archives/1.0.13-download.md)
 
 ## Blog Round up
 
@@ -22,9 +22,9 @@ The [.NET Core Docker images](https://hub.docker.com/r/microsoft/dotnet/) have b
 
 ## .NET Core Lifecycle News
 
-See [.NET Core Supported OS Lifecycle Policy](https://github.com/dotnet/core/blob/master/os-lifecycle-policy.md) to learn about Windows, macOS and Linux versions that are supported for each .NET Core release.
+See [.NET Core Supported OS Lifecycle Policy](https://github.com/dotnet/core/blob/main/os-lifecycle-policy.md) to learn about Windows, macOS and Linux versions that are supported for each .NET Core release.
 
-As .NET Core 2.1 has become LTS (anounced in [August 2018 blog post](https://blogs.msdn.microsoft.com/dotnet/2018/08/21/net-core-august-2018-update)), 1.0 and 1.1 have entered their maintenance phase and will only get critical security fixes going forward till their end of support on June 27, 2019.
+As .NET Core 2.1 has become LTS (announced in [August 2018 blog post](https://blogs.msdn.microsoft.com/dotnet/2018/08/21/net-core-august-2018-update)), 1.0 and 1.1 have entered their maintenance phase and will only get critical security fixes going forward till their end of support on June 27, 2019.
 
 ## Notable Changes in 1.0.13
 

release-notes/1.0/1.0.14/1.0.14-download.md

@@ -5,7 +5,7 @@
 * .NET Core Runtime 1.0.14
 * .NET Core SDK 1.1.12
 
-See the [Release Notes](https://github.com/dotnet/core/blob/master/release-notes/1.0/1.0.14/1.0.14.md) for details about what is included in this update.
+See the [Release Notes](https://github.com/dotnet/core/blob/main/release-notes/1.0/1.0.14/1.0.14.md) for details about what is included in this update.
 
 |           | SDK Installer<sup>1</sup>                                   | SDK Binaries<sup>1</sup>                            | Runtime Installer                                        | Runtime Binaries                                 | ASP.NET Core Runtime           |
 | --------- | :------------------------------------------:     | :----------------------:                 | :---------------------------:                            | :-------------------------:                      | :-----------------:            |
@@ -53,7 +53,7 @@ sudo apt-get install dotnet-sharedframework-microsoft.netcore.app-1.0.14
 
 ## Installation from a binary archive
 
-Installing from the packages detailed above is recommended or you can install from binary archive, if that better suits your needs. When using binary archives to install, the contents must be extracted to a user location such as `$HOME/dotnet`, a symbolic link created for `dotnet` and a few dependencies installed. Dependency requirements can be seen in the [Linux System Prerequisites](https://github.com/dotnet/core/blob/master/Documentation/linux-prereqs.md) document.
+Installing from the packages detailed above is recommended or you can install from binary archive, if that better suits your needs. When using binary archives to install, the contents must be extracted to a user location such as `$HOME/dotnet`, a symbolic link created for `dotnet` and a few dependencies installed. Dependency requirements can be seen in the [Linux System Prerequisites](https://github.com/dotnet/core/blob/main/Documentation/linux-prereqs.md) document.
 
 ```bash
 mkdir -p $HOME/dotnet && tar zxf dotnet.tar.gz -C $HOME/dotnet
@@ -61,7 +61,7 @@ export PATH=$PATH:$HOME/dotnet
 ```
 [blob-runtime]: https://dotnetcli.blob.core.windows.net/dotnet/Runtime/
 [blob-sdk]: https://dotnetcli.blob.core.windows.net/dotnet/Sdk/
-[release-notes]: https://github.com/dotnet/core/blob/master/release-notes/1.0/1.0.14.md
+[release-notes]: https://github.com/dotnet/core/blob/main/release-notes/1.0/1.0.14.md
 
 [dotnet-centos-x64.tar.gz]: https://download.visualstudio.microsoft.com/download/pr/49f8157c-f170-4e0e-88ab-20170f9f5354/3fe0e777d5953e2919e7ca0a78c08737/dotnet-centos-x64.1.0.14.tar.gz
 [dotnet-debian-x64.tar.gz]: https://download.visualstudio.microsoft.com/download/pr/cf9005e0-2e04-45c5-95fb-617cd1cf23d2/7638479ba289bc6e78e7c4736216f106/dotnet-debian-x64.1.0.14.tar.gz
@@ -97,5 +97,5 @@ export PATH=$PATH:$HOME/dotnet
 [checksums-runtime]: https://dotnetcli.blob.core.windows.net/dotnet/checksums/1.0.14-runtime-sha.txt
 [checksums-sdk]: https://dotnetcli.blob.core.windows.net/dotnet/checksums/1.1.12-sdk-sha.txt
 
-[linux-install]: https://www.microsoft.com/net/download/dotnet-core/1.0
-[linux-setup]: https://github.com/dotnet/core/blob/master/Documentation/linux-setup.md
+[linux-install]: https://dotnet.microsoft.com/download/dotnet/1.0
+[linux-setup]: https://github.com/dotnet/core/blob/main/Documentation/linux-setup.md

release-notes/1.0/1.0.14/1.0.14.md

@@ -22,7 +22,7 @@ There are no changes this month in OS version support status.
 
 .NET Core 1.0 and 1.1, which entered "Maintenance" support status when 2.1 was declared LTS, will be end-of-life June 27, 2019. Updates for the 1.0 and 1.1 channels will no longer be offered after that date. See [.NET Core Support Policy](https://dotnet.microsoft.com/platform/support/policy/dotnet-core) to learn more about the .NET Core support lifecycle.
 
-See [.NET Core Supported OS Lifecycle Policy](https://github.com/dotnet/core/blob/master/os-lifecycle-policy.md) to learn about Windows, macOS and Linux versions that are supported for each .NET Core release.
+See [.NET Core Supported OS Lifecycle Policy](https://github.com/dotnet/core/blob/main/os-lifecycle-policy.md) to learn about Windows, macOS and Linux versions that are supported for each .NET Core release.
 
 ## Notable Changes in 1.0.14
 

release-notes/1.0/1.0.15/1.0.15-download.md

@@ -52,7 +52,7 @@ sudo apt-get install dotnet-sharedframework-microsoft.netcore.app-1.0.15
 
 ## Installation from a binary archive
 
-Installing from the packages detailed above is recommended or you can install from binary archive, if that better suits your needs. When using binary archives to install, the contents must be extracted to a user location such as `$HOME/dotnet`, a symbolic link created for `dotnet` and a few dependencies installed. Dependency requirements can be seen in the [Linux System Prerequisites](https://github.com/dotnet/core/blob/master/Documentation/linux-prereqs.md) document.
+Installing from the packages detailed above is recommended or you can install from binary archive, if that better suits your needs. When using binary archives to install, the contents must be extracted to a user location such as `$HOME/dotnet`, a symbolic link created for `dotnet` and a few dependencies installed. Dependency requirements can be seen in the [Linux System Prerequisites](https://github.com/dotnet/core/blob/main/Documentation/linux-prereqs.md) document.
 
 ```bash
 mkdir -p $HOME/dotnet && tar zxf dotnet.tar.gz -C $HOME/dotnet
@@ -60,7 +60,7 @@ export PATH=$PATH:$HOME/dotnet
 ```
 [blob-runtime]: https://dotnetcli.blob.core.windows.net/dotnet/Runtime/
 [blob-sdk]: https://dotnetcli.blob.core.windows.net/dotnet/Sdk/
-[release-notes]: https://github.com/dotnet/core/blob/master/release-notes/1.0/1.0.15.md
+[release-notes]: https://github.com/dotnet/core/blob/main/release-notes/1.0/1.0.15.md
 
 [dotnet-centos-x64.tar.gz]: https://download.visualstudio.microsoft.com/download/pr/160b5882-cc9f-4887-b641-b2049d0a1844/74e559657e6ca8f92319164506f8ad64/dotnet-centos-x64.1.0.15.tar.gz
 [dotnet-osx-x64.pkg]: https://download.visualstudio.microsoft.com/download/pr/171b6b96-9368-40f2-87a6-77a7a0f422e3/f706ac99ee323d1061611d4e84df742d/dotnet-osx-x64.1.0.15.pkg
@@ -94,6 +94,6 @@ export PATH=$PATH:$HOME/dotnet
 [checksums-runtime]: https://dotnetcli.blob.core.windows.net/dotnet/checksums/1.0.15-runtime-sha.txt
 [checksums-sdk]: https://dotnetcli.blob.core.windows.net/dotnet/checksums/1.1.13-sdk-sha.txt
 
-[linux-install]: https://www.microsoft.com/net/download/dotnet-core/1.0
-[linux-setup]: https://github.com/dotnet/core/blob/master/Documentation/linux-setup.md
+[linux-install]: https://dotnet.microsoft.com/download/dotnet/1.0
+[linux-setup]: https://github.com/dotnet/core/blob/main/Documentation/linux-setup.md
 [dotnet-blog]: https://blogs.msdn.microsoft.com/dotnet/2019/03/12/net-core-march-2019/

release-notes/1.0/1.0.15/1.0.15.md

@@ -24,13 +24,13 @@ There are no changes this month in OS version support status.
 
 .NET Core 1.0 and 1.1, which entered "Maintenance" support status when 2.1 was declared LTS, will be end-of-life June 27, 2019. Updates for the 1.0 and 1.1 channels will no longer be offered after that date. See [.NET Core Support Policy](https://dotnet.microsoft.com/platform/support/policy/dotnet-core) to learn more about the .NET Core support lifecycle.
 
-See [.NET Core Supported OS Lifecycle Policy](https://github.com/dotnet/core/blob/master/os-lifecycle-policy.md) to learn about Windows, macOS and Linux versions that are supported for each .NET Core release.
+See [.NET Core Supported OS Lifecycle Policy](https://github.com/dotnet/core/blob/main/os-lifecycle-policy.md) to learn about Windows, macOS and Linux versions that are supported for each .NET Core release.
 
 ## Changes in 1.0.15
 
-* [CVE-2019-0657: .NET Core NuGet Tampering Vulnerability](https://portal.msrc.microsoft.com/en-us/security-guidance/advisory/CVE-2019-0757)
+* [CVE-2019-0657: .NET Core NuGet Tampering Vulnerability](https://msrc.microsoft.com/update-guide/vulnerability/CVE-2019-0757)
 
-    A tampering vulnerability exists in NuGet software when executed in a Linux or Mac environment. An attacker who successfully exploited the vulnerability could run arbitrary code in the context of the current user. If the current user is logged on with administrative user rights, an attacker could take control of the affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights. Exploitation of the vulnerability requires that an attacker can login as any other user on that machine. At that point, the attacker will be able to replace or add to files that were created by a NuGet restore operation in the current users account. 
+    A tampering vulnerability exists in NuGet software when executed in a Linux or Mac environment. An attacker who successfully exploited the vulnerability could run arbitrary code in the context of the current user. If the current user is logged on with administrative user rights, an attacker could take control of the affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights. Exploitation of the vulnerability requires that an attacker can login as any other user on that machine. At that point, the attacker will be able to replace or add to files that were created by a NuGet restore operation in the current users account.
 
     The security update addresses the vulnerability by correcting how NuGet restore creates file permissions for all files extracted to the client machine.
 

release-notes/1.0/1.0.16/1.0.16-download.md

@@ -52,7 +52,7 @@ sudo apt-get install dotnet-sharedframework-microsoft.netcore.app-1.0.16
 
 ## Installation from a binary archive
 
-Installing from the packages detailed above is recommended or you can install from binary archive, if that better suits your needs. When using binary archives to install, the contents must be extracted to a user location such as `$HOME/dotnet`, a symbolic link created for `dotnet` and a few dependencies installed. Dependency requirements can be seen in the [Linux System Prerequisites](https://github.com/dotnet/core/blob/master/Documentation/linux-prereqs.md) document.
+Installing from the packages detailed above is recommended or you can install from binary archive, if that better suits your needs. When using binary archives to install, the contents must be extracted to a user location such as `$HOME/dotnet`, a symbolic link created for `dotnet` and a few dependencies installed. Dependency requirements can be seen in the [Linux System Prerequisites](https://github.com/dotnet/core/blob/main/Documentation/linux-prereqs.md) document.
 
 ```bash
 mkdir -p $HOME/dotnet && tar zxf dotnet.tar.gz -C $HOME/dotnet
@@ -60,7 +60,7 @@ export PATH=$PATH:$HOME/dotnet
 ```
 [blob-runtime]: https://dotnetcli.blob.core.windows.net/dotnet/Runtime/
 [blob-sdk]: https://dotnetcli.blob.core.windows.net/dotnet/Sdk/
-[release-notes]: https://github.com/dotnet/core/blob/master/release-notes/1.0/1.0.16/1.0.16.md
+[release-notes]: https://github.com/dotnet/core/blob/main/release-notes/1.0/1.0.16/1.0.16.md
 
 [dotnet-centos-x64.tar.gz]: https://download.visualstudio.microsoft.com/download/pr/b15f877f-1299-466b-805c-439c4b208229/6b0ebc8e907cd732744974e4f1f0b04f/dotnet-centos-x64.1.0.16.tar.gz
 [dotnet-osx-x64.pkg]: https://download.visualstudio.microsoft.com/download/pr/10f564b1-0578-4de0-9ed8-7890c60ccfb2/8dc054cf37402b2af50b11b1b9014130/dotnet-osx-x64.1.0.16.pkg
@@ -95,6 +95,6 @@ export PATH=$PATH:$HOME/dotnet
 [checksums-runtime]: https://dotnetcli.blob.core.windows.net/dotnet/checksums/1.0.16-runtime-sha.txt
 [checksums-sdk]: https://dotnetcli.blob.core.windows.net/dotnet/checksums/1.1.14-sdk-sha.txt
 
-[linux-install]: https://www.microsoft.com/net/download/dotnet-core/1.0
-[linux-setup]: https://github.com/dotnet/core/blob/master/Documentation/linux-setup.md
+[linux-install]: https://dotnet.microsoft.com/download/dotnet/1.0
+[linux-setup]: https://github.com/dotnet/core/blob/main/Documentation/linux-setup.md
 [dotnet-blog]: https://devblogs.microsoft.com/dotnet/net-core-may-2019/

release-notes/1.0/1.0.16/1.0.16.md

@@ -24,11 +24,11 @@ Ubuntu 14.04 reached the [end of standard support April 2019](https://wiki.ubunt
 
 .NET Core 1.0 and 1.1, which entered "Maintenance" support status when 2.1 was declared LTS, will be end-of-life June 27, 2019. Updates for the 1.0 and 1.1 channels will no longer be offered after that date. See [.NET Core Support Policy](https://dotnet.microsoft.com/platform/support/policy/dotnet-core) to learn more about the .NET Core support lifecycle.
 
-See [.NET Core Supported OS Lifecycle Policy](https://github.com/dotnet/core/blob/master/os-lifecycle-policy.md) to learn about Windows, macOS and Linux versions that are supported for each .NET Core release.
+See [.NET Core Supported OS Lifecycle Policy](https://github.com/dotnet/core/blob/main/os-lifecycle-policy.md) to learn about Windows, macOS and Linux versions that are supported for each .NET Core release.
 
 ## Changes in 1.0.16
 
-* [CVE-2019-0820: .NET Core Tampering Vulnerability](https://portal.msrc.microsoft.com/en-us/security-guidance/advisory/CVE-2019-0820)
+* [CVE-2019-0820: .NET Core Tampering Vulnerability](https://msrc.microsoft.com/update-guide/vulnerability/CVE-2019-0820)
 
 Microsoft is releasing this security advisory to provide information about a vulnerability in .NET Core 1.0, 1.1, 2.1 and 2.2. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability.
 
@@ -39,12 +39,12 @@ A remote unauthenticated attacker could exploit this vulnerability by issuing sp
 The update addresses the vulnerability by correcting how .NET Core applications handle RegEx string processing.
 
     **Affected Package and Binary updates**
-    
+
     Package name | Vulnerable versions | Secure versions
     ------------ | ------------------- | -------------------------
     System.Text.RegularExpressions.dll | 4.3.0 | 4.3.1
-    
-* [CVE-2019-0980: ASP.NET Core Denial of Service Vulnerability](https://portal.msrc.microsoft.com/en-us/security-guidance/advisory/CVE-2019-0980)
+
+* [CVE-2019-0980: ASP.NET Core Denial of Service Vulnerability](https://msrc.microsoft.com/update-guide/vulnerability/CVE-2019-0980)
 
 Microsoft is releasing this security advisory to provide information about a vulnerability in .NET Core and ASP.NET Core 1.0, 1.1, 2.1 and 2.2. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability.
 
@@ -59,8 +59,8 @@ The update addresses the vulnerability by correcting how .NET Core and ASP.NET C
     Package name | Vulnerable versions | Secure versions
     ------------ | ------------------- | -------------------------
     System.Private.Uri | 4.3.0, 4.3.1 | 4.3.2
-    
-* [CVE-2019-0981: ASP.NET Core Denial of Service Vulnerability](https://portal.msrc.microsoft.com/en-us/security-guidance/advisory/CVE-2019-0981)
+
+* [CVE-2019-0981: ASP.NET Core Denial of Service Vulnerability](https://msrc.microsoft.com/update-guide/vulnerability/CVE-2019-0981)
 
 Microsoft is releasing this security advisory to provide information about a vulnerability in .NET Core and ASP.NET Core 1.0, 1.1, 2.1 and 2.2. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability.
 

release-notes/1.0/1.0.3-SDK-RC4.md

@@ -8,7 +8,7 @@ Today we are releasing updates to the .NET Core SDK and Visual Studio 2017 RC. I
 
 We’re getting close to the final release of .NET Core Tools and Visual Studio 2017 making it a great time to try out the migration tools on your projects. and give us feedback on the experience. If you want to try .NET Core Tools in Visual Studio 2017, visit [Visual Studio 2017 RC](https://www.visualstudio.com/vs/visual-studio-2017-rc/) to download. You’ll need to choose the Web workload when installing.
 
-If you’re using another dev tool on Windows, macOS or Linux, go to the [.NET Core RC Download](https://github.com/dotnet/core/blob/master/release-notes/rc4-download.md) for all installation options.
+If you’re using another dev tool on Windows, macOS or Linux, go to the [.NET Core RC Download](https://github.com/dotnet/core/blob/main/release-notes/rc4-download.md) for all installation options.
 
 Want a helping hand from Microsoft for migrating your .NET Core and ASP.NET Core projects from project.json to the new VS2017 csproj format? Please click [here](http://landinghub.visualstudio.com/migrate-dotnetcore).
 

release-notes/1.0/1.0.3-manifest.md

@@ -1,4 +1,4 @@
-# .NET Core December 2016 Update for .NET Core 1.0 mainfest
+# .NET Core December 2016 Update for .NET Core 1.0 manifest
 
 The following is a comprehensive manifest of packages released with December 2016 Update for .NET Core 1.0.
 

release-notes/1.0/1.0.3.md

@@ -2,7 +2,7 @@
 
 ## .NET Core December 2016 Update - 1.0.3 released 12/13/2016
 
-A few highlights on this release can be read about on the [.NET Blog](https://blogs.msdn.microsoft.com/dotnet/). This update can be downloaded and installed from the [.NET Portal](https://www.microsoft.com/net/download/core?v=lts).
+A few highlights on this release can be read about on the [.NET Blog](https://blogs.msdn.microsoft.com/dotnet/). This update can be downloaded and installed from the [.NET Portal](https://dotnet.microsoft.com/download).
 
 ## Closed Issues for 1.0.3
 
@@ -24,4 +24,4 @@ The fix list below includes a number of components under the .NET Core umbrella
 
 ### ASP.NET Core
 
-* Please see the [ASP.NET Core release page](https://github.com/aspnet/home/releases/1.0.3) for details on fixes from ASP.NET Core, MVC, Entitiy Framework Core and others.
+* Please see the [ASP.NET Core release page](https://github.com/aspnet/home/releases/1.0.3) for details on fixes from ASP.NET Core, MVC, Entity Framework Core and others.

release-notes/1.0/1.0.4-sdk.md

@@ -2,11 +2,11 @@
 
 ## .NET Core May 2017 Update - SDK 1.0.4 Released 5/8/2017
 
-This release includes critical security and reliability updates to improve the quality of .NET Core. The latest releases can be found on the [.NET Core download pages](https://www.microsoft.com/net/download/core#/runtime) or from the following.
+This release includes critical security and reliability updates to improve the quality of .NET Core. The latest releases can be found on the [.NET Core download pages](https://dotnet.microsoft.com/download/dotnet/current/runtime) or from the following.
 
-* [.NET Core Runtime 1.0.5](https://github.com/dotnet/core/blob/master/release-notes/download-archives/1.0.5-download.md)
-* [.NET Core Runtime 1.1.2](https://github.com/dotnet/core/blob/master/release-notes/download-archives/1.1.2-download.md)
-* [.NET Core SDK 1.0.4](https://github.com/dotnet/core/blob/master/release-notes/download-archives/1.0.4-sdk-download.md)
+* [.NET Core Runtime 1.0.5](https://github.com/dotnet/core/blob/main/release-notes/download-archives/1.0.5-download.md)
+* [.NET Core Runtime 1.1.2](https://github.com/dotnet/core/blob/main/release-notes/download-archives/1.1.2-download.md)
+* [.NET Core SDK 1.0.4](https://github.com/dotnet/core/blob/main/release-notes/download-archives/1.0.4-sdk-download.md)
 
 The .NET Core SDK 1.0.4 includes .NET Core 1.0.5 and 1.1.2 runtimes so downloading the runtime packages separately is not needed when installing the SDK.
 

release-notes/1.0/1.0.4.md

@@ -2,7 +2,7 @@
 
 ## .NET Core March 2017 Update - 1.0.4 Released 3/7/2017
 
-[.NET Core 1.0.4](https://github.com/dotnet/core/blob/master/release-notes/1.0/1.0.4.md) was released today. Both releases include reliability updates to improve the quality of .NET Core. You can download the .NET Core Runtime releases via our [.NET Core Runtimes download page](https://www.microsoft.com/net/download/core#/runtime). If you are looking for the .NET Core SDK, to get the latest tools, try the [.NET Core SDK download page](https://www.microsoft.com/net/download/core#/sdk).
+[.NET Core 1.0.4](https://github.com/dotnet/core/blob/main/release-notes/1.0/1.0.4.md) was released today. Both releases include reliability updates to improve the quality of .NET Core. You can download the .NET Core Runtime releases via our [.NET Core Runtimes download page](https://dotnet.microsoft.com/download/dotnet/current/runtime). If you are looking for the .NET Core SDK, to get the latest tools, try the [.NET Core SDK download page](https://dotnet.microsoft.com/download).
 
 Have a look at the [.NET announcement blog post](https://blogs.msdn.microsoft.com/dotnet/2017/03/07/announcing-net-core-tools-1-0/) for details and great context around the release. Visual Studio 2017 is also releasing today and you can read about it in their [announcement](https://blogs.msdn.microsoft.com/visualstudio/).
 
@@ -10,7 +10,7 @@ Have a look at the [.NET announcement blog post](https://blogs.msdn.microsoft.co
 
 **.NET Core SDK 1.0.0** is releasing with Visual Studio 2017. The [announcement blog](https://blogs.msdn.microsoft.com/dotnet/2017/03/07/announcing-net-core-tools-1-0/) as well as the [RC4 blog post](https://blogs.msdn.microsoft.com/dotnet/2017/02/07/announcing-net-core-tools-updates-in-vs-2017-rc) have great details on what is available in this final release.
 
-**.NET Core SDK 1.0.1**, available for download from the [.NET Core download page](https://www.microsoft.com/net/core), also includes support for Fedora 24, OpenSUSE 42.1 and Ubuntu 16.10.
+**.NET Core SDK 1.0.1**, available for download from the [.NET Core download page](https://dotnet.microsoft.com/download), also includes support for Fedora 24, OpenSUSE 42.1 and Ubuntu 16.10.
 
 ### project.json tools
 

release-notes/1.0/1.0.5.md

@@ -2,11 +2,11 @@
 
 ## .NET Core May 2017 Update - 1.0.5 Released 5/8/2017
 
-This release includes critical security and reliability updates to improve the quality of .NET Core. The latest releases can be found on the [.NET Core download pages](https://www.microsoft.com/net/download/core#/runtime) or from the following.
+This release includes critical security and reliability updates to improve the quality of .NET Core. The latest releases can be found on the [.NET Core download pages](https://dotnet.microsoft.com/download/dotnet/current/runtime) or from the following.
 
-* [.NET Core Runtime 1.0.5](https://github.com/dotnet/core/blob/master/release-notes/download-archives/1.0.5-download.md)
-* [.NET Core Runtime 1.1.2](https://github.com/dotnet/core/blob/master/release-notes/download-archives/1.1.2-download.md)
-* [.NET Core SDK 1.0.4](https://github.com/dotnet/core/blob/master/release-notes/download-archives/1.0.4-sdk-download.md)
+* [.NET Core Runtime 1.0.5](https://github.com/dotnet/core/blob/main/release-notes/download-archives/1.0.5-download.md)
+* [.NET Core Runtime 1.1.2](https://github.com/dotnet/core/blob/main/release-notes/download-archives/1.1.2-download.md)
+* [.NET Core SDK 1.0.4](https://github.com/dotnet/core/blob/main/release-notes/download-archives/1.0.4-sdk-download.md)
 
 The .NET Core SDK 1.0.4 includes .NET Core 1.0.5 and 1.1.2 runtimes so downloading the runtime packages separately is not needed when installing the SDK.
 

release-notes/1.0/1.0.7.md

@@ -4,8 +4,8 @@
 
 ## Downloads
 
-* [.NET Core 1.0.7](https://github.com/dotnet/core/blob/master/release-notes/download-archives/1.0.7-download.md)
-* [.NET Core 1.1.4](https://github.com/dotnet/core/blob/master/release-notes/download-archives/1.1.4-download.md)
+* [.NET Core 1.0.7](https://github.com/dotnet/core/blob/main/release-notes/download-archives/1.0.7-download.md)
+* [.NET Core 1.1.4](https://github.com/dotnet/core/blob/main/release-notes/download-archives/1.1.4-download.md)
 
 After installing the .NET Core SDK 1.1.4, the following command will show that you're running version `1.1.4` of the tools.
 

release-notes/1.0/1.0.8.md

@@ -4,8 +4,8 @@
 
 ## Downloads
 
-* [.NET Core 1.0.8](https://github.com/dotnet/core/blob/master/release-notes/download-archives/1.0.8.md)
-* [.NET Core 1.1.5](https://github.com/dotnet/core/blob/master/release-notes/download-archives/1.1.5.md)
+* [.NET Core 1.0.8](https://github.com/dotnet/core/blob/main/release-notes/download-archives/1.0.8.md)
+* [.NET Core 1.1.5](https://github.com/dotnet/core/blob/main/release-notes/download-archives/1.1.5.md)
 
 After installing the .NET Core SDK 1.1.5, the following command will show that you're running version `1.1.5` of the tools.
 

release-notes/1.0/1.0.9.md

@@ -5,8 +5,8 @@ Microsoft is releasing security advisories for .NET Core and ASP.NET Core. Issue
 .NET Core 1.0.9 and SDK 1.1.7 are available for download and usage in your environment.
 
 * [Announcement](https://blogs.msdn.microsoft.com/)
-* [Getting Started](https://www.microsoft.com/net/core/)
-* [Downloads](https://github.com/dotnet/core/blob/master/release-notes/download-archives/2.0.5-download.md)
+* [Getting Started](https://dotnet.microsoft.com/download)
+* [Downloads](https://github.com/dotnet/core/blob/main/release-notes/download-archives/2.0.5-download.md)
 
 The .NET Core SDK 1.1.7 includes .NET Core 1.0.9 Runtime so downloading the runtime packages separately is not needed when installing the SDK. After installing the .NET Core SDK 1.1.7, the following command will show that you're running version `1.1.7` of the tools.
 

release-notes/1.0/Known-Issues-RC2.md

@@ -8,7 +8,7 @@ This document lists known issues for *.NET Core 1.0 RC2* and *.NET Core SDK 1.0
 
 ## .NET Core 1.0 SDK Preview 1
 
-All previous versions of .NET Core and any tooling **must be** removed from the machine in order to properly install and use RC2 release. Details and steps to uninstall can be found on the [.NET Core Getting Started](http://go.microsoft.com/fwlink/?LinkID=798687) pages and in the [RC1 to RC2 Upgrade Roadmap](RC1-RC2_Upgrade.md).
+All previous versions of .NET Core and any tooling **must be** removed from the machine in order to properly install and use RC2 release. Details and steps to uninstall can be found on the [.NET Core Getting Started](https://go.microsoft.com/fwlink/?LinkID=798687) pages and in the [RC1 to RC2 Upgrade Roadmap](RC1-RC2_Upgrade.md).
 
 https://github.com/dotnet/cli/issues/2833
 

release-notes/1.0/RC1-RC2_Upgrade.md

@@ -6,10 +6,7 @@ Due to schedule changes for the .NET Core all-up, there was a rename of the tool
 
 This does not impact RC1 release. Since the tooling and the way you write applications has changed, having DNX (or many of them) installed should not be a problem. However, one caveat is what tooling you are using for what project. For RC2 projects you may get wrong results and/or errors if you try to restore dependencies using `dnu restore`. Please use the appropriate tooling. You can see what are the new commands in the DNX to CLI migration document listed below.
 
-For updating your code, you can check these two documents:
-
-* [Migrating from DNX to CLI](http://dotnet.github.io/docs/core-concepts/dnx-migration.html)
-* [Updating from ASP.NET Core RC1 to RC2]()
+For updating your code, you can check [Migrating from DNX to CLI](https://docs.microsoft.com/dotnet/core/migration/from-dnx).
 
 ## Native installers
 
@@ -43,7 +40,7 @@ Before installing the RC2 bits it is also prudent to check whether you have the
 
 ## OpenSSL and OSX specifics
 
-If you read the [getting started](http://go.microsoft.com/fwlink/?LinkID=798306&clcid=0x409) instructions you will notice that  you need to update OpenSSL to version 1.0.1 or higher. By default, OS X "El Capitan" comes with OpenSSL 0.9.8. To check what version is installed use `openssl verion`. We are giving instructions for updating using Homebrew because that is what we use on the team. MacPorts can be used as well. You can also do it manually.
+If you read the [getting started](https://go.microsoft.com/fwlink/?LinkID=798306&clcid=0x409) instructions you will notice that  you need to update OpenSSL to version 1.0.1 or higher. By default, OS X "El Capitan" comes with OpenSSL 0.9.8. To check what version is installed use `openssl verion`. We are giving instructions for updating using Homebrew because that is what we use on the team. MacPorts can be used as well. You can also do it manually.
 
 What is important is that you have the new version of OpenSSL on the path when you start using the .NET Core RC2. With brew, you can use the `brew link --force openssl` command to relink the OpenSSL. On MacPorts there is no analogue to linking, so you should just uninstall version(s) that are less than 1.0.1. For Mac Ports you can use the following command: `port -f uninstall openssl @0.9.8`.
 

release-notes/1.0/README.md

@@ -1,17 +1,21 @@
-# .NET Core 1.0 Releases
+# .NET Core 1.0 Release -- Out of support
 
-The following .NET Core 1.0 releases have been shipped. You must be on the latest patch release to be [supported by Microsoft](../../microsoft-support.md)
+This release is out of support. See [.NET releases](../../releases.md) for in-support releases.
+
+[.NET Core 1.0](https://devblogs.microsoft.com/dotnet/announcing-net-core-1-0/) was released on June 27th, 2016. The release was a collaborative effort by many [contributors](1.0.0-contributor-list.md). [.NET Core 1.0 reached end of life on June 27th, 2019](https://devblogs.microsoft.com/dotnet/net-core-1-0-and-1-1-will-reach-end-of-life-on-june-27-2019/). It was [supported by Microsoft](../../microsoft-support.md) on [multiple operating systems](1.0-supported-os.md).
+
+Release notes and download information is provided for each update, in the follow table.
 
 | Release Date | Description | |
 | :-- | :-- | :--: |
-| 2019/06/27 | Out of support | [details](https://github.com/dotnet/core/blob/master/microsoft-support.md#out-of-support-net-core-releases) |
+| 2019/06/27 | Out of support |  [.NET Core 1.0 end of life](https://devblogs.microsoft.com/dotnet/net-core-1-0-and-1-1-will-reach-end-of-life-on-june-27-2019/) |
 | 2019/05/14 | 1.0.16 with SDK 1.1.14 | [release notes](1.0.16/1.0.16.md)/[download](1.0.16/1.0.16-download.md) |
 | 2019/03/12 | 1.0.15 with SDK 1.1.13 | [release notes](1.0.15/1.0.15.md)/[download](1.0.15/1.0.15-download.md) |
 | 2019/02/12 | 1.0.14 with SDK 1.1.12 | [release notes](1.0.14/1.0.14.md)/[download](1.0.14/1.0.14-download.md) |
-| 2018/10/09 | 1.0.13 with SDK 1.1.11 | [release notes](1.0.13.md)/[download](../download-archives/1.0.13.md) |
-| 2018/07/10 | 1.0.12 with SDK 1.1.10 | [release notes](1.0.12.md)/[download](../download-archives/1.0.12.md) |
-| 2018/04/17 | 1.0.11 with SDK 1.1.9 | [release notes](1.0.11.md)/[download](../download-archives/1.0.11.md) |
-| 2018/03/13 | 1.0.10 with SDK 1.1.8 | [release notes](1.0.10.md)/[download](../download-archives/1.0.10.md) |
+| 2018/10/09 | 1.0.13 with SDK 1.1.11 | [release notes](1.0.13.md)/[download](../download-archives/1.0.13-download.md) |
+| 2018/07/10 | 1.0.12 with SDK 1.1.10 | [release notes](1.0.12.md)/[download](../download-archives/1.0.12-download.md) |
+| 2018/04/17 | 1.0.11 with SDK 1.1.9 | [release notes](1.0.11.md)/[download](../download-archives/1.0.11-download.md) |
+| 2018/03/13 | 1.0.10 with SDK 1.1.8 | [release notes](1.0.10.md)/[download](../download-archives/1.0.10-download.md) |
 | 2018/01/09 | 1.0.9 with SDK 1.1.7 | [release notes](1.0.9.md)  |
 | 2017/11/14 | 1.0.8 with SDK 1.1.5 | [release notes](1.0.8.md)/[download](../download-archives/1.0.8.md) |
 | 2017/09/21 | 1.0.7 with SDK 1.1.4 | [release notes](1.0.7.md)/[download](../download-archives/1.0.7-download.md) |
@@ -23,6 +27,6 @@ The following .NET Core 1.0 releases have been shipped. You must be on the lates
 | 2016/12/13 | 1.0.3 with SDK Preview 2 build 3156 | [release notes](1.0.3.md)/[download](../download-archives/1.0.3-preview2-download.md) |
 | 2016/10/24 | 1.0.1 with SDK Preview 4 build 4233 | [release notes](1.0.1-release-notes.md)/[download](../download-archives/preview4-download.md) | | [1.0.1 Known Issues](1.0.1-known-issue
 | 2016/10/17 | 1.0.2 with SDK Preview 2 build 3148 | [release notes](https://github.com/dotnet/core/releases/tag/1.0.2)/[download](../download-archives/1.0.2-preview2-download.md) |
-| 2016/10/03 | 1.0.1 with SDK Preview 3 build 4056 | [release notes](https://github.com/dotnet/core/blob/master/release-notes/1.0/1.0.1-release-notes.md)/[download](../download-archives/preview3-download.md) |
-| 2016/09/13 | 1.0.1 with SDK Preview 2 build 3131 and 3133 | [release notes](https://github.com/dotnet/core/blob/master/release-notes/1.0/1.0.1-release-notes.md)/[download](../download-archives/1.0.1-preview2-download.md) |
-| 2016/06/27 | 1.0 with SDK Preview 2 build 3121 | [release notes](https://github.com/dotnet/core/blob/master/release-notes/1.0/1.0.0.md)/[download](../download-archives/1.0-preview2-download.md) | | | [Contributors](1.0.0-contributor-list
+| 2016/10/03 | 1.0.1 with SDK Preview 3 build 4056 | [release notes](https://github.com/dotnet/core/blob/main/release-notes/1.0/1.0.1-release-notes.md)/[download](../download-archives/preview3-download.md) |
+| 2016/09/13 | 1.0.1 with SDK Preview 2 build 3131 and 3133 | [release notes](https://github.com/dotnet/core/blob/main/release-notes/1.0/1.0.1-release-notes.md)/[download](../download-archives/1.0.1-preview2-download.md) |
+| 2016/06/27 | 1.0 with SDK Preview 2 build 3121 | [release notes](https://github.com/dotnet/core/blob/main/release-notes/1.0/1.0.0.md)/[download](../download-archives/1.0-preview2-download.md) | | | [Contributors](1.0.0-contributor-list

release-notes/1.0/Release-Notes-RC1.md

@@ -3,7 +3,7 @@
 ## RC1 released 11/18/2015
 
 Full details on this release can be read about in this blog post:
-[Announcing .NET Core and ASP.NET 5 RC](http://aka.ms/netcorerc)
+[Announcing .NET Core and ASP.NET 5 RC](https://aka.ms/netcorerc)
 
 Supported platforms for this release are Ubuntu 14.04 LTS, OS X 10.10, and Windows 7+.
 

release-notes/1.0/Release-Notes-RC2.md

@@ -3,7 +3,7 @@
 ## RC2 released 5/16/2016
 
 Details on this release can be read about on
-[the .NET Blog](https://blogs.msdn.microsoft.com/dotnet/2016/05/16/announcing-net-core-rc2/) and if you haven't already discovered the updated [.NET Portal](http://go.microsoft.com/fwlink/?LinkID=798306), make that your next destination for getting started with .NET Core.
+[the .NET Blog](https://blogs.msdn.microsoft.com/dotnet/2016/05/16/announcing-net-core-rc2/) and if you haven't already discovered the updated [.NET Portal](https://go.microsoft.com/fwlink/?LinkID=798306), make that your next destination for getting started with .NET Core.
 
 Before installing RC2, please have a look at the [RC1 to RC2 Upgrade Roadmap](RC1-RC2_Upgrade.md). All previous versions of .NET Core and any tooling **must be** removed from the machine in order to properly install and use RC2 release.
 
@@ -37,8 +37,8 @@ A little style note for the rest of this document - any references to 'Unix' enc
 
 ### Introduction of .NET Core API Documentation
 
-* API: http://dotnet.github.io/api/
-* Conceptual: http://dotnet.github.io/docs
+* API: https://docs.microsoft.com/dotnet/api/
+* Conceptual: https://docs.microsoft.com/dotnet/
 
 ### Runtime
 

release-notes/1.0/cli-known-issues.md

@@ -21,9 +21,9 @@ Known issues & workarounds
 # Preview 2 tooling known issues
 
 ## OpenSSL dependency on OS X
-OS X "El Capitan" (10.11) comes with 0.9.8 version of OpenSSL. .NET Core depends on versions >= 1.0.1 of OpenSSL. You can update the version by using [Homebrew](https://brew.sh), [MacPorts](https://www.macports.org/) or manually. The important bit is that you need to have the required OpenSSL version on the path when you work with .NET Core. 
+OS X "El Capitan" (10.11) comes with 0.9.8 version of OpenSSL. .NET Core depends on versions >= 1.0.1 of OpenSSL. You can update the version by using [Homebrew](https://brew.sh), [MacPorts](https://www.macports.org/) or manually. The important bit is that you need to have the required OpenSSL version on the path when you work with .NET Core.
 
-With Homebrew, you can run the following commands to get this done: 
+With Homebrew, you can run the following commands to get this done:
 
 ```console
 brew update
@@ -54,41 +54,41 @@ deprecated system version while using the headers from the Homebrew version.
 Instead, pass the full include/library paths to your compiler e.g.:
   -I/usr/local/opt/openssl/include -L/usr/local/opt/openssl/lib
 ```
-This is due to a recent update from `brew` where it refuses to link `openssl`. The installation steps have been updated with instructions on how to deal with this. 
+This is due to a recent update from `brew` where it refuses to link `openssl`. The installation steps have been updated with instructions on how to deal with this.
 
 ## Users of zsh (z shell) don't get `dotnet` on the path after install
-There is a known issue in oh-my-zsh installer that interferes with how `path_helper` works on OS X systems. In short, 
-the said installer creates a `.zshrc` file which contains the exploded path at the time of installation. This clobbers 
-any dynamically generated path, such as the one generated by `path_helper`. 
+There is a known issue in oh-my-zsh installer that interferes with how `path_helper` works on OS X systems. In short,
+the said installer creates a `.zshrc` file which contains the exploded path at the time of installation. This clobbers
+any dynamically generated path, such as the one generated by `path_helper`.
 
-There is an [outstanding PR](https://github.com/robbyrussell/oh-my-zsh/pull/4925) on the oh-my-zsh repo for this. 
+There is an [outstanding PR](https://github.com/robbyrussell/oh-my-zsh/pull/4925) on the oh-my-zsh repo for this.
 
-**Workaround 1:** symlink the `dotnet` binary in the installation directory to a place in the global path, e.g. `/usr/local/bin`. 
+**Workaround 1:** symlink the `dotnet` binary in the installation directory to a place in the global path, e.g. `/usr/local/bin`.
 The command you can use is:
 
 ```console
 ln -s /usr/local/share/dotnet/dotnet /usr/local/bin
 ```
 
-**Workaround 2:** edit your `.zshrc` and/or `.zshprofile` files to add the `/usr/local/share/dotnet` to the $PATH. 
+**Workaround 2:** edit your `.zshrc` and/or `.zshprofile` files to add the `/usr/local/share/dotnet` to the $PATH.
 
-## `app.config` file needs to be checked out before publishing 
+## `app.config` file needs to be checked out before publishing
 If you have an `app.config` file in source control that places locks on local files (such as TFS), you will receive the following error during publishing:
 
 ```console
 Failed to make the following project runnable: <project name> reason: Access to the path <path> is denied.
 ```
 
-To resolve this, checkout the `app.config` file from the source control prior to publishing. 
+To resolve this, checkout the `app.config` file from the source control prior to publishing.
 
 ## `dotnet` commands in the root of the file system fails
 If you run any `dotnet` command on project and code files that reside in the root of the file system (`/` in Linux/macOS or `C:\` in Windows) it may fail due to security reasons. The most common error that is encountered is:
 
 > Object reference not set to an instance of an object.
 
-This affects the situation where the actual code files are in the root. So, the example path that would trigger this behavior would be `/project.json` or `C:\project.json` on UNIX or Windows respectively. 
+This affects the situation where the actual code files are in the root. So, the example path that would trigger this behavior would be `/project.json` or `C:\project.json` on UNIX or Windows respectively.
 
-**Workaround:** use a directory to store your projects and source files. 
+**Workaround:** use a directory to store your projects and source files.
 
 **More information:** https://github.com/NuGet/Home/issues/3038
 
@@ -110,16 +110,16 @@ When using non-release versions of the CLI, `dotnet restore` will fail to restor
 ```
 
 ## Running `dotnet` on Debian distributions causes a segmentation fault
-If a Debian machine is set in a certain way it may cause the native host (`dotnet`) to produce a segmentation fault. The culprit is the failed installation of the `libicu` dependency due to mirror package repository setup. If you fail to set up mirror package repositories, `apt-get` may not be able to resolve the dependency and the host will fail at runtime. 
+If a Debian machine is set in a certain way it may cause the native host (`dotnet`) to produce a segmentation fault. The culprit is the failed installation of the `libicu` dependency due to mirror package repository setup. If you fail to set up mirror package repositories, `apt-get` may not be able to resolve the dependency and the host will fail at runtime.
 
 **Affects:** the native host
 
-**Workaround:** make sure that all of the [native pre-requisites](../Documentation/prereqs.md) are installed correctly. You can usually do this by running `apt-get` package manager. 
+**Workaround:** make sure that all of the [native pre-requisites](../../Documentation/prereqs.md) are installed correctly. You can usually do this by running `apt-get` package manager.
 
 ## Uninstalling/reinstalling the PKG on OS X
-OS X doesn't really have an uninstall capacity for PKGs like Windows has for 
-MSIs. There is, however, a way to remove the bits as well as the "recipe" for 
-dotnet. More information can be found on [this SuperUser question](http://superuser.com/questions/36567/how-do-i-uninstall-any-apple-pkg-package-file).
+OS X doesn't really have an uninstall capacity for PKGs like Windows has for
+MSIs. There is, however, a way to remove the bits as well as the "recipe" for
+dotnet. More information can be found on [this SuperUser question](https://superuser.com/questions/36567/how-do-i-uninstall-any-apple-pkg-package-file).
 
 # Preview 3 tooling known issues
 
@@ -139,18 +139,18 @@ you don't restore on macOS/Linux machines:
 
 >  /usr/local/share/dotnet/sdk/1.0.0-preview3-004056/Microsoft.Common.CurrentVersion.targets(1107,5): error MSB3644: The reference assemblies for framework ".NETFramework,Version=v4.0" were not found. To resolve this, install the SDK or Targeting Pack for this framework version or retarget your application to a version of the framework for which you have the SDK or Targeting Pack installed. Note that assemblies will be resolved from the Global Assembly Cache (GAC) and will be used in place of reference assemblies. Therefore your assembly may not be correctly targeted for the framework you intend.
 
-If you don't get this error on a Windows machine, that is most likely due to the fact that the targeting pack for .NET Framework 4.0 are installed. To be sure that you have the targets, run restore again if you are not sure. 
+If you don't get this error on a Windows machine, that is most likely due to the fact that the targeting pack for .NET Framework 4.0 are installed. To be sure that you have the targets, run restore again if you are not sure.
 
 ## `dotnet test` has changed from Preview 2 `dotnet test`
 As part of the overall Preview 3 work, `dotnet test` command has been been revised and is quite different in usage and behavior then Preview 2 `dotnet test` command. Please consult the official [dotnet test
-docs](https://docs.microsoft.com/en-us/dotnet/articles/core/preview3/tools/dotnet-test) for more information and expect more documentation in coming days. 
+docs](https://docs.microsoft.com/dotnet/articles/core/preview3/tools/dotnet-test) for more information and expect more documentation in coming days.
 
-# What is this document about? 
-This document outlines the known issues and workarounds for the current state of 
-the CLI tools. Issues will also have a workaround and affects sections if necessary. You can use this page to 
+# What is this document about?
+This document outlines the known issues and workarounds for the current state of
+the CLI tools. Issues will also have a workaround and affects sections if necessary. You can use this page to
 get information and get unblocked.
 
 # What is a "known issue"?
-A "known issue" is a major issue that block users in doing their everyday tasks and that affect all or 
-most of the commands in the CLI tools. If you want to report or see minor issues, you can use the [issues list](https://github.com/dotnet/cli/issues). 
+A "known issue" is a major issue that block users in doing their everyday tasks and that affect all or
+most of the commands in the CLI tools. If you want to report or see minor issues, you can use the [issues list](https://github.com/dotnet/cli/issues).
 

release-notes/1.0/manual-shared-update.md

@@ -9,7 +9,7 @@ Again, this process should be done only in the event that required updates are a
 3. Back up existing files to be updated
 4. Copy new files to the target directory
 
-## Download NuGet packages containing the udpated files ##
+## Download NuGet packages containing the updated files ##
 
 Download the updated CoreCLR and JIT NuGet package which correspond to your system. Links below will download the packages directly.
 
@@ -31,7 +31,7 @@ JIT
 
 ## Rename and Extract ##
 
-If your system doesn't recognize *nupkg files as archives, rename them to *.zip or *.tar.gz and extract the `/runtimes` directory to a temporary location. For CoreCLR there will be `/native` and `/lib/netstandard1.0` directories under `/runtimes`. JIT will have only a `/native` directory. Here's an example of what the tmp location should look like when you are done if the Debian 8 packages were used. The list of binaries will be different for other distros.
+If your system doesn't recognize \*nupkg files as archives, rename them to \*.zip or \*.tar.gz and extract the `/runtimes` directory to a temporary location. For CoreCLR there will be `/native` and `/lib/netstandard1.0` directories under `/runtimes`. JIT will have only a `/native` directory. Here's an example of what the tmp location should look like when you are done if the Debian 8 packages were used. The list of binaries will be different for other distros.
 
 ```
 ~/tmp-update/
@@ -51,7 +51,7 @@ If your system doesn't recognize *nupkg files as archives, rename them to *.zip
 
 ## Back up existing files ##
 
-Since we'll be updating files in-place it's a good idea to make a backup. First you need to locate the `Microsoft.NETCoreApp/1.0.0` directory. If you used the installers for Ubuntu, 1.0.0 will be found under `/usr/share/dotnet/shared/Microsoft.NETCore.App/`. Other distro installations are still manual extraction from archives so it's whereever you copied the directory structure. Something like `/opt/dotnet/shared/Microsoft.NETCore.App` would not be uncommon.
+Since we'll be updating files in-place it's a good idea to make a backup. First you need to locate the `Microsoft.NETCoreApp/1.0.0` directory. If you used the installers for Ubuntu, 1.0.0 will be found under `/usr/share/dotnet/shared/Microsoft.NETCore.App/`. Other distro installations are still manual extraction from archives so it's wherever you copied the directory structure. Something like `/opt/dotnet/shared/Microsoft.NETCore.App` would not be uncommon.
 
 Now that `Microsoft.NETCore.App/1.0.0` has been located, the easiest way to make the backup will be to copy the entire directory which will be updated. `sudo rsync -r 1.0.0/ 1.0.0-backup/` will create the backup directory and copy the entire contents of the source directory.
 

release-notes/1.0/releases.json

@@ -6,7 +6,7 @@
   "latest-sdk": "1.1.14",
   "support-phase": "eol",
   "eol-date": "2019-06-27",
-  "lifecycle-policy": "https://www.microsoft.com/net/support/policy",
+  "lifecycle-policy": "https://dotnet.microsoft.com/platform/support/policy/",
   "releases": [
     {
       "release-date": "2019-05-14",
@@ -26,7 +26,7 @@
           "cve-url": "https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-0981"
         }
       ],
-      "release-notes": "https://github.com/dotnet/core/blob/master/release-notes/1.0/1.0.16/1.0.16.md",
+      "release-notes": "https://github.com/dotnet/core/blob/main/release-notes/1.0/1.0.16/1.0.16.md",
       "runtime": {
         "version": "1.0.16",
         "version-display": "1.0.16",
@@ -244,7 +244,7 @@
           "cve-url": "https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-0757"
         }
       ],
-      "release-notes": "https://github.com/dotnet/core/blob/master/release-notes/1.0/1.0.15/1.0.15.md",
+      "release-notes": "https://github.com/dotnet/core/blob/main/release-notes/1.0/1.0.15/1.0.15.md",
       "runtime": {
         "version": "1.0.15",
         "version-display": "1.0.15",
@@ -455,7 +455,7 @@
           "cve-url": "https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-0657"
         }
       ],
-      "release-notes": "https://github.com/dotnet/core/blob/master/release-notes/1.0/1.0.14/1.0.14.md",
+      "release-notes": "https://github.com/dotnet/core/blob/main/release-notes/1.0/1.0.14/1.0.14.md",
       "runtime": {
         "version": "1.0.14",
         "version-display": "1.0.14",
@@ -678,7 +678,7 @@
           "cve-url": "https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-8292"
         }
       ],
-      "release-notes": "https://github.com/dotnet/core/blob/master/release-notes/1.0/1.0.13.md",
+      "release-notes": "https://github.com/dotnet/core/blob/main/release-notes/1.0/1.0.13.md",
       "runtime": {
         "version": "1.0.13",
         "version-display": null,
@@ -894,7 +894,7 @@
           "cve-url": "https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-8356"
         }
       ],
-      "release-notes": "https://github.com/dotnet/core/blob/master/release-notes/1.0/1.0.12.md",
+      "release-notes": "https://github.com/dotnet/core/blob/main/release-notes/1.0/1.0.12.md",
       "runtime": {
         "version": "1.0.12",
         "version-display": null,
@@ -1059,7 +1059,7 @@
       "release-version": "1.0.11",
       "security": false,
       "cve-list": null,
-      "release-notes": "https://github.com/dotnet/core/blob/master/release-notes/1.0/1.0.11.md",
+      "release-notes": "https://github.com/dotnet/core/blob/main/release-notes/1.0/1.0.11.md",
       "runtime": {
         "version": "1.0.11",
         "version-display": null,
@@ -1203,7 +1203,7 @@
           "cve-url": "https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-0808"
         }
       ],
-      "release-notes": "https://github.com/dotnet/core/blob/master/release-notes/1.0/1.0.10.md",
+      "release-notes": "https://github.com/dotnet/core/blob/main/release-notes/1.0/1.0.10.md",
       "runtime": {
         "version": "1.0.10",
         "version-display": null,
@@ -1343,7 +1343,7 @@
           "cve-url": "https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-0784"
         }
       ],
-      "release-notes": "https://github.com/dotnet/core/blob/master/release-notes/1.0/1.0.9.md",
+      "release-notes": "https://github.com/dotnet/core/blob/main/release-notes/1.0/1.0.9.md",
       "runtime": {
         "version": "1.0.9",
         "version-display": null,
@@ -1473,7 +1473,7 @@
           "cve-url": "https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-11883"
         }
       ],
-      "release-notes": "https://github.com/dotnet/core/blob/master/release-notes/1.0/1.0.8.md",
+      "release-notes": "https://github.com/dotnet/core/blob/main/release-notes/1.0/1.0.8.md",
       "runtime": {
         "version": "1.0.8",
         "version-display": null,
@@ -1595,7 +1595,7 @@
           "cve-url": "https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-8585"
         }
       ],
-      "release-notes": "https://github.com/dotnet/core/blob/master/release-notes/1.0/1.0.7.md",
+      "release-notes": "https://github.com/dotnet/core/blob/main/release-notes/1.0/1.0.7.md",
       "runtime": {
         "version": "1.0.7",
         "version-display": null,
@@ -1730,7 +1730,7 @@
           "cve-url": "https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-0247"
         }
       ],
-      "release-notes": "https://github.com/dotnet/core/blob/master/release-notes/1.0/1.0.5.md",
+      "release-notes": "https://github.com/dotnet/core/blob/main/release-notes/1.0/1.0.5.md",
       "runtime": {
         "version": "1.0.5",
         "version-display": null,
@@ -1865,7 +1865,7 @@
       "release-version": "1.0.4",
       "security": false,
       "cve-list": null,
-      "release-notes": "https://github.com/dotnet/core/blob/master/release-notes/1.0/1.0.4.md",
+      "release-notes": "https://github.com/dotnet/core/blob/main/release-notes/1.0/1.0.4.md",
       "runtime": {
         "version": "1.0.4",
         "version-display": null,
@@ -2018,7 +2018,7 @@
       "release-version": "1.0.3",
       "security": false,
       "cve-list": null,
-      "release-notes": "https://github.com/dotnet/core/blob/master/release-notes/1.0/1.0.3.md",
+      "release-notes": "https://github.com/dotnet/core/blob/main/release-notes/1.0/1.0.3.md",
       "runtime": {
         "version": "1.0.3",
         "version-display": null,
@@ -2228,7 +2228,7 @@
       "release-version": "1.0.1",
       "security": false,
       "cve-list": null,
-      "release-notes": "https://github.com/dotnet/core/blob/master/release-notes/1.0/1.0.1-release-notes.md",
+      "release-notes": "https://github.com/dotnet/core/blob/main/release-notes/1.0/1.0.1-release-notes.md",
       "runtime": {
         "version": "1.0.1",
         "version-display": null,
@@ -2363,7 +2363,7 @@
       "release-version": "1.0.0",
       "security": false,
       "cve-list": null,
-      "release-notes": "https://github.com/dotnet/core/blob/master/release-notes/1.0/1.0.0.md",
+      "release-notes": "https://github.com/dotnet/core/blob/main/release-notes/1.0/1.0.0.md",
       "runtime": {
         "version": "1.0.0",
         "version-display": null,

release-notes/1.0/sdk/1.0-rc3-implicit-package-refs.md

@@ -1,27 +1,27 @@
 ## Implicit metapackage package reference in the .NET Core SDK - Visual Studio 2017 RC3
 While working with the previous versions of the .NET Core tooling (both project.json and csproj-based tools), you  probably have become acquainted with the concept of the "metapackage". It is a dependency/package reference (for example, `Microsoft.NETCore.App` or `NetStandard.Library`) that you add to your project in addition to the target framework (for example, `netcoreapp1.0` or `netstandard1.6`).
 
-During the previous months, we've received a lot of feedback that having two data points in the project file is confusing, especially for the upgrade scenario. For example, if you wanted to upgrade from `netcoreapp1.0` to `netcoreapp1.1`, you had to change the target framework **as well** as change the version of the metapackage. This led many users to errors and weird behaviors. 
+During the previous months, we've received a lot of feedback that having two data points in the project file is confusing, especially for the upgrade scenario. For example, if you wanted to upgrade from `netcoreapp1.0` to `netcoreapp1.1`, you had to change the target framework **as well** as change the version of the metapackage. This led many users to errors and weird behaviors.
 
 As part of the RC3 release of the [.NET Core SDK](https://github.com/dotnet/sdk), we've moved to the model where the SDK implies a certain version of the `Microsoft.NETCore.App` and `NetStandard.Library` metapackages based on the framework you're targeting. This change makes targeting easier. The intent is for developers to target .NET Core or .NET Standard using just the targeted framework. The package is, in this context, a pure implementation detail that the developer doesn't have to worry about.
 
 ### Behavior description
-The metapackage included is tied to the target framework. That means that for `netcoreapp1.0` a proper version of the `Microsoft.NETCore.App` metapackage is referenced. Same goes for `netcoreapp1.1` target framework as well as `netstandard1.x` target frameworks. 
+The metapackage included is tied to the target framework. That means that for `netcoreapp1.0` a proper version of the `Microsoft.NETCore.App` metapackage is referenced. Same goes for `netcoreapp1.1` target framework as well as `netstandard1.x` target frameworks.
 
-As far as the rest of the behavior is concerned, the tools will work as expected and most of the gestures will remain the same (for example, `dotnet restore`). 
+As far as the rest of the behavior is concerned, the tools will work as expected and most of the gestures will remain the same (for example, `dotnet restore`).
 
 ### Migrating a project
 If you have an existing reference to the metapackage in your project.json, the migration (both in `dotnet migrate` as well as Visual Studio 2017) will include that reference in your new csproj project. This will cause the tools to issue the following warning when you try to build your project:
 
 > A PackageReference for [metapackage ID] was included in your project. This package is implicitly referenced by the .NET SDK and you do not typically need to reference it from your project. For more information, see https://aka.ms/sdkimplicitrefs.
 
-This warning simply means that you probably want to remove that package reference from your project file. If you do keep it, the specified version of the metapackage will be used. 
+This warning simply means that you probably want to remove that package reference from your project file. If you do keep it, the specified version of the metapackage will be used.
 
 ## Recommendations
 With this new feature, you might be wondering when you should specify a version of the metapackage in the project and when not. Here is the overall guidance:
 
-* For new projects, you should use the template and not add an explicit reference to any metapackage. 
-* For existing projects, you should remove the reference. 
+* For new projects, you should use the template and not add an explicit reference to any metapackage.
+* For existing projects, you should remove the reference.
 * If you need a specific version of the runtime, you should use the `<RuntimeFrameworkVersion>` property in your project (for example, `1.0.4`) instead of referencing the metapackage.
-    * This might happen if you are using [self-contained deployments](https://docs.microsoft.com/en-us/dotnet/articles/core/preview3/deploying/#self-contained-deployments-scd) and you need a specific patch version of 1.0.0 LTS runtime, for example.
-* If you need a specific version of the `NetStandard.Library` metapackage, you can use the `<NetStandardImplicitPackageVersion>` property and set the version you need. 
+    * This might happen if you are using [self-contained deployments](https://docs.microsoft.com/dotnet/articles/core/preview3/deploying/#self-contained-deployments-scd) and you need a specific patch version of 1.0.0 LTS runtime, for example.
+* If you need a specific version of the `NetStandard.Library` metapackage, you can use the `<NetStandardImplicitPackageVersion>` property and set the version you need.

release-notes/1.1/1.1-known-issues.md

@@ -14,7 +14,7 @@ This is expected behavior. See discussion in [coreclr issue #4318](https://githu
 
 ## .NET Core SDK Preview 3
 
-We're releasing an update to the .NET Core SDK which is available directly in Visual Studio 2017 RC. Please see the [CLI Known Issues](https://github.com/dotnet/core/blob/master/cli/known-issues.md) document for important information about this release.
+We're releasing an update to the .NET Core SDK which is available directly in Visual Studio 2017 RC. Please see the [CLI Known Issues](https://github.com/dotnet/core/blob/main/cli/known-issues.md) document for important information about this release.
 
 Have a look at [Project Json To CSProj](https://github.com/dotnet/cli/blob/rel/1.0.0/Documentation/ProjectJsonToCSProj.md) for details on working with project.json and csproj-based projects.
 

release-notes/1.1/1.1.0-preview1-known-issues.md

@@ -4,7 +4,7 @@ This document lists known issues for *.NET Core 1.1.0 Preview 1* and *.NET Core
 
 ## Previous versions of the Host Resolver are removed
 
-Everything about .NET Core is designed to be side-by-side but there is an issue with the Preview 1 installers which removes previous versions of the Host Resolver (dotnet/host/fxr). The Preview 1 version is compatible with previous releases and you should see no changes in behavior with Preview 1 installed. However, if 1.1 is uninstalled the Host Resolver will be removed and dotnet commands will fail. Re-installing the latest released [.NET Core SDK](https://www.microsoft.com/net/download) will resolve the issue.
+Everything about .NET Core is designed to be side-by-side but there is an issue with the Preview 1 installers which removes previous versions of the Host Resolver (dotnet/host/fxr). The Preview 1 version is compatible with previous releases and you should see no changes in behavior with Preview 1 installed. However, if 1.1 is uninstalled the Host Resolver will be removed and dotnet commands will fail. Re-installing the latest released [.NET Core SDK](https://dotnet.microsoft.com/download) will resolve the issue.
 
 ## Visual Studio unable to find the SDK
 

release-notes/1.1/1.1.0-preview1.md

@@ -2,7 +2,7 @@
 
 ## .NET Core 1.1.0 Preview 1 released 10/24/2016
 
-.NET Core 1.1.0 Preview 1 and SDK 1.0.0 Preview2.1 are available for [download](https://github.com/dotnet/core/blob/master/release-notes/preview-download.md) and testing. Have a look at the [Announcement blog post](https://blogs.msdn.microsoft.com/dotnet/2016/10/25/announcing-net-core-1-1-preview-1/) for details and other good context for the release.
+.NET Core 1.1.0 Preview 1 and SDK 1.0.0 Preview2.1 are available for [download](https://github.com/dotnet/core/blob/main/release-notes/preview-download.md) and testing. Have a look at the [Announcement blog post](https://blogs.msdn.microsoft.com/dotnet/2016/10/25/announcing-net-core-1-1-preview-1/) for details and other good context for the release.
 
 Have a look at [.NET Core 1.1.0 Preview 1 Known Issues](1.1.0-preview1-known-issues.md) document as there are a few things to be aware of before installing.
 
@@ -33,7 +33,7 @@ Changes to the .NET Core API surface are can be seen in the [1.0-1.1-api-diff](1
 
 ### ASP.NET Core
 
-* Please see the [ASP.NET Core release page](https://github.com/aspnet/home/releases/1.1.0-preview1) for details on fixes from ASP.NET Core, MVC, Entitiy Framework Core and others.
+* Please see the [ASP.NET Core release page](https://github.com/aspnet/home/releases/1.1.0-preview1) for details on fixes from ASP.NET Core, MVC, Entity Framework Core and others.
 
 ### Commits for 1.1 Preview 1
 
@@ -41,5 +41,5 @@ Changes to the .NET Core API surface are can be seen in the [1.0-1.1-api-diff](1
 
 ### Contributors
 
-The list of contributors can be found in the [1.1.0 Preview 1 Contributor List](https://github.com/dotnet/core/blob/master/release-notes/1.1/1.1.0-preview1-contibutor-list.md)
+The list of contributors can be found in the [1.1.0 Preview 1 Contributor List](https://github.com/dotnet/core/blob/main/release-notes/1.1/1.1.0-preview1-contibutor-list.md)
 

release-notes/1.1/1.1.1.md

@@ -2,7 +2,7 @@
 
 ## .NET Core March 2017 Update - 1.1.1 Released 3/7/2017
 
-[.NET Core 1.1.1](https://github.com/dotnet/core/blob/master/release-notes/1.1/1.1.1.md) was released today. Both releases include reliability updates to improve the quality of .NET Core. You can download the .NET Core Runtime releases via our [.NET Core Runtimes download page](https://www.microsoft.com/net/download/core#/runtime). If you are looking for the .NET Core SDK, to get the latest tools, try the [.NET Core SDK download page](https://www.microsoft.com/net/download/core#/sdk).
+[.NET Core 1.1.1](https://github.com/dotnet/core/blob/main/release-notes/1.1/1.1.1.md) was released today. Both releases include reliability updates to improve the quality of .NET Core. You can download the .NET Core Runtime releases via our [.NET Core Runtimes download page](https://dotnet.microsoft.com/download/dotnet/current/runtime). If you are looking for the .NET Core SDK, to get the latest tools, try the [.NET Core SDK download page](https://dotnet.microsoft.com/download).
 
 Have a look at the [.NET announcement blog post](https://blogs.msdn.microsoft.com/dotnet/2017/03/07/announcing-net-core-tools-1-0/) for details and great context around the release. Visual Studio 2017 is also releasing today and you can read about it in their [announcement](https://blogs.msdn.microsoft.com/visualstudio/).
 
@@ -10,7 +10,7 @@ Have a look at the [.NET announcement blog post](https://blogs.msdn.microsoft.co
 
 **.NET Core SDK 1.0.0** is releasing with Visual Studio 2017. The [announcement blog](https://blogs.msdn.microsoft.com/dotnet/2017/03/07/announcing-net-core-tools-1-0/) as well as the [RC4 blog post](https://blogs.msdn.microsoft.com/dotnet/2017/02/07/announcing-net-core-tools-updates-in-vs-2017-rc) have great details on what is available in this final release. You can read about the Visual Studio 2017 in their [announcement](https://blogs.msdn.microsoft.com/visualstudio/).
 
-**.NET Core SDK 1.0.1**, available for download from the [.NET Core download page](https://www.microsoft.com/net/core), also includes support for Fedora 24 and OpenSUSE 42.1.
+**.NET Core SDK 1.0.1**, available for download from the [.NET Core download page](https://dotnet.microsoft.com/download), also includes support for Fedora 24 and OpenSUSE 42.1.
 
 ### project.json tools
 

release-notes/1.1/1.1.10.md

@@ -2,7 +2,7 @@
 
 .NET Core 1.1.10 is available for download and usage in your environment.
 
-* [Download .NET Core](https://github.com/dotnet/core/blob/master/release-notes/download-archives/1.1.10-download.md)
+* [Download .NET Core](https://github.com/dotnet/core/blob/main/release-notes/download-archives/1.1.10-download.md)
 
 ## Blog Round up
 
@@ -22,9 +22,9 @@ The [.NET Core Docker images](https://hub.docker.com/r/microsoft/dotnet/) have b
 
 ## .NET Core Lifecycle News
 
-See [.NET Core Supported OS Lifecycle Policy](https://github.com/dotnet/core/blob/master/os-lifecycle-policy.md) to learn about Windows, macOS and Linux versions that are supported for each .NET Core release.
+See [.NET Core Supported OS Lifecycle Policy](https://github.com/dotnet/core/blob/main/os-lifecycle-policy.md) to learn about Windows, macOS and Linux versions that are supported for each .NET Core release.
 
-As .NET Core 2.1 has become LTS (anounced in [August 2018 blog post](https://blogs.msdn.microsoft.com/dotnet/2018/08/21/net-core-august-2018-update)), 1.0 and 1.1 have entered their maintenance phase and will only get critical security fixes going forward till their end of support on June 27, 2019.
+As .NET Core 2.1 has become LTS (announced in [August 2018 blog post](https://blogs.msdn.microsoft.com/dotnet/2018/08/21/net-core-august-2018-update)), 1.0 and 1.1 have entered their maintenance phase and will only get critical security fixes going forward till their end of support on June 27, 2019.
 
 ## Notable Changes in 1.1.10
 

release-notes/1.1/1.1.11/1.1.11-download.md

@@ -5,7 +5,7 @@
 * .NET Core Runtime 1.1.11
 * .NET Core SDK 1.1.12
 
-See the [Release Notes](https://github.com/dotnet/core/blob/master/release-notes/1.1/1.1.11/1.1.11.md) for details about what is included in this update.
+See the [Release Notes](https://github.com/dotnet/core/blob/main/release-notes/1.1/1.1.11/1.1.11.md) for details about what is included in this update.
 
 |           | SDK Installer<sup>1</sup>                                   | SDK Binaries<sup>1</sup>                            | Runtime Installer                                        | Runtime Binaries                                 | ASP.NET Core Runtime           |
 | --------- | :------------------------------------------:     | :----------------------:                 | :---------------------------:                            | :-------------------------:                      | :-----------------:            |
@@ -56,7 +56,7 @@ sudo apt-get install dotnet-sharedframework-microsoft.netcore.app-1.1.11
 
 ## Installation from a binary archive
 
-Installing from the packages detailed above is recommended or you can install from binary archive, if that better suits your needs. When using binary archives to install, the contents must be extracted to a user location such as `$HOME/dotnet`, a symbolic link created for `dotnet` and a few dependencies installed. Dependency requirements can be seen in the [Linux System Prerequisites](https://github.com/dotnet/core/blob/master/Documentation/linux-prereqs.md) document.
+Installing from the packages detailed above is recommended or you can install from binary archive, if that better suits your needs. When using binary archives to install, the contents must be extracted to a user location such as `$HOME/dotnet`, a symbolic link created for `dotnet` and a few dependencies installed. Dependency requirements can be seen in the [Linux System Prerequisites](https://github.com/dotnet/core/blob/main/Documentation/linux-prereqs.md) document.
 
 ```bash
 mkdir -p $HOME/dotnet && tar zxf dotnet.tar.gz -C $HOME/dotnet
@@ -64,7 +64,7 @@ export PATH=$PATH:$HOME/dotnet
 ```
 [blob-runtime]: https://dotnetcli.blob.core.windows.net/dotnet/Runtime/
 [blob-sdk]: https://dotnetcli.blob.core.windows.net/dotnet/Sdk/
-[release-notes]: https://github.com/dotnet/core/blob/master/release-notes/1.1/1.1.11.md
+[release-notes]: https://github.com/dotnet/core/blob/main/release-notes/1.1/1.1.11.md
 
 [dotnet-debian.9-x64.tar.gz]: https://download.visualstudio.microsoft.com/download/pr/e31e3367-6b98-4d1b-9862-a9a63e1c7dc7/88a96cb53c7f01e39e8d3f6d7542921a/dotnet-debian.9-x64.1.1.11.tar.gz
 [dotnet-ubuntu.18.04-x64.tar.gz]: https://download.visualstudio.microsoft.com/download/pr/ad22fcf6-8e22-4a4a-9dc1-8b62196190b3/2a6cb070de5831a13cdff5ec43ceaade/dotnet-ubuntu.18.04-x64.1.1.11.tar.gz
@@ -104,5 +104,5 @@ export PATH=$PATH:$HOME/dotnet
 [checksums-runtime]: https://dotnetcli.blob.core.windows.net/dotnet/checksums/1.1.11-runtime-sha.txt
 [checksums-sdk]: https://dotnetcli.blob.core.windows.net/dotnet/checksums/1.1.12-sdk-sha.txt
 
-[linux-install]: https://www.microsoft.com/net/download/dotnet-core/1.1
-[linux-setup]: https://github.com/dotnet/core/blob/master/Documentation/linux-setup.md
+[linux-install]: https://dotnet.microsoft.com/download/dotnet/1.1
+[linux-setup]: https://github.com/dotnet/core/blob/main/Documentation/linux-setup.md

release-notes/1.1/1.1.11/1.1.11.md

@@ -22,7 +22,7 @@ There are no changes this month in OS version support status.
 
 .NET Core 1.0 and 1.1, which entered "Maintenance" support status when 2.1 was declared LTS, will be end-of-life June 27, 2019. Updates for the 1.0 and 1.1 channels will no longer be offered after that date. See [.NET Core Support Policy](https://dotnet.microsoft.com/platform/support/policy/dotnet-core) to learn more about the .NET Core support lifecycle.
 
-See [.NET Core Supported OS Lifecycle Policy](https://github.com/dotnet/core/blob/master/os-lifecycle-policy.md) to learn about Windows, macOS and Linux versions that are supported for each .NET Core release.
+See [.NET Core Supported OS Lifecycle Policy](https://github.com/dotnet/core/blob/main/os-lifecycle-policy.md) to learn about Windows, macOS and Linux versions that are supported for each .NET Core release.
 
 ## Notable Changes in 1.1.11
 

release-notes/1.1/1.1.12/1.1.12-download.md

@@ -5,7 +5,7 @@
 * .NET Core Runtime 1.1.12
 * .NET Core SDK 1.1.13
 
-See the [Release Notes](https://github.com/dotnet/core/blob/master/release-notes/1.1/1.1.12.md) for details about what is included in this update.
+See the [Release Notes](https://github.com/dotnet/core/blob/main/release-notes/1.1/1.1.12.md) for details about what is included in this update.
 
 |           | SDK Installer<sup>1</sup>                                   | SDK Binaries<sup>1</sup>                            | Runtime Installer                                        | Runtime Binaries                                 | ASP.NET Core Runtime           |
 | --------- | :------------------------------------------:     | :----------------------:                 | :---------------------------:                            | :-------------------------:                      | :-----------------:            |
@@ -56,7 +56,7 @@ sudo apt-get install dotnet-sharedframework-microsoft.netcore.app-1.1.12
 
 ## Installation from a binary archive
 
-Installing from the packages detailed above is recommended or you can install from binary archive, if that better suits your needs. When using binary archives to install, the contents must be extracted to a user location such as `$HOME/dotnet`, a symbolic link created for `dotnet` and a few dependencies installed. Dependency requirements can be seen in the [Linux System Prerequisites](https://github.com/dotnet/core/blob/master/Documentation/linux-prereqs.md) document.
+Installing from the packages detailed above is recommended or you can install from binary archive, if that better suits your needs. When using binary archives to install, the contents must be extracted to a user location such as `$HOME/dotnet`, a symbolic link created for `dotnet` and a few dependencies installed. Dependency requirements can be seen in the [Linux System Prerequisites](https://github.com/dotnet/core/blob/main/Documentation/linux-prereqs.md) document.
 
 ```bash
 mkdir -p $HOME/dotnet && tar zxf dotnet.tar.gz -C $HOME/dotnet
@@ -64,7 +64,7 @@ export PATH=$PATH:$HOME/dotnet
 ```
 [blob-runtime]: https://dotnetcli.blob.core.windows.net/dotnet/Runtime/
 [blob-sdk]: https://dotnetcli.blob.core.windows.net/dotnet/Sdk/
-[release-notes]: https://github.com/dotnet/core/blob/master/release-notes/1.1/1.1.12.md
+[release-notes]: https://github.com/dotnet/core/blob/main/release-notes/1.1/1.1.12.md
 
 [dotnet-centos-x64.tar.gz]: https://download.visualstudio.microsoft.com/download/pr/60439f54-4dd4-4128-8c3e-aaa346e54f63/9eed8f5fae4265f32ab4c859bfcbe720/dotnet-centos-x64.1.1.12.tar.gz
 [dotnet-debian.9-x64.tar.gz]: https://download.visualstudio.microsoft.com/download/pr/4e85cb6b-7a05-4766-b230-372df3ab80b0/6fa4bed7440dda5a10ee961d14c0def3/dotnet-debian.9-x64.1.1.12.tar.gz
@@ -103,7 +103,7 @@ export PATH=$PATH:$HOME/dotnet
 [checksums-runtime]: https://dotnetcli.blob.core.windows.net/dotnet/checksums/1.1.12-runtime-sha.txt
 [checksums-sdk]: https://dotnetcli.blob.core.windows.net/dotnet/checksums/1.1.13-sdk-sha.txt
 
-[linux-install]: https://www.microsoft.com/net/download/dotnet-core/1.1
-[linux-setup]: https://github.com/dotnet/core/blob/master/Documentation/linux-setup.md
+[linux-install]: https://dotnet.microsoft.com/download/dotnet/1.1
+[linux-setup]: https://github.com/dotnet/core/blob/main/Documentation/linux-setup.md
 
 [dotnet-blog]: https://blogs.msdn.microsoft.com/dotnet/2019/03/12/net-core-march-2019/

release-notes/1.1/1.1.12/1.1.12.md

@@ -24,13 +24,13 @@ There are no changes this month in OS version support status.
 
 .NET Core 1.0 and 1.1, which entered "Maintenance" support status when 2.1 was declared LTS, will be end-of-life June 27, 2019. Updates for the 1.0 and 1.1 channels will no longer be offered after that date. See [.NET Core Support Policy](https://dotnet.microsoft.com/platform/support/policy/dotnet-core) to learn more about the .NET Core support lifecycle.
 
-See [.NET Core Supported OS Lifecycle Policy](https://github.com/dotnet/core/blob/master/os-lifecycle-policy.md) to learn about Windows, macOS and Linux versions that are supported for each .NET Core release.
+See [.NET Core Supported OS Lifecycle Policy](https://github.com/dotnet/core/blob/main/os-lifecycle-policy.md) to learn about Windows, macOS and Linux versions that are supported for each .NET Core release.
 
 ## Changes in 1.1.12
 
-* [CVE-2019-0657: .NET Core NuGet Tampering Vulnerability](https://portal.msrc.microsoft.com/en-us/security-guidance/advisory/CVE-2019-0757)
+* [CVE-2019-0657: .NET Core NuGet Tampering Vulnerability](https://msrc.microsoft.com/update-guide/vulnerability/CVE-2019-0757)
 
-    A tampering vulnerability exists in NuGet software when executed in a Linux or Mac environment. An attacker who successfully exploited the vulnerability could run arbitrary code in the context of the current user. If the current user is logged on with administrative user rights, an attacker could take control of the affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights. Exploitation of the vulnerability requires that an attacker can login as any other user on that machine. At that point, the attacker will be able to replace or add to files that were created by a NuGet restore operation in the current users account. 
+    A tampering vulnerability exists in NuGet software when executed in a Linux or Mac environment. An attacker who successfully exploited the vulnerability could run arbitrary code in the context of the current user. If the current user is logged on with administrative user rights, an attacker could take control of the affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights. Exploitation of the vulnerability requires that an attacker can login as any other user on that machine. At that point, the attacker will be able to replace or add to files that were created by a NuGet restore operation in the current users account.
 
     The security update addresses the vulnerability by correcting how NuGet restore creates file permissions for all files extracted to the client machine.
 

release-notes/1.1/1.1.13/1.1.13-download.md

@@ -56,7 +56,7 @@ sudo apt-get install dotnet-sharedframework-microsoft.netcore.app-1.1.13
 
 ## Installation from a binary archive
 
-Installing from the packages detailed above is recommended or you can install from binary archive, if that better suits your needs. When using binary archives to install, the contents must be extracted to a user location such as `$HOME/dotnet`, a symbolic link created for `dotnet` and a few dependencies installed. Dependency requirements can be seen in the [Linux System Prerequisites](https://github.com/dotnet/core/blob/master/Documentation/linux-prereqs.md) document.
+Installing from the packages detailed above is recommended or you can install from binary archive, if that better suits your needs. When using binary archives to install, the contents must be extracted to a user location such as `$HOME/dotnet`, a symbolic link created for `dotnet` and a few dependencies installed. Dependency requirements can be seen in the [Linux System Prerequisites](https://github.com/dotnet/core/blob/main/Documentation/linux-prereqs.md) document.
 
 ```bash
 mkdir -p $HOME/dotnet && tar zxf dotnet.tar.gz -C $HOME/dotnet
@@ -64,7 +64,7 @@ export PATH=$PATH:$HOME/dotnet
 ```
 [blob-runtime]: https://dotnetcli.blob.core.windows.net/dotnet/Runtime/
 [blob-sdk]: https://dotnetcli.blob.core.windows.net/dotnet/Sdk/
-[release-notes]: https://github.com/dotnet/core/blob/master/release-notes/1.1/1.1.13/1.1.13.md
+[release-notes]: https://github.com/dotnet/core/blob/main/release-notes/1.1/1.1.13/1.1.13.md
 
 [dotnet-centos-x64.tar.gz]: https://download.visualstudio.microsoft.com/download/pr/19659750-f708-4f35-99e8-f37e83755f95/971d83ccd6f1bb96b7da341bb4e1e2e4/dotnet-centos-x64.1.1.13.tar.gz
 [dotnet-debian.9-x64.tar.gz]: https://download.visualstudio.microsoft.com/download/pr/70099599-b7e6-425f-a00c-005590a3a880/2bf8884be051ec30b6225116887d3d8e/dotnet-debian.9-x64.1.1.13.tar.gz
@@ -104,7 +104,7 @@ export PATH=$PATH:$HOME/dotnet
 [checksums-runtime]: https://dotnetcli.blob.core.windows.net/dotnet/checksums/1.1.13-runtime-sha.txt
 [checksums-sdk]: https://dotnetcli.blob.core.windows.net/dotnet/checksums/1.1.14-sdk-sha.txt
 
-[linux-install]: https://www.microsoft.com/net/download/dotnet-core/1.1
-[linux-setup]: https://github.com/dotnet/core/blob/master/Documentation/linux-setup.md
+[linux-install]: https://dotnet.microsoft.com/download/dotnet/1.1
+[linux-setup]: https://github.com/dotnet/core/blob/main/Documentation/linux-setup.md
 
 [dotnet-blog]: https://devblogs.microsoft.com/dotnet/net-core-may-2019/

release-notes/1.1/1.1.13/1.1.13.md

@@ -24,11 +24,11 @@ Ubuntu 14.04 reached the [end of standard support April 2019](https://wiki.ubunt
 
 .NET Core 1.0 and 1.1, which entered "Maintenance" support status when 2.1 was declared LTS, will be end-of-life June 27, 2019. Updates for the 1.0 and 1.1 channels will no longer be offered after that date. See [.NET Core Support Policy](https://dotnet.microsoft.com/platform/support/policy/dotnet-core) to learn more about the .NET Core support lifecycle.
 
-See [.NET Core Supported OS Lifecycle Policy](https://github.com/dotnet/core/blob/master/os-lifecycle-policy.md) to learn about Windows, macOS and Linux versions that are supported for each .NET Core release.
+See [.NET Core Supported OS Lifecycle Policy](https://github.com/dotnet/core/blob/main/os-lifecycle-policy.md) to learn about Windows, macOS and Linux versions that are supported for each .NET Core release.
 
 ## Changes in 1.1.13
 
-* [CVE-2019-0820: .NET Core Tampering Vulnerability](https://portal.msrc.microsoft.com/en-us/security-guidance/advisory/CVE-2019-0820)
+* [CVE-2019-0820: .NET Core Tampering Vulnerability](https://msrc.microsoft.com/update-guide/vulnerability/CVE-2019-0820)
 
 Microsoft is releasing this security advisory to provide information about a vulnerability in .NET Core 1.0, 1.1, 2.1 and 2.2. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability.
 
@@ -39,12 +39,12 @@ A remote unauthenticated attacker could exploit this vulnerability by issuing sp
 The update addresses the vulnerability by correcting how .NET Core applications handle RegEx string processing.
 
     **Affected Package and Binary updates**
-    
+
     Package name | Vulnerable versions | Secure versions
     ------------ | ------------------- | -------------------------
     System.Text.RegularExpressions.dll | 4.3.0 | 4.3.1
-    
-* [CVE-2019-0980: ASP.NET Core Denial of Service Vulnerability](https://portal.msrc.microsoft.com/en-us/security-guidance/advisory/CVE-2019-0980)
+
+* [CVE-2019-0980: ASP.NET Core Denial of Service Vulnerability](https://msrc.microsoft.com/update-guide/vulnerability/CVE-2019-0980)
 
 Microsoft is releasing this security advisory to provide information about a vulnerability in .NET Core and ASP.NET Core 1.0, 1.1, 2.1 and 2.2. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability.
 
@@ -59,8 +59,8 @@ The update addresses the vulnerability by correcting how .NET Core and ASP.NET C
     Package name | Vulnerable versions | Secure versions
     ------------ | ------------------- | -------------------------
     System.Private.Uri | 4.3.0, 4.3.1 | 4.3.2
-    
-* [CVE-2019-0981: ASP.NET Core Denial of Service Vulnerability](https://portal.msrc.microsoft.com/en-us/security-guidance/advisory/CVE-2019-0981)
+
+* [CVE-2019-0981: ASP.NET Core Denial of Service Vulnerability](https://msrc.microsoft.com/update-guide/vulnerability/CVE-2019-0981)
 
 Microsoft is releasing this security advisory to provide information about a vulnerability in .NET Core and ASP.NET Core 1.0, 1.1, 2.1 and 2.2. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability.
 

release-notes/1.1/1.1.2.md

@@ -2,11 +2,11 @@
 
 ## .NET Core May 2017 Update - 1.1.2 Released 5/8/2017
 
-This release includes critical security and reliability updates to improve the quality of .NET Core. The latest releases can be found on the [.NET Core download pages](https://www.microsoft.com/net/download/core#/runtime) or from the following.
+This release includes critical security and reliability updates to improve the quality of .NET Core. The latest releases can be found on the [.NET Core download pages](https://dotnet.microsoft.com/download/dotnet/current/runtime) or from the following.
 
-* [.NET Core Runtime 1.0.5](https://github.com/dotnet/core/blob/master/release-notes/download-archives/1.0.5-download.md)
-* [.NET Core Runtime 1.1.2](https://github.com/dotnet/core/blob/master/release-notes/download-archives/1.1.2-download.md)
-* [.NET Core SDK 1.0.4](https://github.com/dotnet/core/blob/master/release-notes/download-archives/1.0.4-sdk-download.md)
+* [.NET Core Runtime 1.0.5](https://github.com/dotnet/core/blob/main/release-notes/download-archives/1.0.5-download.md)
+* [.NET Core Runtime 1.1.2](https://github.com/dotnet/core/blob/main/release-notes/download-archives/1.1.2-download.md)
+* [.NET Core SDK 1.0.4](https://github.com/dotnet/core/blob/main/release-notes/download-archives/1.0.4-sdk-download.md)
 
 The .NET Core SDK 1.0.4 includes .NET Core 1.0.5 and 1.1.2 runtimes so downloading the runtime packages separately is not needed when installing the SDK.
 

release-notes/1.1/1.1.4.md

@@ -4,8 +4,8 @@
 
 ## Downloads
 
-* [.NET Core 1.0.7](https://github.com/dotnet/core/blob/master/release-notes/download-archives/1.0.7-download.md)
-* [.NET Core 1.1.4](https://github.com/dotnet/core/blob/master/release-notes/download-archives/1.1.4-download.md)
+* [.NET Core 1.0.7](https://github.com/dotnet/core/blob/main/release-notes/download-archives/1.0.7-download.md)
+* [.NET Core 1.1.4](https://github.com/dotnet/core/blob/main/release-notes/download-archives/1.1.4-download.md)
 
 After installing the .NET Core SDK 1.1.4, the following command will show that you're running version `1.1.4` of the tools.
 

release-notes/1.1/1.1.5.md

@@ -4,8 +4,8 @@
 
 ## Downloads
 
-* [.NET Core 1.0.8](https://github.com/dotnet/core/blob/master/release-notes/download-archives/1.0.8.md)
-* [.NET Core 1.1.5](https://github.com/dotnet/core/blob/master/release-notes/download-archives/1.1.5.md)
+* [.NET Core 1.0.8](https://github.com/dotnet/core/blob/main/release-notes/download-archives/1.0.8.md)
+* [.NET Core 1.1.5](https://github.com/dotnet/core/blob/main/release-notes/download-archives/1.1.5.md)
 
 After installing the .NET Core SDK 1.1.5, the following command will show that you're running version `1.1.5` of the tools.
 

release-notes/1.1/1.1.6.md

@@ -5,8 +5,8 @@ Microsoft is releasing security advisories for .NET Core and ASP.NET Core. Issue
 .NET Core 1.1.6 and SDK 1.1.7 are available for download and usage in your environment.
 
 * [Announcement](https://blogs.msdn.microsoft.com/)
-* [Getting Started](https://www.microsoft.com/net/core/)
-* [Downloads](https://github.com/dotnet/core/blob/master/release-notes/download-archives/2.0.5-download.md)
+* [Getting Started](https://dotnet.microsoft.com/download)
+* [Downloads](https://github.com/dotnet/core/blob/main/release-notes/download-archives/2.0.5-download.md)
 
 The .NET Core SDK 1.1.7 includes .NET Core 1.1.6 Runtime so downloading the runtime packages separately is not needed when installing the SDK. After installing the .NET Core SDK 1.1.7, the following command will show that you're running version `1.1.7` of the tools.
 

release-notes/1.1/1.1.7.md

@@ -4,8 +4,8 @@ Microsoft is releasing security advisories for .NET Core and ASP.NET Core. Issue
 
 .NET Core 1.1.7 and SDK 1.1.8 are available for download and usage in your environment.
 
-* [Getting Started](https://www.microsoft.com/net/core/)
-* [Downloads](https://github.com/dotnet/core/blob/master/release-notes/download-archives/1.1.7-download.md)
+* [Getting Started](https://dotnet.microsoft.com/download)
+* [Downloads](https://github.com/dotnet/core/blob/main/release-notes/download-archives/1.1.7-download.md)
 
 The .NET Core SDK 1.1.8 includes .NET Core 1.1.7 Runtime so downloading the runtime packages separately is not needed when installing the SDK. After installing the .NET Core SDK 1.1.8, the following command will show that you're running version `1.1.8` of the tools.
 

release-notes/1.1/1.1.8.md

@@ -4,8 +4,8 @@ Microsoft is releasing updates for .NET Core and ASP.NET Core. Issues addressed
 
 .NET Core 1.1.8 and SDK 1.1.9 are available for download and usage in your environment.
 
-* [Getting Started](https://www.microsoft.com/net/core/)
-* [Downloads](https://github.com/dotnet/core/blob/master/release-notes/download-archives/1.1.8-download.md)
+* [Getting Started](https://dotnet.microsoft.com/download)
+* [Downloads](https://github.com/dotnet/core/blob/main/release-notes/download-archives/1.1.8-download.md)
 
 The .NET Core SDK 1.1.9 includes .NET Core 1.1.8 Runtime so downloading the runtime packages separately is not needed when installing the SDK. After installing the .NET Core SDK 1.1.9, the following command will show that you're running version `1.1.9` of the tools.
 

release-notes/1.1/1.1.9.md

@@ -2,7 +2,7 @@
 
 .NET Core 1.1.9 is available for download and usage in your environment.
 
-* [Download .NET Core](https://github.com/dotnet/core/blob/master/release-notes/download-archives/1.1.9-download.md)
+* [Download .NET Core](https://github.com/dotnet/core/blob/main/release-notes/download-archives/1.1.9-download.md)
 
 ## Blog Round up
 
@@ -22,7 +22,7 @@ The [.NET Core Docker images](https://hub.docker.com/r/microsoft/dotnet/) have b
 
 ## .NET Core Lifecycle News
 
-See [.NET Core Supported OS Lifecycle Policy](https://github.com/dotnet/core/blob/master/os-lifecycle-policy.md) to learn about Windows, macOS and Linux versions that are supported for each .NET Core release.
+See [.NET Core Supported OS Lifecycle Policy](https://github.com/dotnet/core/blob/main/os-lifecycle-policy.md) to learn about Windows, macOS and Linux versions that are supported for each .NET Core release.
 
 .NET Core 2.1 is expected to be declared LTS in the next few months. It is recommended that 2.1 be the default target for projects. .NET Core 2.0 will go out of support October 2018.
 

release-notes/1.1/1.1.md

@@ -2,7 +2,7 @@
 
 ## .NET Core 1.1 released 11/16/2016
 
-.NET Core 1.1 and SDK 1.0.0 Preview 2.1 are available for download from our freshly revamped [site](https://www.microsoft.com/net/core). Have a look at the [Announcement blog post](https://blogs.msdn.microsoft.com/dotnet/) for details and great context around the release.
+.NET Core 1.1 and SDK 1.0.0 Preview 2.1 are available for download from our freshly revamped [site](https://dotnet.microsoft.com/download). Have a look at the [Announcement blog post](https://blogs.msdn.microsoft.com/dotnet/) for details and great context around the release.
 
 The [.NET Core 1.1 Known Issues](1.1-known-issues.md) document covers a few things to be aware of before installing.
 
@@ -49,4 +49,4 @@ The great work included in .NET Core 1.1 can be seen in the [1.1 commits](1.1-co
 
 ### Contributors
 
-The list of contributors can be found in the [1.1 Contributor List](https://github.com/dotnet/core/blob/master/release-notes/1.1/1.1-contributor-list.md).
+The list of contributors can be found in the [1.1 Contributor List](https://github.com/dotnet/core/blob/main/release-notes/1.1/1.1-contributor-list.md).

release-notes/1.1/README.md

@@ -1,10 +1,14 @@
-# .NET Core 1.1 Releases
+# .NET Core 1.1 Releases -- Out of support
 
-The following .NET Core 1.1 releases have been shipped. You must be on the latest patch release to be [supported by Microsoft](../../microsoft-support.md)
+This release is out of support. See [.NET releases](../../releases.md) for in-support releases.
+
+[.NET Core 1.1](https://devblogs.microsoft.com/dotnet/announcing-net-core-1-1/) was released on November 16th, 2016. The release was a collaborative effort by many [contributors](1.1-contributor-list.md). [.NET Core 1.1 reached end of life on June 27th, 2019](https://devblogs.microsoft.com/dotnet/net-core-1-0-and-1-1-will-reach-end-of-life-on-june-27-2019/). It was [supported by Microsoft](../../microsoft-support.md) on [multiple operating systems](1.1-supported-os.md).
+
+Release notes and download information is provided for each update, in the follow table.
 
 | Release Date | Description | Commits | Known Issues | Contributors |
 | :-- | :-- | :--: | :--: | :--: |
-| 2019/06/27 | Out of support - see [details](https://github.com/dotnet/core/blob/master/microsoft-support.md#out-of-support-net-core-releases) | - | - | - |
+| 2019/06/27 | [.NET Core 1.1 end of life](https://devblogs.microsoft.com/dotnet/net-core-1-0-and-1-1-will-reach-end-of-life-on-june-27-2019/) | - | - | - |
 | 2019/05/14 | 1.1.13 with SDK 1.1.14 ([release notes](1.1.13/1.1.13.md) / [download](1.1.13/1.1.13-download.md)) | see release notes | - | - |
 | 2019/03/12 | 1.1.12 with SDK 1.1.13 ([release notes](1.1.12/1.1.12.md) / [download](1.1.12/1.1.12-download.md)) | see release notes | - | - |
 | 2019/02/12 | 1.1.11 with SDK 1.1.12 ([release notes](1.1.11/1.1.11.md) / [download](1.1.11/1.1.11-download.md)) | see release notes | - | - |

release-notes/1.1/releases.json

@@ -6,7 +6,7 @@
   "latest-sdk": "1.1.14",
   "support-phase": "eol",
   "eol-date": "2019-06-27",
-  "lifecycle-policy": "https://www.microsoft.com/net/support/policy",
+  "lifecycle-policy": "https://dotnet.microsoft.com/platform/support/policy/",
   "releases": [
     {
       "release-date": "2019-05-14",
@@ -26,7 +26,7 @@
           "cve-url": "https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-0981"
         }
       ],
-      "release-notes": "https://github.com/dotnet/core/blob/master/release-notes/1.1/1.1.13/1.1.13.md",
+      "release-notes": "https://github.com/dotnet/core/blob/main/release-notes/1.1/1.1.13/1.1.13.md",
       "runtime": {
         "version": "1.1.13",
         "version-display": "1.1.13",
@@ -130,8 +130,8 @@
         "runtime-version": "1.1.13",
         "vs-version": "15.0",
         "vs-support": null,
-        "csharp-version": null,
-        "fsharp-version": null,
+        "csharp-version": "",
+        "fsharp-version": "",
         "vb-version": null,
         "files": [
           {
@@ -274,7 +274,7 @@
           "cve-url": "https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-0757"
         }
       ],
-      "release-notes": "https://github.com/dotnet/core/blob/master/release-notes/1.1/1.1.12/1.1.12.md",
+      "release-notes": "https://github.com/dotnet/core/blob/main/release-notes/1.1/1.1.12/1.1.12.md",
       "runtime": {
         "version": "1.1.12",
         "version-display": "1.1.12",
@@ -377,8 +377,8 @@
         "version-display": "1.1.13",
         "runtime-version": "1.1.12",
         "vs-version": "15.0.22",
-        "csharp-version": null,
-        "fsharp-version": null,
+        "csharp-version": "",
+        "fsharp-version": "",
         "vb-version": "15.0",
         "files": [
           {
@@ -515,7 +515,7 @@
           "cve-url": "https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-0657"
         }
       ],
-      "release-notes": "https://github.com/dotnet/core/blob/master/release-notes/1.1/1.1.11/1.1.11.md",
+      "release-notes": "https://github.com/dotnet/core/blob/main/release-notes/1.1/1.1.11/1.1.11.md",
       "runtime": {
         "version": "1.1.11",
         "version-display": "1.1.11",
@@ -612,8 +612,8 @@
         "version-display": "1.1.12",
         "runtime-version": "1.1.11",
         "vs-version": "15.0",
-        "csharp-version": null,
-        "fsharp-version": null,
+        "csharp-version": "",
+        "fsharp-version": "",
         "vb-version": "15.0",
         "files": [
           {
@@ -756,7 +756,7 @@
           "cve-url": "https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-8292"
         }
       ],
-      "release-notes": "https://github.com/dotnet/core/blob/master/release-notes/1.1/1.1.10.md",
+      "release-notes": "https://github.com/dotnet/core/blob/main/release-notes/1.1/1.1.10.md",
       "runtime": {
         "version": "1.1.10",
         "version-display": "1.1.10",
@@ -882,7 +882,7 @@
         "version": "1.1.11",
         "version-display": "1.1.11",
         "runtime-version": "1.1.10",
-        "vs-version": null,
+        "vs-version": "",
         "csharp-version": null,
         "fsharp-version": null,
         "vb-version": null,
@@ -1015,7 +1015,7 @@
           "cve-url": "https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-8356"
         }
       ],
-      "release-notes": "https://github.com/dotnet/core/blob/master/release-notes/1.1/1.1.9.md",
+      "release-notes": "https://github.com/dotnet/core/blob/main/release-notes/1.1/1.1.9.md",
       "runtime": {
         "version": "1.1.9",
         "version-display": "1.1.9",
@@ -1117,7 +1117,7 @@
         "version": "1.1.10",
         "version-display": "1.1.10",
         "runtime-version": "1.1.9",
-        "vs-version": null,
+        "vs-version": "",
         "csharp-version": null,
         "fsharp-version": null,
         "vb-version": null,
@@ -1235,7 +1235,7 @@
       "release-version": "1.1.8",
       "security": false,
       "cve-list": null,
-      "release-notes": "https://github.com/dotnet/core/blob/master/release-notes/1.1/1.1.8.md",
+      "release-notes": "https://github.com/dotnet/core/blob/main/release-notes/1.1/1.1.8.md",
       "runtime": {
         "version": "1.1.8",
         "version-display": "1.1.8",
@@ -1410,7 +1410,7 @@
           "cve-url": "https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-0808"
         }
       ],
-      "release-notes": "https://github.com/dotnet/core/blob/master/release-notes/1.1/1.1.7.md",
+      "release-notes": "https://github.com/dotnet/core/blob/main/release-notes/1.1/1.1.7.md",
       "runtime": {
         "version": "1.1.7",
         "version-display": "1.1.7",
@@ -1482,7 +1482,7 @@
         "version": "1.1.8",
         "version-display": "1.1.8",
         "runtime-version": "1.1.7",
-        "vs-version": null,
+        "vs-version": "",
         "csharp-version": null,
         "fsharp-version": null,
         "vb-version": null,
@@ -1583,7 +1583,7 @@
           "cve-url": "https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-0784"
         }
       ],
-      "release-notes": "https://github.com/dotnet/core/blob/master/release-notes/1.1/1.1.6.md",
+      "release-notes": "https://github.com/dotnet/core/blob/main/release-notes/1.1/1.1.6.md",
       "runtime": {
         "version": "1.1.6",
         "version-display": "1.1.6",
@@ -1655,7 +1655,7 @@
         "version": "1.1.7",
         "version-display": "1.1.7",
         "runtime-version": "1.1.6",
-        "vs-version": null,
+        "vs-version": "",
         "csharp-version": null,
         "fsharp-version": null,
         "vb-version": null,
@@ -1822,7 +1822,7 @@
         "version": "1.1.5",
         "version-display": "1.1.5",
         "runtime-version": "1.1.5",
-        "vs-version": null,
+        "vs-version": "",
         "csharp-version": null,
         "fsharp-version": null,
         "vb-version": null,
@@ -1890,7 +1890,7 @@
           "cve-url": "https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-8585"
         }
       ],
-      "release-notes": "https://github.com/dotnet/core/blob/master/release-notes/1.1/1.1.4.md",
+      "release-notes": "https://github.com/dotnet/core/blob/main/release-notes/1.1/1.1.4.md",
       "runtime": {
         "version": "1.1.4",
         "version-display": "1.1.4",
@@ -1950,7 +1950,7 @@
         "version": "1.1.4",
         "version-display": "1.1.4",
         "runtime-version": "1.1.4",
-        "vs-version": null,
+        "vs-version": "",
         "csharp-version": null,
         "fsharp-version": null,
         "vb-version": null,
@@ -2031,7 +2031,7 @@
           "cve-url": "https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-0247"
         }
       ],
-      "release-notes": "https://github.com/dotnet/core/blob/master/release-notes/1.1/1.1.2.md",
+      "release-notes": "https://github.com/dotnet/core/blob/main/release-notes/1.1/1.1.2.md",
       "runtime": {
         "version": "1.1.2",
         "version-display": "1.1.2",
@@ -2202,7 +2202,7 @@
       "release-version": "1.1.1",
       "security": false,
       "cve-list": null,
-      "release-notes": "https://github.com/dotnet/core/blob/master/release-notes/1.1/1.1.1.md",
+      "release-notes": "https://github.com/dotnet/core/blob/main/release-notes/1.1/1.1.1.md",
       "runtime": {
         "version": "1.1.1",
         "version-display": "1.1.1",
@@ -2286,7 +2286,7 @@
         "version": "1.0.1",
         "version-display": "1.0.1",
         "runtime-version": "1.1.1",
-        "vs-version": null,
+        "vs-version": "",
         "csharp-version": null,
         "fsharp-version": null,
         "vb-version": null,
@@ -2373,7 +2373,7 @@
       "release-version": "1.1.0",
       "security": false,
       "cve-list": null,
-      "release-notes": "https://github.com/dotnet/core/blob/master/release-notes/1.1/1.1.md",
+      "release-notes": "https://github.com/dotnet/core/blob/main/release-notes/1.1/1.1.md",
       "runtime": {
         "version": "1.1.0",
         "version-display": "1.1.0",
@@ -2457,7 +2457,7 @@
         "version": "1.0.0-preview2.1-003177",
         "version-display": "1.0.0-preview2",
         "runtime-version": "1.1.0",
-        "vs-version": null,
+        "vs-version": "",
         "csharp-version": null,
         "fsharp-version": null,
         "vb-version": null,
@@ -2540,4 +2540,4 @@
       "symbols": null
     }
   ]
-}
+}

release-notes/2.0/2.0-supported-os.md

@@ -18,7 +18,7 @@ Windows Client                | 7 SP1+, 8.1                  | x64, x86       |
 Windows 10 Client             | Version 1607+                 | x64, x86       |
 Windows Server                | 2008 R2 SP1+                  | x64, x86       |
 
-See the [Windows Lifecycle Fact Sheet](https://support.microsoft.com/en-us/help/13853/windows-lifecycle-fact-sheet) for details regarding each Windows release lifecycle.
+See the [Windows Lifecycle Fact Sheet](https://support.microsoft.com/help/13853/windows-lifecycle-fact-sheet) for details regarding each Windows release lifecycle.
 
 ## macOS
 
@@ -30,8 +30,8 @@ Mac OS X                      | 10.12+                        | x64            |
 
 OS                            | Version                       | Architectures  | Notes
 ------------------------------|-------------------------------|----------------|-----
-Red Hat Enterprise Linux      | 6                             | x64            | [Microsoft support policy](https://www.microsoft.com/net/support/policy) 
-Red Hat Enterprise Linux <br> CentOS <br> Oracle Linux     | 7                             | x64            | [Red Hat support policy](https://access.redhat.com/support/policy/updates/errata/) <br> [CentOS lifecycle](https://wiki.centos.org/FAQ/General#head-fe8a0be91ee3e7dea812e8694491e1dde5b75e6d) <br> [Oracle Linux lifecycle](http://www.oracle.com/us/support/library/elsp-lifetime-069338.pdf)
+Red Hat Enterprise Linux      | 6                             | x64            | [Microsoft support policy](https://dotnet.microsoft.com/platform/support/policy/)
+Red Hat Enterprise Linux <br> CentOS <br> Oracle Linux     | 7                             | x64            | [Red Hat support policy](https://access.redhat.com/support/policy/updates/errata/) <br> [CentOS lifecycle](https://wiki.centos.org/FAQ/General#head-fe8a0be91ee3e7dea812e8694491e1dde5b75e6d) <br> [Oracle Linux lifecycle](https://www.oracle.com/a/ocom/docs/elsp-lifetime-069338.pdf)
 Fedora                        | 28, 27                | x64            | [Fedora lifecycle](https://fedoraproject.org/wiki/End_of_life)
 Debian                        | 9, 8.7+                   | x64            | [Debian lifecycle](https://wiki.debian.org/DebianReleases)
 Ubuntu                        | 18.04, 16.04, 14.04       | x64            | [Ubuntu lifecycle](https://wiki.ubuntu.com/Releases)
@@ -44,7 +44,7 @@ SUSE Enterprise Linux (SLES)  | 12 SP2+                   | x64            | [SU
 
 ## Out of support OS versions
 
-Support for the following versions was ended by the distribution owners and are [not supported by .NET Core 2](https://github.com/dotnet/core/blob/master/os-lifecycle-policy.md).
+Support for the following versions was ended by the distribution owners and are [not supported by .NET Core 2](https://github.com/dotnet/core/blob/main/os-lifecycle-policy.md).
 
 OS         | Version  | End of Life | Supported Version
 -----------|----------|-------------|------------------

release-notes/2.0/2.0.0-preview1.md

@@ -2,7 +2,7 @@
 
 ## .NET Core 2.0.0 Preview 1 released 5/10/2017
 
-.NET Core 2.0.0 Preview 1 and SDK 2.0.0 Preview 1 are available for download and testing. These can be found on [.NET Core Preview 1](https://www.microsoft.com/net/core/preview) or the [Preview 1 download page](https://github.com/dotnet/core/blob/master/release-notes/download-archives/2.0.0-preview1-download.md).
+.NET Core 2.0.0 Preview 1 and SDK 2.0.0 Preview 1 are available for download and testing. These can be found on [.NET Core Preview 1](https://dotnet.microsoft.com/download/dotnet) or the [Preview 1 download page](https://github.com/dotnet/core/blob/main/release-notes/download-archives/2.0.0-preview1-download.md).
 
 The .NET Core SDK 2.0.0-Preview 1 includes .NET Core 2.0.0-Preview 1 runtime so downloading the runtime packages separately is not needed when installing the SDK.
 
@@ -22,7 +22,7 @@ You can visit the following locations to learn more about .NET Standard.
 
 ### Linux Binaries
 
-The 'generic' Linux binary archives are new for the 2.0 release. This package contains binaries which are compatible with [Linux distros and versions supported by .NET Core](https://github.com/dotnet/core/blob/master/roadmap.md). This will also enable you to experiment with Distros not present on the supported list but are libc compatible.
+The 'generic' Linux binary archives are new for the 2.0 release. This package contains binaries which are compatible with [Linux distros and versions supported by .NET Core](https://github.com/dotnet/core/blob/main/roadmap.md). This will also enable you to experiment with Distros not present on the supported list but are libc compatible.
 
 ### OpenSSL is no longer needed on OSX
 

release-notes/2.0/2.0.0-preview2-known-issues.md

@@ -18,13 +18,13 @@ When referencing a NETStandard2.0 library from a .NETFramework application you m
 
 ## .NET Core 2.0 and Visual Studio 2017 15.3 Preview
 
-[https://github.com/aspnet/Tooling/blob/master/known-issues-vs2017-preview.md](https://github.com/aspnet/Tooling/blob/master/known-issues-vs2017-preview.md)
+<https://github.com/aspnet/Tooling/blob/master/known-issues-vs2017-preview.md>
 
 ## Preview 1 issues which have been resolved
 
 ### Running 1.0 first run experience after installing 2.0 CLI
 
-[https://github.com/dotnet/cli/issues/6550](https://github.com/dotnet/cli/issues/6550)
+<https://github.com/dotnet/cli/issues/6550>
 
 This fails because the 1.0 first run shells out two dotnet commands to do dotnet new and dotnet restore. Because this is a simple shell out, the 2.0 CLI ends up being picked up to execute the commands. However, in the 1.0 CLI, we invoke dotnet new passing –f netcoreapp1.0 and netcoreapp1.1 and the 2.0 CLI no longer carries these templates, which causes the command and the whole first run to fail.
 

release-notes/2.0/2.0.0-preview2.md

@@ -2,8 +2,8 @@
 
 .NET Core 2.0.0 Preview 2 and SDK 2.0.0 Preview 2 are available for download and testing.
 
-* [Getting Started](https://www.microsoft.com/net/core/preview)
-* [Downloads](https://github.com/dotnet/core/blob/master/release-notes/download-archives/2.0.0-preview2-download.md)
+* [Getting Started](https://dotnet.microsoft.com/download/dotnet)
+* [Downloads](https://github.com/dotnet/core/blob/main/release-notes/download-archives/2.0.0-preview2-download.md)
 
 The .NET Core SDK 2.0.0 Preview 2 includes .NET Core 2.0.0 Preview 2 Runtime so downloading the runtime packages separately is not needed when installing the SDK. After installing the .NET Core SDK 2.0.0 Preview 2, the following command will show that you're running version `2.0.0-preview2-006497` of the tools.
 

release-notes/2.0/2.0.0.md

@@ -4,8 +4,8 @@
 
 .NET Core 2.0.0 and SDK 2.0.0 are available for download and testing.
 
-* [Getting Started](https://www.microsoft.com/net/core/)
-* [Downloads](https://github.com/dotnet/core/blob/master/release-notes/download-archives/2.0.0-download.md)
+* [Getting Started](https://dotnet.microsoft.com/download)
+* [Downloads](https://github.com/dotnet/core/blob/main/release-notes/download-archives/2.0.0-download.md)
 
 The blog roundup
 
@@ -62,7 +62,7 @@ Because the Runtime Package Store contains crossgen'ed files for a specific rele
 
 ### Support
 
-.NET Core 2.0 is being released as a 'current' release. See the [.NET Core support document](https://github.com/dotnet/core/blob/master/microsoft-support.md) for details on release types. We have also posted [OS Lifecycle Support Policy](https://github.com/dotnet/core/blob/master/os-lifecycle-policy.md) detailing OS version policies.
+.NET Core 2.0 is being released as a 'current' release. See the [.NET Core support document](https://github.com/dotnet/core/blob/main/microsoft-support.md) for details on release types. We have also posted [OS Lifecycle Support Policy](https://github.com/dotnet/core/blob/main/os-lifecycle-policy.md) detailing OS version policies.
 
 ### WCF
 

release-notes/2.0/2.0.3.md

@@ -3,8 +3,8 @@
 .NET Core 2.0.3 and SDK 2.0.3 are available for download and usage in your environment.
 
 * [Announcement](https://blogs.msdn.microsoft.com/dotnet/2017/11/14/net-core-november-2017-update/)
-* [Getting Started](https://www.microsoft.com/net/core/)
-* [Downloads](https://github.com/dotnet/core/blob/master/release-notes/download-archives/2.0.3.md)
+* [Getting Started](https://dotnet.microsoft.com/download)
+* [Downloads](https://github.com/dotnet/core/blob/main/release-notes/download-archives/2.0.3.md)
 
 The .NET Core SDK 2.0.3 includes .NET Core 2.0.3 Runtime so downloading the runtime packages separately is not needed when installing the SDK. After installing the .NET Core SDK 2.0.3, the following command will show that you're running version `2.0.3` of the tools.
 
@@ -38,7 +38,7 @@ Microsoft is aware of a security vulnerability in ASP.NET Core 1.0, 1.1 and 2.0
 
 ### RHEL 6 support
 
-[Runtime tarballs](http://download.microsoft.com/download/5/C/1/5C190037-632B-443D-842D-39085F02E1E8/dotnet-runtime-2.0.3-rhel.6-x64.tar.gz) are now available for use on Red Hat Enterprise Linux 6.
+[Runtime tarballs](https://download.microsoft.com/download/5/C/1/5C190037-632B-443D-842D-39085F02E1E8/dotnet-runtime-2.0.3-rhel.6-x64.tar.gz) are now available for use on Red Hat Enterprise Linux 6.
 
 ### Docker Images
 

release-notes/2.0/2.0.4.md

@@ -2,8 +2,8 @@
 
 .NET Core 2.0.4 and SDK 2.1.3 are available for download and usage in your environment.
 
-* [Getting Started](https://www.microsoft.com/net/core/)
-* [Downloads](https://github.com/dotnet/core/blob/master/release-notes/download-archives/2.0.4-download.md)
+* [Getting Started](https://dotnet.microsoft.com/download)
+* [Downloads](https://github.com/dotnet/core/blob/main/release-notes/download-archives/2.0.4-download.md)
 
 The .NET Core SDK 2.1.3 includes .NET Core 2.0.4 Runtime so downloading the runtime packages separately is not needed when installing the SDK. After installing the .NET Core SDK 2.1.3, the following command will show that you're running version `2.0.4` of the tools.
 

release-notes/2.0/2.0.5.md

@@ -5,8 +5,8 @@ Microsoft is releasing security advisories for .NET Core and ASP.NET Core. Issue
 .NET Core 2.0.5 and SDK 2.1.4 are available for download and usage in your environment.
 
 * [Announcement](https://blogs.msdn.microsoft.com/dotnet/2018/01/09/net-core-january-2018-update/)
-* [Getting Started](https://www.microsoft.com/net/core/)
-* [Downloads](https://github.com/dotnet/core/blob/master/release-notes/download-archives/2.0.5-download.md)
+* [Getting Started](https://dotnet.microsoft.com/download)
+* [Downloads](https://github.com/dotnet/core/blob/main/release-notes/download-archives/2.0.5-download.md)
 
 The .NET Core SDK 2.1.4 includes .NET Core 2.0.5 Runtime so downloading the runtime packages separately is not needed when installing the SDK. After installing the .NET Core SDK 2.1.4, the following command will show that you're running version `2.1.4` of the tools.
 

release-notes/2.0/2.0.6.md

@@ -4,8 +4,8 @@ Microsoft is releasing security advisories for .NET Core and ASP.NET Core. Issue
 
 .NET Core 2.0.6 and SDK 2.1.101 are available for download and usage in your environment.
 
-* [Getting Started](https://www.microsoft.com/net/core/)
-* [Downloads](https://github.com/dotnet/core/blob/master/release-notes/download-archives/2.0.6-download.md)
+* [Getting Started](https://dotnet.microsoft.com/download)
+* [Downloads](https://github.com/dotnet/core/blob/main/release-notes/download-archives/2.0.6-download.md)
 
 The .NET Core SDK 2.1.101 includes .NET Core 2.0.6 Runtime so downloading the runtime packages separately is not needed when installing the SDK. After installing the .NET Core SDK 2.1.101, the following command will show that you're running version `2.1.101` of the tools.
 

release-notes/2.0/2.0.7.md

@@ -4,8 +4,8 @@ Microsoft is releasing updates for .NET Core and ASP.NET Core. Issues addressed
 
 .NET Core 2.0.7 and SDK 2.1.105 are available for download and usage in your environment.
 
-* [Getting Started](https://www.microsoft.com/net/core/)
-* [Downloads](https://github.com/dotnet/core/blob/master/release-notes/download-archives/2.0.7-download.md)
+* [Getting Started](https://dotnet.microsoft.com/download)
+* [Downloads](https://github.com/dotnet/core/blob/main/release-notes/download-archives/2.0.7-download.md)
 
 The .NET Core SDK 2.1.105 includes .NET Core 2.0.7 Runtime so downloading the runtime packages separately is not needed when installing the SDK. After installing the .NET Core SDK 2.1.105, the following command will show that you're running version `2.1.105` of the tools.
 

release-notes/2.0/2.0.9.md

@@ -2,7 +2,7 @@
 
 .NET Core 2.0.9 is available for download and usage in your environment.
 
-* [Download .NET Core](https://github.com/dotnet/core/blob/master/release-notes/download-archives/2.0.9-download.md)
+* [Download .NET Core](https://github.com/dotnet/core/blob/main/release-notes/download-archives/2.0.9-download.md)
 
 ## Blog Round up
 
@@ -24,7 +24,7 @@ The [.NET Core Docker images](https://hub.docker.com/r/microsoft/dotnet/) have b
 
 ## .NET Core Lifecycle News
 
-See [.NET Core Supported OS Lifecycle Policy](https://github.com/dotnet/core/blob/master/os-lifecycle-policy.md) to learn about Windows, macOS and Linux versions that are supported for each .NET Core release.
+See [.NET Core Supported OS Lifecycle Policy](https://github.com/dotnet/core/blob/main/os-lifecycle-policy.md) to learn about Windows, macOS and Linux versions that are supported for each .NET Core release.
 
 .NET Core 2.1 is expected to be declared LTS in the next few months. It is recommended that 2.1 be the default target for projects. .NET Core 2.0 will go out of support October 2018.
 

release-notes/2.0/2.1.200-sdk.md

@@ -4,8 +4,8 @@ Microsoft is releasing updates for .NET Core SDK and ASP.NET Core. This release
 
 .NET Core 2.0.7 (previously released) and SDK 2.1.200 are available for download and usage in your environment.
 
-* [Getting Started](https://www.microsoft.com/net/core/)
-* [Downloads](https://github.com/dotnet/core/blob/master/release-notes/download-archives/2.1.200-sdk-download.md)
+* [Getting Started](https://dotnet.microsoft.com/download)
+* [Downloads](https://github.com/dotnet/core/blob/main/release-notes/download-archives/2.1.200-sdk-download.md)
 
 The .NET Core SDK 2.1.200 includes .NET Core 2.0.7 Runtime so downloading the runtime packages separately is not needed when installing the SDK. After installing the .NET Core SDK 2.1.200, the following command will show that you're running version `2.1.200` of the tools.
 

release-notes/2.0/README.md

@@ -1,10 +1,14 @@
-# .NET Core 2.0 Releases - Out of support
+# .NET Core 2.0 Release -- Out of support
 
-The following .NET Core 2.0 releases have been shipped.
+This release is out of support. See [.NET releases](../../releases.md) for in-support releases.
+
+[.NET Core 2.0](https://devblogs.microsoft.com/dotnet/announcing-net-core-2-0/) was released on December 4th, 2018. The release was a collaborative effort by many [contributors](2.0.0-contributor.md). [.NET Core 2.0 reached end of life on October 1st, 2018](https://devblogs.microsoft.com/dotnet/net-core-2-0-will-reach-end-of-life-on-september-1-2018/). It was [supported by Microsoft](../../microsoft-support.md) on [multiple operating systems](2.0-supported-os.md).
+
+Release notes and download information is provided for each update, in the follow table.
 
 | Release Date | Description |  |  |
 | :-- | :-- | :--: | :-- |
-| 2018/10/01 | Out of support | [details](https://github.com/dotnet/core/blob/master/microsoft-support.md#out-of-support-net-core-releases) | |
+| 2018/10/01 | Out of support | [.NET Core 2.0 end of life](https://devblogs.microsoft.com/dotnet/net-core-2-0-will-reach-end-of-life-on-september-1-2018/) | |
 | 2018/07/10 | 2.0.9 with SDK 2.1.202 | [release notes](2.0.9.md)/[download](../download-archives/2.0.9-download.md) | |
 | 2018/05/08 | 2.0.7 with SDK 2.1.200 | [release notes](https://github.com/dotnet/cli/releases/tag/v2.1.200)/[download](../download-archives/2.1.200-sdk-download.md) |
 | 2018/04/17 | 2.0.7 with SDK 2.1.105 | [release notes](2.0.7.md)/[download](../download-archives/2.0.7-download.md) | |

release-notes/2.0/releases.json

@@ -6,7 +6,7 @@
   "latest-sdk": "2.1.202",
   "support-phase": "eol",
   "eol-date": "2018-10-01",
-  "lifecycle-policy": "https://www.microsoft.com/net/support/policy",
+  "lifecycle-policy": "https://dotnet.microsoft.com/platform/support/policy/",
   "releases": [
     {
       "release-date": "2018-07-10",
@@ -22,7 +22,7 @@
             "cve-url": "https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-8356"
           }
         ],
-      "release-notes": "https://github.com/dotnet/core/blob/master/release-notes/2.0/2.0.9.md",
+      "release-notes": "https://github.com/dotnet/core/blob/main/release-notes/2.0/2.0.9.md",
       "runtime": {
         "version": "2.0.9",
         "version-display": "2.0.9",
@@ -280,7 +280,7 @@
             "cve-url": "https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-0765"
           }
         ],
-      "release-notes": "https://github.com/dotnet/core/blob/master/release-notes/2.0/2.1.200-sdk.md",
+      "release-notes": "https://github.com/dotnet/core/blob/main/release-notes/2.0/2.1.200-sdk.md",
       "runtime": {
         "version": "2.0.8",
         "version-display": "2.0.8",
@@ -458,7 +458,7 @@
       "release-version": "2.0.7",
       "security": false,
       "cve-list": null,
-      "release-notes": "https://github.com/dotnet/core/blob/master/release-notes/2.0/2.0.7.md",
+      "release-notes": "https://github.com/dotnet/core/blob/main/release-notes/2.0/2.0.7.md",
       "runtime": {
         "version": "2.0.7",
         "version-display": "2.0.7",
@@ -870,7 +870,7 @@
             "cve-url": "https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-0808"
           }
         ],
-      "release-notes": "https://github.com/dotnet/core/blob/master/release-notes/2.0/2.0.6.md",
+      "release-notes": "https://github.com/dotnet/core/blob/main/release-notes/2.0/2.0.6.md",
       "runtime": {
         "version": "2.0.6",
         "version-display": null,

release-notes/2.1/2.1-supported-os.md

@@ -12,11 +12,13 @@ The tables below provide OS version information supported by .NET Core 2.1.
 
 OS                            | Version                       | Architectures  | Notes
 ------------------------------|-------------------------------|----------------|-----
-Windows Client                | 7 SP1+, 8.1                   | x64, x86       |
+Windows Client                | 7 SP1(**\***), 8.1            | x64, x86       |
 Windows 10 Client             | Version 1607+                 | x64, x86       | 1607 is the minimum version for support. See [Out of support OS versions](#out-of-support-os-versions) below for Windows 10 releases that are no longer supported.
 Windows Server                | 2008 R2 SP1+                  | x64, x86       |
 
-See the [Windows Lifecycle Fact Sheet](https://support.microsoft.com/en-us/help/13853/windows-lifecycle-fact-sheet) for details regarding each Windows release lifecycle.
+**\*** Windows 7 SP1 is supported with [Extended Security Updates](https://docs.microsoft.com/troubleshoot/windows-client/windows-7-eos-faq/windows-7-extended-security-updates-faq) installed.
+
+See the [Windows Lifecycle Fact Sheet](https://support.microsoft.com/help/13853/windows-lifecycle-fact-sheet) for details regarding each Windows release lifecycle.
 
 ## macOS
 
@@ -28,15 +30,14 @@ Mac OS X (macOS)              | 10.12+                        | x64            |
 
 OS                            | Version                       | Architectures  | Notes
 ------------------------------|-------------------------------|----------------|-----
-Red Hat Enterprise Linux      | 6                             | x64            | [Microsoft support policy](https://www.microsoft.com/net/support/policy)
-Red Hat Enterprise Linux <br> CentOS <br> Oracle Linux | 7+    | x64            | [Red Hat support policy](https://access.redhat.com/support/policy/updates/errata/) <br> [CentOS lifecycle](https://wiki.centos.org/FAQ/General#head-fe8a0be91ee3e7dea812e8694491e1dde5b75e6d) <br> [Oracle Linux lifecycle](http://www.oracle.com/us/support/library/elsp-lifetime-069338.pdf)
-Fedora                        | 30, 31                        | x64            | [Fedora lifecycle](https://fedoraproject.org/wiki/End_of_life)
+Red Hat Enterprise Linux <br> CentOS <br> Oracle Linux | 7+    | x64            | [Red Hat support policy](https://access.redhat.com/support/policy/updates/errata/) <br> [CentOS lifecycle](https://wiki.centos.org/FAQ/General#head-fe8a0be91ee3e7dea812e8694491e1dde5b75e6d) <br> [Oracle Linux lifecycle](https://www.oracle.com/us/support/library/elsp-lifetime-069338.pdf)
+Fedora                        | 33+                     | x64            | [Fedora lifecycle](https://fedoraproject.org/wiki/End_of_life)
 Debian                        | 9+                             | x64, ARM32     | [Debian lifecycle](https://wiki.debian.org/DebianReleases)
-Ubuntu                        | 20.04, 18.04, 16.04           | x64, ARM32\*   | [Ubuntu lifecycle](https://wiki.ubuntu.com/Releases)
+Ubuntu                        | 21.04, 20.04, 18.04, 16.04           | x64, ARM32\*   | [Ubuntu lifecycle](https://wiki.ubuntu.com/Releases)
 Linux Mint                    | 18, 17                        | x64            | [Linux Mint end of life announcements](https://forums.linuxmint.com/search.php?keywords=%22end+of+life%22&terms=all&author=&sc=1&sf=titleonly&sr=posts&sk=t&sd=d&st=0&ch=300&t=0&submit=Search)
 openSUSE                      | 15+                         | x64            | [OpenSUSE lifecycle](https://en.opensuse.org/Lifetime)
 SUSE Enterprise Linux (SLES)  | 12 SP2+                       | x64            | [SUSE lifecycle](https://www.suse.com/lifecycle/)
-Alpine Linux                  | 3.10+                          | x64            | [Alpine lifecycle](https://wiki.alpinelinux.org/wiki/Alpine_Linux:Releases)
+Alpine Linux                  | 3.10, 3.11, 3.12                          | x64            | [Alpine lifecycle](https://wiki.alpinelinux.org/wiki/Alpine_Linux:Releases)
 
 * **Bold numbers** indicate additions in this release.
 * '+' indicates the minimum supported version.
@@ -45,12 +46,15 @@ Alpine Linux                  | 3.10+                          | x64
 
 ## Out of support OS versions
 
-Support for the following versions was ended by the distribution owners and are [no longer supported by .NET Core 2.1](https://github.com/dotnet/core/blob/master/os-lifecycle-policy.md).
+Support for the following versions was ended by the distribution owners and are [no longer supported by .NET Core 2.1](https://github.com/dotnet/core/blob/main/os-lifecycle-policy.md).
 
 |OS         | Version  | End of Life |
 |-----------|----------|-------------|
-| Windows 10| 1703     | [10/08/2019](https://support.microsoft.com/en-us/help/13853/windows-lifecycle-fact-sheet) |
-| Fedora    | 29       | [11/30/2019](https://fedoraproject.org/wiki/End_of_life)   |
+| RHEL    | 6    | [11/30/2020](https://access.redhat.com/support/policy/updates/errata)   |
+| Windows 10| 1703     | [10/08/2019](https://support.microsoft.com/help/13853/windows-lifecycle-fact-sheet) |
+| Fedora    | 31       | [24/11/2020](https://lists.fedoraproject.org/archives/list/announce@lists.fedoraproject.org/thread/NU5AENRUFG4XK5D34SJN5FZPLYMZF6ZQ/)   |
+| Fedora    | 30       | [26/05/2020](https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/7UTUFY7WEL6RTFRXJB75XAFH44Y6RPUC/)   |
+| Fedora    | 29       | [11/26/2019](https://lists.fedoraproject.org/archives/list/announce@lists.fedoraproject.org/thread/BB4ECDFSJ66AQU63ZKNYROEFMMLSLFUK/)   |
 | Fedora    | 28       | [05/28/2019](https://fedoramagazine.org/fedora-28-end-of-life/)   |
 | Fedora    | 27       | [11/30/2018](https://fedoramagazine.org/fedora-27-end-of-life/)   |
 | Fedora    | 26       | [5/29/2018](https://fedoramagazine.org/fedora-26-end-life/)   |

release-notes/2.1/2.1.0-preview1.md

@@ -2,7 +2,7 @@
 
 .NET Core 2.1.0 Preview 1 is available for download and usage in your environment.
 
-* [Downloads](https://www.microsoft.com/net/download/dotnet-core/sdk-2.1.300-preview1)
+* [Downloads](https://dotnet.microsoft.com/download/dotnet/2.1)
 
 ## Blog Round up
 

release-notes/2.1/2.1.0.md

@@ -1,8 +1,8 @@
 # .NET Core 2.1 - May 30, 2018
 
-.NET Core 2.1.0 is available for download and usage in your environment. Have a look at the [Known Issues](2.1.0-known-issues.md) document as there are a few things to be aware of before installing. A [changelist](https://github.com/dotnet/core/blob/master/release-notes/2.1/2.1.0-commit.md) for the entire 2.1 development cycle is also available. This does not include ASP.NET Core or Entity Framework Core.
+.NET Core 2.1.0 is available for download and usage in your environment. Have a look at the [Known Issues](2.1.0-known-issues.md) document as there are a few things to be aware of before installing. A [changelist](https://github.com/dotnet/core/blob/main/release-notes/2.1/2.1.0-commit.md) for the entire 2.1 development cycle is also available. This does not include ASP.NET Core or Entity Framework Core.
 
-* [Download .NET Core](https://www.microsoft.com/net/download/dotnet-core/)
+* [Download .NET Core](https://dotnet.microsoft.com/download)
 
 ## Blog Round up
 
@@ -93,4 +93,4 @@ On Linux and macOS, you can only configure `HttpClient` on a process-basis. On L
 
 ### API changes
 
-See all changes from 2.0 in the [detailed API diff](https://github.com/dotnet/core/blob/master/release-notes/2.1/api-diff/2.0-vs-2.1.md) to help determine if any will impact existing projects built on .NET Core 2.0.
+See all changes from 2.0 in the [detailed API diff](https://github.com/dotnet/core/blob/main/release-notes/2.1/api-diff/2.0-vs-2.1.md) to help determine if any will impact existing projects built on .NET Core 2.0.

release-notes/2.1/2.1.1.md

@@ -1,8 +1,8 @@
 # .NET Core June 2018 Update - June 21, 2018
 
-.NET Core 2.1.1 is available for download and usage in your environment. Have a look at the [Known Issues](2.1.1-known-issues.md) document as there are a few things to be aware of before installing. A [changelist](https://github.com/dotnet/core/blob/master/release-notes/2.1/2.1.1-commit.md) for the entire 2.1 development cycle is also available. This does not include ASP.NET Core or Entity Framework Core.
+.NET Core 2.1.1 is available for download and usage in your environment. Have a look at the [Known Issues](2.1.1-known-issues.md) document as there are a few things to be aware of before installing. A [changelist](https://github.com/dotnet/core/blob/main/release-notes/2.1/2.1.1-commit.md) for the entire 2.1 development cycle is also available. This does not include ASP.NET Core or Entity Framework Core.
 
-* [Download .NET Core](https://github.com/dotnet/core/blob/master/release-notes/download-archives/2.1.1-download.md)
+* [Download .NET Core](https://github.com/dotnet/core/blob/main/release-notes/download-archives/2.1.1-download.md)
 
 ## Blog Round up
 
@@ -29,14 +29,14 @@ It was announced in the [2.1 blog post](https://blogs.msdn.microsoft.com/dotnet/
 [.NET Core 2.0](https://blogs.msdn.microsoft.com/dotnet/2017/08/14/announcing-net-core-2-0/) was released on August 14, 2017. As a non-LTS release, it is supported for 3 months after the next release.
 [.NET Core 2.1](https://blogs.msdn.microsoft.com/dotnet/2018/05/30/announcing-net-core-2-1/) was released on May 30th, 2018. As a result, .NET Core 2.0 will be supported until September 1, 2018.
 
-Microsoft has a published [support policy](https://github.com/dotnet/core/blob/master/microsoft-support.md) for .NET Core. It includes policies for two release types: LTS and Current. .NET Core 2.0 is a Current release.
+Microsoft has a published [support policy](https://github.com/dotnet/core/blob/main/microsoft-support.md) for .NET Core. It includes policies for two release types: LTS and Current. .NET Core 2.0 is a Current release.
 
 * LTS releases include features and components that have been stabilized, requiring few updates over a longer support release lifetime. These releases are a good choice for hosting applications that you do not intend to update often.
 * Current releases include features and components that are new and that may undergo future change based on feedback. These releases are a good choice for applications in active development, giving you access to the latest features and improvements. You need to upgrade to later .NET Core releases more often to stay in support.
 
 Both types of releases receive critical fixes throughout their lifecycle, for security, reliability, or to add support for new operating system versions. You must stay up-to-date with the latest patches to qualify for support.
 
-See [.NET Core Supported OS Lifecycle Policy](https://github.com/dotnet/core/blob/master/os-lifecycle-policy.md) to learn about Windows, macOS and Linux versions that are supported for each .NET Core release.
+See [.NET Core Supported OS Lifecycle Policy](https://github.com/dotnet/core/blob/main/os-lifecycle-policy.md) to learn about Windows, macOS and Linux versions that are supported for each .NET Core release.
 
 After that time, .NET Core patch updates will no longer include updated packages for .NET Core 2.0.
 

release-notes/2.1/2.1.10/2.1.10-download.md

@@ -6,7 +6,7 @@
 * ASP.NET Core 2.1.10
 * .NET Core SDK
 
-See the [Release Notes](https://github.com/dotnet/core/blob/master/release-notes/2.1/2.1.10/2.1.10.md) for details about what is included in this update.
+See the [Release Notes](https://github.com/dotnet/core/blob/main/release-notes/2.1/2.1.10/2.1.10.md) for details about what is included in this update.
 
 **Note:** If you are a Visual Studio user, there are MSBuild version requirements so use only the .NET Core SDK supported for each Visual Studio version. If you use other development environments, we recommend using the latest SDK release.
 
@@ -14,7 +14,7 @@ See the [Release Notes](https://github.com/dotnet/core/blob/master/release-notes
 | :-- | :--: |
 | Visual Studio 2017 (Windows) | [2.1.506](#downloads) |
 | Visual Studio 2019 (Windows) | [2.1.603](../2.1.603-SDK/2.1.603-SDK-download.md) |
-| Visual Studio for Mac | https://docs.microsoft.com/en-us/visualstudio/mac/net-core-support |
+| Visual Studio for Mac | https://docs.microsoft.com/visualstudio/mac/net-core-support |
 
 ## Downloads
 
@@ -49,7 +49,7 @@ When .NET Core in installed using the Snap package, the default .NET Core comman
 
 `sudo snap alias dotnet-sdk.dotnet dotnet`
 
-**Note:** Some distros require an additional step to enable access to the SSL certificate. If you experience SSL errors when running `dotnet restore`, see [Linux Setup](https://github.com/dotnet/core/blob/master/Documentation/linux-setup.md) for a possible resolution.
+**Note:** Some distros require an additional step to enable access to the SSL certificate. If you experience SSL errors when running `dotnet restore`, see [Linux Setup](https://github.com/dotnet/core/blob/main/Documentation/linux-setup.md) for a possible resolution.
 
 ### Install using a Package Manager
 
@@ -82,7 +82,7 @@ sudo [package manager] install aspnetcore-runtime-2.1
 
 ### Installation from a binary archive
 
-Installing from the packages detailed above is recommended or you can install from binary archive, if that better suits your needs. When using binary archives to install, the contents must be extracted to a user location such as `$HOME/dotnet`, a symbolic link created for `dotnet` and a few dependencies installed. Dependency requirements can be seen in the [Linux System Prerequisites](https://github.com/dotnet/core/blob/master/Documentation/linux-prereqs.md) document.
+Installing from the packages detailed above is recommended or you can install from binary archive, if that better suits your needs. When using binary archives to install, the contents must be extracted to a user location such as `$HOME/dotnet`, a symbolic link created for `dotnet` and a few dependencies installed. Dependency requirements can be seen in the [Linux System Prerequisites](https://github.com/dotnet/core/blob/main/Documentation/linux-prereqs.md) document.
 
 ```bash
 mkdir -p $HOME/dotnet && tar zxf dotnet.tar.gz -C $HOME/dotnet
@@ -107,7 +107,7 @@ This will install the ASP.NET Core Module for IIS.
 
 [blob-runtime]: https://dotnetcli.blob.core.windows.net/dotnet/Runtime/
 [blob-sdk]: https://dotnetcli.blob.core.windows.net/dotnet/Sdk/
-[release-notes]: https://github.com/dotnet/core/blob/master/release-notes/2.1/2.1.10/2.1.10.md
+[release-notes]: https://github.com/dotnet/core/blob/main/release-notes/2.1/2.1.10/2.1.10.md
 
 [dotnet-runtime-linux-arm.tar.gz]: https://download.visualstudio.microsoft.com/download/pr/b3a0363f-4ea6-43c1-b5bf-f15e1b88b428/eda34aff06bd3bfd53cf156427ccd3a3/dotnet-runtime-2.1.10-linux-arm.tar.gz
 [dotnet-runtime-linux-arm64.tar.gz]: https://download.visualstudio.microsoft.com/download/pr/23bde323-de7b-4176-b120-6b5d242b49dd/a7a88339ce8c9708b7654f373f484910/dotnet-runtime-2.1.10-linux-arm64.tar.gz
@@ -155,7 +155,7 @@ This will install the ASP.NET Core Module for IIS.
 [checksums-runtime]: https://dotnetcli.blob.core.windows.net/dotnet/checksums/2.1.10-runtime-sha.txt
 [checksums-sdk]: https://dotnetcli.blob.core.windows.net/dotnet/checksums/2.1.506-sdk-sha.txt
 
-[linux-install]: https://www.microsoft.com/net/download/linux
-[linux-setup]: https://github.com/dotnet/core/blob/master/Documentation/linux-setup.md
+[linux-install]: https://docs.microsoft.com/dotnet/core/install/linux
+[linux-setup]: https://github.com/dotnet/core/blob/main/Documentation/linux-setup.md
 
 [dotnet-blog]: https://devblogs.microsoft.com/dotnet/

release-notes/2.1/2.1.10/2.1.10.md

@@ -8,7 +8,7 @@
 | :-- | :--: |
 | Visual Studio 2017 (Windows) | [2.1.506](#downloads) |
 | Visual Studio 2019 (Windows) | [2.1.603](../2.1.603-SDK/2.1.603-SDK-download.md) |
-| Visual Studio for Mac | https://docs.microsoft.com/en-us/visualstudio/mac/net-core-support |
+| Visual Studio for Mac | https://docs.microsoft.com/visualstudio/mac/net-core-support |
 
 * [Blog Post][dotnet-blog]
 * [Downloads](#downloads)
@@ -54,7 +54,7 @@ There are no changes this month in OS version support status.
 
 .NET Core 1.0 and 1.1, which entered "Maintenance" support status when 2.1 was declared LTS, will be end-of-life June 27, 2019. Updates for the 1.0 and 1.1 channels will no longer be offered after that date. See [.NET Core Support Policy](https://dotnet.microsoft.com/platform/support/policy/dotnet-core) to learn more about the .NET Core support lifecycle.
 
-See [.NET Core Supported OS Lifecycle Policy](https://github.com/dotnet/core/blob/master/os-lifecycle-policy.md) to learn about Windows, macOS and Linux versions that are supported for each .NET Core release.
+See [.NET Core Supported OS Lifecycle Policy](https://github.com/dotnet/core/blob/main/os-lifecycle-policy.md) to learn about Windows, macOS and Linux versions that are supported for each .NET Core release.
 
 ## Changes in 2.1.10
 
@@ -144,7 +144,7 @@ runtime.win-x86.microsoft.netcore.dotnethostresolver | 2.1.10
 
 [blob-runtime]: https://dotnetcli.blob.core.windows.net/dotnet/Runtime/
 [blob-sdk]: https://dotnetcli.blob.core.windows.net/dotnet/Sdk/
-[release-notes]: https://github.com/dotnet/core/blob/master/release-notes/2.1/2.1.10/2.1.10.md
+[release-notes]: https://github.com/dotnet/core/blob/main/release-notes/2.1/2.1.10/2.1.10.md
 
 [dotnet-runtime-linux-arm.tar.gz]: https://download.visualstudio.microsoft.com/download/pr/b3a0363f-4ea6-43c1-b5bf-f15e1b88b428/eda34aff06bd3bfd53cf156427ccd3a3/dotnet-runtime-2.1.10-linux-arm.tar.gz
 [dotnet-runtime-linux-arm64.tar.gz]: https://download.visualstudio.microsoft.com/download/pr/23bde323-de7b-4176-b120-6b5d242b49dd/a7a88339ce8c9708b7654f373f484910/dotnet-runtime-2.1.10-linux-arm64.tar.gz
@@ -192,6 +192,6 @@ runtime.win-x86.microsoft.netcore.dotnethostresolver | 2.1.10
 [checksums-runtime]: https://dotnetcli.blob.core.windows.net/dotnet/checksums/2.1.10-runtime-sha.txt
 [checksums-sdk]: https://dotnetcli.blob.core.windows.net/dotnet/checksums/2.1.506-sdk-sha.txt
 
-[linux-install]: https://www.microsoft.com/net/download/linux
+[linux-install]: https://docs.microsoft.com/dotnet/core/install/linux
 
 [dotnet-blog]: https://devblogs.microsoft.com/dotnet/net-core-april-2019/

release-notes/2.1/2.1.11/2.1.11-download.md

@@ -14,7 +14,7 @@ See the [Release Notes](2.1.11.md) for details about what is included in this up
 | :-- | :--: |
 | Visual Studio 2017 (Windows) | [2.1.507](#downloads) |
 | Visual Studio 2019 (Windows) | [2.1.604](../2.1.604-SDK/2.1.604-SDK-download.md) |
-| Visual Studio for Mac | https://docs.microsoft.com/en-us/visualstudio/mac/net-core-support |
+| Visual Studio for Mac | https://docs.microsoft.com/visualstudio/mac/net-core-support |
 
 ## Downloads
 
@@ -49,7 +49,7 @@ When .NET Core in installed using the Snap package, the default .NET Core comman
 
 `sudo snap alias dotnet-sdk.dotnet dotnet`
 
-**Note:** Some distros require an additional step to enable access to the SSL certificate. If you experience SSL errors when running `dotnet restore`, see [Linux Setup](https://github.com/dotnet/core/blob/master/Documentation/linux-setup.md) for a possible resolution.
+**Note:** Some distros require an additional step to enable access to the SSL certificate. If you experience SSL errors when running `dotnet restore`, see [Linux Setup](https://github.com/dotnet/core/blob/main/Documentation/linux-setup.md) for a possible resolution.
 
 ### Install using a Package Manager
 
@@ -82,7 +82,7 @@ sudo [package manager] install aspnetcore-runtime-2.1
 
 ### Installation from a binary archive
 
-Installing from the packages detailed above is recommended or you can install from binary archive, if that better suits your needs. When using binary archives to install, the contents must be extracted to a user location such as `$HOME/dotnet`, a symbolic link created for `dotnet` and a few dependencies installed. Dependency requirements can be seen in the [Linux System Prerequisites](https://github.com/dotnet/core/blob/master/Documentation/linux-prereqs.md) document.
+Installing from the packages detailed above is recommended or you can install from binary archive, if that better suits your needs. When using binary archives to install, the contents must be extracted to a user location such as `$HOME/dotnet`, a symbolic link created for `dotnet` and a few dependencies installed. Dependency requirements can be seen in the [Linux System Prerequisites](https://github.com/dotnet/core/blob/main/Documentation/linux-prereqs.md) document.
 
 ```bash
 mkdir -p $HOME/dotnet && tar zxf dotnet.tar.gz -C $HOME/dotnet
@@ -107,7 +107,7 @@ This will install the ASP.NET Core Module for IIS.
 
 [blob-runtime]: https://dotnetcli.blob.core.windows.net/dotnet/Runtime/
 [blob-sdk]: https://dotnetcli.blob.core.windows.net/dotnet/Sdk/
-[release-notes]: https://github.com/dotnet/core/blob/master/release-notes/2.1/2.1.11/2.1.11.md
+[release-notes]: https://github.com/dotnet/core/blob/main/release-notes/2.1/2.1.11/2.1.11.md
 
 [dotnet-runtime-linux-arm.tar.gz]: https://download.visualstudio.microsoft.com/download/pr/7e34e5f5-e817-4ba4-9bfe-03f341e2a807/5779a613184dd09596f71681064cdaa8/dotnet-runtime-2.1.11-linux-arm.tar.gz
 [dotnet-runtime-linux-arm64.tar.gz]: https://download.visualstudio.microsoft.com/download/pr/f3238746-7a47-407f-9d30-20de4bfd93e2/0c26aad99851325fd5240909f120614d/dotnet-runtime-2.1.11-linux-arm64.tar.gz
@@ -152,7 +152,7 @@ This will install the ASP.NET Core Module for IIS.
 [checksums-runtime]: https://dotnetcli.blob.core.windows.net/dotnet/checksums/2.1.11-runtime-sha.txt
 [checksums-sdk]: https://dotnetcli.blob.core.windows.net/dotnet/checksums/2.1.507-sdk-sha.txt
 
-[linux-install]: https://www.microsoft.com/net/download/linux
-[linux-setup]: https://github.com/dotnet/core/blob/master/Documentation/linux-setup.md
+[linux-install]: https://docs.microsoft.com/dotnet/core/install/linux
+[linux-setup]: https://github.com/dotnet/core/blob/main/Documentation/linux-setup.md
 [dotnet-blog]: https://devblogs.microsoft.com/dotnet/net-core-may-2019/