diff --git a/src/pages/docs/ai-transport/going-to-production.mdx b/src/pages/docs/ai-transport/going-to-production.mdx
index 483aa5b94c..ef4b9866da 100644
--- a/src/pages/docs/ai-transport/going-to-production.mdx
+++ b/src/pages/docs/ai-transport/going-to-production.mdx
@@ -61,13 +61,12 @@ If you persist conversations beyond the channel's retention:
 
 ## Compliance <a id="compliance"/>
 
-Ably is SOC 2 Type II certified and HIPAA compliant. See [security and compliance](https://ably.com/security) for the current certifications and how to enable HIPAA-eligible workloads.
+Ably is SOC 2 Type II certified and HIPAA compliant. See [security and compliance](/security-and-compliance) for more information.
 
-For application-side compliance:
+For the application-side:
 
-- Log message metadata (turn IDs, client IDs, timestamps), not message contents, by default. Surface content logs through an opt-in path with the right retention.
-- Treat tool inputs and outputs as conversation content. They are visible to every subscriber by capability.
-- For region-pinned data residency, scope capabilities to namespaces hosted in the right region. See [Ably's data residency](/docs/platform/architecture/regions).
+- Message content, including tool inputs and outputs are conversation content. They are visible to every subscriber by capability.
+- For region-pinned data residency, scope capabilities to namespaces hosted in the right region. See [Ably's edge network](/docs/platform/architecture/edge-network).
 
 ## Deployment notes <a id="deployment"/>