Terminology fixes (#1839)

* terminology fix

* terminology fix

Author: PeloWriter

src/collections/_documentation/accounts/quotas/manage-event-stream-guide.md

@@ -25,8 +25,8 @@ The SDK includes multiple `Integrations` - functional plugins that you can confi
 
 The integration is enabled by default and adds the following configuration options to the SDK:
 
-- `whitelistUrls`: Domains that might raise acceptable exceptions represented in a regex pattern format.
-- `blacklistUrls`: A list of strings or regex patterns that match error URLs which should be blocked from sending events (Configuring both options on the SDK can be used to block **subdomains** of the domains listed in `whitelistUrls`).
+- `allowUrls`: Domains that might raise acceptable exceptions represented in a regex pattern format.
+- `denyUrls`: A list of strings or regex patterns that match error URLs which should be blocked from sending events (Configuring both options on the SDK can be used to block **subdomains** of the domains listed in `allowUrls`).
 - `ignoreErrors`: Instruct the SDK to never send an error to Sentry if it matches any of the listed error **messages**. If no message is available, the SDK will try to compare against an underlying **exception type and value**.
 
 For more information and code samples checkout:

src/collections/_documentation/clients/ruby/integrations.md

@@ -23,7 +23,7 @@ require 'sentry-raven-without-integrations'
 Raven.inject_only(:railties, :rack, :rake)
 ```
 
-To blacklist integrations:
+To deny integrations:
 
 ```ruby
 require 'sentry-raven-without-integrations'

src/collections/_documentation/performance-monitoring/configuration/javascript.md

@@ -78,7 +78,7 @@ The default value of `tracingOrigins` is `['localhost', /^\//]`. The JavaScript
 - Therefore, the option needs to be configured like this: `new ApmIntegrations.Tracing({tracingOrigins: ['api.example.com']})`
 - Now outgoing XHR/fetch requests to `api.example.com` will get the `sentry-trace` header attached
 
-*NOTE:* You need to make sure your web server CORS is configured to allow the `sentry-trace` header. The configuration might look like `"Access-Control-Allow-Headers: sentry-trace"`, but this depends a lot on your setup. If you do not whitelist the `sentry-trace` header, the request might be blocked.
+*NOTE:* You need to make sure your web server CORS is configured to allow the `sentry-trace` header. The configuration might look like `"Access-Control-Allow-Headers: sentry-trace"`, but this depends a lot on your setup. If you do not allow the `sentry-trace` header, the request might be blocked.
 
 **beforeNavigation Option**s
 

src/collections/_documentation/platforms/javascript/cordova.md

@@ -11,7 +11,7 @@ When you [install](/error-reporting/quickstart/?platform=cordova) `sentry-cordov
 
 ## Configuration
 
-You will need to whitelist Sentry's domain in your `config.xml` like:
+You will need to allow Sentry's domain in your `config.xml` like:
 
 ```xml
 <access origin="sentry.io" />

src/collections/_documentation/platforms/javascript/index.md

@@ -639,7 +639,7 @@ Sentry.init({
 
 #### Decluttering Sentry
 
-The first thing to do is consider constructing a whitelist of domains which might raise acceptable exceptions.
+The first thing to do is consider constructing an allowed list of domains which might raise acceptable exceptions.
 
 If your scripts are loaded from `cdn.example.com` and your site is `example.com` it’d be reasonable to set `allowUrls` to:
 

src/collections/_documentation/platforms/node/default-integrations.md

@@ -17,10 +17,10 @@ to `integrations` option. For example: to change fatal error handler
 
 _Import name: `Sentry.Integrations.InboundFilters`_
 
-This integration allows developers to ignore specific errors based on the type of message, as well as blocklist/whitelist URLs from which the exception originated.
-Keep in mind that blocklist and whitelist work only for captured exceptions, not raw message events.
+This integration allows developers to ignore specific errors based on the type of message, as well as deny/allow URLs from which the exception originated.
+Keep in mind that denyUrl and allowUrl work only for captured exceptions, not raw message events.
 
-To configure it, use `ignoreErrors`, `blocklistUrls` and `whitelistUrls` SDK options directly.
+To configure it, use `ignoreErrors`, `denyUrls` and `allowUrls` SDK options directly.
 
 ### FunctionToString
 

src/collections/_documentation/workflow/integrations/global-integrations.md

@@ -230,7 +230,7 @@ openssl x509 -pubkey -noout -in bitbucket_publickey.cer  > bitbucket_publickey.p
 
 ##### III. Connect your Bitbucket Server application with Sentry
 {% capture __alert_content -%}
-Confirm [Sentry's IP ranges](/meta/ip-ranges/) are whitelisted.
+Confirm [Sentry's IP ranges](/meta/ip-ranges/) are allowed.
 {%- endcapture -%}
 {%- include components/alert.html
   title="Note"
@@ -458,7 +458,7 @@ Sentry owner or manager permissions, and GitHub owner permissions are required t
 
 ###### Add new GitHub App
 
-1. Confirm [Sentry's IP ranges](/meta/ip-ranges/) are whitelisted for your GitHub Enterprise instance.
+1. Confirm [Sentry's IP ranges](/meta/ip-ranges/) are allowed for your GitHub Enterprise instance.
 2. In your GitHub Enterprise organization, navigate to Settings > Developer Settings > **GitHub Apps** and click to add a new **New GitHub App**.
 
     [{% asset github-e-new-app.png %}]({% asset github-e-new-app.png @path %})
@@ -685,7 +685,7 @@ A `<SHORT-ID>` may look something like 'BACKEND-C' in the image below.
 #### Troubleshooting
 
 FAQ:
-- I'm using GitLab on-premise. Do I need to whitelist Sentry's IP addresses?
+- I'm using GitLab on-premise. Do I need to allow Sentry's IP addresses?
     - Yes. You can find our IP ranges [ here ](/meta/ip-ranges/).
 - Do you support subgroups?
     - Currently, we only support subgroups for users using GitLab 11.6 or higher.
@@ -815,7 +815,7 @@ openssl x509 -pubkey -noout -in jira_publickey.cer  > jira_publickey.pem
 
 ##### III. Connect your Jira Server application with Sentry
 {% capture __alert_content -%}
-Confirm [Sentry's IP ranges](/meta/ip-ranges/) are whitelisted.
+Confirm [Sentry's IP ranges](/meta/ip-ranges/) are allowed.
 {%- endcapture -%}
 {%- include components/alert.html
   title="Note"
@@ -1140,5 +1140,5 @@ Follow the instructions in the link below:
 
 If you're having trouble setting up Sentry with your on-premise integration like JIRA Server, Bitbucket Server, GitHub Enterprise, or Gitlab:
 - Ensure that the installation URL you provided is a fully qualified domain name (FQDN), which is resolvable on the internet.
-- Double-check that the IP addresses Sentry uses to make outbound requests are whitelisted </meta/ip-ranges/>.
+- Double-check that the IP addresses Sentry uses to make outbound requests are [allowed](/meta/ip-ranges/).
 - Make sure that Sentry's access to your installation URL is not path restricted.

src/collections/_documentation/workflow/integrations/integration-platform/index.md

@@ -301,7 +301,7 @@ For more information, see the [full documentation on UI Components](/workflow/in
 Webhooks allows your service to receive requests about specific resources, depending on your selection. For more information, see the [full documentation on Webhooks](/workflow/integrations/integration-platform/webhooks/).
 
 ## Authorized Origins
-It is possible to use Auth Tokens from the browser if you whitelist the origins of the pages making the requests. In the field that is called `Authorized JavaScript Origins`, add each origin you want to be separated by a newline (for example, docs.sentry.io). You do not need the protocol in the origin (http or https). At this moment, you cannot use any wildcard characters (for example, `*.sentry.io`), so if you have multiple subdomains, you will need to add them individually.
+It is possible to use Auth Tokens from the browser if you allow the origins of the pages making the requests. In the field that is called `Authorized JavaScript Origins`, add each origin you want to be separated by a newline (for example, docs.sentry.io). You do not need the protocol in the origin (http or https). At this moment, you cannot use any wildcard characters (for example, `*.sentry.io`), so if you have multiple subdomains, you will need to add them individually.
 
 ## FAQ