acrolinx (#33852)

Author: gewarren

docs/azure/azure-tools.md

@@ -22,7 +22,7 @@ Azure PowerShell is a PowerShell module of cmdlets for managing Azure resource d
 
 ## Azure Developer CLI (preview)
 
-Azure Developer CLI (`azd`) is an open-source tool that accelerates the process of building cloud apps on Azure. The CLI provides best practice, developer-friendly commands that map to key stages in your workflow, whether you’re working in the terminal, your editor or integrated development environment (IDE), or DevOps.
+Azure Developer CLI (`azd`) is an open-source tool that accelerates the process of building cloud apps on Azure. The CLI provides best practice, developer-friendly commands that map to key stages in your workflow, whether you're working in the terminal, your editor or integrated development environment (IDE), or DevOps.
 
 You can use `azd` with extensible templates that include everything you need to get an application up and running in Azure. These templates include application code, and reusable infrastructure as code assets.
 

docs/azure/install-azure-cli.md

@@ -11,9 +11,9 @@ recommendations: false
 
 # Install the Azure CLI
 
-In addition to the Azure Portal, Azure also offers the [Azure CLI](/cli/azure/) as a command-line tool to create and manage Azure resources. The Azure CLI offers the benefits of efficiency, repeatability, and the ability to script recurring tasks.  
+In addition to the Azure portal, Azure also offers the [Azure CLI](/cli/azure/) as a command-line tool to create and manage Azure resources. The Azure CLI offers the benefits of efficiency, repeatability, and the ability to script recurring tasks.  
 
-In practice, most developers use both the Azure Portal and the Azure CLI. Where as the Azure Portal is useful when exploring new services and getting an overview of all of the resources in your Azure account, most developers find the Azure CLI to be faster and more efficient.  The Azure CLI can often accomplish in a single command what takes multiple steps in the Azure Portal.  In addition, since Azure CLI commands can be saved to a file, developers can assure that recurrent tasks are run the same way each time.
+In practice, most developers use both the Azure portal and the Azure CLI. Whereas the Azure portal is useful when exploring new services and getting an overview of all of the resources in your Azure account, most developers find the Azure CLI to be faster and more efficient. The Azure CLI can often accomplish in a single command what takes multiple steps in the Azure portal. In addition, since Azure CLI commands can be saved to a file, you can ensure that recurrent tasks are run the same way each time.
 
 The Azure CLI is available for Windows, macOS, and Linux.
 
@@ -26,12 +26,12 @@ The Azure CLI is available for Windows, macOS, and Linux.
 > [!div class="nextstepaction"]
 > [Install the Azure CLI for Linux](/cli/azure/install-azure-cli-linux)
 
-### Azure Cloud Shell
+## Azure Cloud Shell
 
-You can also use the Azure CLI in the Azure Cloud Shell at [https://shell.azure.com](https://shell.azure.com).  The Azure Cloud Shell is a fully functional, browser-based shell for managing Azure resources.  The Azure Cloud Shell is useful when you need a command line environment but are working on a device where you are unable to install the Azure CLI.
+You can also use the Azure CLI in the Azure Cloud Shell at [https://shell.azure.com](https://shell.azure.com).  The Azure Cloud Shell is a fully functional, browser-based shell for managing Azure resources.  The Azure Cloud Shell is useful when you need a command line environment but are working on a device where you're unable to install the Azure CLI.
 
 ![Screenshot of the Azure Cloud Shell running in a browser](media/azure-cloud-shell.png)
 
-### Next steps
+## Next steps
 
-Next, you will want to [install additional Azure tools](./azure-tools.md) like Azure Storage Explorer and Azure Data Studio to make you more productive with Azure.
+Next, you'll want to [install other Azure tools](./azure-tools.md) like Azure Storage Explorer and Azure Data Studio to make you more productive with Azure.

docs/core/compatibility/core-libraries/8.0/anonymouspipeserverstream-dispose.md

@@ -21,7 +21,7 @@ Starting in .NET 8, the client handle owned by a server that was created for out
 
 ## Type of breaking change
 
-This is a [behavioral change](../../categories.md#behavioral-change).
+This change is a [behavioral change](../../categories.md#behavioral-change).
 
 ## Reason for change
 

docs/core/diagnostics/metrics-collection.md

@@ -168,7 +168,7 @@ dotnet add package OpenTelemetry.Exporter.Prometheus --version 1.2.0-beta1
 > to the application.
 
 > [!NOTE]
-> This tutorial is using a pre-release build of OpenTelemetry's Prometheus support available at the time of writing. The OpenTelemetry
+> This tutorial uses a pre-release build of OpenTelemetry's Prometheus support available at the time of writing. The OpenTelemetry
 > project maintainers might make changes prior to the official release.
 
 Modify the code of `Program.cs` so that it contains the extra code to configure OpenTelemetry at the beginning of Main():

docs/core/extensions/sslstream-migration-from-framework.md

@@ -1,16 +1,16 @@
 ---
-title: Migrate SSL code from .NET Framework to .NET
+title: Migrate SslStream code from .NET Framework to .NET
 description: Learn how to migrate code that uses SslStream in .NET Framework to .NET.
 author: rzikm
 ms.author: radekzikmund
 ms.date: 1/9/2023
 ---
 
-# Migrate SSL code from .NET Framework to .NET
+# Migrate SslStream code from .NET Framework to .NET
 
 .NET Core brought many improvements as well as breaking changes to how <xref:System.Net.Security.SslStream> works. The most important change related to network security is that the <xref:System.Net.ServicePointManager> class has been mostly obsoleted and affects only the legacy <xref:System.Net.WebRequest> interface.
 
-For each <xref:System.Net.Security.SslStream> instance, you must configure the allowed SSL/TLS protocols and certificate validation callbacks separately via <xref:System.Net.Security.SslServerAuthenticationOptions> or <xref:System.Net.Security.SslClientAuthenticationOptions>. To configure network security options used in HTTPS in <xref:System.Net.Http.HttpClient>, you need to configure the security options in the underlying handler. The default handler used by <xref:System.Net.Http.HttpClient> is <xref:System.Net.Http.SocketsHttpHandler>, which has an <xref:System.Net.Http.SocketsHttpHandler.SslOptions> property that accepts <xref:System.Net.Security.SslClientAuthenticationOptions>.
+For each <xref:System.Net.Security.SslStream> instance, you must configure the allowed TLS protocols and certificate validation callbacks separately via <xref:System.Net.Security.SslServerAuthenticationOptions> or <xref:System.Net.Security.SslClientAuthenticationOptions>. To configure network security options used in HTTPS in <xref:System.Net.Http.HttpClient>, you need to configure the security options in the underlying handler. The default handler used by <xref:System.Net.Http.HttpClient> is <xref:System.Net.Http.SocketsHttpHandler>, which has an <xref:System.Net.Http.SocketsHttpHandler.SslOptions> property that accepts <xref:System.Net.Security.SslClientAuthenticationOptions>.
 
 Consider the following example that demonstrates how to create an <xref:System.Net.Http.HttpClient> with a custom certificate validation callback:
 
@@ -36,7 +36,7 @@ HttpClient httpClient = new(
     });
 ```
 
-The following table show how to migrate individual <xref:System.Net.ServicePointManager> properties related to SSL/TLS.
+The following table shows how to migrate individual <xref:System.Net.ServicePointManager> properties related to TLS.
 
 | Source API | Target API |
 |---|---|

docs/csharp/versioning.md

@@ -25,7 +25,7 @@ The most basic approach to SemVer is the 3 component format `MAJOR.MINOR.PATCH`,
 - `MINOR` is incremented when you add functionality in a backwards-compatible manner
 - `PATCH` is incremented when you make backwards-compatible bug fixes
 
-There are also ways to specify other scenarios like pre-release versions etc. when applying version information to your .NET library.
+There are also ways to specify other scenarios, for example, pre-release versions, when applying version information to your .NET library.
 
 ### Backwards Compatibility