Fix linter errors

Author: richlander

release-notes/2.0/2.0.0-preview2.md

@@ -11,7 +11,8 @@ The .NET Core SDK 2.0.0 Preview 2 includes .NET Core 2.0.0 Preview 2 Runtime so
 
 **Note** that if you want to use .NET Core 2.0.0 Preview 2 with Visual Studio 2017 15.3, you need to install the SDK.
 
-A [number of improvements](2.0.0-preview2-commit.md) have been made since Preview 1 by an [incredible list of folks](2.0.0-preview2-contributor.md). You can see details for other areas of the release in the [.NET Blog](<https://devblogs.microsoft.com/dotnet/announcing-net-core-2-0-preview-2/> and have a look at [.NET Core 2.0.0 Preview 2 Known Issues](2.0.0-preview2-known-issues.md) document as there are a few things to be aware of before installing.
+A [number of improvements](2.0.0-preview2-commit.md) have been made since Preview 1 by an [incredible list of folks](2.0.0-preview2-contributor.md).
+You can see details for other areas of the release in the [.NET Blog](<https://devblogs.microsoft.com/dotnet/announcing-net-core-2-0-preview-2/> and have a look at [.NET Core 2.0.0 Preview 2 Known Issues](2.0.0-preview2-known-issues.md) document as there are a few things to be aware of before installing.
 
 You're feedback is important and appreciated. We've created [dotnet/core #711](https://github.com/dotnet/core/issues/711) for your questions and comments.
 

release-notes/2.0/2.0.5.md

@@ -1,6 +1,7 @@
 # .NET Core January 2018 Update - January 9, 2018
 
-Microsoft is releasing security advisories for .NET Core and ASP.NET Core. Issues addressed by this update are summarized in the [fixes](#notable-fixes-and-commits) section below. Details can be found in corresponding announcements in the [.NET Core](https://github.com/dotnet/announcements/issues?q=is%3Aopen+is%3Aissue+label%3ASecurity) and [ASP.NET Core](https://github.com/aspnet/announcements/issues?q=is%3Aopen+is%3Aissue+label%3ASecurity) repos.
+Microsoft is releasing security advisories for .NET Core and ASP.NET Core. Issues addressed by this update are summarized in the [fixes](#notable-fixes-and-commits) section below.
+Details can be found in corresponding announcements in the [.NET Core](https://github.com/dotnet/announcements/issues?q=is%3Aopen+is%3Aissue+label%3ASecurity) and [ASP.NET Core](https://github.com/aspnet/announcements/issues?q=is%3Aopen+is%3Aissue+label%3ASecurity) repos.
 
 .NET Core 2.0.5 and SDK 2.1.4 are available for download and usage in your environment.
 

release-notes/2.0/2.0.6.md

@@ -1,6 +1,7 @@
 # .NET Core March 2018 Update - March 13, 2018
 
-Microsoft is releasing security advisories for .NET Core and ASP.NET Core. Issues addressed by this update are summarized in the [fixes](#notable-fixes-and-commits) section below. Details can be found in corresponding announcements in the [.NET Core](https://github.com/dotnet/announcements/issues?q=is%3Aopen+is%3Aissue+label%3ASecurity) and [ASP.NET Core](https://github.com/aspnet/announcements/issues?q=is%3Aopen+is%3Aissue+label%3ASecurity) repos.
+Microsoft is releasing security advisories for .NET Core and ASP.NET Core. Issues addressed by this update are summarized in the [fixes](#notable-fixes-and-commits) section below.
+Details can be found in corresponding announcements in the [.NET Core](https://github.com/dotnet/announcements/issues?q=is%3Aopen+is%3Aissue+label%3ASecurity) and [ASP.NET Core](https://github.com/aspnet/announcements/issues?q=is%3Aopen+is%3Aissue+label%3ASecurity) repos.
 
 .NET Core 2.0.6 and SDK 2.1.101 are available for download and usage in your environment.
 

release-notes/2.0/README.md

@@ -2,7 +2,8 @@
 
 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).
+[.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-notes/2.1/2.1.0-preview1.md

@@ -28,7 +28,8 @@ Details for running .NET Core 2.1 Preview 1 in Azure App Services can be seen in
 
 **System.IO** - Path APIs no longer check invalid characters directly.
 
-To improve performance and unblock cross platform scenarios System.IO.Path methods no longer check for validity of characters outside of the null character. Most System.IO APIs that take a path are impacted by this. Attempting to use a path that the OS/file system doesn't handle will return the system reported `IOException` when actually using the path as opposed to an ArgumentException before passing the path to the OS.
+To improve performance and unblock cross platform scenarios System.IO.Path methods no longer check for validity of characters outside of the null character. Most System.IO APIs that take a path are impacted by this.
+Attempting to use a path that the OS/file system doesn't handle will return the system reported `IOException` when actually using the path as opposed to an ArgumentException before passing the path to the OS.
 
 **System.IO** - Directory enumeration performance improvements
 
@@ -56,7 +57,8 @@ By switching to Span-based computations the computations of `Rfc2898DeriveBytes`
 
 **System.Memory** - New APIs for efficient low-allocation access to memory
 
-The component contains primitives and libraries that can be used to optimize memory usage. The primitives, `Span<T>`, `ReadOnlySpan<T>`, `Memory<T>`, and `ReadOnlyMemory<T>` are types for efficient representation of managed, stack, and native memory segments.  `ReadOnlySequence<T>` represents a sequence of such segments. The rest of the component are reusable APIs operating on these primitives. For example, the `Utf8Parser` class can be used to parse UTF-8 encoded text stored in a memory segment. Similarly, Utf8Formatter can be used to format UTF-8 text into a memory segment. It also contains `BinaryPrimitive` APIs which let you read and write blittable types into and from `Span<byte>` with support for endian-ness.
+The component contains primitives and libraries that can be used to optimize memory usage. The primitives, `Span<T>`, `ReadOnlySpan<T>`, `Memory<T>`, and `ReadOnlyMemory<T>` are types for efficient representation of managed, stack, and native memory segments.  `ReadOnlySequence<T>` represents a sequence of such segments. The rest of the component are reusable APIs operating on these primitives.
+For example, the `Utf8Parser` class can be used to parse UTF-8 encoded text stored in a memory segment. Similarly, Utf8Formatter can be used to format UTF-8 text into a memory segment. It also contains `BinaryPrimitive` APIs which let you read and write blittable types into and from `Span<byte>` with support for endian-ness.
 
 ### Global Tools
 

release-notes/2.1/2.1.0.md

@@ -39,7 +39,8 @@ The .NET Core installers now support package manager updates (eg `apt-get update
 
 #### Snap support
 
-We have been working on bringing .NET Core to Snap and are ready to hear what you think. Snaps, along with a few other technologies, are an emerging application installation and sandboxing technology which we think is pretty intriguing. The Snap install works well on Debian-based systems and other distros such as Fedora are having challenges that we're working to run down. The following steps can be used if you would like to give this a try.
+We have been working on bringing .NET Core to Snap and are ready to hear what you think. Snaps, along with a few other technologies, are an emerging application installation and sandboxing technology which we think is pretty intriguing. The Snap install works well on Debian-based systems and other distros such as Fedora are having challenges that we're working to run down.
+The following steps can be used if you would like to give this a try.
 
 * Visit [Snapcraft.io](https://snapcraft.io/) for guidance on preparing your system to use Snaps.
 * As with our other installers, the Runtime and SDK are available depending on your needs.

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

@@ -83,7 +83,8 @@ 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/main/linux.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/linux.md) document.
 
 ```bash
 mkdir -p $HOME/dotnet && tar zxf dotnet.tar.gz -C $HOME/dotnet

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

@@ -83,7 +83,8 @@ 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/main/linux.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/linux.md) document.
 
 ```bash
 mkdir -p $HOME/dotnet && tar zxf dotnet.tar.gz -C $HOME/dotnet

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

@@ -85,7 +85,8 @@ 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/main/linux.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/linux.md) document.
 
 ```bash
 mkdir -p $HOME/dotnet && tar zxf dotnet.tar.gz -C $HOME/dotnet

release-notes/2.1/2.1.12/2.1.605-sdk-download.md

@@ -85,7 +85,8 @@ 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/main/linux.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/linux.md) document.
 
 ```bash
 mkdir -p $HOME/dotnet && tar zxf dotnet.tar.gz -C $HOME/dotnet