Acrolinx

Author: tomvcassidy

articles/service-fabric/quickstart-guest-app.md

@@ -15,7 +15,7 @@ This quickstart helps you deploy an existing application (Node.js in this exampl
 
 ## Prerequisites
 
-Before you get started, make sure that you have [set up your development environment](service-fabric-get-started.md). Which includes installing the Service Fabric SDK and Visual Studio 2019 or 2015.
+Before you get started, make sure that you have [set up your development environment](service-fabric-get-started.md), which includes installing the Service Fabric SDK and Visual Studio 2019 or 2015.
 
 You also need to have an existing Node.js application for deployment. This quickstart uses a simple Node.js website that can be downloaded [here][download-sample]. Extract this file to your `<path-to-project>\ApplicationPackageRoot\<package-name>\Code\` folder after you create the project in the next step.
 

articles/service-fabric/quickstart-managed-cluster-template.md

@@ -11,7 +11,7 @@ ms.date: 07/14/2022
 
 # Quickstart: Deploy a Service Fabric managed cluster with an Azure Resource Manager template
 
-Service Fabric managed clusters are an evolution of the Azure Service Fabric cluster resource model that streamlines your deployment and cluster management experience. Service Fabric managed clusters are a fully encapsulated resource that enable you to deploy a single Service Fabric cluster resource rather than having to deploy all of the underlying resources that make up a Service Fabric cluster. This article describes how to do deploy a Service Fabric managed cluster for testing in Azure using an Azure Resource Manager template (ARM template).
+Service Fabric managed clusters are an evolution of the Azure Service Fabric cluster resource model that streamlines your deployment and cluster management experience. A Service Fabric managed cluster is a fully encapsulated resource that enables you to deploy a single Service Fabric cluster resource rather than having to deploy all of the underlying resources that make up a Service Fabric cluster. This article describes how to do deploy a Service Fabric managed cluster for testing in Azure using an Azure Resource Manager template (ARM template).
 
 The three-node Basic SKU cluster deployed in this tutorial is only intended to be used for instructional purposes (rather than production workloads). For further information, see  [Service Fabric managed cluster SKUs](overview-managed-cluster.md#service-fabric-managed-cluster-skus).
 

articles/service-fabric/release-notes.md

@@ -29,7 +29,7 @@ We are excited to announce that 9.0 release of the Service Fabric runtime has st
 ### Key announcements
 - **General Availability** Support for .NET 6.0
 - **General Availability** Support for Ubuntu 20.04
-- **General Availability** Support for Multi-AZ within a single VM Scale Set (VMSS)
+- **General Availability** Support for Multi-AZ within a single virtual machine scale set
 - Added support for IHost, IHostBuilder and Minimal Hosting Model
 - Enabling opt-in option for Data Contract Serialization (DCS) based remoting exception
 - Support creation of End-to-End Developer Experience for Linux development on Windows using WSL2

articles/service-fabric/service-fabric-api-management-overview.md

@@ -46,7 +46,7 @@ In the simplest case, traffic is forwarded to a stateless service instance. To a
 
 **Example**
 
-In the following scenario, a Service Fabric application contains a stateless service named `fabric:/app/fooservice`, that exposes an internal HTTP API. The service instance name is well known and can be hard-coded directly in the API Management inbound processing policy. 
+In the following scenario, a Service Fabric application contains a stateless service named `fabric:/app/fooservice` that exposes an internal HTTP API. The service instance name is well known and can be hard-coded directly in the API Management inbound processing policy. 
 
 ![Diagram that shows a Service Fabric application contains a stateless service that exposes an internal HTTP API.][sf-apim-static-stateless]
 

articles/service-fabric/service-fabric-application-upgrade-advanced.md

@@ -180,7 +180,7 @@ HealthState            : Ok
 ApplicationParameters  : { "ImportantParameter" = "1"; "NewParameter" = "testBefore" }
 ```
 
-Now, upgrade the application using the **Start-ServiceFabricApplicationUpgrade** cmdlet. This example shows an monitored upgrade, but an unmonitored upgrade can also be used. To see a full description of flags accepted by this cmdlet, see the [Azure Service Fabric PowerShell module reference](/powershell/module/servicefabric/start-servicefabricapplicationupgrade#parameters)
+Now, upgrade the application using the **Start-ServiceFabricApplicationUpgrade** cmdlet. This example shows a monitored upgrade, but an unmonitored upgrade can also be used. To see a full description of flags accepted by this cmdlet, see the [Azure Service Fabric PowerShell module reference](/powershell/module/servicefabric/start-servicefabricapplicationupgrade#parameters)
 
 ```PowerShell
 PS C:\> $appParams = @{ "ImportantParameter" = "2"; "NewParameter" = "testAfter"}