Update api-management-configuration-repository-git.md

Adeegithub · web-flow · commit ae4c4a5d340e · 2025-06-07T12:46:32.000+05:30
Rephrased for more clarity
using the plural form "configurations" to match "policies"
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).
 >
 
 

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`