diff --git a/website/docs/using-unleash/compliance/fedramp.mdx b/website/docs/using-unleash/compliance/fedramp.mdx
index 9f986aaf21..ce7ade42ee 100644
--- a/website/docs/using-unleash/compliance/fedramp.mdx
+++ b/website/docs/using-unleash/compliance/fedramp.mdx
@@ -9,7 +9,7 @@ description: 'FedRAMP compliant feature flags at scale with Unleash.'
 
 When operating in a [FedRAMP-compliant](https://www.fedramp.gov/program-basics/) environment, it's crucial to ensure that all integrated systems, including feature flagging solutions, adhere to the same compliance standards. Using a homegrown or third-party feature flag system that does not support FedRAMP standards can compromise your certification and introduce unnecessary risks.
 
-This guide provides an overview of how Unleash features align with FedRAMP controls, helping your organization meet its compliance requirements. 
+This guide provides an overview of how [Unleash Enterprise](https://www.getunleash.io/pricing) features align with FedRAMP controls, helping your organization meet its compliance requirements. 
 
 ## Access Control
 
@@ -53,4 +53,4 @@ This guide provides an overview of how Unleash features align with FedRAMP contr
 | **FedRAMP Control**                                                                                   | **Unleash Feature**                                                                                                         |
 |-------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------|
 | [SC-08 (01) Transmission Confidentiality and Integrity](https://csrc.nist.gov/projects/cprt/catalog#/cprt/framework/version/SP_800_53_5_1_0/home?element=SC-8) (Cryptographic Protection) | Unleash implements cryptographic protection for data in transit, as detailed in our SOC2 report (available upon [request](https://www.getunleash.io/plans/enterprise). |
-| [SC-17 Public Key Infrastructure Certificates](https://csrc.nist.gov/projects/cprt/catalog#/cprt/framework/version/SP_800_53_5_1_0/home?element=SC-17)                              | Unleash uses PKI certificates issued by AWS and Google.                                                                    |
\ No newline at end of file
+| [SC-17 Public Key Infrastructure Certificates](https://csrc.nist.gov/projects/cprt/catalog#/cprt/framework/version/SP_800_53_5_1_0/home?element=SC-17)                              | Unleash uses PKI certificates issued by AWS and Google.                                                                    |
diff --git a/website/docs/using-unleash/compliance/soc2.mdx b/website/docs/using-unleash/compliance/soc2.mdx
index 4148af8de1..d715672f53 100644
--- a/website/docs/using-unleash/compliance/soc2.mdx
+++ b/website/docs/using-unleash/compliance/soc2.mdx
@@ -9,7 +9,7 @@ description: 'SOC2-compliant feature flags at scale with Unleash.'
 
 To get SOC2 certified and maintain your compliance, you must ensure that any system you integrate with, including feature flagging solutions, are also SOC2 certified. Using a homegrown or third-party feature flagging system without SOC2 compliance can compromise your certification and introduce unnecessary risks.
 
-This guide provides an overview of how Unleash features align with SOC2 Type II controls, helping your organization meet its compliance requirements.
+This guide provides an overview of how [Unleash Enterprise](https://www.getunleash.io/pricing) features align with SOC2 Type II controls, helping your organization meet its compliance requirements.
  
 
 ## How Unleash features map to SOC2 Type II controls
@@ -29,4 +29,4 @@ This guide provides an overview of how Unleash features align with SOC2 Type II
 | CC 6.1, CC 6.6 Remote access MFA enforced   | The company's production systems can only be remotely accessed by authorized employees possessing a valid multi-factor authentication (MFA) method. | You can enable MFA through your identity provider, such as Okta or Microsoft Entra ID, after implementing [single sign-on](/reference/sso).                                                      |
 | CC 6.1, CC 6.6 Remote access encrypted and enforced | The company's production systems can only be remotely accessed by authorized employees via an approved encrypted connection. | Unleash is secured by enforcing TLS 1.2.                                                                                                               |
 | CC 6.7 Data transmission encrypted          | The company uses secure data transmission protocols to encrypt confidential and sensitive data when transmitted over public networks. | Unleash is secured by enforcing TLS 1.2.                                                                                                               |
-| SD SOC 2 System Description                 | The company has completed a description of its systems for Section III of the audit report.                                           | This documentation is available in the SOC 2 report in the Trust Center. The report is performed by an external auditor and renewed annually. |
\ No newline at end of file
+| SD SOC 2 System Description                 | The company has completed a description of its systems for Section III of the audit report.                                           | This documentation is available in the SOC 2 report in the Trust Center. The report is performed by an external auditor and renewed annually. |