Rename more instances of blacklist/whitelist

Fixes cockroachdb#7533.

jekyll-algolia-dev/lib/jekyll/algolia/overwrites/githubpages-configuration.rb

@@ -2,7 +2,7 @@
 
 module GitHubPages
   # The github-pages gem will automatically disable every plugin that is not in
-  # the whitelist of plugins allowed by GitHub. This includes any plugin defined
+  # the allowlist of plugins allowed by GitHub. This includes any plugin defined
   # in the `_plugins` folder as well.
   #
   # Users of the jekyll-algolia plugin will use custom plugins in _plugins to

releases/v19.1.0-beta.20190318.md

@@ -8,7 +8,7 @@ summary: Additions and changes in CockroachDB version v19.1.0-beta.20190318 sinc
 
 In addition to bug fixes and various general, enterprise, SQL, and Admin UI enhancements, this release includes several major highlights:
 
-- [**Managed CockroachDB Console**](../cockroachcloud/stable/cockroachcloud-create-your-account.html): Paid managed CockroachDB customers can now sign into their organization's account, view the connection string details, add and edit their IP whitelists on the management console.
+- [**Managed CockroachDB Console**](../cockroachcloud/stable/cockroachcloud-create-your-account.html): Paid managed CockroachDB customers can now sign into their organization's account, view the connection string details, add and edit thier list of allowed IPs on the management console.
 - [**GSSAPI with Kerberos Authentication**](../v19.1/gssapi_authentication.html): CockroachDB now supports the Generic Security Services API (GSSAPI) with Kerberos authentication, which lets you use an external enterprise directory system that supports Kerberos, such as Active Directory. This feature requires an [Enterprise License](../v19.1/enterprise-licensing.html).
 - [**Query Optimizer Hints**](../v19.1/cost-based-optimizer.html#join-hints): The cost-based optimizer now supports hint syntax to force the use of a merge, hash, or lookup join. This let you override the cost-based optimizer's join algorithm selection in cases where you have information about your data that the cost-based optimizer does not yet have.
 - [**Correlated Subqueries**](../v19.1/subqueries.html#correlated-subqueries): Most correlated subqueries are decorrelated and processed by the cost-based-optimizer. However, for those that cannot be decorrelated, CockroachDB now emits an "apply" operator that executes a sub-plan for every row in its input. This allows CockroachDB to execute a large number of additional correlated subqueries that were not able to be executed in v2.1.  

releases/v19.1.0.md

@@ -67,7 +67,7 @@ This section summarizes the most significant, user-facing changes in v19.1.0. Fo
 
 Feature | Description
 --------|------------
-[**Managed CockroachDB Console**](../cockroachcloud/stable/) | Paid managed CockroachDB customers can now sign into their organization's account, view the connection string details, add and edit their IP whitelists on the management console.
+[**Managed CockroachDB Console**](../cockroachcloud/stable/) | Paid managed CockroachDB customers can now sign into their organization's account, view the connection string details, add and edit their list of allowed IPs on the management console.
 
 ### Enterprise features
 

scripts/docs_csat.py

@@ -52,7 +52,7 @@
 args = parser.parse_args()
 
 
-blacklist = ['cockroachdb-in-comparison.html']
+blocklist = ['cockroachdb-in-comparison.html']
 
 
 def initialize_analyticsreporting():
@@ -193,8 +193,8 @@ def create_dict(response, dict):
 
 def calculate_csat(no_votes, yes_votes, pageviews):
 
-    # Remove blacklisted pages.
-    for p in blacklist:
+    # Remove blocklisted pages.
+    for p in blocklist:
         for k in list(pageviews):
             if p in k:
                 del pageviews[k]

v19.1/cluster-setup-troubleshooting.md

@@ -227,7 +227,7 @@ Again, firewalls or hostname issues can cause any of these steps to fail.
 
 If the Admin UI lists live nodes in the **Dead Nodes** table, then you might have a network partition.
 
-**Explanation:** A network partition indicates that the nodes can't communicate with each other in one or both directions because of a configuration problem with the network itself. A symmetric partition is one where the communication is broken in both directions. An asymmetric partition means the connection works in one direction but not the other. An example of a scenario that can cause a network partition is when specific IP addresses or hostnames are whitelisted in the firewall, and then those addresses or names change after tearing down and rebuilding a node.
+**Explanation:** A network partition indicates that the nodes can't communicate with each other in one or both directions because of a configuration problem with the network itself. A symmetric partition is one where the communication is broken in both directions. An asymmetric partition means the connection works in one direction but not the other. An example of a scenario that can cause a network partition is when specific IP addresses or hostnames are allowed by the firewall, and then those addresses or names change after tearing down and rebuilding a node.
 
 The effect of a network partition depends on which nodes are partitioned and where the ranges are located. It depends to a large extent on whether localities have been defined.
 

v19.2/cluster-setup-troubleshooting.md

@@ -227,7 +227,7 @@ Again, firewalls or hostname issues can cause any of these steps to fail.
 
 If the Admin UI lists live nodes in the **Dead Nodes** table, then you might have a network partition.
 
-**Explanation:** A network partition indicates that the nodes can't communicate with each other in one or both directions because of a configuration problem with the network itself. A symmetric partition is one where the communication is broken in both directions. An asymmetric partition means the connection works in one direction but not the other. An example of a scenario that can cause a network partition is when specific IP addresses or hostnames are whitelisted in the firewall, and then those addresses or names change after tearing down and rebuilding a node.
+**Explanation:** A network partition indicates that the nodes can't communicate with each other in one or both directions because of a configuration problem with the network itself. A symmetric partition is one where the communication is broken in both directions. An asymmetric partition means the connection works in one direction but not the other. An example of a scenario that can cause a network partition is when specific IP addresses or hostnames are allowed by the firewall, and then those addresses or names change after tearing down and rebuilding a node.
 
 The effect of a network partition depends on which nodes are partitioned and where the ranges are located. It depends to a large extent on whether localities have been defined.
 

v20.1/admin-ui-network-latency-page.md

@@ -23,7 +23,7 @@ Each cell in the matrix displays the round-trip latency in milliseconds between
 
 Rows represent origin nodes, and columns represent destination nodes. Hover over a cell to see round-trip latency and locality metadata for origin and destination nodes.
 
-On a [typical multi-region cluster](demo-low-latency-multi-region-deployment.html#step-4-access-the-admin-ui), you can expect much lower latencies between nodes in the same region/availability zone. Nodes in different regions/availability zones, meanwhile, will experience higher latencies that reflect their geographical distribution. 
+On a [typical multi-region cluster](demo-low-latency-multi-region-deployment.html#step-4-access-the-admin-ui), you can expect much lower latencies between nodes in the same region/availability zone. Nodes in different regions/availability zones, meanwhile, will experience higher latencies that reflect their geographical distribution.
 
 For instance, the cluster shown above has nodes in `us-west1`, `us-east1`, and `europe-west2`. Latencies are highest between nodes in `us-west1` and `europe-west2`, which span the greatest distance. This is especially clear when sorting by region or availability zone and collapsing nodes:
 
@@ -34,7 +34,7 @@ For instance, the cluster shown above has nodes in `us-west1`, `us-east1`, and `
 Nodes that have lost a connection are displayed in a separate color. This can help you locate a network partition in your cluster.
 
 {{site.data.alerts.callout_info}}
-A network partition prevents nodes from communicating with each other in one or both directions. This can be due to a configuration problem with the network, such as when whitelisted IP addresses or hostnames change after a node is torn down and rebuilt. In a symmetric partition, node communication is broken in both directions. In an asymmetric partition, node communication works in one direction but not the other.
+A network partition prevents nodes from communicating with each other in one or both directions. This can be due to a configuration problem with the network, such as when allowlisted IP addresses or hostnames change after a node is torn down and rebuilt. In a symmetric partition, node communication is broken in both directions. In an asymmetric partition, node communication works in one direction but not the other.
 
 The effect of a network partition depends on which nodes are partitioned, where the ranges are located, and to a large extent, whether [localities](cockroach-start.html#locality) are defined. If localities are not defined, a partition that cuts off at least (n-1)/2 nodes will cause data unavailability.
 {{site.data.alerts.end}}
@@ -46,12 +46,12 @@ Click the **NO CONNECTIONS** link to see lost connections between nodes or [loca
 {% include {{ page.version.version }}/topology-patterns/fundamentals.md %}
 
 {{site.data.alerts.callout_info}}
-Network latency limits the performance of individual operations. You can use the [Statements](admin-ui-statements-page.html) page to see the latencies of SQL statements on gateway nodes. 
+Network latency limits the performance of individual operations. You can use the [Statements](admin-ui-statements-page.html) page to see the latencies of SQL statements on gateway nodes.
 {{site.data.alerts.end}}
 
 ## See also
 
 - [Topology Patterns](topology-patterns.html)
 - [CockroachDB Performance](performance.html#latency)
 - [Performance Tuning](performance-tuning.html)
-- [Low Latency Reads and Writes in a Multi-Region Cluster](demo-low-latency-multi-region-deployment.html)
+- [Low Latency Reads and Writes in a Multi-Region Cluster](demo-low-latency-multi-region-deployment.html)

v20.1/cluster-setup-troubleshooting.md

@@ -227,7 +227,7 @@ Again, firewalls or hostname issues can cause any of these steps to fail.
 
 If the Admin UI lists any dead nodes on the [**Cluster Overview** page](admin-ui-cluster-overview-page.html), then you might have a network partition.
 
-**Explanation:** A network partition prevents nodes from communicating with each other in one or both directions. This can be due to a configuration problem with the network, such as when whitelisted IP addresses or hostnames change after a node is torn down and rebuilt. In a symmetric partition, node communication is broken in both directions. In an asymmetric partition, node communication works in one direction but not the other.
+**Explanation:** A network partition prevents nodes from communicating with each other in one or both directions. This can be due to a configuration problem with the network, such as when allowlisted IP addresses or hostnames change after a node is torn down and rebuilt. In a symmetric partition, node communication is broken in both directions. In an asymmetric partition, node communication works in one direction but not the other.
 
 The effect of a network partition depends on which nodes are partitioned, where the ranges are located, and to a large extent, whether [localities](cockroach-start.html#locality) are defined. If localities are not defined, a partition that cuts off at least (n-1)/2 nodes will cause data unavailability.
 

v20.1/cockroachcloud-frequently-asked-questions.md

@@ -11,9 +11,9 @@ This page answers the frequently asked questions.
 
 ### Is my cluster secure?
 
-Yes. We create individual sub-accounts and VPCs for each cluster within the cloud provider. These VPCs are firewalled from each other and any other outside connection, unless whitelisted for SQL and Web UI ports.
+Yes. We create individual sub-accounts and VPCs for each cluster within the cloud provider. These VPCs are firewalled from each other and any other outside connection, unless allowlisted for SQL and Web UI ports.
 
-The allowlist is comprised of IP addresses that you provide to us, and is an additional layer of protection for your cluster. Connections will only be accepted if they come from a whitelisted IP address, which protects against both compromised passwords and any potential bugs in the server.
+The allowlist is comprised of IP addresses that you provide to us, and is an additional layer of protection for your cluster. Connections will only be accepted if they come from an allowlisted IP address, which protects against both compromised passwords and any potential bugs in the server.
 
 We use separate certificate authorities for each cluster, and all connections to the cluster over the internet use TLS 1.2.
 

v20.2/admin-ui-network-latency-page.md

@@ -23,7 +23,7 @@ Each cell in the matrix displays the round-trip latency in milliseconds between
 
 Rows represent origin nodes, and columns represent destination nodes. Hover over a cell to see round-trip latency and locality metadata for origin and destination nodes.
 
-On a [typical multi-region cluster](demo-low-latency-multi-region-deployment.html#step-4-access-the-admin-ui), you can expect much lower latencies between nodes in the same region/availability zone. Nodes in different regions/availability zones, meanwhile, will experience higher latencies that reflect their geographical distribution. 
+On a [typical multi-region cluster](demo-low-latency-multi-region-deployment.html#step-4-access-the-admin-ui), you can expect much lower latencies between nodes in the same region/availability zone. Nodes in different regions/availability zones, meanwhile, will experience higher latencies that reflect their geographical distribution.
 
 For instance, the cluster shown above has nodes in `us-west1`, `us-east1`, and `europe-west2`. Latencies are highest between nodes in `us-west1` and `europe-west2`, which span the greatest distance. This is especially clear when sorting by region or availability zone and collapsing nodes:
 
@@ -34,7 +34,7 @@ For instance, the cluster shown above has nodes in `us-west1`, `us-east1`, and `
 Nodes that have lost a connection are displayed in a separate color. This can help you locate a network partition in your cluster.
 
 {{site.data.alerts.callout_info}}
-A network partition prevents nodes from communicating with each other in one or both directions. This can be due to a configuration problem with the network, such as when whitelisted IP addresses or hostnames change after a node is torn down and rebuilt. In a symmetric partition, node communication is broken in both directions. In an asymmetric partition, node communication works in one direction but not the other.
+A network partition prevents nodes from communicating with each other in one or both directions. This can be due to a configuration problem with the network, such as when allowlisted IP addresses or hostnames change after a node is torn down and rebuilt. In a symmetric partition, node communication is broken in both directions. In an asymmetric partition, node communication works in one direction but not the other.
 
 The effect of a network partition depends on which nodes are partitioned, where the ranges are located, and to a large extent, whether [localities](cockroach-start.html#locality) are defined. If localities are not defined, a partition that cuts off at least (n-1)/2 nodes will cause data unavailability.
 {{site.data.alerts.end}}
@@ -46,12 +46,12 @@ Click the **NO CONNECTIONS** link to see lost connections between nodes or [loca
 {% include {{ page.version.version }}/topology-patterns/fundamentals.md %}
 
 {{site.data.alerts.callout_info}}
-Network latency limits the performance of individual operations. You can use the [Statements](admin-ui-statements-page.html) page to see the latencies of SQL statements on gateway nodes. 
+Network latency limits the performance of individual operations. You can use the [Statements](admin-ui-statements-page.html) page to see the latencies of SQL statements on gateway nodes.
 {{site.data.alerts.end}}
 
 ## See also
 
 - [Topology Patterns](topology-patterns.html)
 - [CockroachDB Performance](performance.html#latency)
 - [Performance Tuning](performance-tuning.html)
-- [Low Latency Reads and Writes in a Multi-Region Cluster](demo-low-latency-multi-region-deployment.html)
+- [Low Latency Reads and Writes in a Multi-Region Cluster](demo-low-latency-multi-region-deployment.html)

v20.2/cluster-setup-troubleshooting.md

@@ -227,7 +227,7 @@ Again, firewalls or hostname issues can cause any of these steps to fail.
 
 If the Admin UI lists any dead nodes on the [**Cluster Overview** page](admin-ui-cluster-overview-page.html), then you might have a network partition.
 
-**Explanation:** A network partition prevents nodes from communicating with each other in one or both directions. This can be due to a configuration problem with the network, such as when whitelisted IP addresses or hostnames change after a node is torn down and rebuilt. In a symmetric partition, node communication is broken in both directions. In an asymmetric partition, node communication works in one direction but not the other.
+**Explanation:** A network partition prevents nodes from communicating with each other in one or both directions. This can be due to a configuration problem with the network, such as when allowlisted IP addresses or hostnames change after a node is torn down and rebuilt. In a symmetric partition, node communication is broken in both directions. In an asymmetric partition, node communication works in one direction but not the other.
 
 The effect of a network partition depends on which nodes are partitioned, where the ranges are located, and to a large extent, whether [localities](cockroach-start.html#locality) are defined. If localities are not defined, a partition that cuts off at least (n-1)/2 nodes will cause data unavailability.