Fix issues

Author: vicancy

articles/azure-signalr/signalr-howto-use.md

@@ -10,15 +10,15 @@ ms.author: lianwei
 
 # Use Azure SignalR Service
 
-## Provision an Azure SignalR Service instance
+## Create an Azure SignalR Service instance
 
-Follow [Quickstart: Use an ARM template to deploy Azure SignalR](./signalr-quickstart-azure-signalr-service-arm-template.md) to provision a SignalR service instance.
+Follow [Quickstart: Use an ARM template to deploy Azure SignalR](./signalr-quickstart-azure-signalr-service-arm-template.md) to create a SignalR service instance.
 
 ## For ASP.NET Core SignalR
 
 ### 1. Install the SDK
 
-Run below command to install SignalR Service SDK to your ASP.NET Core project.
+Run the command to install SignalR Service SDK to your ASP.NET Core project.
 
 ```bash
 dotnet add package Microsoft.Azure.SignalR
@@ -48,7 +48,7 @@ There are two approaches to configure SignalR Service's connection string in you
 
 - Set an environment variable with name `Azure:SignalR:ConnectionString` or `Azure__SignalR__ConnectionString`.
   - In Azure App Service, put it in application settings.
-- Pass the connection string as a parameter of `AddAzureSignalR()` as below sample codes.
+- Pass the connection string as a parameter of `AddAzureSignalR()`.
 
     ```csharp
     services.AddSignalR()
@@ -69,17 +69,17 @@ There are a few [options](https://github.com/Azure/azure-signalr/blob/dev/src/Mi
 #### `ConnectionString`
 
 - Default value is the `Azure:SignalR:ConnectionString` `connectionString` or `appSetting` in `web.config` file.
-- It can be reconfigured, but please make sure the value is **NOT** hard coded.
+- It can be reconfigured, but make sure the value is **NOT** hard coded.
 
 #### `InitialHubServerConnectionCount`
 
 - Default value is `5`.
-- This option controls the initial count of connections per hub between application server and Azure SignalR Service. Usually keep it as the default value is enough. During runtime, the SDK might start new server connections for performance tuning or load balancing. When you have big number of clients, you can give it a larger number for better throughput. For example, if you have 100,000 clients in total, the connection count can be increased to `10` or `15`.
+- This option controls the initial count of connections per hub between application server and Azure SignalR Service. Usually keep it as the default value is enough. During runtime, the SDK might start new server connections for performance tuning or load balancing. When you have large number of clients, you can give it a larger number for better throughput. For example, if you have 100,000 clients in total, the connection count can be increased to `10` or `15`.
 
 #### `MaxHubServerConnectionCount`
 
 - Default value is `null`.
-- This option controls the max count of connections allowed per hub between application server and Azure SignalR Service. During runtime, the SDK might start new server connections for performance tuning or load balancing. By default a new server connection starts whenever needed. When the max allowed server connection count is configured, the SDK does not start new connections when server connection count reaches the limit.
+- This option controls the max count of connections allowed per hub between application server and Azure SignalR Service. During runtime, the SDK might start new server connections for performance tuning or load balancing. By default a new server connection starts whenever needed. When the max allowed server connection count is configured, the SDK doesn't start new connections when server connection count reaches the limit.
 
 #### `ApplicationName`
 
@@ -90,23 +90,23 @@ There are a few [options](https://github.com/Azure/azure-signalr/blob/dev/src/Mi
 
 - Default value is `null`.
 - This option controls what claims you want to associate with the client connection.
-It will be used when Service SDK generates access token for client in client's negotiate request.
-By default, all claims from `HttpContext.User` of the negotiate request will be reserved.
+It is used when Service SDK generates access token for client in client's negotiate request.
+By default, all claims from `HttpContext.User` of the negotiated request are reserved.
 They can be accessed at [`Hub.Context.User`](/dotnet/api/microsoft.aspnetcore.signalr.hubcallercontext.user).
-- Normally you should leave this option as is. Make sure you understand what will happen before customizing it.
+- Normally you should leave this option as is. Make sure you understand what happens before customizing it.
 
 #### `AccessTokenLifetime`
 
 - Default value is `1 hour`.
-- This option controls the valid lifetime of the access token, which is generated by Service SDK for each client.
+- This option controls the valid lifetime of the access token, that Service SDK generates for each client.
 The access token is returned in the response to client's negotiate request.
-- When `ServerSentEvent` or `LongPolling` is used as transport, client connection will be closed due to authentication failure after the expire time.
+- When `ServerSentEvent` or `LongPolling` is used as transport, client connection will be closed due to authentication failure after the expired time.
 You can increase this value to avoid client disconnect.
 
 #### `AccessTokenAlgorithm`
 
 - Default value is `HS256`
-- This option provides choice of [`SecurityAlgorithms`](https://github.com/AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet/blob/dev/src/Microsoft.IdentityModel.Tokens/SecurityAlgorithms.cs) when generate access token. Now supported optional values are `HS256` and `HS512`. Please note `HS512` is more secure but the generated token will be comparatively longer than that using `HS256`.
+- This option provides choice of [`SecurityAlgorithms`](https://github.com/AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet/blob/dev/src/Microsoft.IdentityModel.Tokens/SecurityAlgorithms.cs) when generate access token. Now supported optional values are `HS256` and `HS512`. Note `HS512` is more secure but the generated token is comparatively longer than that using `HS256`.
 
 #### `ServerStickyMode`