Remove Details tags from all recommended policy pages

Author: maxvp

src/content/docs/learning-paths/secure-internet-traffic/build-dns-policies/recommended-dns-policies.mdx

@@ -5,7 +5,7 @@ sidebar:
   order: 3
 ---
 
-import { Details, Render, Tabs, TabItem } from "~/components";
+import { Render, Tabs, TabItem } from "~/components";
 
 We recommend you add the following DNS policies to build an Internet and SaaS app security strategy for your organization.
 

src/content/docs/learning-paths/secure-internet-traffic/build-http-policies/recommended-http-policies.mdx

@@ -5,11 +5,11 @@ sidebar:
   order: 5
 ---
 
-import { Details, Render } from "~/components";
+import { Render } from "~/components";
 
 We recommend you add the following HTTP policies to build an Internet and SaaS app security strategy for your organization.
 
-<Details header="All-HTTP-Application-InspectBypass">
+## All-HTTP-Application-InspectBypass
 
 Bypass HTTP inspection for applications that use embedded certificates. This will help avoid any certificate pinning errors that may arise from an initial rollout.
 
@@ -18,9 +18,7 @@ Bypass HTTP inspection for applications that use embedded certificates. This wil
 	product="cloudflare-one"
 />
 
-</Details>
-
-<Details header="Android-HTTP-Application-InspectionBypass">
+## Android-HTTP-Application-InspectionBypass
 
 Bypass HTTPS inspection for Android applications (such as Google Drive) that use certificate pinning, which is incompatible with Gateway inspection.
 
@@ -29,9 +27,7 @@ Bypass HTTPS inspection for Android applications (such as Google Drive) that use
 | Application                  | in       | _Google Drive_                    | And   | Do Not Inspect |
 | Passed Device Posture Checks | in       | _OS Version Android (OS version)_ |       |                |
 
-</Details>
-
-<Details header="All-HTTP-Domain-Inspection-Bypass">
+## All-HTTP-Domain-Inspection-Bypass
 
 Bypass HTTP inspection for a custom list of domains identified as incompatible with TLS inspection.
 
@@ -40,19 +36,15 @@ Bypass HTTP inspection for a custom list of domains identified as incompatible w
 | Domain   | in list  | _DomainInspectionBypass_ | Or    | Do Not Inspect |
 | Domain   | in list  | _Known Domains_          |       |                |
 
-</Details>
-
-<Details header="All-HTTP-SecurityRisks-Blocklist">
+## All-HTTP-SecurityRisks-Blocklist
 
 <Render file="zero-trust/blocklist-security-categories" />
 
 | Selector       | Operator | Value                | Action |
 | -------------- | -------- | -------------------- | ------ |
 | Security Risks | in       | _All security risks_ | Block  |
 
-</Details>
-
-<Details header="All-HTTP-ContentCategories-Blocklist">
+## All-HTTP-ContentCategories-Blocklist
 
 <Render
 	file="zero-trust/content-categories-description"
@@ -64,9 +56,7 @@ Bypass HTTP inspection for a custom list of domains identified as incompatible w
 	product="cloudflare-one"
 />
 
-</Details>
-
-<Details header="All-HTTP-DomainHost-Blocklist">
+## All-HTTP-DomainHost-Blocklist
 
 <Render file="zero-trust/blocklist-domain-host" params={{ one: "HTTP" }} />
 
@@ -76,9 +66,7 @@ Bypass HTTP inspection for a custom list of domains identified as incompatible w
 | Host     | in list       | _Host Blocklist_   | Or    |        |
 | Host     | matches regex | `.*example\.com`   |       |        |
 
-</Details>
-
-<Details header="All-HTTP-Application-Blocklist">
+## All-HTTP-Application-Blocklist
 
 <Render file="zero-trust/blocklist-application" />
 
@@ -87,9 +75,7 @@ Bypass HTTP inspection for a custom list of domains identified as incompatible w
 	product="cloudflare-one"
 />
 
-</Details>
-
-<Details header="PrivilegedUsers-HTTP-Any-Isolate">
+## PrivilegedUsers-HTTP-Any-Isolate
 
 Isolate traffic for privileged users who regularly access critical systems or execute actions such as threat analysis and malware testing.
 
@@ -99,9 +85,7 @@ Security teams often need to perform threat analysis or malware testing that cou
 | ---------------- | -------- | ------------------ | ------- |
 | User Group Names | in       | _Privileged Users_ | Isolate |
 
-</Details>
-
-<Details header="Quarantined-Users-HTTP-Restricted-Access">
+## Quarantined-Users-HTTP-Restricted-Access
 
 <Render file="zero-trust/blocklist-restricted-users" />
 
@@ -110,15 +94,11 @@ Security teams often need to perform threat analysis or malware testing that cou
 | Destination IP   | not in list | _Quarantined-Users-IPAllowlist_ | And   | Block  |
 | User Group Names | in          | _Quarantined Users_             |       |        |
 
