diff --git a/docs/docs.json b/docs/docs.json
index 211cb9c4d3..d9ac4c2bd8 100644
--- a/docs/docs.json
+++ b/docs/docs.json
@@ -139,7 +139,9 @@
               {
                 "group": "Compliance",
                 "pages": [
-                  "user-guide/compliance/tutorials/cross-provider-compliance"
+                  "user-guide/compliance/tutorials/compliance",
+                  "user-guide/compliance/tutorials/cross-provider-compliance",
+                  "user-guide/compliance/tutorials/threatscore"
                 ]
               },
               {
@@ -425,13 +427,6 @@
               }
             ]
           },
-          {
-            "group": "Compliance",
-            "pages": [
-              "user-guide/compliance/tutorials/compliance",
-              "user-guide/compliance/tutorials/threatscore"
-            ]
-          },
           {
             "group": "Cookbooks",
             "pages": [
diff --git a/docs/style.css b/docs/style.css
index 9585e7cdeb..9a1ed19a0f 100644
--- a/docs/style.css
+++ b/docs/style.css
@@ -71,7 +71,7 @@
    Rendered as a trailing ::after glyph so sidebar labels stay left-aligned.
    Nested groups render as li[data-title] with a button toggle; top-level groups
    render as h3 headings. Every ungated group that shares a name with a gated one
-   (Providers, Compliance, Prowler Cloud, Prowler Lighthouse AI) is top-level,
+   (Providers, Prowler Cloud, Prowler Lighthouse AI) is top-level,
    so plain li[data-title] selectors match only the gated nested groups, folded
    or unfolded. The Security tab group is top-level (h3) and always expanded,
    so it is selected through its sibling list content with :has().
@@ -82,7 +82,6 @@
 li[data-title="Prowler Cloud"] > button span:first-child::after,
 li[data-title="Prowler Lighthouse AI"] > button span:first-child::after,
 li[data-title="Providers"] > button span:first-child::after,
-li[data-title="Compliance"] > button span:first-child::after,
 li[data-title="Scans"] > button span:first-child::after,
 li[data-title="Prowler MCP"] > button span:first-child::after,
 div:has(+ ul a[href="/security/encryption"]) h3 span::after,
diff --git a/docs/user-guide/compliance/tutorials/compliance.mdx b/docs/user-guide/compliance/tutorials/compliance.mdx
index 9ee5df438d..6c13f60529 100644
--- a/docs/user-guide/compliance/tutorials/compliance.mdx
+++ b/docs/user-guide/compliance/tutorials/compliance.mdx
@@ -1,5 +1,6 @@
 ---
 title: 'Compliance'
+sidebarTitle: 'Overview'
 description: 'Run security checks against compliance frameworks, review posture across providers, and download CSV or PDF reports from Prowler Cloud and Prowler Local Server, or CSV reports from Prowler CLI.'
 ---
 
@@ -8,7 +9,7 @@ Prowler maps every security check to one or more industry-standard compliance fr
 Out of the box, Prowler covers frameworks such as CIS Benchmarks, NIST 800-53, NIST CSF, NIS2, ENS RD2022, ISO 27001, PCI-DSS, SOC 2, GDPR, HIPAA, AWS Well-Architected, BSI C5, CSA CCM, MITRE ATT&CK, KISA ISMS-P, FedRAMP, and Prowler ThreatScore. The full catalog is available at [Prowler Hub](https://hub.prowler.com/compliance).
 
 <Note>
-For the unified compliance score methodology used across frameworks, see [Prowler ThreatScore Documentation](/user-guide/compliance/tutorials/threatscore).
+For the unified compliance score methodology used across frameworks, see [Prowler ThreatScore](/user-guide/compliance/tutorials/threatscore).
 </Note>
 
 <CardGroup cols={2}>
@@ -74,7 +75,7 @@ When the selected scan includes Prowler ThreatScore data, a dedicated card appea
 
 Selecting the card opens the ThreatScore framework detail page, covered in [Working With the Framework Detail Page](#working-with-the-framework-detail-page).
 
-For a complete explanation of the methodology, formula, and weighting, see [Prowler ThreatScore Documentation](/user-guide/compliance/tutorials/threatscore).
+For a complete explanation of the methodology, formula, and weighting, see [Prowler ThreatScore](/user-guide/compliance/tutorials/threatscore).
 
 ### Exploring the Framework Grid
 
@@ -263,6 +264,6 @@ To request a new framework or contribute one, see [Creating a New Security Compl
 ## Related Documentation
 
 * [Cross-Provider Compliance](/user-guide/compliance/tutorials/cross-provider-compliance)
-* [Prowler ThreatScore Documentation](/user-guide/compliance/tutorials/threatscore)
+* [Prowler ThreatScore](/user-guide/compliance/tutorials/threatscore)
 * [Creating a New Security Compliance Framework in Prowler](/developer-guide/security-compliance-framework)
 * [Prowler Cloud — Getting Started](/user-guide/tutorials/prowler-app)
diff --git a/docs/user-guide/compliance/tutorials/cross-provider-compliance.mdx b/docs/user-guide/compliance/tutorials/cross-provider-compliance.mdx
index b05fb6b5be..545f5fb834 100644
--- a/docs/user-guide/compliance/tutorials/cross-provider-compliance.mdx
+++ b/docs/user-guide/compliance/tutorials/cross-provider-compliance.mdx
@@ -204,6 +204,6 @@ The PDF detail section renders only **failed** requirements by default so the re
 ## Related Documentation
 
 * [Compliance](/user-guide/compliance/tutorials/compliance)
-* [Prowler ThreatScore Documentation](/user-guide/compliance/tutorials/threatscore)
+* [Prowler ThreatScore](/user-guide/compliance/tutorials/threatscore)
 * [Creating a New Security Compliance Framework in Prowler](/developer-guide/security-compliance-framework)
 * [Prowler Cloud — Getting Started](/user-guide/tutorials/prowler-app)
diff --git a/docs/user-guide/compliance/tutorials/threatscore.mdx b/docs/user-guide/compliance/tutorials/threatscore.mdx
index 492f84c5d2..8d790cf90d 100644
--- a/docs/user-guide/compliance/tutorials/threatscore.mdx
+++ b/docs/user-guide/compliance/tutorials/threatscore.mdx
@@ -1,5 +1,5 @@
 ---
-title: "Prowler ThreatScore Documentation"
+title: "Prowler ThreatScore"
 ---
 
 ## Introduction