Merge pull request #127062 from Adeegithub/patch-1

v-dirichards · web-flow · commit 59c317ccf8af · 2025-06-23T15:15:48.000-05:00
Update api-management-configuration-repository-git.md
diff --git a/articles/api-management/api-management-configuration-repository-git.md b/articles/api-management/api-management-configuration-repository-git.md
@@ -52,7 +52,7 @@ This article describes how to enable and use Git to manage your service configur
 ## Save the service configuration to the Git repository
 
 > [!CAUTION]
-> Any secrets that are not defined as named values will be stored in the repository and will remain in its history. Named values provide a secure place to manage constant string values, including secrets, across all API configuration and policies, so you don't have to store them directly in your policy statements. For more information, see [Use named values in Azure API Management policies](api-management-howto-properties.md).
+> Any secrets that are not defined as named values will be stored in the repository and will remain in its history. Named values provide a secure place to manage constant string values, including secrets, across all API configurations and policies, so you don't have to store them directly in your policy statements. For more information, see [Use named values in Azure API Management policies](api-management-howto-properties.md).
 >
 
 
diff --git a/articles/api-management/api-management-get-started-publish-versions.md b/articles/api-management/api-management-get-started-publish-versions.md
@@ -16,7 +16,7 @@ ms.author: danlep
 
 [!INCLUDE [api-management-availability-all-tiers](../../includes/api-management-availability-all-tiers.md)]
 
-There are times when it's impractical to have all callers to your API use the same version. When callers want to upgrade to a later version, they want an approach that's easy to understand. As shown in this tutorial, it's possible to provide multiple *versions* in Azure API Management. 
+There are situations where it's impractical for all API consumers to use the same version. When consumers are ready to upgrade to a newer version, they prefer a simple and understandable approach. As demonstrated in this tutorial, Azure API Management supports exposing multiple API versions to meet this need.
 
 For background, see [Versions](api-management-versions.md) and [Revisions](api-management-revisions.md).
 

Original file line number	Diff line number	Diff line change
`@@ -52,7 +52,7 @@ This article describes how to enable and use Git to manage your service configur`
`52`	`52`	`## Save the service configuration to the Git repository`
`53`	`53`
`54`	`54`	`> [!CAUTION]`
`55`		`-> Any secrets that are not defined as named values will be stored in the repository and will remain in its history. Named values provide a secure place to manage constant string values, including secrets, across all API configuration and policies, so you don't have to store them directly in your policy statements. For more information, see [Use named values in Azure API Management policies](api-management-howto-properties.md).`
	`55`	`+> Any secrets that are not defined as named values will be stored in the repository and will remain in its history. Named values provide a secure place to manage constant string values, including secrets, across all API configurations and policies, so you don't have to store them directly in your policy statements. For more information, see [Use named values in Azure API Management policies](api-management-howto-properties.md).`
`56`	`56`	`>`
`57`	`57`
`58`	`58`