rephrase docs and update image file paths

Author: terencefan

articles/azure-signalr/TOC.yml

@@ -212,4 +212,4 @@
   - name: Twitter
     href: https://twitter.com/SignalR
   - name: ASP.NET forums
-    href: https://social.msdn.microsoft.com/Forums/en-US/home?forum=aspsignalr
+    href: https://social.msdn.microsoft.com/Forums/en-US/home?forum=aspsignalr

articles/azure-signalr/howto-disable-local-auth.md

@@ -30,7 +30,7 @@ In this section, you will learn how to use the Azure portal to disable local aut
 
 4. Click **Save** button.
 
-![Screenshot of disabling local auth](./media/howto-azure-active-directory/disable-local-auth.png)
+![Screenshot of disabling local auth](./media/howto-disable-local-auth/disable-local-auth.png)
 
 ## Use Azure Resource Manager template
 
@@ -110,7 +110,7 @@ You can disable local authentication by setting `disableLocalAuth` property to t
 
 You can assign the [Azure SignalR Service should have local authentication methods disabled](https://ms.portal.azure.com/#view/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2Ff70eecba-335d-4bbc-81d5-5b17b03d498f) Azure policy to an Azure subscription or a resource group to enforce disabling of local authentication for all SignalR resources in the subscription or the resource group.
 
-![Screenshot of disabling local auth policy](./media/howto-azure-active-directory/disable-local-auth-policy.png)
+![Screenshot of disabling local auth policy](./media/howto-disable-local-auth/disable-local-auth-policy.png)
 
 ## Next steps
 

articles/azure-signalr/media/howto-azure-active-directory/disable-local-auth-policy.png renamed to articles/azure-signalr/media/howto-disable-local-auth/disable-local-auth-policy.png

@@ -24,14 +24,14 @@ The first step is to register an Azure application.
 2. Under **Manage** section, select **App registrations**.
 3. Select **New registration**.
 
-    ![Screenshot of registering an application](./media/howto-azure-active-directory/register-an-application.png)
+    ![Screenshot of registering an application](./media/signalr-howto-authorize-application/register-an-application.png)
 
 4. Enter a display **Name** for your application.
 5. Select **Register** to confirm the register.
 
 Once you have your application registered, you can find the **Application (client) ID** and **Directory (tenant) ID** under its Overview page. These GUIDs can be useful in the following steps.
 
-![Screenshot of an application](./media/howto-azure-active-directory/application-overview.png)
+![Screenshot of an application](./media/signalr-howto-authorize-application/application-overview.png)
 
 To learn more about registering an application, see
 - [Quickstart: Register an application with the Microsoft identity platform](../active-directory/develop/quickstart-register-app.md).
@@ -47,7 +47,7 @@ The application requires a client secret to prove its identity when requesting a
 
 1. Under **Manage** section, select **Certificates & secrets**
 1. On the **Client secrets** tab, select **New client secret**.
-![Screenshot of creating a client secret](./media/howto-azure-active-directory/new-client-secret.png)
+![Screenshot of creating a client secret](./media/signalr-howto-authorize-application/new-client-secret.png)
 1. Enter a **description** for the client secret, and choose a **expire time**.
 1. Copy the value of the **client secret** and then paste it to a secure location. 
     > [!NOTE]
@@ -57,7 +57,7 @@ The application requires a client secret to prove its identity when requesting a
 
 You can also upload a certification instead of creating a client secret.
 
-![Screenshot of uploading a certification](./media/howto-azure-active-directory/upload-certificate.png)
+![Screenshot of uploading a certification](./media/signalr-howto-authorize-application/upload-certificate.png)
 
 To learn more about adding credentials, see