update per comments

Author: ekmineev

articles/remote-rendering/how-tos/authentication.md

@@ -9,7 +9,7 @@ ms.topic: how-to
 
 # Configure authentication
 
-Azure Remote Rendering uses the same authentication mechanism as [Azure Spatial Anchors (ASA)](../../spatial-anchors/concepts/authentication.md?tabs=csharp). To access a given Azure Remote Rendering account, clients need to first obtain an access token from Azure Mixed Reality Security Token Service (STS). Tokens obtained from STS have a lifetime of 24 hours. Clients need to set *one* of the following to call the REST APIs successfully:
+Azure Remote Rendering uses the same authentication mechanism as [Azure Spatial Anchors (ASA)](../../spatial-anchors/concepts/authentication.md?tabs=csharp). To access a given Azure Remote Rendering account, clients need to obtain an access token from Azure Mixed Reality Security Token Service (STS). Tokens obtained from STS have a lifetime of 24 hours. Clients need to set *one* of the following to call the REST APIs successfully:
 
 * **AccountKey**: can be obtained in the "Keys" tab for the Remote Rendering account on the Azure portal. Account Keys are only recommend for development/prototyping.
     ![Account ID](./media/azure-account-primary-key.png)

articles/remote-rendering/how-tos/move-remote-rendering-account.md

@@ -12,7 +12,7 @@ ms.custom: subject-moving-resources
 
 # Move a Remote Rendering account between regions
 
-This article describes how to move a Remote Rendering account to a different Azure region. While a Remote Rendering account can be used to connect to any region where Remote Rendering service is available, there are reasons to move your resources to another region. For example, to meet internal policy and governance requirements, or in response to capacity planning requirements.
+This article describes how to move a Remote Rendering account to a different Azure region. While a Remote Rendering account can be used to connect to any [region where Remote Rendering service is available](../reference/regions.md), there are reasons to move your resources to another region. For example, to meet internal policy and governance requirements, or in response to capacity planning requirements.
 
 ## Prerequisites
 
@@ -35,7 +35,7 @@ Run your app or web service and verify it's still functional after the move.
 
 ## Clean up
 
-To complete the move of the Remote Rendering account, delete the source Remote Rendering or resource group. To do so, select the Remote Rendering account or resource group from your dashboard in the portal and select Delete at the top of each page.
+To complete the move of the Remote Rendering account, delete the source Remote Rendering or resource group. To do so, select the Remote Rendering account or resource group from your dashboard in the portal and select "Delete" at the top of each page.
 
 ## Next steps
 

articles/remote-rendering/how-tos/toc.yml

@@ -4,6 +4,8 @@
   href: tokens.md
 - name: Configure authentication
   href: authentication.md
+- name: Move an Azure Remote Rendering account between regions
+  href: move-remote-rendering-account.md
 - name: Use the Azure Frontend APIs for authentication
   href: frontend-apis.md
 - name: Use the session management REST API