minor edits

Author: SnehaSudhirG

articles/automation/automation-managed-identity-faq.md

@@ -15,7 +15,7 @@ This Microsoft FAQ is a list of commonly asked questions when you're migrating f
 
 ## How long will you support Run As account?
 
-Automation Run As account would be supported for the next three years until **September 30, 2025**. While we continue to support for existing users, we recommend all new users to use Managed identities as the preferred way of runbook authentication. Existing users can create the Run As account, see the  account properties and renew the certificate upon expiration till **May 30, 2023**. After this date, you won't be able to create Run As account from the Azure portal. Users could still create a Run As account through [PowerShell script](/azure/automation/create-run-as-account#create-account-using-powershell) until the supported time of three years.
+Automation Run As account would be supported for the next three years until **September 30, 2025**. While we continue to support for existing users, we recommend all new users to use Managed identities as the preferred way of runbook authentication. Existing users can create the Run As account, see the  account properties and renew the certificate upon expiration till **May 30, 2023**. After this date, you won't be able to create Run As account from the Azure portal. You could still create a Run As account through [PowerShell script](/azure/automation/create-run-as-account#create-account-using-powershell) until the supported time of three years.
 
 ## What is Managed Identity?
 Managed identities provide an automatically managed identity in Azure Active Directory for applications to use when connecting to resources that support Azure Active Directory (Azure AD) authentication. Applications can use managed identities to obtain Azure AD tokens without managing credentials, secrets, certificates or keys. 

articles/automation/migrate-run-as-accounts-managed-identity.md

@@ -11,7 +11,7 @@ ms.custom: devx-track-azurepowershell
 # Migrate from existing Run As accounts to managed identity
 
 > [!IMPORTANT]
-> Azure Automation Run As Account will retire on **September 30, 2025**, and there will be no support provided beyond this date. From now through **September 30, 2025**, you can continue to use the Azure Automation Run As Account. However, we recommend you to transition to [managed identities](/automation-security-overview.md#managed-identities) before **September 30, 2025**.
+> Azure Automation Run As Account will retire on **September 30, 2025**, and there will be no support provided beyond this date. From now through **September 30, 2025**, you can continue to use the Azure Automation Run As Account. However, we recommend you to transition to [managed identities](/automation-security-overview.md#managed-identities) before **September 30, 2025**. See the official announcement here.
 
  Run As accounts in Azure Automation provide authentication for managing Azure Resource Manager resources or resources deployed on the classic deployment model. Whenever a Run As account is created, an Azure AD application is registered, and a self-signed certificate will be generated which will be valid for one year. This adds an overhead of renewing the certificate every year before it expires to prevent the Automation account to stop working. 
 
@@ -162,4 +162,7 @@ foreach ($ResourceGroup in $ResourceGroups)
 
 - For an overview of Azure Automation account security, see [Automation account authentication overview](automation-security-overview.md).
 
-- For FQAs on Migrating to Managed Identities, see[FAQ - Migrating from Run As account to Managed Identity](automation-managed-identity-faq.md)
+- Review the Frequently asked questions for [Migrating to Managed Identities](automation-managed-identity-faq.md).
+
+
+