acrolinx

Author: tomvcassidy

articles/service-fabric/service-fabric-cluster-creation-via-arm.md

@@ -26,7 +26,7 @@ If you are creating a production cluster to run production workloads, we recomme
 [!INCLUDE [updated-for-az](../../includes/updated-for-az.md)]
 
 ## Prerequisites 
-In this article, use the Service Fabric RM powershell or Azure CLI modules to deploy a cluster:
+In this article, use the Service Fabric RM PowerShell or Azure CLI modules to deploy a cluster:
 
 * [Azure PowerShell 4.1 and above][azure-powershell]
 * [Azure CLI version 2.0 and above][azure-CLI]
@@ -60,7 +60,7 @@ You can use either the following PowerShell or Azure CLI commands to create a cl
 The default template used is available here for [Windows](https://github.com/Azure-Samples/service-fabric-cluster-templates/tree/master/5-VM-Windows-1-NodeTypes-Secure-NSG)
  and here for [Ubuntu](https://github.com/Azure-Samples/service-fabric-cluster-templates/tree/master/5-VM-Ubuntu-1-NodeTypes-Secure).
 
-The following commands can create either Windows or Linux clusters, depending on how specify the OS parameter. Both PowerShell/CLI commands output the certificate in the specified *CertificateOutputFolder* (make sure the certificate folder location you specify already exists before running the command!).
+The following commands can create either Windows or Linux clusters, depending on how you specify the OS parameter. Both PowerShell/CLI commands output the certificate in the specified *CertificateOutputFolder* (make sure the certificate folder location you specify already exists before running the command!).
 
 > [!NOTE]
 > The following PowerShell command only works with the Azure PowerShell `Az` module. To check the current version of Azure Resource Manager PowerShell version, run the following PowerShell command "Get-Module Az". Follow [this link](/powershell/azure/install-Az-ps) to upgrade your Azure Resource Manager PowerShell version.
@@ -159,7 +159,7 @@ You can use the following command to specify an existing certificate to create a
 
 If this is a CA signed certificate that you will end up using for other purposes as well, then it is recommended that you provide a distinct resource group specifically for your key vault. We recommend that you put the key vault into its own resource group. This action lets you remove the compute and storage resource groups, including the resource group that contains your Service Fabric cluster, without losing your keys and secrets. **The resource group that contains your key vault *must be in the same region* as the cluster that is using it.**
 
-### Use the default five node, one node type template that ships in the module
+### Use the default five nodes, one node type template that ships in the module
 
 The default template used is available here for [Windows](https://github.com/Azure-Samples/service-fabric-cluster-templates/tree/master/5-VM-Windows-1-NodeTypes-Secure-NSG)
  and here for [Ubuntu](https://github.com/Azure-Samples/service-fabric-cluster-templates/tree/master/5-VM-Ubuntu-1-NodeTypes-Secure).

articles/service-fabric/service-fabric-get-started-linux.md

@@ -88,7 +88,7 @@ For manual installation of the Service Fabric runtime and common SDK, follow the
     sudo add-apt-repository "deb [arch=amd64] https://download.docker.com/linux/ubuntu $(lsb_release -cs) stable"
     ```
 
-6. Add Azul JDK Key to your APT keyring and setup its repository.
+6. Add Azul JDK Key to your APT keyring and set up its repository.
 
     ```bash
     sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 0xB1998361219BD9C9

articles/service-fabric/service-fabric-get-started-mac.md

@@ -14,16 +14,16 @@ ms.date: 07/14/2022
 # service-fabric-local-linux-cluster-windows.md
 ---
 
-# Set up your development environment on Mac OS X
+# Set up your development environment on macOS X
 > [!div class="op_single_selector"]
 > * [Windows](service-fabric-get-started.md)
 > * [Linux](service-fabric-get-started-linux.md)
-> * [Mac OS X](service-fabric-get-started-mac.md)
+> * [macOS X](service-fabric-get-started-mac.md)
 
-You can build Azure Service Fabric applications to run on Linux clusters by using Mac OS X. This document covers how to set up your Mac for development.
+You can build Azure Service Fabric applications to run on Linux clusters by using macOS X. This document covers how to set up your Mac for development.
 
 ## Prerequisites
-Azure Service Fabric doesn't run natively on Mac OS X. To run a local Service Fabric cluster, a pre-configured Docker container image is provided. Before you get started, you'll need:
+Azure Service Fabric doesn't run natively on macOS X. To run a local Service Fabric cluster, a pre-configured Docker container image is provided. Before you get started, you'll need:
 
 * The system requirements for installing [Docker Desktop on Mac](https://docs.docker.com/docker-for-mac/install/)
 
@@ -147,14 +147,14 @@ sfctl cluster select --endpoint http://localhost:19080
 
 Service Fabric provides scaffolding tools that help you to create a Service Fabric application from the terminal by using the Yeoman template generator. Use the following steps to ensure that the Service Fabric Yeoman template generator is working on your machine:
 
-1. Node.js and Node Package Manager (NPM) must be installed on your Mac. The software can be installed by using [HomeBrew](https://brew.sh/), as follows:
+1. Node.js and Node Package Manager must be installed on your Mac. The software can be installed by using [HomeBrew](https://brew.sh/), as follows:
 
     ```bash
     brew install node
     node -v
     npm -v
     ```
-2. Install the [Yeoman](https://yeoman.io/) template generator on your machine from NPM:
+2. Install the [Yeoman](https://yeoman.io/) template generator on your machine from Node Package Manager:
 
     ```bash
     npm install -g yo

articles/service-fabric/service-fabric-how-to-publish-linux-app-vs.md

@@ -1,6 +1,6 @@
 ---
-title: Create and Publish a.Net Core app to a remote Linux Cluster
-description: Create and publish .Net Core apps targeting a remote Linux cluster from Visual Studio
+title: Create and Publish a .NET Core app to a remote Linux Cluster
+description: Create and publish .NET Core apps targeting a remote Linux cluster from Visual Studio
 ms.topic: how-to
 ms.author: tomcassidy
 author: tomvcassidy
@@ -9,26 +9,26 @@ services: service-fabric
 ms.date: 07/14/2022
 ---
 
-# Use Visual Studio to create and publish .Net Core applications targeting a remote Linux Service Fabric cluster
-With Visual Studio tooling you can develop and publish Service Fabric .Net Core applications targeting a Linux Service Fabric cluster. The SDK version must be 3.4 or above to deploy a .Net Core application targeting Linux Service Fabric clusters from Visual Studio.
+# Use Visual Studio to create and publish .NET Core applications targeting a remote Linux Service Fabric cluster
+With Visual Studio tooling you can develop and publish Service Fabric .NET Core applications targeting a Linux Service Fabric cluster. The SDK version must be 3.4 or above to deploy a .NET Core application targeting Linux Service Fabric clusters from Visual Studio.
 
 > [!Note]
 > Visual Studio doesn't support debugging Service Fabric applications which target Linux.
 >
 
-## Create a Service Fabric application targeting .Net Core
+## Create a Service Fabric application targeting .NET Core
 1. Launch Visual Studio as an **administrator**.
 2. Create a project with **File->New->Project**.
 3. In the **New Project** dialog, choose **Cloud -> Service Fabric Application**.
 ![create-application]
 4. Name the application and click **Ok**.
-5. On the **New Service Fabric Service** page, select the type of service you would like to create under the **.Net Core Section**.
+5. On the **New Service Fabric Service** page, select the type of service you would like to create under the **.NET Core Section**.
 ![create-service]
 
 ## Deploy to a remote Linux cluster
 1. In the solution explorer, right click on the application and select **Build**.
 ![build-application]
-2. Once the build process for the application has completed, right click on the service and select edit the **csproj file**.
+2. Once the build process for the application has completed, right click on the service and choose to edit the **csproj file**.
 ![edit-csproj]
 3. Edit the UpdateServiceFabricManifestEnabled property from True to **False** if the service is an **actor project type**. If your application does not have an actor service, skip to step 4.
 ```xml
@@ -62,4 +62,4 @@ With Visual Studio tooling you can develop and publish Service Fabric .Net Core
 [publish-application]:./media/service-fabric-how-to-vs-remote-linux-cluster/publish-remote-linux.png
 
 ## Next steps
-* Learn about [Getting started with Service Fabric with .Net Core](https://azure.microsoft.com/resources/samples/service-fabric-dotnet-core-getting-started/)
+* Learn about [Getting started with Service Fabric with .NET Core](https://azure.microsoft.com/resources/samples/service-fabric-dotnet-core-getting-started/)

articles/service-fabric/service-fabric-tutorial-create-vnet-and-linux-cluster.md

@@ -63,7 +63,7 @@ In the **Microsoft.ServiceFabric/clusters** resource, a Linux cluster is deploye
 
 ### Azure load balancer
 
-In the **Microsoft.Network/loadBalancers** resource, a load balancer is configured and probes and rules setup for the following ports:
+In the **Microsoft.Network/loadBalancers** resource, a load balancer is configured and probes and rules set up for the following ports:
 
 * client connection endpoint: 19000
 * HTTP gateway endpoint: 19080
@@ -99,7 +99,7 @@ The **AzureDeploy.Parameters** file declares many values used to deploy the clus
 
 Next, set up the network topology and deploy the Service Fabric cluster. The **AzureDeploy.json** Resource Manager template creates a virtual network (VNET) and a subnet for Service Fabric. The template also deploys a cluster with certificate security enabled.  For production clusters, use a certificate from a certificate authority (CA) as the cluster certificate. A self-signed certificate can be used to secure test clusters.
 
-The template in this article deploy a cluster that uses the certificate thumbprint to identify the cluster certificate.  No two certificates can have the same thumbprint, which makes certificate management more difficult. Switching a deployed cluster from using certificate thumbprints to using certificate common names makes certificate management much simpler.  To learn how to update the cluster to use certificate common names for certificate management, read [change cluster to certificate common name management](service-fabric-cluster-change-cert-thumbprint-to-cn.md).
+The template in this article deploys a cluster that uses the certificate thumbprint to identify the cluster certificate.  No two certificates can have the same thumbprint, which makes certificate management more difficult. Switching a deployed cluster from using certificate thumbprints to using certificate common names makes certificate management much simpler.  To learn how to update the cluster to use certificate common names for certificate management, read [change cluster to certificate common name management](service-fabric-cluster-change-cert-thumbprint-to-cn.md).
 
 ### Create a cluster using an existing certificate
 
@@ -170,7 +170,7 @@ If you're not immediately moving on to the next article, you might want to [dele
 
 Learn how to [scale a Cluster](service-fabric-tutorial-scale-cluster.md).
 
-The template in this article deploy a cluster that uses the certificate thumbprint to identify the cluster certificate.  No two certificates can have the same thumbprint, which makes certificate management more difficult. Switching a deployed cluster from using certificate thumbprints to using certificate common names makes certificate management much simpler.  To learn how to update the cluster to use certificate common names for certificate management, read [change cluster to certificate common name management](service-fabric-cluster-change-cert-thumbprint-to-cn.md).
+The template in this article deploys a cluster that uses the certificate thumbprint to identify the cluster certificate.  No two certificates can have the same thumbprint, which makes certificate management more difficult. Switching a deployed cluster from using certificate thumbprints to using certificate common names makes certificate management much simpler.  To learn how to update the cluster to use certificate common names for certificate management, read [change cluster to certificate common name management](service-fabric-cluster-change-cert-thumbprint-to-cn.md).
 
 [template]:https://github.com/Azure-Samples/service-fabric-cluster-templates/blob/master/7-VM-Ubuntu-3-NodeTypes-Secure/AzureDeploy.json
 [parameters]:https://github.com/Azure-Samples/service-fabric-cluster-templates/blob/master/7-VM-Ubuntu-3-NodeTypes-Secure/AzureDeploy.Parameters.json

articles/service-fabric/service-fabric-tutorial-package-containers.md

@@ -30,13 +30,13 @@ This tutorial is part two in a series. In this tutorial, a template generator to
 
 Service fabric provides scaffolding tools to help create applications from terminal using Yeoman template generator. Follow the steps below to ensure you have the Yeoman template generator.
 
-1. Install nodejs and NPM on your machine. Note that, Mac OSX users will have to use the package manager Homebrew
+1. Install nodejs and Node Package Manager on your machine. Note that, Mac OSX users will have to use the package manager Homebrew
 
     ```bash
     curl -o- https://raw.githubusercontent.com/creationix/nvm/v0.33.0/install.sh | bash
     nvm install node 
     ```
-2. Install Yeoman template generator on your machine from NPM
+2. Install Yeoman template generator on your machine from Node Package Manager:
 
     ```bash
     npm install -g yo

articles/service-fabric/service-fabric-versions.md

@@ -130,17 +130,17 @@ The following table lists the version names of Service Fabric and their correspo
 | 8.1 CU1 | 8.1.321.9590 | 8.1.323.1 |
 | 8.1 RTO | 8.1.316.9590 | 8.1.320.1 |
 | 8.0 CU3 | 8.0.536.9590 | 8.0.527.1 |
-| 8.0 CU2 | 8.0.521.9590 | NA |
-| 8.0 CU1 | 8.0.516.9590 | 8.0.515.1 | 
-| 8.0 RTO | 8.0.514.9590 | 8.0.513.1 | 
+| 8.0 CU2 | 8.0.521.9590 | Not applicable |
+| 8.0 CU1 | 8.0.516.9590 | 8.0.515.1 |
+| 8.0 RTO | 8.0.514.9590 | 8.0.513.1 |
 | 7.2 CU7 | 7.2.477.9590 | 7.2.476.1 |
 | 7.2 CU6 | 7.2.457.9590 | 7.2.456.1 |
 | 7.2 CU5 | 7.2.452.9590 | 7.2.454.1 |
 | 7.2 CU4 | 7.2.445.9590 | 7.2.447.1 |
-| 7.2 CU3 | 7.2.433.9590 | NA |
+| 7.2 CU3 | 7.2.433.9590 | Not applicable |
 | 7.2 CU2 | 7.2.432.9590 | 7.2.431.1 |
-| 7.2 RTO | 7.2.413.9590 | NA |
-| 7.1 CU10 | 7.1.510.9590 | NA |
+| 7.2 RTO | 7.2.413.9590 | Not applicable |
+| 7.1 CU10 | 7.1.510.9590 | Not applicable |
 | 7.1 CU8 | 7.1.503.9590 | 7.1.508.1 |
 | 7.1 CU6 | 7.1.459.9590 | 7.1.455.1 |
 | 7.1 CU5 | 7.1.458.9590 | 7.1.454.1 |