Merge pull request #111050 from BethWilke/branch113

Fixing documentation task 1704208

Author: v-albemi

articles/automation/TOC.yml

@@ -10,30 +10,30 @@
   items:
     - name: Create an Automation account
       href: automation-quickstart-create-account.md
-    - name: Create standalone Automation account
+    - name: Create a standalone Automation account
       href: automation-create-standalone-account.md
-    - name: Manage Automation Run As account
+    - name: Manage an Automation Run As account
       href: manage-runas-account.md
       displayName: certificate renewal
     - name: Manage role-based access control
       href: automation-role-based-access-control.md
       displayName: RBAC
-    - name: Use Azure AD in Azure Automation to authenticate to Azure
+    - name: Use Azure AD to authenticate to Azure
       href: automation-use-azure-ad.md
-    - name: Manage Office 365 services using Azure Automation
+    - name: Manage Office 365 services
       href: manage-office-365.md
     - name: Configure authentication with AWS
       href: automation-config-aws-account.md
     - name: Encrypt secure assets in Azure Automation
       href: automation-secure-asset-encryption.md
-    - name: Move your Automation Account to another Subscription
+    - name: Move your Automation Account to another subscription
       href: how-to/move-account.md
-    - name: Automate onboarding of Automation Services
+    - name: Automate onboarding of Automation services
       href: /azure/architecture/cloud-adoption/operations/azure-server-management/onboarding-automation
     - name: Manage Azure Automation data
       href: automation-managing-data.md
       displayName: backup
-    - name: Supported Regions for Log Analytics Workspace Mappings
+    - name: Supported regions for Log Analytics workspace mappings
       href: how-to/region-mappings.md
     - name: Troubleshoot
       items:  

articles/automation/automation-create-standalone-account.md

@@ -28,7 +28,7 @@ To create or update an Automation account, and to complete the tasks described i
 * To create an Automation account, your Azure AD user account must be added to a role with permissions equivalent to the Owner role for **Microsoft. Automation** resources. For more information, see [Role-Based Access Control in Azure Automation](automation-role-based-access-control.md).
 * In the Azure portal, under **Azure Active Directory** > **MANAGE** > **User settings**, if **App registrations** is set to **Yes**, non-admin users in your Azure AD tenant can [register Active Directory applications](../active-directory/develop/howto-create-service-principal-portal.md#check-azure-subscription-permissions). If **App registrations** is set to **No**, the user who performs this action must be a global administrator in Azure AD.
 
-If you aren't a member of the subscription’s Active Directory instance before you are added to the subscription's global administrator/coadministrator role, you are added to Active Directory as a guest. In this scenario, you see this message on the **Add Automation Account** page: “You do not have permissions to create."
+If you aren't a member of the subscription's Active Directory instance before you are added to the subscription's global administrator/coadministrator role, you are added to Active Directory as a guest. In this scenario, you see this message on the **Add Automation Account** page: "You do not have permissions to create."
 
 If a user is added to the global administrator/coadministrator role first, you can remove them from the subscription's Active Directory instance, and then readd them to the full User role in Active Directory.
 
@@ -86,7 +86,7 @@ When the Automation account is successfully created, several resources are autom
 | AzureRunAsCertificate |A certificate asset that's automatically created when the Automation account is created, or by using a PowerShell script for an existing account. The certificate authenticates with Azure so you can manage Azure Resource Manager resources from runbooks. This certificate has a one-year lifespan. |
 | AzureRunAsConnection |A connection asset that's automatically created when the Automation account is created, or by using a PowerShell script for an existing account. |
 
-## Classic Run-As Accounts
+## Create a Classic Run-As account
 
 Classic Run-As accounts are no longer created, by default, when you create an Azure Automation account. If you still require a Classic Run-As account, please perform the following steps.
 

articles/automation/automation-solution-vm-management-enable.md

@@ -12,7 +12,7 @@ ms.topic: conceptual
 Perform the following steps to add the Start/Stop VMs during off-hours solution to a new or existing Automation account and linked Log Analytics workspace. After completing the onboarding process, configure the variables to customize the solution.
 
 >[!NOTE]
->To use this solution with Classic VMs, you need a Classic RunAs account, which is not created by default. For instructions on creating a Classic RunAs account, see [Classic Run-As Accounts](automation-create-standalone-account.md#classic-run-as-accounts).
+>To use this solution with Classic VMs, you need a Classic Run As account, which is not created by default. For instructions on creating a Classic Run As account, see [Create a Classic Run As account](automation-create-standalone-account.md#create-a-classic-run-as-account).
 >
 
 ## Enable solution