minor edit

SnehaSudhirG · SnehaSudhirG · commit c88f986d407c · 2024-09-19T10:29:55.000+05:30
diff --git a/articles/automation/change-tracking/configure-alerts.md b/articles/automation/change-tracking/configure-alerts.md
@@ -13,7 +13,7 @@ ms.service: azure-automation
 [!INCLUDE [./log-analytics-retirement-announcement.md](../includes/log-analytics-retirement-announcement.md)]
 
 > [!NOTE]
-> CT&I (V1) onboarding via Azure portal will not be allowed since the service has retired on **31st August 2024**. We recommend that you configure new version of Change Tracking & Inventory with AMA. Your existing VMs on CT&I with legacy agent will continue to work till **1st February, 2025**. For more information, see[Enable Change Tracking and Inventory using Azure Monitoring Agent](enable-vms-monitoring-agent.md).
+> CT&I (V1) onboarding via Azure portal will not be allowed since the service has retired on **31st August 2024**. We recommend that you configure new version of Change Tracking & Inventory with AMA. Your existing VMs on CT&I with legacy agent will continue to work till **1st February, 2025**. For more information, see [Enable Change Tracking and Inventory using Azure Monitoring Agent](enable-vms-monitoring-agent.md).
 
 Alerts in Azure proactively notify you of results from runbook jobs, service health issues, or other scenarios related to your Automation account. Azure Automation does not include pre-configured alert rules, but you can create your own based on data that it generates. This article provides guidance on creating alert rules based on changes identified by Change Tracking and Inventory.
 
diff --git a/articles/automation/change-tracking/manage-change-tracking.md b/articles/automation/change-tracking/manage-change-tracking.md
@@ -13,7 +13,7 @@ ms.service: azure-automation
 [!INCLUDE [./log-analytics-retirement-announcement.md](../includes/log-analytics-retirement-announcement.md)]
 
 > [!NOTE]
-> CT&I (V1) onboarding via Azure portal will not be allowed since the service has retired on **31st August 2024**. We recommend that you configure new version of Change Tracking & Inventory with AMA. Your existing VMs on CT&I with legacy agent will continue to work till **1st February, 2025**. For more information, see[Enable Change Tracking and Inventory using Azure Monitoring Agent](enable-vms-monitoring-agent.md).
+> CT&I (V1) onboarding via Azure portal will not be allowed since the service has retired on **31st August 2024**. We recommend that you configure new version of Change Tracking & Inventory with AMA. Your existing VMs on CT&I with legacy agent will continue to work till **1st February, 2025**. For more information, see [Enable Change Tracking and Inventory using Azure Monitoring Agent](enable-vms-monitoring-agent.md).
 
 When you add a new file or registry key to track, Azure Automation enables it for [Change Tracking and Inventory](overview.md). This article describes how to configure tracking, review tracking results, and handle alerts when changes are detected.
 
diff --git a/articles/automation/change-tracking/manage-inventory-vms.md b/articles/automation/change-tracking/manage-inventory-vms.md
@@ -13,7 +13,7 @@ ms.service: azure-automation
 [!INCLUDE [./log-analytics-retirement-announcement.md](../includes/log-analytics-retirement-announcement.md)]
 
 > [!NOTE]
-> CT&I (V1) onboarding via Azure portal will not be allowed since the service has retired on **31st August 2024**. We recommend that you configure new version of Change Tracking & Inventory with AMA. Your existing VMs on CT&I with legacy agent will continue to work till **1st February, 2025**. For more information, see[Enable Change Tracking and Inventory using Azure Monitoring Agent](enable-vms-monitoring-agent.md).
+> CT&I (V1) onboarding via Azure portal will not be allowed since the service has retired on **31st August 2024**. We recommend that you configure new version of Change Tracking & Inventory with AMA. Your existing VMs on CT&I with legacy agent will continue to work till **1st February, 2025**. For more information, see [Enable Change Tracking and Inventory using Azure Monitoring Agent](enable-vms-monitoring-agent.md).
 
 You can enable inventory tracking for an Azure VM from the resource page of the machine. You can collect and view the following inventory information on your computers:
 
diff --git a/articles/automation/change-tracking/manage-scope-configurations.md b/articles/automation/change-tracking/manage-scope-configurations.md
@@ -13,7 +13,7 @@ ms.service: azure-automation
 [!INCLUDE [./log-analytics-retirement-announcement.md](../includes/log-analytics-retirement-announcement.md)]
 
 > [!NOTE]
-> CT&I (V1) onboarding via Azure portal will not be allowed since the service has retired on **31st August 2024**. We recommend that you configure new version of Change Tracking & Inventory with AMA. Your existing VMs on CT&I with legacy agent will continue to work till **1st February, 2025**. For more information, see[Enable Change Tracking and Inventory using Azure Monitoring Agent](enable-vms-monitoring-agent.md).
+> CT&I (V1) onboarding via Azure portal will not be allowed since the service has retired on **31st August 2024**. We recommend that you configure new version of Change Tracking & Inventory with AMA. Your existing VMs on CT&I with legacy agent will continue to work till **1st February, 2025**. For more information, see [Enable Change Tracking and Inventory using Azure Monitoring Agent](enable-vms-monitoring-agent.md).
 
 This article describes how to work with scope configurations when using the [Change Tracking and Inventory](overview.md) feature to deploy changes to your VMs. For more information, see [Targeting monitoring solutions in Azure Monitor (Preview)](/previous-versions/azure/azure-monitor/insights/solution-targeting).
 
