Updated TOC

Author: MGoedtel

articles/automation/TOC.yml

@@ -50,6 +50,8 @@
           href: automation-create-standalone-account.md
         - name: Create Automation account with Resource Manager template
           href: automation-create-account-template.md
+        - name: Configure authentication with Amazon Web Services
+          href: automation-config-aws-account.md
         - name: Manage an Automation Run As account
           href: manage-runas-account.md
         - name: Manage role permissions and security
@@ -250,8 +252,6 @@
           href: automation-create-alert-triggered-runbook.md
         - name: Manage Office 365 services
           href: manage-office-365.md
-        - name: Authenticate runbooks with Amazon Web Services
-          href: automation-config-aws-account.md
         - name: Deploy AWS VM with Automation runbook
           href: automation-scenario-aws-deployment.md
         - name: Deploy Resource Manager template with runbook

articles/automation/automation-config-aws-account.md

@@ -4,7 +4,7 @@ description: This article describes how to create and validate an AWS credential
 keywords: aws authentication, configure aws
 services: automation
 ms.subservice: process-automation
-ms.date: 04/17/2018
+ms.date: 04/23/2020
 ms.topic: conceptual
 ---
 # Authenticate Azure Automation runbooks with Amazon Web Services
@@ -14,7 +14,7 @@ Automating common tasks with resources in Amazon Web Services (AWS) can be accom
 * An AWS subscription and a set of credentials. Specifically your AWS Access Key and Secret Key. For more information, review the article [Using AWS Credentials](https://docs.aws.amazon.com/powershell/latest/userguide/specifying-your-aws-credentials.html).
 * An Azure subscription and Automation account.
 
-To authenticate with AWS, you must specify a set of AWS credentials to authenticate your runbooks running from Azure Automation. If you already have an Automation account created and you want to use that to authenticate with AWS, you can follow the steps in the following section: If you want to dedicate an account for runbooks targeting AWS resources, you should first create a new [Automation account](automation-offering-get-started.md) (skip the option to create a service principal) and use the following steps:
+To authenticate with AWS, you must specify a set of AWS credentials to authenticate your runbooks running from Azure Automation. If you already have an Automation account created and you want to use that to authenticate with AWS, you can follow the steps in the following section. If you want to dedicate an account for runbooks targeting AWS resources, you should first create a new [Automation account](automation-create-standalone-account.md) and skip the step to create a Run As account. After creating the account, follow the steps below to complete the configuration.
 
 ## Configure Automation account
 

articles/automation/automation-security-overview.md

@@ -26,12 +26,12 @@ The service principal for a Run as Account does not have permissions to read Azu
 
 Role-based access control is available with Azure Resource Manager to grant permitted actions to an Azure AD user account and Run As account, and authenticate that service principal. Read [Role-based access control in Azure Automation article](automation-role-based-access-control.md) for further information to help develop your model for managing Automation permissions.  
 
-Runbooks running on a Hybrid Runbook Worker in your data center or against computing services in other cloud environments like AWS, cannot use the same method that is typically used for runbooks authenticating to Azure resources. This is because those resources are running outside of Azure and therefore, requires their own security credentials defined in Automation to authenticate to resources that they access locally. For more information about runbook authentication with runbook workers, see [Authenticate runbooks for Hybrid Runbook Workers](automation-hrw-run-runbooks.md).
+Runbooks running on a Hybrid Runbook Worker in your data center or against computing services in other cloud environments like AWS, cannot use the same method that is typically used for runbooks authenticating to Azure resources. This is because those resources are running outside of Azure and therefore, requires their own security credentials defined in Automation to authenticate to resources that they access locally. For more information about runbook authentication with runbook workers, see [Authenticate runbooks for Hybrid Runbook Workers](automation-hrw-run-runbooks.md). 
 
 ## Next steps
 
 * [Create an Automation account from the Azure portal](automation-create-standalone-account.md).
 
 * [Create an Automation account using Azure Resource Manager template](automation-create-account-template.md).
 
-* [Authenticate runbooks with Amazon Web Services (AWS)](automation-config-aws-account.md).
+* [Authenticate with Amazon Web Services (AWS)](automation-config-aws-account.md).