Acronlinx

tomvcassidy · tomvcassidy · commit aa9876a7ab2f · 2022-07-14T17:08:22.000-04:00
diff --git a/articles/service-fabric/service-fabric-manage-application-in-visual-studio.md b/articles/service-fabric/service-fabric-manage-application-in-visual-studio.md
@@ -24,7 +24,7 @@ By default, deploying an application combines the following steps into one simpl
 In Visual Studio, pressing **F5** deploys your application and attach the debugger to all application instances. You can use **Ctrl+F5** to deploy an application without debugging, or you can publish to a local or remote cluster by using the publish profile.
 
 ### Application Debug Mode
-Visual Studio provide a property called **Application Debug Mode**, which controls how you want Visual Studios to handle Application deployment as part of debugging.
+Visual Studio provides a property called **Application Debug Mode**, which controls how you want Visual Studios to handle Application deployment as part of debugging.
 
 #### To set the Application Debug Mode property
 1. On the Service Fabric application project's (*.sfproj) shortcut menu, choose **Properties** (or press the **F4** key).
diff --git a/articles/service-fabric/service-fabric-manifest-example-container-app.md b/articles/service-fabric/service-fabric-manifest-example-container-app.md
@@ -254,7 +254,7 @@ See [Application manifest elements](#application-manifest-elements), [FrontEndSe
 
 ## Application manifest elements
 ### ApplicationManifest Element
-Declaratively describes the application type and version. One or more service manifests of the constituent services are referenced to compose an application type. Configuration settings of the constituent services can be overridden using parameterized application settings. Default services, service templates, principals, policies, diagnostics set-up, and certificates can also declared at the application level. For more information, see [ApplicationManifest Element](service-fabric-service-model-schema-elements.md#ApplicationManifestElementApplicationManifestTypeComplexType)
+Declaratively describes the application type and version. One or more service manifests of the constituent services are referenced to compose an application type. Configuration settings of the constituent services can be overridden using parameterized application settings. Default services, service templates, principals, policies, diagnostics set-up, and certificates can also be declared at the application level. For more information, see [ApplicationManifest Element](service-fabric-service-model-schema-elements.md#ApplicationManifestElementApplicationManifestTypeComplexType)
 
 ### Parameters Element
 Declares the parameters that are used in this application manifest. The value of these parameters can be supplied when the application is instantiated and can be used to override application or service configuration settings. For more information, see [Parameters Element](service-fabric-service-model-schema-elements.md#ParametersElementanonymouscomplexTypeComplexTypeDefinedInApplicationManifestTypecomplexType)
@@ -299,7 +299,7 @@ Windows Server containers may not be compatible across different versions of the
         is assumed to work across all versions of the OS and overrides the image specified in the service manifest. For more information, see [ImageOverrides Element](service-fabric-service-model-schema-elements.md#ImageOverridesElementImageOverridesTypeComplexTypeDefinedInContainerHostPoliciesTypecomplexType)
 
 ### Image Element
-Container image corresponding to OS build version number to be launched. If the Os attribute is not specified, the container image
+Container image corresponding to OS build version number to be launched. If the OS attribute is not specified, the container image
             is assumed to work across all versions of the OS and overrides the image specified in the service manifest. For more information, see [Image Element](service-fabric-service-model-schema-elements.md#ImageElementImageTypeComplexTypeDefinedInImageOverridesTypecomplexType)
 
 ### EnvironmentOverrides Element
diff --git a/articles/service-fabric/service-fabric-manifest-example-reliable-services-app.md b/articles/service-fabric/service-fabric-manifest-example-reliable-services-app.md
@@ -270,7 +270,7 @@ See [Application manifest elements](#application-manifest-elements), [VotingWeb
 
 ## Application manifest elements
 ### ApplicationManifest Element
-Declaratively describes the application type and version. One or more service manifests of the constituent services are referenced to compose an application type. Configuration settings of the constituent services can be overridden using parameterized application settings. Default services, service templates, principals, policies, diagnostics set-up, and certificates can also declared at the application level. For more information, see [ApplicationManifest Element](service-fabric-service-model-schema-elements.md#ApplicationManifestElementApplicationManifestTypeComplexType)
+Declaratively describes the application type and version. One or more service manifests of the constituent services are referenced to compose an application type. Configuration settings of the constituent services can be overridden using parameterized application settings. Default services, service templates, principals, policies, diagnostics set-up, and certificates can also be declared at the application level. For more information, see [ApplicationManifest Element](service-fabric-service-model-schema-elements.md#ApplicationManifestElementApplicationManifestTypeComplexType)
 
 ### Parameters Element
 Declares the parameters that are used in this application manifest. The value of these parameters can be supplied when the application is instantiated and can be used to override application or service configuration settings. For more information, see [Parameters Element](service-fabric-service-model-schema-elements.md#ParametersElementanonymouscomplexTypeComplexTypeDefinedInApplicationManifestTypecomplexType)
diff --git a/articles/service-fabric/service-fabric-migrate-old-javaapp-to-use-maven.md b/articles/service-fabric/service-fabric-migrate-old-javaapp-to-use-maven.md
@@ -1,6 +1,6 @@
 ---
 title: Migrate from Java SDK to Maven
-description: Update the older Java applications which used to use the Service Fabric Java SDK, to fetch Service Fabric Java dependencies from Maven. After completing this setup, your older Java applications would be able to build .
+description: Update the older Java applications which used to use the Service Fabric Java SDK, to fetch Service Fabric Java dependencies from Maven. After completing this setup, your older Java applications would be able to build.
 ms.topic: how-to
 ms.author: tomcassidy
 author: tomvcassidy
diff --git a/articles/service-fabric/service-fabric-node-transition-apis.md b/articles/service-fabric/service-fabric-node-transition-apis.md
@@ -21,7 +21,7 @@ As described earlier, a *stopped* Service Fabric node is a node intentionally ta
 
 In addition, some errors returned by these APIs are not as descriptive as they could be.  For example, invoking the Stop Node API on an already *stopped* node will return the error *InvalidAddress*.  This experience could be improved.
 
-Also, the duration a node is stopped for is "infinite" until the Start Node API is invoked.  We've found this can cause problems and may be error-prone.  For example, we've seen problems where a user invoked the Stop Node API on a node and then forgot about it.  Later, it was unclear if the node was *down* or *stopped*.
+Also, the duration a node remains stopped for is "infinite" until the Start Node API is invoked.  We've found this can cause problems and may be error-prone.  For example, we've seen problems where a user invoked the Stop Node API on a node and then forgot about it.  Later, it was unclear if the node was *down* or *stopped*.
 
 
 ## Introducing the Node Transition APIs
@@ -30,7 +30,7 @@ We've addressed these issues above in a new set of APIs.  The new Node Transitio
 
 **Usage**
 
-If the Node Transition API does not throw an exception when invoked, then the system has accepted the asynchronous operation, and will execute it.  A successful call does not imply the operation is finished yet.  To get information about the current state of the operation, call the Node Transition Progress API (managed: [GetNodeTransitionProgressAsync()][gntp]) with the guid used when invoking Node Transition API for this operation.  The Node Transition Progress API returns an NodeTransitionProgress object.  This object's State property specifies the current state of the operation.  If the state is "Running", then the operation is executing.  If it is Completed, the operation finished without error.  If it is Faulted, there was a problem executing the operation.  The Result property's Exception property will indicate what the issue was.  See [TestCommandProgressState Enum](/dotnet/api/system.fabric.testcommandprogressstate) for more information about the State property, and the "Sample Usage" section below for code examples.
+If the Node Transition API does not throw an exception when invoked, then the system has accepted the asynchronous operation, and will execute it.  A successful call does not imply the operation is finished yet.  To get information about the current state of the operation, call the Node Transition Progress API (managed: [GetNodeTransitionProgressAsync()][gntp]) with the guid used when invoking Node Transition API for this operation.  The Node Transition Progress API returns a NodeTransitionProgress object.  This object's State property specifies the current state of the operation.  If the state is "Running", then the operation is executing.  If it is Completed, the operation finished without error.  If it is Faulted, there was a problem executing the operation.  The Result property's Exception property will indicate what the issue was.  See [TestCommandProgressState Enum](/dotnet/api/system.fabric.testcommandprogressstate) for more information about the State property, and the "Sample Usage" section below for code examples.
 
 **Differentiating between a stopped node and a down node**
 If a node is *stopped* using the Node Transition API, the output of a node query (managed: [GetNodeListAsync()][nodequery], PowerShell: [Get-ServiceFabricNode][nodequeryps]) will show that this node has an *IsStopped* property value of true.  Note this is different from the value of the *NodeStatus* property, which will say *Down*.  If the *NodeStatus* property has a value of *Down*, but *IsStopped* is false, then the node was not stopped using the Node Transition API, and is *Down* due to some other reason.  If the *IsStopped* property is true, and the *NodeStatus* property is *Down*, then it was stopped using the Node Transition API.
diff --git a/articles/service-fabric/service-fabric-quickstart-dotnet.md b/articles/service-fabric/service-fabric-quickstart-dotnet.md
@@ -22,7 +22,7 @@ Using this application you learn how to:
 * Use ASP.NET core as a web front end
 * Store application data in a stateful service
 * Debug your application locally
-* Scale-out the application across multiple nodes
+* Scale out the application across multiple nodes
 * Perform a rolling application upgrade
 
 ## Prerequisites
@@ -182,7 +182,7 @@ In this quickstart, you learned how to:
 * Use ASP.NET core as a web front end
 * Store application data in a stateful service
 * Debug your application locally
-* Scale-out the application across multiple nodes
+* Scale out the application across multiple nodes
 * Perform a rolling application upgrade
 
 To learn more about Service Fabric and .NET, take a look at this tutorial:
diff --git a/articles/service-fabric/service-fabric-quickstart-java-reliable-services.md b/articles/service-fabric/service-fabric-quickstart-java-reliable-services.md
@@ -89,7 +89,7 @@ In this quickstart, you learned how to:
 
 * Use Eclipse as a tool for your Service Fabric Java applications
 * Deploy Java applications to your local cluster
-* Scale-out the application across multiple nodes
+* Scale out the application across multiple nodes
 
 To learn more about working with Java apps in Service Fabric, continue to the tutorial for Java apps.
 
diff --git a/articles/service-fabric/service-fabric-quickstart-java-spring-boot.md b/articles/service-fabric/service-fabric-quickstart-java-spring-boot.md
@@ -10,7 +10,7 @@ ms.date: 07/11/2022
 ---
 # Quickstart: Deploy a Java Spring Boot app on Azure Service Fabric
 
-In this quickstart, you deploy a Java Spring Boot application to Azure Service Fabric by using familiar command-line tools on Linux or MacOS. Azure Service Fabric is a distributed systems platform for deploying and managing microservices and containers. 
+In this quickstart, you deploy a Java Spring Boot application to Azure Service Fabric by using familiar command-line tools on Linux or macOS. Azure Service Fabric is a distributed systems platform for deploying and managing microservices and containers. 
 
 ## Prerequisites
 
@@ -20,7 +20,7 @@ In this quickstart, you deploy a Java Spring Boot application to Azure Service F
 - [Service Fabric SDK & Service Fabric Command Line Interface (CLI)](./service-fabric-get-started-linux.md#installation-methods)
 - [Git](https://git-scm.com/downloads)
 
-#### [MacOS](#tab/macos)
+#### [macOS](#tab/macos)
 
 - [Java environment and Yeoman](./service-fabric-get-started-mac.md#create-your-application-on-your-mac-by-using-yeoman)
 - [Service Fabric SDK & Service Fabric Command Line Interface (CLI)](./service-fabric-cli.md#cli-mac)
@@ -191,7 +191,7 @@ In this quickstart, you learned how to:
 
 * Deploy a Spring Boot application to Service Fabric
 * Deploy the application to your local cluster
-* Scale-out the application across multiple nodes
+* Scale out the application across multiple nodes
 * Perform failover of your service with no hit to availability
 
 To learn more about working with Java apps in Service Fabric, continue to the tutorial for Java apps.
diff --git a/articles/service-fabric/service-fabric-reliable-actors-access-save-remove-state.md b/articles/service-fabric/service-fabric-reliable-actors-access-save-remove-state.md
@@ -314,6 +314,6 @@ class MyActorImpl extends FabricActor implements  MyActor
 
 ## Next steps
 
-State that's stored in Reliable Actors must be serialized before its written to disk and replicated for high availability. Learn more about [Actor type serialization](service-fabric-reliable-actors-notes-on-actor-type-serialization.md).
+State that's stored in Reliable Actors must be serialized before it's written to disk and replicated for high availability. Learn more about [Actor type serialization](service-fabric-reliable-actors-notes-on-actor-type-serialization.md).
 
 Next, learn more about [Actor diagnostics and performance monitoring](service-fabric-reliable-actors-diagnostics.md).
diff --git a/articles/service-fabric/service-fabric-reliable-actors-backup-and-restore.md b/articles/service-fabric/service-fabric-reliable-actors-backup-and-restore.md
@@ -1,6 +1,6 @@
 ---
-title: Backup and restore Azure Service Fabric actors 
-description: Learn how to implement backup and restore in your Azure Service Fabric actors.
+title: Back up and restore Azure Service Fabric actors 
+description: Learn how to implement back up and restore in your Azure Service Fabric actors.
 ms.topic: how-to
 ms.author: tomcassidy
 author: tomvcassidy
@@ -10,10 +10,10 @@ ms.date: 07/11/2022
 ---
 
 
-# Implement Reliable Actors backup and restore
+# Implement Reliable Actors back up and restore
 
 > [!NOTE]
-> Microsoft recommends to use [Periodic backup and restore](service-fabric-backuprestoreservice-quickstart-azurecluster.md) for configuring data backup of Reliable Stateful services and Reliable Actors. 
+> Microsoft recommends to use [Periodic back up and restore](service-fabric-backuprestoreservice-quickstart-azurecluster.md) for configuring data backup of Reliable Stateful services and Reliable Actors. 
 > 
 
 In the following example, a custom actor service exposes a method to back up actor data by taking advantage of the remoting listener already present in `ActorService`:
diff --git a/articles/service-fabric/service-fabric-reliable-actors-fabrictransportsettings.md b/articles/service-fabric/service-fabric-reliable-actors-fabrictransportsettings.md
@@ -118,7 +118,7 @@ If the client is not running as part of a service, you can create a "&lt;Client
   </Section>
    ```
   * Configuring FabricTransport  Settings for Securing Actor Service/Client Using Subject Name.
-	User needs to provide findType as FindBySubjectName,add CertificateIssuerThumbprints and CertificateRemoteCommonNames values.
+	User needs to provide findType as FindBySubjectName, add CertificateIssuerThumbprints and CertificateRemoteCommonNames values.
     Below is the example for the Listener TransportSettings.
 
     ```xml
diff --git a/articles/service-fabric/service-fabric-reliable-actors-introduction.md b/articles/service-fabric/service-fabric-reliable-actors-introduction.md
@@ -35,7 +35,7 @@ Service Fabric actors are virtual, meaning that their lifetime is not tied to th
 This virtual actor lifetime abstraction carries some caveats as a result of the virtual actor model, and in fact the Reliable Actors implementation deviates at times from this model.
 
 * An actor is automatically activated (causing an actor object to be constructed) the first time a message is sent to its actor ID. After some period of time, the actor object is garbage collected. In the future, using the actor ID again, causes a new actor object to be constructed. An actor's state outlives the object's lifetime when stored in the state manager.
-* Calling any actor method for an actor ID activates that actor. For this reason, actor types have their constructor called implicitly by the runtime. Therefore, client code cannot pass parameters to the actor type's constructor, although parameters may be passed to the actor's constructor by the service itself. The result is that actors may be constructed in a partially-initialized state by the time other methods are called on it, if the actor requires initialization parameters from the client. There is no single entry point for the activation of an actor from the client.
+* Calling any actor method for an actor ID activates that actor. For this reason, actor types have their constructor called implicitly by the runtime. Therefore, client code cannot pass parameters to the actor type's constructor, although parameters may be passed to the actor's constructor by the service itself. The result is that actors may be constructed in a partially initialized state by the time other methods are called on it, if the actor requires initialization parameters from the client. There is no single entry point for the activation of an actor from the client.
 * Although Reliable Actors implicitly create actor objects; you do have the ability to explicitly delete an actor and its state.
 
 ## Distribution and failover
@@ -98,7 +98,7 @@ The `ActorProxy`(C#) / `ActorProxyBase`(Java) class on the client side performs
 The Reliable Actors runtime provides a simple turn-based access model for accessing actor methods. This means that no more than one thread can be active inside an actor object's code at any time. Turn-based access greatly simplifies concurrent systems as there is no need for synchronization mechanisms for data access. It also means systems must be designed with special considerations for the single-threaded access nature of each actor instance.
 
 * A single actor instance cannot process more than one request at a time. An actor instance can cause a throughput bottleneck if it is expected to handle concurrent requests.
-* Actors can deadlock on each other if there is a circular request between two actors while an external request is made to one of the actors simultaneously. The actor runtime will automatically time out on actor calls and throw an exception to the caller to interrupt possible deadlock situations.
+* Actors can deadlock each other if there is a circular request between two actors while an external request is made to one of the actors simultaneously. The actor runtime will automatically time out on actor calls and throw an exception to the caller to interrupt possible deadlock situations.
 
 ![Reliable Actors communication][3]
 
