Address PoliCheck issue

Author: JKirsch1

articles/azure-maps/how-to-manage-consent.md

@@ -13,7 +13,7 @@ ms.subservice: manage-account
 
 In some cases, it may be necessary to process requests in a region different from your Azure Maps Account's region due to local data residency laws. When this happens, you can grant Azure Maps consent to process your data in other specified regions. For more information, see [Consent management].
 
-This article guides you on configuring global data processing settings to comply with data residency laws using multiple approaches including the [Azure portal](#configure-global-data-processing-in-the-azure-portal), [REST APIs](#configure-global-data-processing-using-rest-api) or an [ARM deployment template](#configure-global-data-processing-using-an-arm-deployment-template). This allows Azure Maps to process address requests within the specified country's region, regardless of your Azure Maps Account's region.
+This article guides you on configuring global data processing settings to comply with data residency laws using multiple approaches including the [Azure portal](#configure-global-data-processing-in-the-azure-portal), [REST APIs](#configure-global-data-processing-using-rest-api) or an [ARM deployment template](#configure-global-data-processing-using-an-arm-deployment-template). This allows Azure Maps to process address requests within the region of the specified country/region, regardless of your Azure Maps Account's region.
 
 > [!IMPORTANT]
 > If your scenarios don't involve Korean data, there is no need to enable cross-region processing. This requirement is specific to Korea due to its data residency laws.