From f6eafb59acdbfe869a800ae354b1f4f564749772 Mon Sep 17 00:00:00 2001 From: kylehakala Date: Fri, 16 Feb 2024 02:12:59 -0600 Subject: [PATCH] Misc typos and phrasing improvements (#31456) --- source/_integrations/google_maps.markdown | 2 +- source/_integrations/group.markdown | 2 +- source/_integrations/homekit_controller.markdown | 2 +- source/_integrations/homewizard.markdown | 6 +++--- source/_integrations/hue.markdown | 4 ++-- 5 files changed, 8 insertions(+), 8 deletions(-) diff --git a/source/_integrations/google_maps.markdown b/source/_integrations/google_maps.markdown index f2e63f1bc4e..5de714d2fcd 100644 --- a/source/_integrations/google_maps.markdown +++ b/source/_integrations/google_maps.markdown @@ -55,7 +55,7 @@ device_tracker: Once enabled and you have rebooted devices discovered through this integration will be listed in the `known_devices.yaml` file within your configuration directory. -They will be created with indentifiers like `google_maps_`. To be able to properly track entities you must set the `track` attribute to `true`. +They will be created with identifiers like `google_maps_`. To be able to properly track entities you must set the `track` attribute to `true`. {% configuration %} username: diff --git a/source/_integrations/group.markdown b/source/_integrations/group.markdown index 2970a679fc1..2ae28d74fd7 100644 --- a/source/_integrations/group.markdown +++ b/source/_integrations/group.markdown @@ -253,7 +253,7 @@ name: required: false type: string unique_id: - description: An ID that uniquely identifies this group. If two groups have the same unique ID, Home Assistant will raise an error. Giving an group a unique ID allow the group name, icon and area to be customized via the UI. + description: An ID that uniquely identifies this group. If two groups have the same unique ID, Home Assistant will raise an error. Giving the group a unique ID allows the group name, icon and area to be customized via the UI. required: false type: string all: diff --git a/source/_integrations/homekit_controller.markdown b/source/_integrations/homekit_controller.markdown index a4278a88b3a..d38ac079152 100644 --- a/source/_integrations/homekit_controller.markdown +++ b/source/_integrations/homekit_controller.markdown @@ -116,7 +116,7 @@ You can add a HomeKit [compatible device](#supported-devices) to Home Assistant ## Adding a HomeKit device through Thread -This section shows the the ways you can join a HomeKit device to a {% term Thread %} network: +This section shows the ways you can join a HomeKit device to a {% term Thread %} network: 1. via Home Assistant 2. via Apple Thread border router diff --git a/source/_integrations/homewizard.markdown b/source/_integrations/homewizard.markdown index a2021f23d02..952d7f1785c 100644 --- a/source/_integrations/homewizard.markdown +++ b/source/_integrations/homewizard.markdown @@ -64,14 +64,14 @@ Sensors for P1 meter, only available when smart meter exposes these values: - **Frequency (Hz)**: Net frequency. - **Voltage sags and swells**: Number of times a voltage sag or well has been detected. - **Power failures**: Two sensors that indicate the number of power failures that have been detected by the smart meter. One for all power failures and another for 'long' power failures. -- **Peak demand**: Belgium users are started to get charged for the peak usage per month (see [capaciteitstarief](https://www.fluvius.be/thema/factuur-en-tarieven/capaciteitstarief)). Two sensors are available: One that shows the current quarterly average and another that shows the peak measured this month. Both these sensors are provided directly from the smart meter and can be used to keep the peak as low as possible. +- **Peak demand**: Belgium users are starting to get charged for the peak usage per month (see [capaciteitstarief](https://www.fluvius.be/thema/factuur-en-tarieven/capaciteitstarief)). Two sensors are available: One that shows the current quarterly average and another that shows the peak measured this month. Both these sensors are provided directly from the smart meter and can be used to keep the peak as low as possible. Sensors for kWh meter: - **Voltage (V)**: Active voltage that is measured on each phase. - **Current (A)**: Active current that is measured on each phase. - **Frequency (Hz)**: Net frequency. -- **Reactive power (VAR)**: Active reactive power measurent on each phase. -- **Apparent power (VA)**: Active reactie power measurent on each phase. +- **Reactive power (VAR)**: Active reactive power measurement on each phase. +- **Apparent power (VA)**: Active apparent power measurement on each phase. Sensors for Water meter: diff --git a/source/_integrations/hue.markdown b/source/_integrations/hue.markdown index a613469f845..f115aab7b04 100644 --- a/source/_integrations/hue.markdown +++ b/source/_integrations/hue.markdown @@ -45,7 +45,7 @@ If you'd like to use those `grouped lights`, you can enable them from Settings - ## Scenes -In the Hue concept you can create (dynamic) scenes for the lights within rooms and zones. You can create, edit and delete Hue scenes from the (official) Hue app on iOS and Android. Each Zone/Room can have it's own scenes assigned and there is a large library of precreated scenes for specific moods. These Hue scenes are automatically imported in Home Assistant and they're available as `scene entities`. Creating or editing Hue scenes in Home Assistant is not supported. +In the Hue concept you can create (dynamic) scenes for the lights within rooms and zones. You can create, edit and delete Hue scenes from the (official) Hue app on iOS and Android. Each Zone/Room can have its own scenes assigned and there is a large library of preset scenes for specific moods. These Hue scenes are automatically imported in Home Assistant and they're available as `scene entities`. Creating or editing Hue scenes in Home Assistant is not supported. It is advised to use Hue scenes for controlling multiple lights at once for a smooth experience. If you individually control multiple lights and/or use Home Assistant scenes, each light command will be sent to each light one by one which doesn't give a very good user experience, while using a Hue scene sends commands to all lights at once in an optimized way, resulting in a smooth experience. @@ -59,7 +59,7 @@ To have more control over Hue scenes we've implemented a secondary, more advance | `transition` | no | Transition duration (in seconds) it takes to bring devices to the state defined in the scene. | | `dynamic` | no | Enable (true) or Disable (false) dynamic mode for the scene. | | `speed` | no | Set the speed (of the dynamic palette) for this scene. | -| `brightness` | no | Set the brightnes for this scene. | +| `brightness` | no | Set the brightness for this scene. | You can use this service for example if you'd like to start/stop Dynamic Mode.