minor edits

Author: SnehaSudhirG

articles/automation/automation-security-overview.md

@@ -12,7 +12,7 @@ ms.custom: devx-track-azurepowershell
 # Azure Automation account authentication overview
 
 > [!IMPORTANT]
-> Azure Automation Run As Account will retire on September 30, 2025 and will be replaced with Managed Identities.Before that date, you'll need to start migrating your runbooks to use [managed identities](/automation-security-overview.md#managed-identities). For more information, see [migrating from an existing Run As accounts to managed identity](/migrate-run-as-accounts-managed-identity?tabs=ua-managed-identity#sample-scripts) to start migrating the runbooks from Run As account to managed identities before 30 September 2025. See the official announcement [here](https://azure.microsoft.com/updates/azure-automation-runas-account-retiring-on-30-september-2025/preview/).
+> Azure Automation Run As Account will retire on September 30, 2025 and will be replaced with Managed Identities.Before that date, you'll need to start migrating your runbooks to use [managed identities](automation-security-overview.md#managed-identities). For more information, see [migrating from an existing Run As accounts to managed identity](migrate-run-as-accounts-managed-identity?tabs=ua-managed-identity.md#sample-scripts) to start migrating the runbooks from Run As account to managed identities before 30 September 2025. See the official announcement [here](https://azure.microsoft.com/updates/azure-automation-runas-account-retiring-on-30-september-2025/preview/).
 
 Azure Automation allows you to automate tasks against resources in Azure, on-premises, and with other cloud providers such as Amazon Web Services (AWS). You can use runbooks to automate your tasks, or a Hybrid Runbook Worker if you have business or operational processes to manage outside of Azure. Working in any one of these environments require permissions to securely access the resources with the minimal rights required.
 

articles/automation/delete-run-as-account.md

@@ -10,7 +10,7 @@ ms.topic: conceptual
 # Delete an Azure Automation Run As account
 
 > [!IMPORTANT]
-> Azure Automation Run As Account will retire on September 30, 2025 and will be replaced with Managed Identities.Before that date, you'll need to start migrating your runbooks to use [managed identities](/automation-security-overview.md#managed-identities). For more information, see [migrating from an existing Run As accounts to managed identity](/migrate-run-as-accounts-managed-identity?tabs=ua-managed-identity#sample-scripts) to start migrating the runbooks from Run As account to managed identities before 30 September 2025. See the official announcement [here](https://azure.microsoft.com/updates/azure-automation-runas-account-retiring-on-30-september-2025/preview/).
+> Azure Automation Run As Account will retire on September 30, 2025 and will be replaced with Managed Identities.Before that date, you'll need to start migrating your runbooks to use [managed identities](automation-security-overview.md#managed-identities). For more information, see [migrating from an existing Run As accounts to managed identity](migrate-run-as-accounts-managed-identity?tabs=ua-managed-identity.md#sample-scripts) to start migrating the runbooks from Run As account to managed identities before 30 September 2025. See the official announcement [here](https://azure.microsoft.com/updates/azure-automation-runas-account-retiring-on-30-september-2025/preview/).
 
 Run As accounts in Azure Automation provide authentication for managing resources on the Azure Resource Manager or Azure Classic deployment model using Automation runbooks and other Automation features. This article describes how to delete a Run As or Classic Run As account. When you perform this action, the Automation account is retained. After you delete the Run As account, you can re-create it in the Azure portal or with the provided PowerShell script.