Link fixed.

Author: v-rajagt

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

@@ -98,9 +98,9 @@ When **_AG1_** is created, go to **Health probes** tab under **Settings** sectio
 
 ### Quick test
 
-* Try with an invalid client request https://asrs1.service.signalr.net/client and it returns *400* with error message *'hub' query parameter is required.* It means the request arrived at the SignalR Service and did the request validation.
+* Try with an invalid client request `https://asrs1.service.signalr.net/client` and it returns *400* with error message *'hub' query parameter is required.* It means the request arrived at the SignalR Service and did the request validation.
     ```bash
-    curl -v https://asrs1.service.signalr.net/client
+    curl -v `https://asrs1.service.signalr.net/client`
     ```
     returns
     ```
@@ -196,9 +196,9 @@ Go to the **Backend pools** tab for **_AG1_**, and select **signalr**:
 
 ### Quick test
 
-* Now let's visit https://asrs1.service.signalr.net/client again. With public access disabled, it returns *403* instead.
+* Now let's visit `https://asrs1.service.signalr.net/client` again. With public access disabled, it returns *403* instead.
     ```bash
-    curl -v https://asrs1.service.signalr.net/client
+    curl -v `https://asrs1.service.signalr.net/client`
     ```
     returns
     ```
@@ -287,4 +287,4 @@ Now the web app is deployed, let's go to the portal for **_WA1_** and make the f
 
 ## Next steps
 
-Now, you have successfully built a real-time chat application with SignalR Service and used Application Gateway to protect your applications and set up end-to-end security. [Learn more about SignalR Service](./signalr-overview.md).
+Now, you have successfully built a real-time chat application with SignalR Service and used Application Gateway to protect your applications and set up end-to-end security. [Learn more about SignalR Service](./signalr-overview.md).