diff --git a/src/content/docs/page-shield/how-it-works/index.mdx b/src/content/docs/page-shield/how-it-works/index.mdx
index d89e229e458566e..2c89cf63f14fc33 100644
--- a/src/content/docs/page-shield/how-it-works/index.mdx
+++ b/src/content/docs/page-shield/how-it-works/index.mdx
@@ -18,7 +18,7 @@ Enabling Page Shield adds a <GlossaryTooltip term="content security policy (CSP)
 
 The **Monitors** dashboard shows the list of active scripts, connections, and cookies. The **All Reported Scripts** and **All Reported Connections** dashboards show the full list of detected scripts and connections in your domain, respectively, including infrequent and inactive ones.
 
-Page Shield adds a CSP report-only HTTP header used to monitor webpage resources to a sample of sent responses. This means that there may be a [small delay](/page-shield/troubleshooting/#why-do-i-not-see-scripts-after-i-activated-page-shield) between deploying a script or cookie and having its data displayed in Page Shield's dashboards.
+Page Shield adds a CSP report-only HTTP header used to monitor webpage resources to a sample of sent responses. This means that there may be a [small delay](/page-shield/troubleshooting/#page-shield-does-not-show-any-resources-after-activating-it) between deploying a script or cookie and having its data displayed in Page Shield's dashboards.
 
 Enterprise customers with a paid add-on have access to additional classification mechanisms based on threat feeds to determine if a script, or a connection made by a script, is malicious. For more information, refer to [Malicious script and connection detection](/page-shield/how-it-works/malicious-script-detection/).
 
diff --git a/src/content/docs/page-shield/troubleshooting.mdx b/src/content/docs/page-shield/troubleshooting.mdx
index 6175aa61e78bced..90510390b785e22 100644
--- a/src/content/docs/page-shield/troubleshooting.mdx
+++ b/src/content/docs/page-shield/troubleshooting.mdx
@@ -8,17 +8,21 @@ sidebar:
 
 import { GlossaryTooltip } from "~/components";
 
-## Why do I not see scripts after I activated Page Shield?
+### How do I set up Page Shield?
+
+For help setting up Page Shield, refer to our [get started guide](/page-shield/get-started/).
+
+## Page Shield does not show any resources after activating it
 
 Page Shield does not collect data on every single page view. Instead, it uses a sampling approach to gather information efficiently. This means that domains with lower traffic might take longer to generate initial reports, as these domains need more page views to accumulate enough samples. To speed up the reporting process, it is recommended that you actively generate traffic to your application after [activating Page Shield](/page-shield/get-started/). This will provide Page Shield with more data to work with, leading to faster report generation.
 
-## Why do I see scripts that I do not recognize?
+## Page Shield shows scripts and connections that I do not recognize
 
 Scripts often reference other scripts outside your application.
 
 But, if you see unexpected scripts on your Script Monitor dashboard, check them for signs of malicious activity.
 
-## Why do I see warnings in my browser's developer tools related to Content Security Policy (CSP)?
+## I get warnings in my browser's developer tools related to Content Security Policy (CSP)
 
 Page Shield uses a <GlossaryTooltip term="content security policy (CSP)">Content Security Policy (CSP)</GlossaryTooltip> report-only directive to gather a list of all scripts running on your application.
 
@@ -34,7 +38,7 @@ is required to enable inline execution.
 
 You can safely ignore these warnings, since they are related to the reports that Page Shield requires to detect loaded scripts. For more information, refer to [How Page Shield works](/page-shield/how-it-works/).
 
-## Why do I get policy violation reports for a domain I allowlisted?
+## I get policy violation reports for a domain I allowlisted
 
 Policy violations reported via CSP's [report-only directive](/page-shield/reference/csp-header/) do not take into consideration any redirects or redirect HTTP status codes. This is [by design](https://www.w3.org/TR/CSP3/#create-violation-for-request) for security reasons.
 
@@ -43,11 +47,3 @@ Some third-party services you may want to cover in your Page Shield allow polici
 For example, if you add the `adservice.google.com` domain to an allow policy, you could get policy violation reports for this domain due to redirects to a different domain (not present in your allow policy). In this case, the violation report would still mention the original domain, and not the domain of the redirected destination, which can cause some confusion.
 
 To try to solve this issue, add the domain of the redirected destination to your allow policy. You may need to add several domains to your policy due to redirects.
-
-## Do I have access to Page Shield?
-
-Yes, Page Shield is available on all plans. For details on the available features per plan, refer to [Availability](/page-shield/#availability).
-
-### How do I set up Page Shield?
-
-For help setting up Page Shield, refer to our [get started guide](/page-shield/get-started/).