diff --git a/source/_integrations/wake_on_lan.markdown b/source/_integrations/wake_on_lan.markdown index 37ed3ae9458..b1b87bc3c39 100644 --- a/source/_integrations/wake_on_lan.markdown +++ b/source/_integrations/wake_on_lan.markdown @@ -29,7 +29,7 @@ To use this integration in your installation, add the following to your `configu wake_on_lan: ``` -### Component services +### Integration services Available services: `send_magic_packet`. diff --git a/source/_integrations/water_heater.markdown b/source/_integrations/water_heater.markdown index 14f5a23a6e5..3426fda2d24 100644 --- a/source/_integrations/water_heater.markdown +++ b/source/_integrations/water_heater.markdown @@ -12,7 +12,7 @@ ha_integration_type: entity The `water_heater` integration is built for the controlling and monitoring of hot water heaters. -To enable this component, pick one of the platforms, and add it to your `configuration.yaml`: +To enable this integration, pick one of the platforms, and add it to your `configuration.yaml`: ```yaml # Example configuration.yaml entry diff --git a/source/_integrations/watson_iot.markdown b/source/_integrations/watson_iot.markdown index 0a8ecdb27da..bbac6c9a4c2 100644 --- a/source/_integrations/watson_iot.markdown +++ b/source/_integrations/watson_iot.markdown @@ -14,7 +14,7 @@ with an [IBM Watson IoT Platform instance](https://www.ibm.com/us-en/marketplace ## Configuration -To use this component, you first need to register a gateway device type and then +To use this integration, you first need to register a gateway device type and then a gateway device in your IoT platform instance. For instructions on how to do this check the [official documentation](https://cloud.ibm.com/docs/services/IoT?topic=iot-platform-getting-started#IoT_connectGateway) which provides the details on doing this. After you register the gateway device @@ -25,7 +25,7 @@ for your Home Assistant instance you'll need four pieces of information: - Gateway device ID - Authentication Token -With this basic information you can configure the component: +With this basic information you can configure the integration: ```yaml # Example configuration.yaml entry: diff --git a/source/_integrations/wemo.markdown b/source/_integrations/wemo.markdown index 88d26218359..305cff51047 100644 --- a/source/_integrations/wemo.markdown +++ b/source/_integrations/wemo.markdown @@ -47,7 +47,7 @@ There is currently support for the following device types within Home Assistant: type: list {% endconfiguration %} -Supported devices will be automatically discovered if the optional `discovery` configuration item is omitted or set to true or if the `discovery` integration is enabled. If the `discovery` configuration item is set to false, then automatic discovery of WeMo devices is disabled both for the `wemo` integration and for the `discovery` component. Loading the `wemo` integration with the `discovery` configuration item omitted or set to true will scan the local network for WeMo devices, even if you are not using the `discovery` component. +Supported devices will be automatically discovered if the optional `discovery` configuration item is omitted or set to true or if the `discovery` integration is enabled. If the `discovery` configuration item is set to false, then automatic discovery of WeMo devices is disabled both for the `wemo` integration and for the `discovery` integration. Loading the `wemo` integration with the `discovery` configuration item omitted or set to true will scan the local network for WeMo devices, even if you are not using the `discovery` integration. ```yaml # Example configuration.yaml entry with automatic discovery enabled (by omitting the discovery configuration item) diff --git a/source/_integrations/xiaomi_miio.markdown b/source/_integrations/xiaomi_miio.markdown index b91e1b7aca2..17d0ca3d3cf 100644 --- a/source/_integrations/xiaomi_miio.markdown +++ b/source/_integrations/xiaomi_miio.markdown @@ -1689,7 +1689,7 @@ Water Shortage**: ### Attributes -The vacuums from the `xiaomi` platform does not expose additional attributes other the ones provided by [the `vacuum` component](/integrations/vacuum/#attributes), +The vacuums from the `xiaomi` platform does not expose additional attributes other the ones provided by [the `vacuum` integration](/integrations/vacuum/#attributes), ### Example on how to clean a specific room diff --git a/source/_integrations/xs1.markdown b/source/_integrations/xs1.markdown index c3e37879582..8f4c4f59a82 100644 --- a/source/_integrations/xs1.markdown +++ b/source/_integrations/xs1.markdown @@ -86,7 +86,7 @@ Home Assistant can combine temperature sensors and climate actuators into a sing ## Examples -In this section, you find some real-life examples of how to use this component. +In this section, you find some real-life examples of how to use this integration. ### Full configuration diff --git a/source/_integrations/zha.markdown b/source/_integrations/zha.markdown index fd002a20bc1..12d0d4036d2 100644 --- a/source/_integrations/zha.markdown +++ b/source/_integrations/zha.markdown @@ -232,7 +232,7 @@ custom_quirks_path: ### OTA firmware updates -ZHA component has the ability to automatically download and perform OTA (Over-The-Air) firmware updates of Zigbee devices if the OTA firmware provider source URL for updates is available. OTA firmware updating is set to disabled (`false`) in the configuration by default. +The ZHA integration has the ability to automatically download and perform OTA (Over-The-Air) firmware updates of Zigbee devices if the OTA firmware provider source URL for updates is available. OTA firmware updating is set to disabled (`false`) in the configuration by default. Online OTA providers for firmware updates are currently only available for IKEA, LEDVANCE/OSRAM, SALUS/Computime, and INOVELLI devices. Support for OTA updates from other manufacturers could be supported in the future if they publish their firmware images publicly. @@ -554,7 +554,7 @@ When reporting issues, please provide the following information in addition to i ### Debug logging -To enable debug logging for ZHA component and radio libraries, add the following [logger](/integrations/logger/) configuration to `configuration.yaml`: +To enable debug logging for the ZHA integration and radio libraries, add the following [logger](/integrations/logger/) configuration to `configuration.yaml`: ```yaml logger: diff --git a/source/_integrations/zoneminder.markdown b/source/_integrations/zoneminder.markdown index a8f0044b74f..a9d2309723b 100644 --- a/source/_integrations/zoneminder.markdown +++ b/source/_integrations/zoneminder.markdown @@ -109,7 +109,7 @@ action: The `zoneminder` binary sensor platform lets you monitor the availability of your [ZoneMinder](https://www.zoneminder.com) install. -Each binary_sensor created will be named after the hostname used when configuring the [ZoneMinder component](/integrations/zoneminder/). +Each binary_sensor created will be named after the hostname used when configuring the [ZoneMinder integration](/integrations/zoneminder/). ## Camera @@ -167,7 +167,7 @@ The `zoneminder` switch platform allows you to toggle the current function of al
-You must have the [ZoneMinder component](/integrations/zoneminder/) configured to use this and if ZoneMinder authentication is enabled the account specified in the integration configuration must have "Edit" permission for "System". +You must have the [ZoneMinder integration](/integrations/zoneminder/) configured to use this and if ZoneMinder authentication is enabled the account specified in the integration configuration must have "Edit" permission for "System".