diff --git a/docs/data-governance/data-clean-up.mdx b/docs/data-governance/data-clean-up.mdx
index 7e2dd636..7b9ac00e 100644
--- a/docs/data-governance/data-clean-up.mdx
+++ b/docs/data-governance/data-clean-up.mdx
@@ -246,5 +246,5 @@ No. Dropped events are discarded at ingestion and cannot be recovered. If you ne
 
 ### Other resources
 
-- [Event Approval](/changelogs/2023-06-01-event-approval)
+- [Event Approval](/changelogs#vet-new-events-and-ensure-data-trust-with-event-approval)
 - [Recovering from a hot shard](/docs/debugging/distinct-id-limits)
diff --git a/docs/privacy/eu-residency.mdx b/docs/privacy/eu-residency.mdx
index 89156b13..5352fa4c 100644
--- a/docs/privacy/eu-residency.mdx
+++ b/docs/privacy/eu-residency.mdx
@@ -14,7 +14,7 @@ You can enable this by selecting the "EU Data Residency" option when creating a
 
 <Warning>
 Important: For new EU projects created on or after August 18, 2025, no data will be ingested into your new EU data residency project unless your SDK is sending data to the EU endpoint. Ensure you are using the EU endpoint in your SDK configuration.
-For EU Projects created before August 18, 2025, US-to-EU Data Forwarding ends July 2026, please ensure you are using the EU endpoint in your SDK configuration. See [changelog here](/changelogs/2026-02-20-eu-forwarding-deprecation).
+For EU Projects created before August 18, 2025, US-to-EU Data Forwarding ends July 2026, please ensure you are using the EU endpoint in your SDK configuration. See [changelog here](/changelogs#deprecation-notice-legacy-us-to-eu-data-forwarding-ends-july-2026-for-eu-projects).
 </Warning>
 
 For existing EU projects created prior to August 18, 2025, we encourage you to update your SDK configuration to use the dedicated EU endpoint. This is a best practice that ensures your project is correctly aligned with its data residency.