Apply suggestions from code review

Co-authored-by: Luke Knepper <lukeknepper@gmail.com>

Author: lukeknep

docs/cloud/connectivity/aws-connectivity.mdx

@@ -197,7 +197,7 @@ The DNS resolver inside your VPC returns the private endpoint, while TLS still v
 
 ## Configure private DNS for Namespaces with High Availability
 
-For Namespaces with [High Availability features](/cloud/high-availability), you need to override DNS for `region.tmprl.io` so each region resolves to the local VPC Endpoint, and you need to ensure Workers can reach whichever region is active. Failover is transparent to clients only when this is set up correctly.
+For Namespaces with [High Availability features](/cloud/high-availability), you need to override DNS for `region.tmprl.cloud` so each region resolves to the local VPC Endpoint, and you need to ensure Workers can reach whichever region is active. Failover is transparent to clients only when this is set up correctly.
 
 The complete guidance — including single-cloud (AWS-only) HA, multi-cloud HA (AWS PrivateLink + GCP Private Service Connect), and a recommended failover-testing plan — lives on a single page: [Connectivity for High Availability](/cloud/high-availability/ha-connectivity).
 

docs/cloud/high-availability/failovers.mdx

@@ -62,7 +62,7 @@ In most scenarios, we recommend you let Temporal handle failovers for you.
 After failover, be aware of the following points:
 
 - When working with Multi-region Namespaces, your CNAME may change.
-  For example, it may switch from us-west-1.aws.api.temporal.io to us-east-1.aws.api.temporal.io.
+  For example, it may switch from aws-us-west-1.region.tmprl.cloud to aws-us-east-1.region.tmprl.cloud.
   This change doesn't affect same-region Namespaces.
 
 - Your Namespace endpoint _will not change_.

docs/cloud/high-availability/ha-connectivity.mdx

@@ -25,7 +25,7 @@ A Namespace with High Availability features has two replicas — a primary and a
 Temporal Cloud expresses the active replica through DNS:
 
 - The Namespace DNS record (`<ns>.<account>.tmprl.cloud`) is a CNAME.
-- It points to the active region's regional record (`<region>.<provider>.api.temporal.io`).
+- It points to the active region's regional record (`<provider>-<region>.region.tmprl.cloud`).
 - On failover, Temporal Cloud rewrites the CNAME target.
 
 Namespace DNS records have a 15-second TTL. Clients should converge to the new region within roughly 30 seconds (about twice the TTL) once their resolver cache expires.

static/json/privatelink_services_aws.json

@@ -12,8 +12,8 @@
         ["eu-west-1","com.amazonaws.vpce.eu-west-1.vpce-svc-04388e89f3479b739"],
         ["eu-west-2","com.amazonaws.vpce.eu-west-2.vpce-svc-0ac7f9f07e7fb5695"],
         ["sa-east-1","com.amazonaws.vpce.sa-east-1.vpce-svc-0ca67a102f3ce525a"],
-        [ "us-east-1","com.amazonaws.vpce.us-east-1.vpce-svc-0822256b6575ea37f"],
-        [ "us-east-2","com.amazonaws.vpce.us-east-2.vpce-svc-01b8dccfc6660d9d4"],
+        ["us-east-1","com.amazonaws.vpce.us-east-1.vpce-svc-0822256b6575ea37f"],
+        ["us-east-2","com.amazonaws.vpce.us-east-2.vpce-svc-01b8dccfc6660d9d4"],
         ["us-west-2","com.amazonaws.vpce.us-west-2.vpce-svc-0f44b3d7302816b94"]
     ]
 }