diff --git a/source/_docs/configuration/templating.markdown b/source/_docs/configuration/templating.markdown index dde02bf7380..5b5be20efbf 100644 --- a/source/_docs/configuration/templating.markdown +++ b/source/_docs/configuration/templating.markdown @@ -292,7 +292,7 @@ Closest to some entity: {{ closest(states.zone.school, ['group.children', states.device_tracker]) }} ``` -It will also work as a filter over a iterable group of entities or groups: +It will also work as a filter over an iterable group of entities or groups: ```text Closest out of given entities: diff --git a/source/_docs/configuration/troubleshooting.markdown b/source/_docs/configuration/troubleshooting.markdown index a41b99ae906..9817a4ac116 100644 --- a/source/_docs/configuration/troubleshooting.markdown +++ b/source/_docs/configuration/troubleshooting.markdown @@ -4,15 +4,15 @@ description: "Common problems with tweaking your configuration and their solutio redirect_from: /getting-started/troubleshooting-configuration/ --- -It can happen that you run into trouble while configuring Home Assistant. Perhaps a integration is not showing up or is acting strangely. This page will discuss a few of the most common problems. +It can happen that you run into trouble while configuring Home Assistant. Perhaps an integration is not showing up or is acting strangely. This page will discuss a few of the most common problems. Before we dive into common issues, make sure you know where your configuration directory is. Home Assistant will print out the configuration directory it is using when starting up. -Whenever a integration or configuration option results in a warning, it will be stored in `home-assistant.log` in the configuration directory. This file is reset on start of Home Assistant. +Whenever an integration or configuration option results in a warning, it will be stored in `home-assistant.log` in the configuration directory. This file is reset on start of Home Assistant. ### My integration does not show up -When a integration does not show up, many different things can be the case. Before you try any of these steps, make sure to look at the `home-assistant.log` file and see if there are any errors related to your integration you are trying to set up. +When an integration does not show up, many different things can be the case. Before you try any of these steps, make sure to look at the `home-assistant.log` file and see if there are any errors related to your integration you are trying to set up. If you have incorrect entries in your configuration files you can use the [`check_config`](/docs/tools/check_config/) script to assist in identifying them: `hass --script check_config`. If you need to provide the path for your configuration you can do this using the `-c` argument like this: `hass --script check_config -c /path/to/your/config/dir`. diff --git a/source/_docs/ecosystem/backup/backup_github.markdown b/source/_docs/ecosystem/backup/backup_github.markdown index 5f3111cb540..3c2c6d7b568 100644 --- a/source/_docs/ecosystem/backup/backup_github.markdown +++ b/source/_docs/ecosystem/backup/backup_github.markdown @@ -58,7 +58,7 @@ Here is an example that will ignore everything but your YAML configuration. ```bash # Example .gitignore file for your config dir. -# A * ensures that everything will be ignored. +# An * ensures that everything will be ignored. * # You can whitelist files/folders with !, these will not be ignored. diff --git a/source/_docs/installation.markdown b/source/_docs/installation.markdown index 0e350ef9094..3807cf4c038 100644 --- a/source/_docs/installation.markdown +++ b/source/_docs/installation.markdown @@ -43,7 +43,7 @@ NUC i7/i9 | Pure power, you should not have *any* performance issues ## Recommended -These install options are fully supported by Home Assistant's documentation. For example, if a integration requires that you install something to make it work on one of these methods then the integration page will document the steps required. +These install options are fully supported by Home Assistant's documentation. For example, if an integration requires that you install something to make it work on one of these methods then the integration page will document the steps required.
diff --git a/source/_docs/installation/freenas.markdown b/source/_docs/installation/freenas.markdown index 0b6c0c362ac..b95d8ed5e66 100644 --- a/source/_docs/installation/freenas.markdown +++ b/source/_docs/installation/freenas.markdown @@ -224,7 +224,7 @@ sudo iocage console hass ```bash ls /dev/cu* ``` -This should ouput the following +This should output the following ```bash /dev/cuau0 /dev/cuaU0 ``` diff --git a/source/_faq/component.markdown b/source/_faq/component.markdown index 49db9c4525a..4acaa816335 100644 --- a/source/_faq/component.markdown +++ b/source/_faq/component.markdown @@ -4,6 +4,6 @@ description: "My integration does not show up" ha_category: Configuration --- -When a integration does not show up, many different things can be the case. Before you try any of these steps, make sure to look at the `home-assistant.log` file and see if there are any errors related to your integration you are trying to set up. +When an integration does not show up, many different things can be the case. Before you try any of these steps, make sure to look at the `home-assistant.log` file and see if there are any errors related to your integration you are trying to set up. If you have incorrect entries in your configuration files you can use the `check_config` script to assist in identifying them: `hass --script check_config`. diff --git a/source/_integrations/climate.mqtt.markdown b/source/_integrations/climate.mqtt.markdown index 7916ae80c62..60c84f1e378 100644 --- a/source/_integrations/climate.mqtt.markdown +++ b/source/_integrations/climate.mqtt.markdown @@ -123,7 +123,7 @@ action_topic: type: string action_template: description: A template to render the value received on the `action_topic` with. - requred: false + required: false type: template temperature_command_topic: description: The MQTT topic to publish commands to change the target temperature. diff --git a/source/_integrations/google_assistant.markdown b/source/_integrations/google_assistant.markdown index fb1bd6c63ab..3921ca205ec 100644 --- a/source/_integrations/google_assistant.markdown +++ b/source/_integrations/google_assistant.markdown @@ -22,7 +22,7 @@ The Google Assistant integration (without Home Assistant Cloud) requires a bit m
-To use Google Assistant, your Home Assistant configuration has to be [externally accessible with a hostname and SSL certificate](/docs/configuration/remote/). If you haven't already configured that, you should do so before continuing. If you make DNS changes to accomplish this, please ensure you have allowed up to the full 48 hours for DNS changes to propogate, otherwise Google may not be able to reach your server. +To use Google Assistant, your Home Assistant configuration has to be [externally accessible with a hostname and SSL certificate](/docs/configuration/remote/). If you haven't already configured that, you should do so before continuing. If you make DNS changes to accomplish this, please ensure you have allowed up to the full 48 hours for DNS changes to propagate, otherwise Google may not be able to reach your server.
diff --git a/source/_integrations/light.mqtt.markdown b/source/_integrations/light.mqtt.markdown index 99405735d26..cdcd0c6db22 100644 --- a/source/_integrations/light.mqtt.markdown +++ b/source/_integrations/light.mqtt.markdown @@ -650,7 +650,7 @@ light: - [AiLight](https://github.com/stelgenhof/AiLight) is a custom firmware for the Ai-Thinker (and equivalent) RGBW WiFi light bulbs that has an ESP8266 onboard and controlled by the MY9291 LED driver. It implements the [MQTT JSON light](/integrations/light.mqtt) platform and supports ON/OFF, RGBW colours, brightness, colour temperature, flashing and transitions. Also it includes [MQTT Auto Discovery](/docs/mqtt/discovery/)) and the MQTT Last Will and Testament is enabled as well. -- [h801-mqtt-json](https://github.com/starkillerOG/h801-mqtt-json) is a custom firmware for the H801 LED dimmer, a 5 channel (RGBWWCW) WiFi LED strip controller for 12V LED strips. The firmware is meant to control the 5 channels of the H801 to simultaneously control an RGB and a Warm-white/Cold-white Led strip such as an 5050 RGB LED strip and a 5025 Dual White strip. It implements the [MQTT JSON light](/integrations/light.mqtt) platform and supports ON/OFF, RGBW colours (RGB strip), brightness, color temperature (CW/WW strip) and transitions. +- [h801-mqtt-json](https://github.com/starkillerOG/h801-mqtt-json) is a custom firmware for the H801 LED dimmer, a 5 channel (RGBWWCW) WiFi LED strip controller for 12V LED strips. The firmware is meant to control the 5 channels of the H801 to simultaneously control an RGB and a Warm-white/Cold-white Led strip such as a 5050 RGB LED strip and a 5025 Dual White strip. It implements the [MQTT JSON light](/integrations/light.mqtt) platform and supports ON/OFF, RGBW colours (RGB strip), brightness, color temperature (CW/WW strip) and transitions. ## Template schema diff --git a/source/_integrations/solaredge_local.markdown b/source/_integrations/solaredge_local.markdown index d536dc76e91..b41a08ad4d8 100644 --- a/source/_integrations/solaredge_local.markdown +++ b/source/_integrations/solaredge_local.markdown @@ -30,7 +30,7 @@ To use the SolarEdge sensors in your installation, add the following to your con # Example configuration.yaml entry sensor: - platform: solaredge_local - ip_address: IP_ADDRES + ip_address: IP_ADDRESS ``` {% configuration %}