fix links

Author: cebundy

articles/azure-signalr/concept-connection-string.md

@@ -196,7 +196,7 @@ Then app server will return the right endpoint url in negotiate response for cli
 > [!NOTE]
 > For more information about how clients get service url through negotiate, see this [article](signalr-concept-internals.md#client-connections).
 
-Similarly, when server wants to make [server connections](signalr-concept-internals.md#server-connections) or call [REST APIs](https://github.com/Azure/azure-signalr/blob/dev/docs/rest-api.md) to service, SignalR service may also be behind another service like Application Gateway. In that case, you can use `ServerEndpoint` to specify the actual endpoint for server connections and REST APIs:
+Similarly, when server wants to make [server connections](signalr-concept-internals.md#azure-signalr-service-internals) or call [REST APIs](https://github.com/Azure/azure-signalr/blob/dev/docs/rest-api.md) to service, SignalR service may also be behind another service like Application Gateway. In that case, you can use `ServerEndpoint` to specify the actual endpoint for server connections and REST APIs:
 
 ```
 Endpoint=https://<resource_name>.service.signalr.net;AccessKey=<access_key>;ServerEndpoint=https://<url_to_app_gateway>;Version=1.0;

articles/azure-signalr/howto-network-access-control.md

@@ -16,7 +16,7 @@ Azure SignalR Service enables you to secure and control the level of access to y
 
 Azure SignalR Service has a public endpoint that is accessible through the internet. You can also create [Private Endpoints for your Azure SignalR Service](howto-private-endpoints.md). Private Endpoint assigns a private IP address from your VNet to the Azure SignalR Service, and secures all traffic between your VNet and the Azure SignalR Service over a private link. The Azure SignalR Service network access control provides access control for both public endpoint and private endpoints.
 
-Optionally, you can choose to allow or deny certain types of requests for public endpoint and each private endpoint. For example, you can block all [Server Connections](signalr-concept-internals.md#server-connections) from public endpoint and make sure they only originate from a specific VNet.
+Optionally, you can choose to allow or deny certain types of requests for public endpoint and each private endpoint. For example, you can block all [Server Connections](signalr-concept-internals.md#application-server-connections) from public endpoint and make sure they only originate from a specific VNet.
 
 An application that accesses an Azure SignalR Service when network access control rules are in effect still requires proper authorization for the request.
 

articles/azure-signalr/signalr-concept-internals.md

@@ -22,6 +22,7 @@ The differences from self-hosted ASP.NET Core SignalR application are discussed
 ![Architecture](./media/signalr-concept-internals/arch.png)
 
 ## Application server connections
+
 A self-hosted ASP.NET Core SignalR application server listens to and connects clients directly.
 
 With SignalR Service, the application server no longer accepts persistent client connections, instead:
@@ -98,6 +99,6 @@ The Azure SignalR Service acts as a logical transport layer between  application
 
 To learn more about Azure SignalR SDKs, see:
 
-- [ASP.NET Core SignalR](https://docs.microsoft.com/aspnet/core/signalr/introduction)
-- [ASP.NET SignalR](https://docs.microsoft.com/aspnet/signalr/overview/getting-started/introduction-to-signalr)
+- [ASP.NET Core SignalR](/aspnet/core/signalr/introduction)
+- [ASP.NET SignalR](/aspnet/signalr/overview/getting-started/introduction-to-signalr)
 - [ASP.NET code samples](https://github.com/aspnet/AzureSignalR-samples)