Apply suggestions from code review

Author: angelampcosta

src/content/docs/data-localization/metadata-boundary/out-of-region-access.mdx

@@ -5,8 +5,8 @@ sidebar:
   order: 5
 ---
 
-With the default configuration for Customer Metadata Boundary, users outside the configured region will not have access to view analytics on the dashboard or the default API endpoint. When "Allow out-of-region access" is enabled, Customer Logs will still be stored exclusively within the configured region but will be made available to users outside the region as well.
+With the default configuration for Customer Metadata Boundary, users outside the configured region will not have access to view analytics on the dashboard or the default API endpoint. When **Allow out-of-region access** is enabled, Customer Logs will still be stored exclusively within the configured region but will be made available to users outside the region as well.
 
-For example, when "Allow out-of-region access" is **disabled** on an account configured for Customer Metadata Boundary in the US, users in Europe will not be able to see any analytics or Customer Logs on the dashboard.
+For example, when **Allow out-of-region access** is disabled on an account configured for Customer Metadata Boundary in the US, users in Europe will not be able to see any analytics or Customer Logs on the dashboard.
 
-When "Allow out-of-region access" is **enabled** on an account configured for Customer Metadata Boundary in the US, users in both Europe and the US will be able to see analytics on the dashboard even though the Customer Logs are stored exclusively in Europe.
+When **Allow out-of-region access** is enabled on an account configured for Customer Metadata Boundary in the US, users in both Europe and the US will be able to see analytics on the dashboard even though the Customer Logs are stored exclusively in Europe.