Change white/blacklist in recorder, history, Pushbullet and Watson IOT docs (#16125)

source/_integrations/history.markdown

@@ -77,7 +77,7 @@ Without any `include` or `exclude` configuration the history displays graphs for
  `scenes` are never shown) on a given date. If you are only interested in some
  of the entities you have several options:
 
-Define domains and entities to `exclude` (aka. blacklist). This is convenient
+Define domains and entities to `exclude` (aka. blocklist). This is convenient
 when you are basically happy with the information displayed, but just want to
 remove some entities or domains. Usually these are entities/domains which do not
 change or rarely change (like `updater` or `automation`).
@@ -97,7 +97,7 @@ history:
 ```
 
 Define domains and entities to display by using the `include` configuration
-(aka. whitelist). If you have a lot of entities in your system and your
+(aka. allowlist). If you have a lot of entities in your system and your
 `exclude` list is getting too large, it might be better just to define the
 entities or domains to `include`.
 

source/_integrations/pushbullet.markdown

@@ -189,6 +189,6 @@ action:
 
 <div class='note'>
 
-Don't forget to [whitelist external directories](/docs/configuration/basic/), so Home Assistant has access to them.
+Don't forget to [allowlist external directories](/docs/configuration/basic/), so Home Assistant has access to them.
 
 </div>

source/_integrations/recorder.markdown

@@ -110,7 +110,7 @@ recorder:
 
 ## Configure Filter
 
-By default, no entity will be excluded. To limit which entities are being exposed to `Recorder`, you can use the `include` and `exclude` parameters.
+By default, no entity will be excluded. To limit which entities are being exposed to `recorder`, you can use the `include` and `exclude` parameters.
 
 ```yaml
 # Example filter to include specified domains and exclude specified entities
@@ -148,7 +148,7 @@ If you only want to hide events from your history, take a look at the [`history`
 
 ### Common filtering examples
 
-Defining domains and entities to `exclude` (i.e. blacklist) is convenient when you are basically happy with the information recorded, but just want to remove some entities or domains.
+Defining domains and entities to `exclude` (i.e. blocklist) is convenient when you are basically happy with the information recorded, but just want to remove some entities or domains.
 
 ```yaml
 # Example configuration.yaml entry with exclude
@@ -169,7 +169,7 @@ recorder:
       - call_service # Don't record service calls
 ```
 
-Defining domains and entities to record by using the `include` configuration (i.e. whitelist) is convenient if you have a lot of entities in your system and your `exclude` lists possibly get very large, so it might be better just to define the entities or domains to record.
+Defining domains and entities to record by using the `include` configuration (i.e. allowlist) is convenient if you have a lot of entities in your system and your `exclude` lists possibly get very large, so it might be better just to define the entities or domains to record.
 
 ```yaml
 # Example configuration.yaml entry with include

source/_integrations/watson_iot.markdown

@@ -66,7 +66,7 @@ exclude:
       required: false
       type: list
 include:
-  description: Configure which integrations should be included in recordings to Watson IoT Platform. If set, all other entities will not be recorded to Watson IoT Platform. Values set by the **blacklist** option will prevail.
+  description: Configure which integrations should be included in recordings to Watson IoT Platform. If set, all other entities will not be recorded to Watson IoT Platform. Values set by the **exclude** option will prevail.
   required: false
   type: map
   keys: