Update src/content/docs/data-localization/metadata-boundary/index.mdx

Co-authored-by: angelampcosta <[email protected]>

Author: mathew-cf

src/content/docs/data-localization/metadata-boundary/index.mdx

@@ -5,7 +5,7 @@ sidebar:
   order: 1
 ---
 
-As part of the Data Localization Suite, the Customer Metadata Boundary (CMB) ensures that Customer Logs — any traffic metadata that can identify a customer’s end user (that is, contains the customer's [Account ID](/fundamentals/setup/find-account-and-zone-ids/)) — will stay in the `EU` (European Union) or in the `US` (United States), depending on the region the customer selects. For example, if a customer selects the `EU` Customer Metadata Boundary, metadata will **only** be sent to our core data center located in the European Union.
+As part of the Data Localization Suite, the Customer Metadata Boundary (CMB) ensures that Customer Logs — any traffic metadata that can identify a customer’s end user (that is, contains the customer's [Account ID](/fundamentals/setup/find-account-and-zone-ids/)) — will stay in the `EU` (European Union) or in the `US` (United States), depending on the region the customer selects. For example, if a customer selects the `EU` Customer Metadata Boundary, Customer Logs will **only** be sent to our core data center located in the European Union.
 
 An exception is made if "Allow out-of-region access" is enabled. When enabled, Customer Logs will still be stored in the configured regions but will be accessible to authorized end users, regardless of physical location. Refer to [Out of region access](/data-localization/metadata-boundary/out-of-region-access/) for more details.