Misc spelling, wording improvements (#31467)

This commit is contained in:
kylehakala 2024-02-17 01:29:20 -06:00 committed by GitHub
parent 5991c25ce9
commit 9c7604f97c
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
13 changed files with 14 additions and 14 deletions

View File

@ -1,6 +1,6 @@
---
title: AccuWeather
description: Instructions on how to integrate Accuweather within Home Assistant.
description: Instructions on how to integrate AccuWeather within Home Assistant.
ha_category:
- Weather
ha_release: 0.114

View File

@ -9,7 +9,7 @@ ha_qa_scale: internal
ha_domain: template
---
The `template` integrations creates alarm control panels that combine integrations or adds pre-processing logic to actions.
The `template` integrations creates alarm control panels that combine integrations or adds preprocessing logic to actions.
There are several powerful ways to use this integration, including grouping existing integrations into a simpler integrations, or adding logic that Home Assistant will execute when accessed.

View File

@ -178,7 +178,7 @@ All data is received and processed by the Home Assistant Analytics Receiver ([so
When your installation sends a payload, that payload includes a unique identifier. This identifier is used to make sure that your installation is only counted once.
Your data is securely stored in [CloudFlare's Key-Value store](https://www.cloudflare.com/products/workers-kv/). It will be stored for a maximum of 60 days since the last update. Only aggregated data is made publicly available.
Your data is securely stored in [Cloudflare's Key-Value store](https://www.cloudflare.com/products/workers-kv/). It will be stored for a maximum of 60 days since the last update. Only aggregated data is made publicly available.
This is an example of how the information is stored:
{% configuration_basic %}

View File

@ -27,7 +27,7 @@ notify:
url: YOUR_APPRISE_URLS
```
You can also pre-define your own configuration files while storing them either remotely or locally. Simply just use the `config` option.
You can also predefine your own configuration files while storing them either remotely or locally. Simply just use the `config` option.
```yaml
# Example configuration.yaml entry using externally located Apprise

View File

@ -1,6 +1,6 @@
---
title: Aurora ABB PowerOne Solar PV
description: Instructions on how to integrate an Aurora ABB Powerone solar inverter within Home Assistant.
description: Instructions on how to integrate an Aurora ABB PowerOne solar inverter within Home Assistant.
ha_category:
- Energy
- Sensor

View File

@ -202,7 +202,7 @@ unique_id:
required: false
type: string
value_template:
description: "Defines a [template](/docs/configuration/templating/#using-templates-with-the-mqtt-integration) that returns a string to be compared to `payload_on`/`payload_off` or an empty string, in which case the MQTT message will be removed. Remove this option when `payload_on` and `payload_off` are sufficient to match your payloads (i.e no pre-processing of original message is required)."
description: "Defines a [template](/docs/configuration/templating/#using-templates-with-the-mqtt-integration) that returns a string to be compared to `payload_on`/`payload_off` or an empty string, in which case the MQTT message will be removed. Remove this option when `payload_on` and `payload_off` are sufficient to match your payloads (i.e no preprocessing of original message is required)."
required: false
type: template
{% endconfiguration %}

View File

@ -70,7 +70,7 @@ availability_template:
required: false
type: template
availability_topic:
description: "The MQTT topic subscribed to to receive birth and LWT messages from the MQTT cover device. If an `availability` topic is not defined, the cover availability state will always be `available`. If an `availability` topic is defined, the cover availability state will be `unavailable` by default. Must not be used together with `availability`."
description: "The subscribed-to MQTT topic to receive birth and LWT messages from the MQTT cover device. If an `availability` topic is not defined, the cover availability state will always be `available`. If an `availability` topic is defined, the cover availability state will be `unavailable` by default. Must not be used together with `availability`."
required: false
type: string
command_topic:

View File

@ -38,7 +38,7 @@ There is currently support for the following DROP products within Home Assistant
- **RO Filter**: reverse osmosis drinking water filtration.
- **Salt Sensor**: alerts when the salt level in the softener brine tank is low.
### Pre-requisites
### Prerequisites
To use DROP with Home Assistant, you must have already configured the [MQTT](/integrations/mqtt/) platform.

View File

@ -25,7 +25,7 @@ elv:
device: SERIAL_PORT
```
This platform will add all PCA 301 switches which are in range. You can read the total used energy in KWh and the current power in Watt.
This platform will add all PCA 301 switches which are in range. You can read the total used energy in kWh and the current power in Watt.
{% configuration %}
device:

View File

@ -59,7 +59,7 @@ line_whitelist:
required: false
type: list
omit_non_boarding:
description: If the sensors should remove resulting departures that doesn't take new passangers, or is at last stop.
description: If the sensors should remove resulting departures that doesn't take new passengers, or is at last stop.
required: false
type: boolean
default: true

View File

@ -83,7 +83,7 @@ This entity reflects the duty you have scheduled, the value can be `on` = on dut
### Incident response switch
With this switch you can respond to an incident, either by manually controlling the switch via the GUI, or by using an automation action.
It gets reset to `unknown` value with every incident received. Switching it to `on` means you send a response acknowledgement, switching it back `off` sends a response rejected.
It gets reset to `unknown` value with every incident received. Switching it to `on` means you send a response acknowledgment, switching it back `off` sends a response rejected.
The following attributes are available:

View File

@ -139,11 +139,11 @@ automation:
```
### Automation: Phone notification with Wi-fi credentials when guest Wi-fi is created
### Automation: Phone notification with Wi-Fi credentials when guest Wi-Fi is created
```yaml
automation:
- alias: "Guests Wi-fi Turned On -> Send Password To Phone"
- alias: "Guests Wi-Fi Turned On -> Send Password To Phone"
trigger:
- platform: state
entity_id: switch.fritzbox_7530_wifi_myssid

View File

@ -42,7 +42,7 @@ frontend:
required: false
type: list
development_repo:
description: Allows you to point to a directory containing frontend files instead of taking them from a pre-built PyPI package. Useful for Frontend development.
description: Allows you to point to a directory containing frontend files instead of taking them from a prebuilt PyPI package. Useful for Frontend development.
required: false
type: string
{% endconfiguration %}