Merge branch 'cloudflare:production' into lucas/flux-seed

Author: coffee-mug

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.
 
-Since Page Shield monitoring is based on sampling, there may be a small delay 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/#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.
 
 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/).
 

src/content/docs/page-shield/reference/csp-header.mdx

@@ -22,7 +22,7 @@ content-security-policy-report-only: script-src 'none'; connect-src 'none'; repo
 
 :::note[Notes]
 
-Cloudflare adds the CSP report-only HTTP header used to monitor webpages resources to a sample of sent responses.
+Cloudflare adds the CSP report-only HTTP header used to monitor webpage resources to a sample of sent responses.
 
 Configuring [log policies](/page-shield/policies/) will add other CSP report-only headers to responses. Cloudflare will not perform any sampling for these report-only headers related to customer-defined policies.
 

src/content/docs/waf/detections/malicious-uploads/example-rules.mdx

@@ -40,10 +40,10 @@ This custom rule example blocks requests addressed at `/upload` with uploaded co
 
 This custom rule example blocks requests with uploaded content objects over 15 MB in size (the current content scanning limit):
 
-- Expression: `any(cf.waf.content_scan.obj_sizes[*] >= 15000000)`
+- Expression: `any(cf.waf.content_scan.obj_sizes[*] >= 15728640)`
 - Action: _Block_
 
-In this example, you must also test for equality because currently any file over 15 MB will be handled internally as if it had a size of 15 MB. This means that using the `>` (greater than) [comparison operator](/ruleset-engine/rules-language/operators/#comparison-operators) would not work for this particular rule — you should use `>=` (greater than or equal) instead.
+In this example, you must also test for equality because currently any file over 15 MB will be handled internally as if it had a size of 15 MB (15,728,640 bytes). This means that using the `>` (greater than) [comparison operator](/ruleset-engine/rules-language/operators/#comparison-operators) would not work for this particular rule — you should use `>=` (greater than or equal) instead.
 
 ---