✅ Various markdown, spelling, and grammar fixes (home-assistant#4503)

.github/PULL_REQUEST_TEMPLATE.md

@@ -5,7 +5,7 @@
 
 ## Checklist:
 
-  - [ ] Branch: Fixes, changes and adjustments should be created against `current`. New documentation for platforms/components and features should go to `next`. 
-  - [ ] The documentation follow the [standards][standards].
+- [ ] Branch: Fixes, changes and adjustments should be created against `current`. New documentation for platforms/components and features should go to `next`.
+- [ ] The documentation follow the [standards][standards].
 
 [standards]: https://home-assistant.io/developers/documentation/standards/

CODE_OF_CONDUCT.md

@@ -23,7 +23,7 @@ include:
 Examples of unacceptable behavior by participants include:
 
 * The use of sexualized language or imagery and unwelcome sexual attention or
-advances
+  advances
 * Trolling, insulting/derogatory comments, and personal or political attacks
 * Public or private harassment
 * Publishing others' private information, such as a physical or electronic

source/_components/abode.markdown

@@ -13,7 +13,7 @@ ha_release: 0.52
 ha_iot_class: "Cloud Push"
 ---
 
-The `abode` component will allow users to integrate their Abode Home Security systems into Home Assistant and use its alarm system and sensors to automate their homes.  
+The `abode` component will allow users to integrate their Abode Home Security systems into Home Assistant and use its alarm system and sensors to automate their homes.
 
 Please visit the [Abode website](https://goabode.com/) for further information about Abode Security.
 

source/_components/ads.markdown

@@ -53,7 +53,6 @@ The ADS component will register the service `write_by_name` allowing you to writ
 
 Service parameters:
 
-- **adsvar**: Name of the variable on the ADS device. To access global variables on *TwinCAT2* use a prepending dot `.myvariable`, for TwinCAT3 use
-`GBL.myvariable`.
+- **adsvar**: Name of the variable on the ADS device. To access global variables on *TwinCAT2* use a prepending dot `.myvariable`, for TwinCAT3 use `GBL.myvariable`.
 - **adstype**: Specify the type of the variable. Use one of the following: `int`, `byte`, `uint`, `bool`
 - **value**: The value that will be written in the variable.

source/_components/alarm_control_panel.abode.markdown

@@ -13,7 +13,6 @@ ha_release: 0.52
 ha_iot_class: "Cloud Push"
 ---
 
-
 The `abode` security control panel platform allows you to control your [Abode](https://goabode.com/) alarms.
 
 The requirement is that you have setup your [Abode hub](/components/abode/).

source/_components/alarm_control_panel.alarmdecoder.markdown

@@ -13,7 +13,6 @@ ha_release: 0.43
 ha_iot_class: "Local Push"
 ---
 
-
 The `alarmdecoder` alarm control panel platform allows you to control your [AlarmDecoder](https://www.alarmdecoder.com) alarms.
 
 The requirement is that you have setup your [AlarmDecoder hub](/components/alarmdecoder/).

source/_components/alarm_control_panel.alarmdotcom.markdown

@@ -30,4 +30,3 @@ Configuration variables:
 - **password** (*Required*): Password for Alarm.com account.
 - **name** (*Optional*): The name of the alarm. Default is 'Alarm.com'.
 - **code** (*Optional*): Specifies a code to enable or disable the alarm in the frontend.
-

source/_components/alarm_control_panel.arlo.markdown

@@ -13,7 +13,6 @@ ha_release: 0.56
 ha_iot_class: "Cloud Polling"
 ---
 
-
 The `arlo` alarm control panel allows you to control your [Arlo](https://arlo.netgear.com/) base stations. You can use it to switch modes and trigger alarms from Home Assistant.
 
 To get your [Arlo](https://arlo.netgear.com/) base stations working within Home Assistant, please follow the instructions for the general [Arlo component](/components/arlo).

source/_components/alarm_control_panel.concord232.markdown

@@ -14,7 +14,7 @@ ha_release: 0.31
 
 The `concord232` platform provides integration with GE, Interlogix (and other brands) alarm panels that support the RS-232 Automation Control Panel interface module (or have it built in). Supported panels include Concord 4.
 
-To use this platform, you will need to have the external concord232 client and server installed. The server must be running on the device which is connected to the automation module's serial port. The client must be installed on the machine running Home Assistant. These may often be the same machine, but do not have to be. For additional details in setting up and testing the client and server, see https://github.com/JasonCarter80/concord232.
+To use this platform, you will need to have the external concord232 client and server installed. The server must be running on the device which is connected to the automation module's serial port. The client must be installed on the machine running Home Assistant. These may often be the same machine, but do not have to be. For additional details in setting up and testing the client and server, see <https://github.com/JasonCarter80/concord232>
 
 To enable this platform in home assistant, add the following lines to your `configuration.yaml`:
 
@@ -28,4 +28,3 @@ Configuration variables:
 
 - **host** (*Optional*): The host where the concord232 server process is running. Defaults to localhost.
 - **port** (*Optional*): The port where the Alarm panel is listening. Defaults to 5007.
-

source/_components/alarm_control_panel.egardia.markdown

@@ -43,25 +43,25 @@ Note that this basic configuration will only enable you to read the armed/armed
 You can change this, however, using the following procedure. This is a more advanced configuration.
 
 1. Log in into your alarm system's control panel. You will need to access http://[IP of your control panel]. You know this already since you need it in the basic configuration from above. Log in to the control panel with your Egardia/Woonveilig username and password.
-2. Once logged in, go to *System Settings*, *Report* and change the Server Address for your primary server to the IP or hostname of your Home Assistant machine. You can leave the port number set to 52010 or change it to anything you like. **Make sure to change the settings of the primary server otherwise the messages will not come through. Note that this will limit (or fully stop) the number of alarm messages you will get through Egardia's / Woonveilig services.** Maybe, that is just what you want. Make sure to save your settings by selecting 'OK'.
-3. On your Home Assistant machine run `$ sudo python3 egardiaserver.py`. Refer to the [python-egardia repository](https://github.com/jeroenterheerdt/python-egardia) for detailed documentation on parameters. This will receive status codes from your alarm control panel and display them. You will need the codes to include in your configuration.yaml. Make sure to change the status of your alarm to all states (disarm, arm, home) by all means possible (all users, remotes, web login, app) as well as trigger the alarm in all ways possible to get 100% coverage. **Before triggering the alarm it might be good to disable the siren temporarily (can be done in Panel Settings).**
-4. Once you have the codes, update your `configuration.yaml`:
-```yaml
-# Example configuration.yaml entry
-alarm_control_panel:
-  - platform: egardia
-    host: YOUR_HOST
-    username: YOUR_USERNAME
-    password: YOUR_PASSWORD
-    report_server_enabled: True
-    report_server_port: PORT_OF_EGARDIASERVER (optional, defaults to 52010)
-    report_server_codes:
-      arm: XXXXXXXXXXXXXXXX, XXXXXXXXXXXXXXXX
-      disarm: XXXXXXXXXXXXXXXX, XXXXXXXXXXXXXXXX
-      home: XXXXXXXXXXXXXXXX
-      triggered: XXXXXXXXXXXXXXXX, XXXXXXXXXXXXXXXX, XXXXXXXXXXXXXXXX
-      ignore: XXXXXXXXXXXXXXXX
-```
+1. Once logged in, go to *System Settings*, *Report* and change the Server Address for your primary server to the IP or hostname of your Home Assistant machine. You can leave the port number set to 52010 or change it to anything you like. **Make sure to change the settings of the primary server otherwise the messages will not come through. Note that this will limit (or fully stop) the number of alarm messages you will get through Egardia's / Woonveilig services.** Maybe, that is just what you want. Make sure to save your settings by selecting 'OK'.
+1. On your Home Assistant machine run `$ sudo python3 egardiaserver.py`. Refer to the [python-egardia repository](https://github.com/jeroenterheerdt/python-egardia) for detailed documentation on parameters. This will receive status codes from your alarm control panel and display them. You will need the codes to include in your configuration.yaml. Make sure to change the status of your alarm to all states (disarm, arm, home) by all means possible (all users, remotes, web login, app) as well as trigger the alarm in all ways possible to get 100% coverage. **Before triggering the alarm it might be good to disable the siren temporarily (can be done in Panel Settings).**
+1. Once you have the codes, update your `configuration.yaml`:
+    ```yaml
+    # Example configuration.yaml entry
+    alarm_control_panel:
+     - platform: egardia
+       host: YOUR_HOST
+       username: YOUR_USERNAME
+       password: YOUR_PASSWORD
+        report_server_enabled: True
+        report_server_port: PORT_OF_EGARDIASERVER (optional, defaults to 52010)
+        report_server_codes:
+          arm: XXXXXXXXXXXXXXXX, XXXXXXXXXXXXXXXX
+          disarm: XXXXXXXXXXXXXXXX, XXXXXXXXXXXXXXXX
+          home: XXXXXXXXXXXXXXXX
+          triggered: XXXXXXXXXXXXXXXX, XXXXXXXXXXXXXXXX, XXXXXXXXXXXXXXXX
+          ignore: XXXXXXXXXXXXXXXX
+    ```
 
 Note that for *triggered*, *arm* and *disarm* multiple codes can be entered since each sensor triggers with a different code and each user of the system has its own arm and disarm codes. Also note that your system will do regular system checks which will be reported as well. Since Home Assistant provides no way of handling them properly, you can enter those codes as *ignore* (again, multiple codes can be used here). The egardia component will ignore these codes and continue returning the old status if it receives any of the codes that are listed as ignore. This is useful for example when you have armed your alarm at night: normally a system check will occur at least once during the night and if that code is not specified anywhere Home Assistant will set the status of the alarm to its default, which is unarmed. This is in fact wrong. Listing the code as ignore changes this behavior and Home Assistant will continue to show the status the alarm is in (disarm, arm, home, triggered) even when system checks occur.
 

source/developers/releasing.markdown

@@ -9,22 +9,22 @@ sharing: true
 footer: true
 ---
 
-This page describes the steps for publishing a new Home Assistant release. Those steps requires that you don't use forks but work with the repositories themself. The [hass-release](https://github.com/home-assistant/hass-release) script is a helper to do a release. 
+This page describes the steps for publishing a new Home Assistant release. Those steps requires that you don't use forks but work with the repositories themself. The [hass-release](https://github.com/home-assistant/hass-release) script is a helper to do a release.
 
 ### {% linkable_title Release preparation (3 days before release) %}
 
 ### {% linkable_title GitHub %}
 
 1. Merge `master` into `dev` to make the PR mergeable.
-2. Cut a release branch from `dev`. Example name `release-0-57`.
-3. Create a pull request from the release branch to `master` with the upcoming release number as the title.
-4. Update `homeassistant/const.py` with the correct version number (remove the `dev` tag) and push that commit to release branch.
+1. Cut a release branch from `dev`. Example name `release-0-57`.
+1. Create a pull request from the release branch to `master` with the upcoming release number as the title.
+1. Update `homeassistant/const.py` with the correct version number (remove the `dev` tag) and push that commit to release branch.
 
 ### {% linkable_title Website %}
 
 1. Merge `current` into `next`
-2. Cut release branch of `next`. For example `release-0-57`.
-3. Open a PR from release branch to `current` with the upcoming release number as the title.
+1. Cut release branch of `next`. For example `release-0-57`.
+1. Open a PR from release branch to `current` with the upcoming release number as the title.
 
 ## {% linkable_title Release day %}
 
@@ -33,22 +33,22 @@ From creating the release branch till it has been merged, we tag bugfixes with t
 ### {% linkable_title GitHub %}
 
 1. Cherry-pick the milestoned PRs that need to get into the release `python3 -m hassrelease milestone_cherry_pick 0.57`
-2. Run `python3 -m hassrelease release_notes 0.56` for the release notes.
-3. Once the release notes has been generated, issue `python3 -m hassrelease milestone_close 0.56`
-4. Merge pull request (DO NOT SQUASH!). Use `Merge pull request`.
-5. Go to [releases](https://github.com/home-assistant/home-assistant/releases), click `Draft a new release` and tag a new release on the `master` branch. "Tag version" and "Release title" are the version number (`O.x` for major version, `0.x.y` for minor and bug fix releases). Release description is the text from PR. Press "Publish release" to finish the process.
-6. Merge `master` into `dev`.
-7. Update `homeassistant/const.py` with the upcoming version number (including the `dev` tag) and push that commit to the `dev` branch.
+1. Run `python3 -m hassrelease release_notes 0.56` for the release notes.
+1. Once the release notes has been generated, issue `python3 -m hassrelease milestone_close 0.56`
+1. Merge pull request (DO NOT SQUASH!). Use `Merge pull request`.
+1. Go to [releases](https://github.com/home-assistant/home-assistant/releases), click `Draft a new release` and tag a new release on the `master` branch. "Tag version" and "Release title" are the version number (`O.x` for major version, `0.x.y` for minor and bug fix releases). Release description is the text from PR. Press "Publish release" to finish the process.
+1. Merge `master` into `dev`.
+1. Update `homeassistant/const.py` with the upcoming version number (including the `dev` tag) and push that commit to the `dev` branch.
 
 ### {% linkable_title Website %}
 
 1. Create a blog post in the release branch and base it on the text of the PR in the main repository. Add images, additional text, links, etc. if it adds value. Tag each platform/component in a message to documentation.
-2. Create missing documentation as stubs.
-3. Run `credits_generator`.
-4. Update `_config.yml` with a link to the new release blog post and version number (at the bottom of the file).
-5. Merge `current` into release branch (`$ git checkout release-0-40 && git merge current`) to make the PR mergeable.
-6. Merge pull request (blog post, updated frontpage, and all new documentation) to `current`. DO NOT SQUASH!
-7. Merge `current` into `next`.
+1. Create missing documentation as stubs.
+1. Run `credits_generator`.
+1. Update `_config.yml` with a link to the new release blog post and version number (at the bottom of the file).
+1. Merge `current` into release branch (`$ git checkout release-0-40 && git merge current`) to make the PR mergeable.
+1. Merge pull request (blog post, updated frontpage, and all new documentation) to `current`. DO NOT SQUASH!
+1. Merge `current` into `next`.
 
 ### {% linkable_title Docker Hub %}
 
@@ -65,10 +65,10 @@ Checkout the `master` branch and run `script/release` to publish the new release
 ## {% linkable_title Bugfix Release %}
 
 1. Checkout `master` and update it. `git checkout master && git pull --rebase`
-2. Create a new release branch from `master`. `git checkout -b release-0-56-2`
-3. Cherry-pick the PRs which were milestoned.
-4. Update `homeassistant/const.py` with the correct version number (increment `PATCH_VERSION`) and push that commit to release branch.
-5. Create a pull request from the release branch to `master` with the upcoming release number as the title.
-6. Merge pull request (DO NOT SQUASH!). Use `Merge pull request`.
-7. Go to [releases](https://github.com/home-assistant/home-assistant/releases), click `Draft a new release` and tag a new release on the `master` branch. "Tag version" and "Release title" are the version number (`O.x` for major version, `0.x.y` for minor and bug fix releases). Release description is the text from PR. Press "Publish release" to finish the process.
-8. [Publish](/developers/releasing/#python-package-index) the new release on PyPI.
+1. Create a new release branch from `master`. `git checkout -b release-0-56-2`
+1. Cherry-pick the PRs which were milestoned.
+1. Update `homeassistant/const.py` with the correct version number (increment `PATCH_VERSION`) and push that commit to release branch.
+1. Create a pull request from the release branch to `master` with the upcoming release number as the title.
+1. Merge pull request (DO NOT SQUASH!). Use `Merge pull request`.
+1. Go to [releases](https://github.com/home-assistant/home-assistant/releases), click `Draft a new release` and tag a new release on the `master` branch. "Tag version" and "Release title" are the version number (`O.x` for major version, `0.x.y` for minor and bug fix releases). Release description is the text from PR. Press "Publish release" to finish the process.
+1. [Publish](/developers/releasing/#python-package-index) the new release on PyPI.