freshness updates: more article updating related articles linked to from signalr-concept-interals.md

cebundy · cebundy · commit 4a28efb420ff · 2023-02-16T09:10:10.000-08:00
diff --git a/articles/azure-signalr/concept-connection-string.md b/articles/azure-signalr/concept-connection-string.md
diff --git a/articles/azure-signalr/howto-network-access-control.md b/articles/azure-signalr/howto-network-access-control.md
@@ -36,14 +36,14 @@ You can manage network access control for Azure SignalR Service through the Azur
 
 1. Go to the Azure SignalR Service you want to secure.
 
-1. Click on the settings menu called **Network access control**.
+1. Select on the settings menu called **Network access control**.
 
     ![Network ACL on portal](media/howto-network-access-control/portal.png)
 
 1. To edit default action, toggle the **Allow/Deny** button.
 
     > [!TIP]
-    > Default action is the action we take when there is no ACL rule matches. For example, if the default action is **Deny**, then request types that are not explicitly approved below will be denied.
+    > The default action is the action the service takes when there is no ACL rule matches. For example, if the default action is **Deny**, then the request types that are not explicitly approved will be denied.
 
 1. To edit public network rule, select allowed types of requests under **Public network**.
 
@@ -53,7 +53,7 @@ You can manage network access control for Azure SignalR Service through the Azur
 
     ![Edit private endpoint ACL on portal ](media/howto-network-access-control/portal-private-endpoint.png)
 
-1. Click **Save** to apply your changes.
+1. Select **Save** to apply your changes.
 
 ## Next steps
 
diff --git a/articles/azure-signalr/signalr-concept-internals.md b/articles/azure-signalr/signalr-concept-internals.md
@@ -28,7 +28,7 @@ A self-hosted ASP.NET Core SignalR application server listens to and connects cl
 With SignalR Service, the application server no longer accepts persistent client connections, instead:
 
 1. A `negotiate` endpoint is exposed by Azure SignalR Service SDK for each hub.
