Replace instances of whitelist/blacklist

content/en/docs/appstore/use-content/platform-supported-content/widgets/htmlelement.md

@@ -79,7 +79,7 @@ For more information, see [Common Section](/refguide/common-widget-properties/#c
 
 #### Sanitization Configuration
 
-This setting stores the [DOMPurify](https://cure53.de/purify) library configuration in JSON. Use this setting to fine-tune how the sanitization process handles input HTML. You can block tags, whitelist dangerous tags and values, and more.
+This setting stores the [DOMPurify](https://cure53.de/purify) library configuration in JSON. Use this setting to fine-tune how the sanitization process handles input HTML. You can block tags, safelist dangerous tags and values, and more.
 
 For example, here is a short config that disallows all `<style>`:
 

content/en/docs/howto8/collaboration-requirements-management/troubleshoot-network-issues-for-team-server.md

@@ -24,7 +24,7 @@ Team Server is implemented using Subversion and Mendix Studio Pro uses the HTTPS
 * The HTTP port (TCP 80) needs to be open
 * WebDAV (verbs within the HTTP protocol) needs to be enabled on any proxy server
 
-Mendix Studio Pro connects to `https://teamserver.sprintr.com/` and with the domains shown in the diagram below over HTTPS on port 443. These domains should be added to the firewall white list:
+Mendix Studio Pro connects to `https://teamserver.sprintr.com/` and with the domains shown in the diagram below over HTTPS on port 443. These domains should be added to the firewall safe list:
 
 {{< figure src="/attachments/howto8/collaboration-requirements-management/troubleshoot-network-issues-for-team-server/networkaccessmendixplatform.jpg" alt="Domains home.mendix.com, cloud.mendix.com, and teamserver.sprintr.com need to be accessible on port 443 from your network" class="no-border" >}}
 

content/en/docs/refguide/mobile/getting-started-with-mobile/prerequisites.md

@@ -38,7 +38,7 @@ Native mobile apps are not run in the device browser like web-based Mendix apps.
 
 ### Air-Gapped Development
 
-Developing and building native mobile apps requires access to several online resources. Without whitelisting these resources, a native mobile build will fail.
+Developing and building native mobile apps requires access to several online resources. Without safelisting these resources, a native mobile build will fail.
 
 For development:
 

content/en/docs/refguide/version-control/version-control-troubleshooting/repository-size.md

@@ -106,7 +106,7 @@ The tool is currently in public beta. The cleanup tool can be downloaded [here](
 {{% /alert %}}
 
 {{% alert color="info" %}}
-This tool is executed on a Mendix Git repository. If your Mendix app is still on SVN you will first have to migrate to Git. In case the Migrate button is not showing on the Team Server page after you open your app in [Apps](https://sprintr.home.mendix.com/), because of the size restrictions, you can reach out to your CSM to get your app whitelisted.
+This tool is executed on a Mendix Git repository. If your Mendix app is still on SVN you will first have to migrate to Git. In case the Migrate button is not showing on the Team Server page after you open your app in [Apps](https://sprintr.home.mendix.com/), because of the size restrictions, you can reach out to your CSM to get your app safelisted.
 {{% /alert %}}
 
 ### Cleanup Process

content/en/docs/refguide/version-control/version-control-troubleshooting/troubleshoot-team-server-issues.md

@@ -19,7 +19,7 @@ Mendix Studio Pro uses the HTTPS (TCP) to communicate with the Team Server. To a
 * The HTTPS port (TCP 443) needs to be open
 * The HTTP port (TCP 80) needs to be open
 
-Mendix Studio Pro connects to `https://teamserver.sprintr.com/` and with the domains shown in the diagram below over HTTPS on port 443. These domains should be added to the firewall white list:
+Mendix Studio Pro connects to `https://teamserver.sprintr.com/` and with the domains shown in the diagram below over HTTPS on port 443. These domains should be added to the firewall safe list:
 
 {{< figure src="/attachments/refguide/version-control/troubleshoot-version-control-issues/networkaccessmendixplatform.png" alt="Domains home.mendix.com, cloud.mendix.com, and git.api.mendix.com need to be accessible on port 443 from your network" class="no-border" >}}
 

content/en/docs/refguide10/mobile/getting-started-with-mobile/prerequisites.md

@@ -38,7 +38,7 @@ Native mobile apps are not run in the device browser like web-based Mendix apps.
 
 ### Air-Gapped Development
 
-Developing and building native mobile apps requires access to several online resources. Without whitelisting these resources, a native mobile build will fail.
+Developing and building native mobile apps requires access to several online resources. Without safelisting these resources, a native mobile build will fail.
 
 For development:
 

content/en/docs/refguide10/version-control/version-control-troubleshooting/repository-size.md

@@ -106,7 +106,7 @@ The tool is currently in public beta. The cleanup tool can be downloaded [here](
 {{% /alert %}}
 
 {{% alert color="info" %}}
-This tool is executed on a Mendix Git repository. If your Mendix app is still on SVN you will first have to migrate to Git. In case the Migrate button is not showing on the Team Server page after you open your app in [Apps](https://sprintr.home.mendix.com/), because of the size restrictions, you can reach out to your CSM to get your app whitelisted.
+This tool is executed on a Mendix Git repository. If your Mendix app is still on SVN you will first have to migrate to Git. In case the Migrate button is not showing on the Team Server page after you open your app in [Apps](https://sprintr.home.mendix.com/), because of the size restrictions, you can reach out to your CSM to get your app safelisted.
 {{% /alert %}}
 
 ### Cleanup Process

content/en/docs/refguide10/version-control/version-control-troubleshooting/troubleshoot-team-server-issues.md

@@ -19,7 +19,7 @@ Mendix Studio Pro uses the HTTPS (TCP) to communicate with the Team Server. To a
 * The HTTPS port (TCP 443) needs to be open
 * The HTTP port (TCP 80) needs to be open
 
-Mendix Studio Pro connects to `https://teamserver.sprintr.com/` and with the domains shown in the diagram below over HTTPS on port 443. These domains should be added to the firewall white list:
+Mendix Studio Pro connects to `https://teamserver.sprintr.com/` and with the domains shown in the diagram below over HTTPS on port 443. These domains should be added to the firewall safe list:
 
 {{< figure src="/attachments/refguide10/version-control/troubleshoot-version-control-issues/networkaccessmendixplatform.png" alt="Domains home.mendix.com, cloud.mendix.com, and git.api.mendix.com need to be accessible on port 443 from your network" class="no-border" >}}
 

content/en/docs/refguide9/mobile/getting-started-with-mobile/prerequisites.md

@@ -37,7 +37,7 @@ Native mobile apps are not run in the device browser like web-based Mendix apps.
 
 ### Air-Gapped Development
 
-Developing and building native mobile apps requires access to several online resources. Without whitelisting these resources, a native mobile build will fail.
+Developing and building native mobile apps requires access to several online resources. Without safelisting these resources, a native mobile build will fail.
 
 For development:
 

content/en/docs/refguide9/version-control/version-control-troubleshooting/troubleshoot-team-server-issues.md

@@ -26,7 +26,7 @@ If you use SVN for version control you also need the following:
 
 * WebDAV (verbs within the HTTP protocol) needs to be enabled on any proxy server
 
-Mendix Studio Pro connects to `https://teamserver.sprintr.com/` and with the domains shown in the diagram below over HTTPS on port 443. These domains should be added to the firewall white list:
+Mendix Studio Pro connects to `https://teamserver.sprintr.com/` and with the domains shown in the diagram below over HTTPS on port 443. These domains should be added to the firewall safe list:
 
 {{< figure src="/attachments/refguide9/version-control/troubleshoot-version-control-issues/networkaccessmendixplatform.png" alt="Domains home.mendix.com, cloud.mendix.com, and git.api.mendix.com (or teamserver.sprintr.com in case of SVN) need to be accessible on port 443 from your network" class="no-border" >}}
 

content/en/docs/releasenotes/studio-pro/9/9.5.md

@@ -90,7 +90,7 @@ weight: 95
 
 * <a id="bc-2678"></a>When changing an object member, the member’s state will now always become `'CHANGED'`, even if the old value and the new value are the same. For example, suppose we have a committed object `$User` with `$User/Name = 'Alice'`. Applying a change to set `$User/Name` to `'Alice'` results in the member becoming `'CHANGED'`, even though the name is the same. Previously, this would have resulted in the member remaining `'UNCHANGED'`.
 * We changed the format of the `mx-name-` class of links inside [menu widget](/refguide9/menu-widgets/) items. Previously, it was `mx-name-GUID-NUMBER`, but now it is `mx-name-WIDGETNAME-NUMBER`. This removes an inconsistency in this class format and should make it easier to use. However, this might require you to change the locators in your tests.
-* [Native Mobile Resources](/appstore/modules/native-mobile-resources/) versions 2.0.1 and below have been black-listed due to changes required to support Android 11.
+* [Native Mobile Resources](/appstore/modules/native-mobile-resources/) versions 2.0.1 and below have been blocklisted due to changes required to support Android 11.
 * In line with the [mobile operating system support policy](/refguide9/system-requirements/#mobile), we are removing support for iOS and Safari 12.
 
 ### Known Issues