resolve comments

Author: vicancy

articles/azure-signalr/signalr-howto-reverse-proxy-overview.md

@@ -14,7 +14,7 @@ A reverse proxy server can be used in front of Azure SignalR Service. Reverse pr
 
 A common architecture using a reverse proxy server with Azure SignalR is as below:
 
-:::image type="content" source="./media/signalr-howto-reverse-proxy-overview/architecture.png" alt-text="Architecture using  Azure SignalR with a reverse proxy server.":::   
+:::image type="content" source="./media/signalr-howto-reverse-proxy-overview/architecture.png" alt-text="Diagram that shows the architecture using Azure SignalR with a reverse proxy server.":::   
 
 ## General practices
 There are several general practices to follow when using a reverse proxy in front of SignalR Service.

articles/azure-signalr/signalr-howto-work-with-app-gateway.md

@@ -21,7 +21,7 @@ This article contains two parts,
 * [The first part](#set-up-and-configure-application-gateway) shows how to configure Application Gateway so that the clients can access SignalR through Application Gateway.
 * [The second part](#secure-signalr-service) shows how to secure SignalR Service by adding access control to SignalR Service and only allow traffic from Application Gateway.
 
-:::image type="content" source="./media/signalr-howto-work-with-app-gateway/architecture.png" alt-text="The architecture of using SignalR Service with Application Gateway.":::
+:::image type="content" source="./media/signalr-howto-work-with-app-gateway/architecture.png" alt-text="Diagram that shows the architecture of using SignalR Service with Application Gateway.":::
 
 ## Set up and configure Application Gateway
 
@@ -45,20 +45,20 @@ Create from the portal an Application Gateway instance **_AG1_**:
 
     - Accept the default values for the other settings and then select **Next: Frontends**
 
-    :::image type="content" source="./media/signalr-howto-work-with-app-gateway/basics.png" alt-text="Create Application Gateway instance with Basics tab.":::  
+    :::image type="content" source="./media/signalr-howto-work-with-app-gateway/basics.png" alt-text="Screenshot of creating Application Gateway instance with Basics tab.":::  
 
 * On the **Frontends** tab:
     - **Frontend IP address type**: **Public**.
     - Select **Add new** for the **Public IP address** and enter *myAGPublicIPAddress* for the public IP address name, and then select **OK**.
     - Select **Next: Backends**
-    :::image type="content" source="./media/signalr-howto-work-with-app-gateway/application-gateway-create-frontends.png" alt-text="Create Application Gateway instance with Frontends tab.":::  
+    :::image type="content" source="./media/signalr-howto-work-with-app-gateway/application-gateway-create-frontends.png" alt-text="Screenshot of creating Application Gateway instance with Frontends tab.":::  
 
 *  On the **Backends** tab, select **Add a backend pool**:
     - **Name**: Enter **_signalr_** for the SignalR Service resource backend pool.
     - Backend targets **Target**: the **host name** of your SignalR Service instance **_ASRS1_**, for example `asrs1.service.signalr.net`
     - Select **Next: Configuration**
 
-    :::image type="content" source="./media/signalr-howto-work-with-app-gateway/application-gateway-create-backends.png" alt-text="Set up the application gateway backend pool for the SignalR Service.":::  
+    :::image type="content" source="./media/signalr-howto-work-with-app-gateway/application-gateway-create-backends.png" alt-text="Screenshot of setting up the application gateway backend pool for the SignalR Service.":::  
 
 * On the **Configuration** tab, select **Add a routing rule** in the **Routing rules** column:
     - **Rule name**: **_myRoutingRule_** 
@@ -70,7 +70,7 @@ Create from the portal an Application Gateway instance **_AG1_**:
             * We use the HTTP frontend protocol on Application Gateway in this article to simplify the demo and help you get started easier. But in reality, you may need to enable HTTPs and Customer Domain on it with production scenario.
         - Accept the default values for the other settings on the **Listener** tab
 
-        :::image type="content" source="./media/signalr-howto-work-with-app-gateway/application-gateway-create-rule-listener.png" alt-text="Set up the application gateway routing rule listener tab for the SignalR Service.":::  
+        :::image type="content" source="./media/signalr-howto-work-with-app-gateway/application-gateway-create-rule-listener.png" alt-text="Screenshot of setting up the application gateway routing rule listener tab for the SignalR Service.":::  
     - On the **Backend targets** tab, use the following values:
         * **Target type**: Backend pool 
         * **Backend target**: select **signalr** we previously created
@@ -82,19 +82,19 @@ Create from the portal an Application Gateway instance **_AG1_**:
             * **Host name override**: **Pick host name from backend target**
             * Others keep the default values
 
-            :::image type="content" source="./media/signalr-howto-work-with-app-gateway/application-gateway-setup-backend.png" alt-text="Set up the application gateway backend setting for the SignalR Service.":::
+            :::image type="content" source="./media/signalr-howto-work-with-app-gateway/application-gateway-setup-backend.png" alt-text="Screenshot of setting up the application gateway backend setting for the SignalR Service.":::
 
-        :::image type="content" source="./media/signalr-howto-work-with-app-gateway/application-gateway-create-rule-backends.png" alt-text="Creating backend targets for application gateway.":::  
+        :::image type="content" source="./media/signalr-howto-work-with-app-gateway/application-gateway-create-rule-backends.png" alt-text="Screenshot of creating backend targets for application gateway.":::  
 
 * Review and create the **_AG1_**
 
-    :::image type="content" source="./media/signalr-howto-work-with-app-gateway/application-gateway-review.png" alt-text="Review and create the application gateway instance.":::   
+    :::image type="content" source="./media/signalr-howto-work-with-app-gateway/application-gateway-review.png" alt-text="Screenshot of reviewing and creating the application gateway instance.":::   
 
 ### Configure Application Gateway health probe
 
 When **_AG1_** is created, go to **Health probes** tab under **Settings** section in the portal, change the health probe path to `/api/health`
 
-:::image type="content" source="./media/signalr-howto-work-with-app-gateway/health-probe.png" alt-text="Set up the application gateway backend health probe for the SignalR Service.":::
+:::image type="content" source="./media/signalr-howto-work-with-app-gateway/health-probe.png" alt-text="Screenshot of setting up the application gateway backend health probe for the SignalR Service.":::
 
 ### Quick test
 
@@ -111,7 +111,7 @@ When **_AG1_** is created, go to **Health probes** tab under **Settings** sectio
     ```
 * Go to the Overview tab of **_AG1_**, and find out the Frontend public IP address 
 
-    :::image type="content" source="./media/signalr-howto-work-with-app-gateway/quick-test.png" alt-text="Quick test SignalR Service health endpoint through Application Gateway.":::
+    :::image type="content" source="./media/signalr-howto-work-with-app-gateway/quick-test.png" alt-text="Screenshot of quick testing SignalR Service health endpoint through Application Gateway.":::
 
 * Visit the health endpoint through **_AG1_** `http://<frontend-public-IP-address>/client`, and it also returns *400* with error message *'hub' query parameter is required.* It means the request successfully went through Application Gateway to SignalR Service and did the request validation.
 
@@ -135,7 +135,7 @@ Now, the traffic can reach SignalR Service through the Application Gateway. The
         * **Client endpoint**: Enter the URL using frontend public IP address of **_AG1_**, for example `http://20.88.8.8`. It's a connection string generator when using reverse proxies, and the value isn't preserved when next time you come back to this tab. When value entered, the connection string appends a `ClientEndpoint` section.
         * Copy the Connection string
 
-        :::image type="content" source="./media/signalr-howto-work-with-app-gateway/connection-string.png" alt-text="Get the connection string for SignalR Service with client endpoint.":::
+        :::image type="content" source="./media/signalr-howto-work-with-app-gateway/connection-string.png" alt-text="Screenshot of getting the connection string for SignalR Service with client endpoint.":::
 
 * Clone the GitHub repo https://github.com/aspnet/AzureSignalR-samples 
 * Go to samples/Chatroom folder:
@@ -149,7 +149,7 @@ Now, the traffic can reach SignalR Service through the Application Gateway. The
     ```
 * Open http://localhost:5000 from the browser and use F12 to view the network traces, you can see that the WebSocket connection is established through **_AG1_**  
 
-    :::image type="content" source="./media/signalr-howto-work-with-app-gateway/chat-local-run.png" alt-text="Run chat application locally with App Gateway and SignalR Service.":::
+    :::image type="content" source="./media/signalr-howto-work-with-app-gateway/chat-local-run.png" alt-text="Screenshot of running chat application locally with App Gateway and SignalR Service.":::
 
 ## Secure SignalR Service
 
@@ -165,7 +165,7 @@ Let's configure SignalR Service to only allow private access. You can find more
 * Go the **Networking** tab:
     * On **Public access** tab: **Public network access** change to **Disabled** and **Save**, now you're no longer able to access SignalR Service from public network
 
-        :::image type="content" source="./media/signalr-howto-work-with-app-gateway/disable-public-access.png" alt-text="Disable public access for SignalR Service.":::
+        :::image type="content" source="./media/signalr-howto-work-with-app-gateway/disable-public-access.png" alt-text="Screenshot of disabling public access for SignalR Service.":::
 
     * On **Private access** tab, select **+ Private endpoint**:
         * On **Basics** tab:
@@ -185,7 +185,7 @@ Let's configure SignalR Service to only allow private access. You can find more
             * **Integration with private DNS zone**: **Yes** 
         * Review and create the private endpoint
 
-    :::image type="content" source="./media/signalr-howto-work-with-app-gateway/application-gateway-setup-private-endpoint.png" alt-text="Set up the private endpoint resource for the SignalR Service.":::  
+    :::image type="content" source="./media/signalr-howto-work-with-app-gateway/application-gateway-setup-private-endpoint.png" alt-text="Screenshot of setting up the private endpoint resource for the SignalR Service.":::  
 
 ### Refresh Application Gateway backend pool
 Since Application Gateway was set up before there was a private endpoint for it to use, we need to **refresh** the backend pool for it to look at the Private DNS Zone and figure out that it should route the traffic to the private endpoint instead of the public address. We do the **refresh** by setting the backend FQDN to some other value and then changing it back.
@@ -271,7 +271,7 @@ Now the web app is deployed, let's go to the portal for **_WA1_** and make the f
 
 
 
-    :::image type="content" source="./media/signalr-howto-work-with-app-gateway/web-app-settings.png" alt-text="Configure web app connection string.":::
+    :::image type="content" source="./media/signalr-howto-work-with-app-gateway/web-app-settings.png" alt-text="Screenshot of configuring web app connection string.":::
 
 * On the **TLS/SSL settings** tab:
     * **HTTPS Only**: **Off**. To Simplify the demo, we used the HTTP frontend protocol on Application Gateway. Therefore, we need to turn off this option to avoid changing the HTTP URL to HTTPs automatically.
@@ -283,7 +283,7 @@ Now the web app is deployed, let's go to the portal for **_WA1_** and make the f
     > Sometimes you need to disable browser's auto https redirection and browser cache to prevent the URL from redirecting to HTTPS automatically.
 
 
-    :::image type="content" source="./media/signalr-howto-work-with-app-gateway/web-app-run.png" alt-text="Run chat application in Azure with App Gateway and SignalR Service.":::
+    :::image type="content" source="./media/signalr-howto-work-with-app-gateway/web-app-run.png" alt-text="Screenshot of running chat application in Azure with App Gateway and SignalR Service.":::
 
 ## Next steps