Update troubleshooting

Author: pedrosousa

src/content/docs/page-shield/troubleshooting.mdx

@@ -8,23 +8,19 @@ sidebar:
 
 import { GlossaryTooltip } from "~/components";
 
-### How do I set up Page Shield?
+## Cloudflare does not show any client-side resources after activation
 
-For help setting up Page Shield, refer to our [get started guide](/page-shield/get-started/).
+Cloudflare 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 client-side resource monitoring](/page-shield/get-started/). This will provide Cloudflare with more data to work with, leading to faster report generation.
 
-## 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.
-
-## Page Shield shows scripts and connections that I do not recognize
+## The dashboard 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.
+But, if you see unexpected scripts on your resource monitoring dashboard, check them for signs of malicious activity.
 
 ## 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.
+Cloudflare 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.
 
 Some browsers display scripts being reported as warnings in the console pane of their developer tools. For example:
 
@@ -36,13 +32,13 @@ Either the 'unsafe-inline' keyword, a hash ('sha256-RFWPLDbv2BY+rCkDzsE+0fr8ylGr
 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/).
+You can safely ignore these warnings, since they are related to the reports that Cloudflare requires to detect loaded scripts. For more information, refer to [How Page Shield works](/page-shield/how-it-works/).
 
 ## 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.
 
-Some third-party services you may want to cover in your Page Shield allow policies perform redirects. An example of such a service is Google Ads, which [does not work well with CSP policies](https://support.google.com/adsense/thread/102839782?hl=en&msgid=103611259).
+Some third-party services you may want to cover in your allow policies perform redirects. An example of such a service is Google Ads, which [does not work well with CSP policies](https://support.google.com/adsense/thread/102839782?hl=en&msgid=103611259).
 
 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.