Spelling and grammar fixes (#6650)

source/_components/bmw_connected_drive.markdown

@@ -21,7 +21,7 @@ This component provides the following platforms:
  - Binary Sensors: Doors, windows, condition based services, check control messages, parking lights, door lock state, charging status (electric cars) and connections status (electric cars).
  - Device tracker: The location of your car.
  - Lock: Control the lock of your car.
- - Sensors: Mileage, remaining range, remaining fuel, charging time remaing (electric cars), charging status (electric cars), remaing range electric (electric cars).
+ - Sensors: Mileage, remaining range, remaining fuel, charging time remaining (electric cars), charging status (electric cars), remaining range electric (electric cars).
 
 To enable this component in your installation, add the following to your
 `configuration.yaml` file:

source/_components/camera.logi_circle.markdown

@@ -64,7 +64,7 @@ The path part of `filename` must be an entry in the `whitelist_external_dirs` in
 
 ### {% linkable_title Service `camera.logi_circle_set_config` %}
 
-Sets an configuration property for your camera.
+Sets a configuration property for your camera.
 
 | Service data attribute | Optional | Description |
 | ---------------------- | -------- | ----------- |

source/_components/camera.xiaomi.markdown

@@ -36,7 +36,7 @@ Hassbian users: Don't forget to install `ffmpeg` support on your platform, other
 </p>
 
 <p class='note warning'>
-The live stream writing by the camera is not an supported format when the hass reads through FTP for Yi 720p and Xiaofang Cameras, so this platform retrives the video which was saved 1 minute earlier.
+The live stream writing by the camera is not a supported format when the hass reads through FTP for Yi 720p and Xiaofang Cameras, so this platform retrives the video which was saved 1 minute earlier.
 </p>
 
 <p class='note warning'>

source/_components/climate.generic_thermostat.markdown

@@ -34,7 +34,7 @@ Configuration variables:
 - **max_temp** (*Optional*): Set maximum set point available (default: 35)
 - **target_temp** (*Optional*): Set initial target temperature. Failure to set this variable will result in target temperature being set to null on startup. As of version 0.59, it will retain the target temperature set before restart if available.
 - **ac_mode** (*Optional*): Set the switch specified in the *heater* option to be treated as a cooling device instead of a heating device.
-- **min_cycle_duration** (*Optional*): Set a minimum amount of time that the switch specified in the *heater* option must be in it's current state prior to being switched either off or on.
+- **min_cycle_duration** (*Optional*): Set a minimum amount of time that the switch specified in the *heater* option must be in its current state prior to being switched either off or on.
 - **cold_tolerance** (*Optional*): Set a minimum amount of difference between the temperature read by the sensor specified in the *target_sensor* option and the target temperature that must change prior to being switched on. For example, if the target temperature is 25 and the tolerance is 0.5 the heater will start when the sensor equals or goes below 24.5.
 - **hot_tolerance** (*Optional*): Set a minimum amount of difference between the temperature read by the sensor specified in the *target_sensor* option and the target temperature that must change prior to being switched off. For example, if the target temperature is 25 and the tolerance is 0.5 the heater will stop when the sensor equals or goes above 25.5.
 - **keep_alive** (*Optional*): Set a keep-alive interval. If set, the switch specified in the *heater* option will be triggered every time the interval elapses. Use with heaters and A/C units that shut off if they don't receive a signal from their remote for a while. Use also with switches that might lose state. The keep-alive call is done with the current valid climate component state (either on or off).

source/_components/homematic.markdown

@@ -309,7 +309,7 @@ When the connection to your HomeMatic CCU or Homegear is lost, Home Assistant wi
         service: homematic.reconnect
   ```
 
-- If you have a CCU you can also create a system variable on the CCU, which stores it's last reboot time. Since Home Assistant can still refresh system variables from the CCU (even after a reboot), this is a pretty reliable way to detect situations where you need to call *homematic.reconnect*. This is how this can be done:
+- If you have a CCU you can also create a system variable on the CCU, which stores its last reboot time. Since Home Assistant can still refresh system variables from the CCU (even after a reboot), this is a pretty reliable way to detect situations where you need to call *homematic.reconnect*. This is how this can be done:
 
   1. Create a string variable **V_Last_Reboot** on the CCU
 

source/_components/insteon.markdown

@@ -61,11 +61,11 @@ insteon:
   hub_version: 1
 ```
 
-Addtional configuration items are available:
+Additional configuration items are available:
 
 ```yaml
 insteon:
-  <PLM or Hub configruation>
+  <PLM or Hub configuration>
   device_override:
      - address: ADDRESS
        cat: CATEGORY

source/_components/notify.flock.markdown

@@ -17,7 +17,7 @@ The `flock` platform uses [Flock.com](https://flock.com) to deliver notification
 
 ## {% linkable_title Setup %}
 
-Go to the [Flock.com Admin website](https://admin.flock.com/#!/webhooks) and create a new "Incoming Webhooks". Choose a channel to send the notifications from Home Assistant to, specifiy a name and press *Save and Generate URL*.
+Go to the [Flock.com Admin website](https://admin.flock.com/#!/webhooks) and create a new "Incoming Webhooks". Choose a channel to send the notifications from Home Assistant to, specify a name and press *Save and Generate URL*.
 
 <p class='img'>
   <img src='{{site_root}}/images/components/flock/flock-webhook.png' />

source/_components/notify.telegram.markdown

@@ -277,11 +277,11 @@ action:
 
 {% configuration %}
 url:
-  description: A remote path to an document. Either this or the `file` configuration option is required.
+  description: A remote path to a document. Either this or the `file` configuration option is required.
   required: true
   type: string
 file:
-  description: A local path to an document. Either this or the `url` configuration option is required.
+  description: A local path to a document. Either this or the `url` configuration option is required.
   required: true
   type: string
 caption:

source/_components/openuv.markdown

@@ -114,5 +114,5 @@ These sensors display the approximate number of minutes a particular skin type c
 * Skin Type VI
 
 <p class='note warning'>
-The above guidelines constitude estimates and are intended to help informed decision making. They should not replace analysis, advice, or diagnosis from a trained medical professional.
+The above guidelines constitute estimates and are intended to help informed decision making. They should not replace analysis, advice, or diagnosis from a trained medical professional.
 </p>

source/_components/sensor.iperf3.markdown

@@ -1,7 +1,7 @@
 ---
 layout: page
 title: "Iperf3 Sensor"
-description: "How to use Iperf3 within Home Assistant to measure your network bandwith."
+description: "How to use Iperf3 within Home Assistant to measure your network bandwidth."
 date: 2018-05-01 02:00
 sidebar: true
 comments: false

source/_components/sensor.trafikverket_weatherstation.markdown

@@ -55,7 +55,7 @@ station:
   required: true  
   type: string  
 monitored_conditions: 
-  description: Specify what measurement data to retreive from the weather station. 
+  description: Specify what measurement data to retrieve from the weather station.
   required: true  
   type: map  
   keys:

source/_components/sensor.zestimate.markdown

@@ -19,7 +19,7 @@ The `zestimate` sensor allows one to track the Zestimate value of properties usi
 
 You will need to sign up for the Zillow API at the following link [Zillow API](https://www.zillow.com/howto/api/APIOverview.htm). You will also need the Zillow property ID for each property you'd like to track. This information is available from the URL of a property you are interested in. 
 
-For example, the White House zpid is 84074482 and can be found in it's Zillow URL: [https://www.zillow.com/homedetails/1600-Pennsylvania-Ave-NW-Washington-DC-20006/84074482_zpid/](https://www.zillow.com/homedetails/1600-Pennsylvania-Ave-NW-Washington-DC-20006/84074482_zpid/)
+For example, the White House zpid is 84074482 and can be found in its Zillow URL: [https://www.zillow.com/homedetails/1600-Pennsylvania-Ave-NW-Washington-DC-20006/84074482_zpid/](https://www.zillow.com/homedetails/1600-Pennsylvania-Ave-NW-Washington-DC-20006/84074482_zpid/)
 
 To enable this sensor, add the following lines to your `configuration.yaml`.
 

source/_components/wink.markdown

@@ -141,7 +141,7 @@ The Wink hub, by default, can only be accessed via the cloud. This means it requ
 
 - GoControl siren and strobe
 - Dome siren/chime/strobe
-- Quirky Nimbus (Legacy device) These can no longer be officialy added to your Wink account
+- Quirky Nimbus (Legacy device) These can no longer be officially added to your Wink account
 
 
 ### {% linkable_title Service `set_siren_auto_shutoff` %}
@@ -290,7 +290,7 @@ script:
 
 ### {% linkable_title Service `set_nimbus_dial_state` %}
 
-You can use the service wink/set_nimbus_dial_state to update an individual dial's value/position and it's labels
+You can use the service wink/set_nimbus_dial_state to update an individual dial's value/position and its labels
 
 | Service data attribute | Optional | Description |
 | ---------------------- | -------- | ----------- |

source/_docs/authentication/multi-factor-auth.markdown

@@ -66,7 +66,7 @@ Notify MFA module using [notify component](https://www.home-assistant.io/compone
 
 User need first set up the MFA module by select one of the available notify service. A 6 digit one-time password will be sent by this notify service, user need to input it to verify the setup.
 
-During the login process, an 6 digit one-time password will be sent again, user need to input it to verify his/her identity. If the validation failed, a new one-time password will be sent again.
+During the login process, a 6 digit one-time password will be sent again, user need to input it to verify his/her identity. If the validation failed, a new one-time password will be sent again.
 
 <p class='note'>
 Notify MFA module would not verify the one-time password delivery success, so that if user cannot received the message due any reason, he/she may not be login again. Edit or remove `[your_config_dir]/.storage/auth_module.notify` can disable notify MFA module to resolve the issue.

source/lovelace/index.markdown

@@ -136,7 +136,7 @@ This is probably because your version of Firefox doesn't have custom components
 
 ### {% linkable_title Custom cards don't load on my iOS device? %}
 
-Home Assistant comes with two versions of the frontend. A compatability mode for older devices and a modern mode. The custom cards need to target one mode and usually choose the modern mode. Before Home Assistant 0.76, we had an issue in the automation and script editor that prevented modern iOS and Mac devices running Safari from using the modern mode.
+Home Assistant comes with two versions of the frontend. A compatibility mode for older devices and a modern mode. The custom cards need to target one mode and usually choose the modern mode. Before Home Assistant 0.76, we had an issue in the automation and script editor that prevented modern iOS and Mac devices running Safari from using the modern mode.
 
 If you can, resolve this issue by upgrading to Home Assistant 0.76 or later. If you are on an older version and don't mind that the automation and script editor don't work on iOS devices, you can force the new version via the configuration: