Merge pull request #17359 from newrelic/sd-cloud-data-update

fix(security): fixing header and docs link

src/content/docs/security/security-privacy/data-privacy/security-controls-privacy.mdx

@@ -44,11 +44,11 @@ Typically the numbered host is fixed for your account, and it appears in `log/ne
 
 For required changes when you want to create firewall rules to allow the agent to communicate, see [Networks](/docs/using-new-relic/cross-product-functions/install-configure/networks). For more information about security measures for your data in transit to New Relic or at rest in our storage, see [Data encryption](/docs/security/new-relic-security/compliance/data-encryption).
 
-## Cloud Data Storage [#cloud-data-storage]
+## Cloud data storage [#cloud-data-storage]
 
 New Relic uses a multi-cloud data storage approach in two regions currently, the United States and the European Union. We currently have data storage in Amazon Web Services and Azure in those regions. Data is stored in our New Relic telemetry database. 
 
-We have specific certifications and standards as it pertains to data storage, which can be found in more detail in our [Certifications, standards, and regulations](https://docs.newrelic.com/docs/security/security-privacy/compliance/regulatory-audits-new-relic-services/) documentation. 
+We have specific certifications and standards as it pertains to data storage, which can be found in more detail in our [Certifications, standards, and regulations](/docs/security/security-privacy/compliance/regulatory-audits-new-relic-services/) documentation. 
 
 ## Data access [#Data_Access]