remove blacklist and whitelist phrases

Author: PaulAngus

source/adminguide/networking/virtual_private_cloud_config.rst

@@ -648,16 +648,16 @@ to be routed back to the gateway.
    Wait for few seconds until the new route is created.
 
 
-Blacklisting Routes
+Deny Listing Routes
 ^^^^^^^^^^^^^^^^^^^
 
 CloudStack enables you to block a list of routes so that they are not
 assigned to any of the VPC private gateways. Specify the list of routes
-that you want to blacklist in the ``blacklisted.routes`` global
+that you want to deny in the ``denylisted.routes`` global
 parameter. Note that the parameter update affects only new static route
 creations. If you block an existing static route, it remains intact and
 continue functioning. You cannot add a static route if the route is
-blacklisted for the zone.
+denied for the zone.
 
 
 Deploying VMs to the Tier

source/adminguide/virtual_machines.rst

@@ -1356,7 +1356,7 @@ VM Instance Settings
 Each user VM has a set of "details" associated with it (as visible via listVirtualMachine API call) - those "details" are shown on the "Settings" tab of the VM in the GUI (words "setting(s)" and "detail(s)" are here used interchangeably). 
 
 The Settings tab is always present/visible, but settings can be changed only when the VM is in a Stopped state. 
-Some VM details/settings can be hidden via "user.vm.blacklisted.details" global setting (you can find below the list of those hidden by default).
+Some VM details/settings can be hidden via "user.vm.denylisted.details" global setting (you can find below the list of those hidden by default).
 
 When adding a new setting or modifying the existing ones, setting names are shown/offered in a drop-down list, as well as their possible values (with the exception of boolean or numerical values).
 

source/installguide/configuration.rst

@@ -1623,7 +1623,7 @@ zone      router.template.kvm                                        Name of the
 zone      router.template.vmware                                     Name of the default router template on VMware.
 zone      enable.dynamic.scale.vm                                    Enable or diable dynamically scaling of a VM.
 zone      use.external.dns                                           Bypass internal DNS, and use the external DNS1 and DNS2
-zone      blacklisted.routes                                         Routes that are blacklisted cannot be used for creating static routes for a VPC Private Gateway.
+zone      denylisted.routes                                          Routes that are deny-listed cannot be used for creating static routes for a VPC Private Gateway.
 ========  =========================================================  ======================================================================================================================================  
 
 

source/installguide/hypervisor/kvm.rst

@@ -827,10 +827,10 @@ Preparing
 ^^^^^^^^^
 
 To make sure that the native bridge module will not interfere with
-openvswitch the bridge module should be added to the blacklist. See the
-modprobe documentation for your distribution on where to find the
-blacklist. Make sure the module is not loaded either by rebooting or
-executing rmmod bridge before executing next steps.
+openvswitch the bridge module should be added to the deny list (likely named
+'blacklist') see the modprobe documentation for your distribution on 
+where to find the deny list. Make sure the module is not loaded either 
+by rebooting or executing rmmod bridge before executing next steps.
 
 The network configurations below depend on the ifup-ovs and ifdown-ovs
 scripts which are part of the openvswitch installation. They should be

source/plugins/ovs-plugin.rst

@@ -83,8 +83,9 @@ KVM hypervisor:
 -  CentOS 6.4 is recommended.
 
 -  To make sure that the native bridge module will not interfere with 
-   openvSwitch the bridge module should be added to the blacklist. See the 
-   modprobe documentation for your distribution on where to find the blacklist. 
+   openvSwitch the bridge module should be added to the deny list. See the 
+   modprobe documentation for your distribution on where to find the deny list
+   (likely named 'blacklist'). 
    Make sure the module is not loaded either by rebooting or executing rmmod 
    bridge before executing next steps.