-1. The endpoint will respond to client's negotiation requests and redirect clients to SignalR Service.
+1. The endpoint responds to client's negotiation requests and redirect clients to SignalR Service.
 1. The clients connect to SignalR Service.
 
 For more information, see [Client connections](#client-connections).
@@ -82,14 +82,14 @@ To learn more about ASP.NET Core SignalR's, see [Transport Protocols](https://gi
 
 ## Data transmission between client and server
 
-When a client is connected to the SignalR Service, the service runtime will find a server connection to serve this client.
+When a client is connected to the SignalR Service, the service runtime finds a server connection to serve this client.
 
 - This step happens only once, and is a one-to-one mapping between the client and server connection.
 - The mapping is maintained in SignalR Service until the client or server disconnects.
 
 At this point, the application server receives an event with information from the new client. A logical connection to the client is created in the application server. The data channel is established from client to application server, via SignalR Service.
 
-SignalR Service transmits data from the client to the pairing application server. Data from the application server will be sent to the mapped clients.
+SignalR Service transmits data from the client to the pairing application server. Data from the application server is sent to the mapped clients.
 
 SignalR Service doesn't save or store customer data, all customer data received is transmitted to target server or clients in real-time.
 
diff --git a/articles/azure-signalr/signalr-howto-authorize-managed-identity.md b/articles/azure-signalr/signalr-howto-authorize-managed-identity.md
@@ -1,5 +1,5 @@
 ---
-title: Authorize request to SignalR resources with Azure AD from managed identities
+title: Authorize managed identity requests to a SignalR resource
 description: This article provides information about authorizing request to SignalR resources with Azure AD from managed identities
 author: vicancy
 ms.author: lianwei
@@ -10,7 +10,7 @@ ms.devlang: csharp
 ms.custom: subject-rbac-steps
 ---
 
-# Authorize request to SignalR resources with Azure AD from managed identities
+# Authorize managed identity requests to a SignalR resource
 
 Azure SignalR Service supports Azure Active Directory (Azure AD) authorizing requests from Azure resources using [Managed identities for Azure resources
 ](../active-directory/managed-identities-azure-resources/overview.md).
diff --git a/articles/azure-signalr/signalr-howto-key-rotation.md b/articles/azure-signalr/signalr-howto-key-rotation.md
@@ -1,19 +1,18 @@
 ---
-title: How to rotate access key for Azure SignalR Service
+title: Rotate access keys for Azure SignalR Service
 description: An overview on why the customer needs to routinely rotate the access keys and how to do it with the Azure portal GUI and the Azure CLI.
 author: vicancy
 ms.service: signalr
 ms.topic: how-to
 ms.date: 07/18/2022
 ms.author: lianwei
 ---
-# How to rotate access key for Azure SignalR Service
+# Rotate access keys for Azure SignalR Service
 
-Each Azure SignalR Service instance has a pair of access keys called Primary and Secondary keys. They're used to authenticate SignalR clients when requests are made to the service. The keys are associated with the instance endpoint URL. Keep your keys secure, and rotate them regularly. You're provided with two access keys so that you can maintain connections by using one key while regenerating the other.
+For security reasons and compliance requirements, it is important to routinely rotate your access keys. This article describes how to rotate access keys for Azure SignalR Service.
 
-## Why rotate access keys?
+Each Azure SignalR Service instance has a primary and a secondary key. They're used to authenticate SignalR clients when requests are made to the service. The keys are associated with the instance endpoint URL. Keep your keys secure, and rotate them regularly. You're provided with two access keys so that you can maintain connections by using one key while regenerating the other.
 
-For security reasons and compliance requirements, routinely rotate your access keys.
 
 ## Regenerate access keys
 
@@ -41,16 +40,12 @@ You also can regenerate keys by using the [Azure CLI](/cli/azure/signalr/key#az-
 
 ## Forced access key regeneration
 
-Azure SignalR Service might enforce a mandatory access key regeneration under certain situations. The service notifies customers via email and portal notification. If you receive this communication or encounter service failure due to an access key, rotate the keys by following the instructions in this guide.
+The Azure SignalR Service can enforce a mandatory access key regeneration under certain situations. The service notifies customers of mandatory key regeneration via email and portal notification. If you receive this communication or encounter service failure due to an access key, rotate the keys by following the instructions in this guide.
 
 ## Next steps
 
-Rotate your access keys regularly as a good security practice.
-
-In this guide, you learned how to regenerate access keys. Continue to the next tutorials about authentication with OAuth or with Azure Functions.
-
 > [!div class="nextstepaction"]
-> [Integrate with ASP.NET core identity](./signalr-concept-authenticate-oauth.md)
+> [Azure SignalR Service authentication](./signalr-concept-authenticate-oauth.md)
 
 > [!div class="nextstepaction"]
 > [Build a serverless real-time app with authentication](./signalr-tutorial-authenticate-azure-functions.md)
diff --git a/articles/azure-signalr/signalr-howto-scale-multi-instances.md b/articles/azure-signalr/signalr-howto-scale-multi-instances.md
@@ -9,12 +9,13 @@ ms.custom: devx-track-csharp
 ms.date: 07/18/2022
 ms.author: lianwei
 ---
-# How to scale SignalR Service with multiple instances?
+# Scale SignalR Service with multiple instances
+
 SignalR Service SDK supports multiple endpoints for SignalR Service instances. You can use this feature to scale the concurrent connections, or use it for cross-region messaging.
 
 ## For ASP.NET Core
 
-### How to add multiple endpoints from config?
+### Add multiple endpoints from config
 
 Config with key `Azure:SignalR:ConnectionString` or `Azure:SignalR:ConnectionString:` for SignalR Service connection string.
 
@@ -28,9 +29,9 @@ dotnet user-secrets set Azure:SignalR:ConnectionString:east-region-b:primary <Co
 dotnet user-secrets set Azure:SignalR:ConnectionString:backup:secondary <ConnectionString3>
 ```
 
-### How to add multiple endpoints from code?
+### Add multiple endpoints from code
 
-A `ServicEndpoint` class is introduced to describe the properties of an Azure SignalR Service endpoint.
+A `ServicEndpoint` class describes the properties of an Azure SignalR Service endpoint.
 You can configure multiple instance endpoints when using Azure SignalR Service SDK through:
 ```cs
 services.AddSignalR()
@@ -49,23 +50,25 @@ services.AddSignalR()
         });
 ```
 
-### How to customize endpoint router?
+### Customize endpoint router
 
 By default, the SDK uses the [DefaultEndpointRouter](https://github.com/Azure/azure-signalr/blob/dev/src/Microsoft.Azure.SignalR/EndpointRouters/DefaultEndpointRouter.cs) to pick up endpoints.
 
 #### Default behavior 
-1. Client request routing
+
+1. Client request routing:
 
     When client `/negotiate` with the app server. By default, SDK **randomly selects** one endpoint from the set of available service endpoints.
 
-2. Server message routing
+2. Server message routing:
 
-    When sending a message to a specific *connection* and the target connection is routed to current server, the message goes directly to that connected endpoint. Otherwise, the messages are broadcasted to every Azure SignalR endpoint.
+    When sending a message to a specific *connection* and the target connection is routed to the current server, the message goes directly to that connected endpoint. Otherwise, the messages are broadcasted to every Azure SignalR endpoint.
 
 #### Customize routing algorithm
+
 You can create your own router when you have special knowledge to identify which endpoints the messages should go to.
 
-A custom router is defined below as an example when groups starting with `east-` always go to the endpoint named `east`:
+The following example defines a custom router that routes messages with a group starting with `east-` to the endpoint named `east`:
 
 ```cs
 private class CustomRouter : EndpointRouterDecorator
