Acrolinx fixes

Author: JamesJBarnett

articles/api-management/breaking-changes/git-configuration-retirement-march-2025.md

@@ -1,6 +1,6 @@
 ---
 title: Azure API Management - Git configuration retirement (March 2025)
-description: Azure API Management is retiring configuration management using a built-in Git repo as of March 2025. If you use the feature, adopt a configuration management solution such as ApiOps.
+description: Azure API Management is retiring configuration management using a built-in Git repo as of March 2025. If you use the feature, adopt a configuration management solution such as APIOps.
 services: api-management
 author: dlepow
 ms.service: api-management
@@ -13,7 +13,7 @@ ms.author: danlep
 
 [!INCLUDE [api-management-availability-premium-dev-standard-basic](../../../includes/api-management-availability-premium-dev-standard-basic.md)]
 
-Effective 15 March 2025, Azure API Management will retire the ability to manage the configuration of your service instance using the built-in Git repository. If you plan to continue using a Git repository to manage the configuration of your service instance after the retirement date, you must update your configuration management to use a different solution such as ApiOps and your own Git repository implementation.
+Effective 15 March 2025, Azure API Management will retire the ability to manage the configuration of your service instance using the built-in Git repository. If you plan to continue using a Git repository to manage the configuration of your service instance after the retirement date, you must update your configuration management to use a different solution such as APIOps and your own Git repository implementation.
 
 ## Is my service affected by this?
 
@@ -27,7 +27,7 @@ Support for the built-in Git repository will no longer be available after 15 Mar
 
 ## What do I need to do?
 
-From now through 15 March 2025, if you have an existing Azure API Management instance using the Git repository, you can continue to use it normally. At any time before the retirement date, update your configuration management to use a different solution and tools based on Azure Resource Management-based REST APIs and Azure RBAC. For example, use a [devops and CI/CD](../devops-api-development-templates.md) solution such as [ApiOps](https://github.com/Azure/apiops) to extract and manage API Management configuration in your own your Git repository implementation like GitHub or Azure DevOps Repositories.
+From now through 15 March 2025, if you have an existing Azure API Management instance using the Git repository, you can continue to use it normally. At any time before the retirement date, update your configuration management to use a different solution and tools based on Azure Resource Management-based REST APIs and Azure RBAC. For example, use a [devops and CI/CD](../devops-api-development-templates.md) solution such as [APIOps](https://github.com/Azure/apiops) to extract and manage API Management configuration in your own your Git repository implementation like GitHub or Azure DevOps Repositories.
 
 After the retirement date, if you create an API Management instance, you won't be able to activate the Git repository feature to save or update your service configuration.