Minor rewording

Author: pwseg

src/connections/sources/catalog/libraries/website/javascript/troubleshooting.md

@@ -205,16 +205,16 @@ The Analytics.js library sets the `context.page.referrer` value from the `window
 
 ## Does Segment support using strict Content Security Policy (CSP) on the page?
 
-If you are using a nonce-based security policy that allows JavaScript to be downloaded from specific locations, then you will need to update the CSP to account for all Segment domains. Therefore, beyond allowing the main `analytics.min.js` script, you should also allow the following paths in your CSP:
+If you're using a security policy that allows JavaScript downloads from specific locations using nonces, then you'll need to update the CSP to include all Segment domains. In addition to allowing the main `analytics.min.js` script, you should also allow the following paths in your CSP:
 - `https://cdn.segment.com/v1/projects/<WRITE_KEY>/settings`
 - `https://cdn.segment.com/analytics-next/bundles/*`
 - `https://cdn.segment.com/next-integrations/integrations/*`
 
-Your CSP may also require whitelisting approved domains, in which case you'll want to allow the following endpoints: 
+Your CSP may also require allowlisting approved domains, in which case you'll want to allow the following endpoints: 
 - `api.segment.io`
 - `cdn.segment.com`
 
-You will also need to modify the Segment script with your `nonce` tag, which should match the value specified in your Content Security Policy.
+You'll also need to modify the Segment script with your `nonce` tag, which should match the value specified in your Content Security Policy.
 
 > info ""
 > Since Segment interacts with several integrations, support surrounding Content Security Policy issues is limited.