@@ -83,12 +86,11 @@ private class CustomRouter : EndpointRouterDecorator
 }
 ```
 
-Another example below, that overrides the default negotiate behavior, to select the endpoints depends on where the app server is located.
+The following example overrides the default negotiate behavior and selects the endpoint depending on the location of the app server.
 
 ```cs
 private class CustomRouter : EndpointRouterDecorator
-{
-    public override ServiceEndpoint GetNegotiateEndpoint(HttpContext context, IEnumerable<ServiceEndpoint> endpoints)
+{    public override ServiceEndpoint GetNegotiateEndpoint(HttpContext context, IEnumerable<ServiceEndpoint> endpoints)
     {
         // Override the negotiate behavior to get the endpoint from query string
         var endpointName = context.Request.Query["endpoint"];
@@ -125,7 +127,7 @@ services.AddSignalR()
 
 ## For ASP.NET
 
-### How to add multiple endpoints from config?
+### Add multiple endpoints from config
 
 Config with key `Azure:SignalR:ConnectionString` or `Azure:SignalR:ConnectionString:` for SignalR Service connection string.
 
@@ -146,9 +148,9 @@ You can add multiple instance connection strings to `web.config`:
 </configuration>
 ```
 
-### How to add multiple endpoints from code?
+### Add multiple endpoints from code
 
-A `ServicEndpoint` class is introduced to describe the properties of an Azure SignalR Service endpoint.
+A `ServicEndpoint` class describes the properties of an Azure SignalR Service endpoint.
 You can configure multiple instance endpoints when using Azure SignalR Service SDK through:
 
 ```cs
@@ -167,11 +169,11 @@ app.MapAzureSignalR(
         });
 ```
 
-### How to customize router?
+### Customize a router
 
 The only difference between ASP.NET SignalR and ASP.NET Core SignalR is the http context type for `GetNegotiateEndpoint`. For ASP.NET SignalR, it is of [IOwinContext](https://github.com/Azure/azure-signalr/blob/dev/src/Microsoft.Azure.SignalR.AspNet/EndpointRouters/DefaultEndpointRouter.cs#L19) type.
 
-Below is the custom negotiate example for ASP.NET SignalR:
+The following code is a custom negotiate example for ASP.NET SignalR:
 
 ```cs
 private class CustomRouter : EndpointRouterDecorator
@@ -211,15 +213,15 @@ app.MapAzureSignalR(GetType().FullName, hub, options => {
 
 ## Service Endpoint Metrics
 
-To enable advanced router, SignalR server SDK provides multiple metrics to help server do smart decision. The properties are under `ServiceEndpoint.EndpointMetrics`.
+To enable an advanced router, SignalR server SDK provides multiple metrics to help server make smart decisions. The properties are under `ServiceEndpoint.EndpointMetrics`.
 
 | Metric Name | Description |
-| -- | -- |
-| `ClientConnectionCount` | Total concurrent connected client connection count on all hubs for the service endpoint |
-| `ServerConnectionCount` | Total concurrent connected server connection count on all hubs for the service endpoint |
+|--|--|
+| `ClientConnectionCount` | Total count concurrent client connections on all hubs for the service endpoint |
+| `ServerConnectionCount` | Total count of concurrent server connections on all hubs for the service endpoint |
 | `ConnectionCapacity` | Total connection quota for the service endpoint, including client and server connections |
 
-Below is an example to customize router according to `ClientConnectionCount`.
+The following code is an example of customizing a router according to `ClientConnectionCount`.
 
 ```cs
 private class CustomRouter : EndpointRouterDecorator
@@ -247,29 +249,27 @@ From SDK version 1.5.0, we're enabling dynamic scale ServiceEndpoints for ASP.NE
 
 The `ServiceEndpoint` object has an `EndpointType` property with value `primary` or `secondary`.
 
-`primary` endpoints are preferred endpoints to receive client traffic, and are considered to have more reliable network connections; `secondary` endpoints are considered to have less reliable network connections and are used only for taking server to client traffic, for example, broadcasting messages, not for taking client to server traffic.
+`primary` endpoints are preferred endpoints to receive client traffic because they've have more reliable network connections. `secondary` endpoints have less reliable network connections and are used only for server to client traffic.  For example, secondary endpoints are used for broadcasting messages instead of client to server traffic.
 
-In cross-region cases, network can be unstable. For one app server located in *East US*, the SignalR Service endpoint located in the same *East US* region can be configured as `primary` and endpoints in other regions marked as `secondary`. In this configuration, service endpoints in other regions can **receive** messages from this *East US* app server, but there will be no **cross-region** clients routed to this app server. The architecture is shown in the diagram below:
+In cross-region cases, the network can be unstable. For an app server located in *East US*, the SignalR Service endpoint located in the same *East US* region is `primary` and endpoints in other regions marked as `secondary`. In this configuration, service endpoints in other regions can **receive** messages from this *East US* app server, but no **cross-region** clients are routed to this app server. The following diagram shows the architecture:
 
 ![Cross-Geo Infra](./media/signalr-howto-scale-multi-instances/cross_geo_infra.png)
 
-When a client tries `/negotiate` with the app server, with the default router, SDK **randomly selects** one endpoint from the set of available `primary` endpoints. When the primary endpoint isn't available, SDK then **randomly selects** from all available `secondary` endpoints. The endpoint is marked as **available** when the connection between server and the service endpoint is alive.
+When a client tries `/negotiate` with the app server with a default router, the SDK **randomly selects** one endpoint from the set of available `primary` endpoints. When the primary endpoint isn't available, the SDK then **randomly selects** from all available `secondary` endpoints. The endpoint is marked as **available** when the connection between server and the service endpoint is alive.
 
-In cross-region scenario, when a client tries `/negotiate` with the app server hosted in *East US*, by default it always returns the `primary` endpoint located in the same region. When all *East US* endpoints aren't available, the client is redirected to endpoints in other regions. Fail over section below describes the scenario in detail.
+In cross-region scenario, when a client tries `/negotiate` with the app server hosted in *East US*, by default it always returns the `primary` endpoint located in the same region. When all *East US* endpoints aren't available, the router redirects the client to endpoints in other regions. The following [failover](#failover) section describes the scenario in detail.
 
 ![Normal Negotiate](./media/signalr-howto-scale-multi-instances/normal_negotiate.png)
 
-## Fail-over
+## Failover
 
-When all `primary` endpoints aren't available, client's `/negotiate` picks from the available `secondary` endpoints. This fail-over mechanism requires that each endpoint should serve as `primary` endpoint to at least one app server.
+When no `primary` endpoint is available, the client's `/negotiate` picks from the available `secondary` endpoints. This failover mechanism requires that each endpoint serves as a `primary` endpoint to at least one app server.
 
-![Fail-over](./media/signalr-howto-scale-multi-instances/failover_negotiate.png)
+![Failover](./media/signalr-howto-scale-multi-instances/failover_negotiate.png)
 
 ## Next steps
 
-In this guide, you learned about how to configure multiple instances in the same application for scaling, sharding, and cross-region scenarios.
-
-Multiple endpoints supports can also be used in high availability and disaster recovery scenarios.
+You can use multiple endpoints in high availability and disaster recovery scenarios.
 
 > [!div class="nextstepaction"]
 > [Setup SignalR Service for disaster recovery and high availability](./signalr-concept-disaster-recovery.md)
diff --git a/articles/azure-signalr/signalr-reference-data-plane-rest-api.md b/articles/azure-signalr/signalr-reference-data-plane-rest-api.md
@@ -93,7 +93,7 @@ The difference is, in this scenario the JWT Token is generated by Azure Active D
 
 You could also use **Role Based Access Control (RBAC)** to authorize the request from your client/server to SignalR Service.
 
-[Learn how to configure Role-based access control roles for your resource](/azure/azure-signalr/authorize-access-azure-active-directory)
+For more information, see [Authorize access with Azure Active Directory for Azure SignalR Service](./signalr-concept-authorize-azure-active-directory.md)
 
 ### Implement Negotiate Endpoint
 