-</Details>
-
-<Details header="All-HTTP-Domain-Isolate">
+## All-HTTP-Domain-Isolate
 
 Isolate high risk domains or create a custom list of known risky domains to avoid data exfiltration or malware infection. Ideally, your incident response teams can update the blocklist with an [API automation](/security-center/intel-apis/) to provide real-time threat protection.
 
 | Selector           | Operator | Value                              | Logic | Action  |
 | ------------------ | -------- | ---------------------------------- | ----- | ------- |
 | Content Categories | in       | _New Domain_, _Newly Seen Domains_ | Or    | Isolate |
 | Domain             | in list  | _Domain Isolation_                 |       |         |
-
-</Details>

src/content/docs/learning-paths/secure-internet-traffic/build-network-policies/recommended-network-policies.mdx

@@ -5,13 +5,13 @@ sidebar:
   order: 2
 ---
 
-import { Details, GlossaryTooltip, Render } from "~/components";
+import { GlossaryTooltip, Render } from "~/components";
 
 We recommend you add the following network policies to build an Internet and SaaS app security strategy for your organization.
 
 For more information on building network policies, refer to [Network policies](/cloudflare-one/policies/gateway/network-policies/).
 
-<Details header="Quarantined-Users-NET-Restricted-Access">
+## Quarantined-Users-NET-Restricted-Access
 
 <Render file="zero-trust/blocklist-restricted-users" />
 
@@ -22,9 +22,7 @@ For more information on building network policies, refer to [Network policies](/
 | Domain SNI       | not in list | _Quarantined-Users-DomainAllowlist_ | And   |        |
 | User Group Names | in          | _Quarantined Users_                 |       |        |
 
-</Details>
-
-<Details header="Posture-Fail-NET-Restricted-Access">
+## Posture-Fail-NET-Restricted-Access
 
 Restrict access for devices where baseline posture checks have not passed. If posture checks are integrated with service providers such as Crowdstrike or Intune via the API, this policy dynamically blocks access for devices that do not meet predetermined security requirements.
 
@@ -37,9 +35,7 @@ Restrict access for devices where baseline posture checks have not passed. If po
 
 You can add a number of WARP client device posture checks as needed, such as [Disk encryption](/cloudflare-one/identity/devices/warp-client-checks/disk-encryption/) and [Domain joined](/cloudflare-one/identity/devices/warp-client-checks/domain-joined/). For more information on device posture checks, refer to [Enforce device posture](/cloudflare-one/identity/devices/).
 
-</Details>
-
-<Details header="FinanceUsers-NET-HTTPS-FinanceServers (example)">
+## FinanceUsers-NET-HTTPS-FinanceServers (example)
 
 Allow HTTPS access for user groups. For example, the following policy gives finance users access to any known financial applications:
 
@@ -48,9 +44,7 @@ Allow HTTPS access for user groups. For example, the following policy gives fina
 | Destination IP   | in list  | _Finance Servers_ | And   | Allow  |
 | User Group Names | in       | _Finance Users_   |       |        |
 
-</Details>
-
-<Details header="All-NET-Internet-Blocklist">
+## All-NET-Internet-Blocklist
 
 Block traffic to destination IPs, <GlossaryTooltip term="Server Name Indication (SNI)">SNIs</GlossaryTooltip>, and domain SNIs that are malicious or pose a threat to your organization.
 
@@ -66,9 +60,7 @@ Block traffic to destination IPs, <GlossaryTooltip term="Server Name Indication
 The **Detected Protocol** selector is only available for Enterprise users. For more information, refer to [Protocol detection](/cloudflare-one/policies/gateway/network-policies/protocol-detection/).
 :::
 
-</Details>
-
-<Details header="All-NET-SSH-Internet-Allowlist">
+## All-NET-SSH-Internet-Allowlist
 
 Allow SSH traffic to specific endpoints on the Internet for specific users. You can create a similar policy for other non-web endpoints that required access.
 
@@ -81,9 +73,7 @@ Optionally, you can include a selector to filter by source IP or IdP group.
 | Detected Protocol | is       | _SSH_               | And   |        |
 | User Group Names  | in       | _SSH-Allowed-Users_ |       |        |
 
-</Details>
-
-<Details header="All-NET-NO-HTTP-HTTPS-Internet-Deny">
+## All-NET-NO-HTTP-HTTPS-Internet-Deny
 
 Block all non-web traffic towards the Internet. By using the **Detected Protocol** selector, you will ensure alternative ports for HTTP and HTTPS are allowed.
 
@@ -92,14 +82,10 @@ Block all non-web traffic towards the Internet. By using the **Detected Protocol
 | Destination IP    | not in list | _InternalNetwork_ | And   | Block  |
 | Detected Protocol | not in      | _HTTP_, _HTTP2_   |       |        |
 
-</Details>
-
-<Details header="All-NET-InternalNetwork-ImplicitDeny">
+## All-NET-InternalNetwork-ImplicitDeny
 
 Implicitly deny all of your internal IP ranges included in a list. We recommend you place this policy at the [bottom of your policy list](/learning-paths/secure-internet-traffic/understand-policies/order-of-enforcement/#order-of-precedence) to ensure you explicitly approve traffic defined in the above policies.
 
 | Selector       | Operator | Value                  | Action |
 | -------------- | -------- | ---------------------- | ------ |
 | Destination IP | in list  | _Internal Network IPs_ | Block  |
-
-</Details>