fixed double 'the' (#3447)

* fixed double 'the'

mostly 's/the the /the /', little style changes where 'is' or 'to' was missing

* removed duplicate words

removed duplicate words like 'to to', 'you you' or 'account account' etc.

a batch of pizza-toasts burnt for this.

source/_components/alarm_control_panel.egardia.markdown

@@ -14,7 +14,7 @@ ha_category: Alarm
 
 The `egardia` platform enables the ability to control an [Egardia](http://egardia.com/)/Woonveilig control panel. These alarm panels are known under different brand names across the world, including Woonveilig in the Netherlands. This was tested on a Gate01 version of the Egardia/Woonveilig platform.
 
-You will need to know the IP of your alarm panel on your local network. Test if you can login to the panel by browsing to the IP address and log in in using your Egardia/Woonveilig account.
+You will need to know the IP of your alarm panel on your local network. Test if you can login to the panel by browsing to the IP address and log in using your Egardia/Woonveilig account.
 
 To enable this, add the following lines to your `configuration.yaml`:
 

source/_components/alexa.markdown

@@ -39,7 +39,7 @@ Additionally, note that at the time of this writing, your Alexa skill endpoint *
 
   1. In your router, forward external 443 to your Home Assistant serving port (defaults to 8123)
   OR
-  2. Change your Home Assistant serving port to 443 this is done in the [`http`](/components/http/) section with the the `server_port` entry in your `configuration.yaml` file
+  2. Change your Home Assistant serving port to 443 this is done in the [`http`](/components/http/) section with the `server_port` entry in your `configuration.yaml` file
 
 [blog-lets-encrypt]: https://home-assistant.io/blog/2015/12/13/setup-encryption-using-lets-encrypt/
 

source/_components/asterisk_mbox.markdown

@@ -18,7 +18,7 @@ To enable the component, a configuration is required in both Home Assistant as w
 
 First follow the [Asterisk PBX configuration guide](/docs/asterisk_mbox) to setup the necessary server on the Asterisk PBX server (this is needed even if Asterisk and Home Assistant are running on the same server)
 
-Once that is complete, add the the following entry `configuration.yaml` file:
+Once that is complete, add the following entry `configuration.yaml` file:
 
 ```yaml
 # Example configuration.yaml entry

source/_components/binary_sensor.arest.markdown

@@ -30,7 +30,7 @@ Configuration variables:
 
 - **resource** (*Required*): IP address and schema of the device that is exposing an aREST API, e.g. http://192.168.1.10.
 - **pin** (*Required*): Number of the pin to monitor.
-- **name** (*Optional*): Let you overwrite the the name of the device. By default *name* from the device is used.
+- **name** (*Optional*): Let you overwrite the name of the device. By default *name* from the device is used.
 
 Accessing the URL http://IP_ADDRESS/digital/PIN_NUMBER should give you the state of the pin inside a JSON response as `return_value`.
 

source/_components/binary_sensor.command_line.markdown

@@ -28,7 +28,7 @@ binary_sensor:
 Configuration variables:
 
 - **command** (*Required*): The action to take to get the value.
-- **name** (*Optional*): Let you overwrite the the name of the device. By default *name* from the device is used.
+- **name** (*Optional*): Let you overwrite the name of the device. By default *name* from the device is used.
 - **device_class** (*Optional*): The [type/class](/components/binary_sensor/) of the sensor to set the icon in the frontend.
 - **payload_on** (*Optional*): The payload that represents enabled state. Default is "ON".
 - **payload_off** (*Optional*): The payload that represents disabled state. Default is "OFF".

source/_components/climate.eq3btsmart.markdown

@@ -19,7 +19,7 @@ As the device doesn't contain a temperature sensor ([read more](https://forum.fh
 we report target temperature also as current one.
 
 ### Testing the connectivity ###
-Before configuring Home Assistant you should check that connectivity with the thermostat is working, which can can be done with the eq3cli tool:
+Before configuring Home Assistant you should check that connectivity with the thermostat is working, which can be done with the eq3cli tool:
 
 ```bash
 eq3cli --mac 00:11:22:33:44:55

source/_components/device_tracker.snmp.markdown

@@ -61,7 +61,7 @@ device_tracker:
 Configuration variables:
 
 - **host** (*Required*): The IP address of the router, eg. 192.168.1.1.
-- **community** (*Required*): The SNMP community which is set for the device. Most devices have a default community set to to `public` with read-only permission (which is sufficient).
+- **community** (*Required*): The SNMP community which is set for the device. Most devices have a default community set to `public` with read-only permission (which is sufficient).
 - **baseoid** (*Required*): The OID prefix where wireless client registrations can be found, usually vendor specific. It's advised to use the numerical notation. To find this base OID, check vendor documentation or check the MIB file for your device.
 - **authkey** (*Inclusive*): Authentication key for SNMPv3. Variable privkey must also be set.
 - **privkey** (*Inclusive*): Privacy key SNMPv3. Variable authkey must also be set.

source/_components/downloader.markdown

@@ -28,7 +28,7 @@ Configuration variables:
 
 ### {% linkable_title Use the service %}
 
-Go the the "Developer Tools", then to "Call Service", and choose `downloader/download_file` from the list of available services. Fill the "Service Data" field as shown in the example below and hit "CALL SERVICE".
+Go to the "Developer Tools", then to "Call Service", and choose `downloader/download_file` from the list of available services. Fill the "Service Data" field as shown in the example below and hit "CALL SERVICE".
 
 ```json
 {"url":"http://domain.tld/path/to/file"}

source/_components/joaoapps_join.markdown

@@ -13,7 +13,7 @@ ha_release: "0.24"
 ---
 
 
-The Join platform exposes services from [Join](http://joaoapps.com/join). In Home Assistant, the Join features are divided up in two locations, the Join component, and the Join notify platform. The notify platform allows us to send messages to Join devices, the the component allows us to access the other special features that Join offers.
+The Join platform exposes services from [Join](http://joaoapps.com/join). In Home Assistant, the Join features are divided up in two locations, the Join component, and the Join notify platform. The notify platform allows us to send messages to Join devices, the component allows us to access the other special features that Join offers.
 
 In the `configuration.yaml` file you need to provide the api key and device id or name of the target device.  You can find your device id and api key [here](https://joinjoaomgcd.appspot.com/).
 

source/_components/lock.markdown

@@ -16,7 +16,7 @@ Keeps track which locks are in your environment, their state and allows you to c
 
 ### {% linkable_title Use the services %}
 
-Go the the **Developer Tools**, then to **Call Service** in the frontend, and choose `lock/lock` or `lock/unlock` from the list of available services (**Available services:** on the left). Enter something like the sample below into the **Service Data** field and hit **CALL SERVICE**.
+Go to the **Developer Tools**, then to **Call Service** in the frontend, and choose `lock/lock` or `lock/unlock` from the list of available services (**Available services:** on the left). Enter something like the sample below into the **Service Data** field and hit **CALL SERVICE**.
 
 ```json
 {"entity_id":"lock.front_door"}

source/_components/media_player.anthemav.markdown

@@ -13,7 +13,7 @@ ha_iot_class: "Local Push"
 ha_release: 0.37
 ---
 
-Both [Anthem]'s current and last generation of A/V Receivers and and Processors support IP-based, network control. This Home Assistant platform adds proper "local push" support for any of these receivers on your network.
+Both [Anthem]'s current and last generation of A/V Receivers and Processors support IP-based, network control. This Home Assistant platform adds proper "local push" support for any of these receivers on your network.
 
 ## {% linkable_title Supported Models %}
 

source/_components/media_player.directv.markdown

@@ -13,7 +13,7 @@ ha_release: 0.25
 ha_iot_class: "Local Polling"
 ---
 
-Master [DirecTV](http://www.directv.com/) receivers (ie: those that have tuners) will be automatically discovered if you enable the [discovery component](/components/discovery/) and the the receiver is powered-on. Slave/RVU client/Genie boxes will also be discovered, but only if they are also online at the time of discovery.
+Master [DirecTV](http://www.directv.com/) receivers (ie: those that have tuners) will be automatically discovered if you enable the [discovery component](/components/discovery/) and the receiver is powered-on. Slave/RVU client/Genie boxes will also be discovered, but only if they are also online at the time of discovery.
 
 To ensure that your DirecTV boxes are always found and configured, they should be added into your `configuration.yaml`.
 

source/_components/plant.markdown

@@ -54,7 +54,7 @@ This is a practical example that uses a multiple of `MQTT sensors` to supply the
 Another good source of this data would be the [Mi Flora](https://home-assistant.io/components/sensor.miflora/) component. 
 
 
-If the sensor data within the the min/max values the status will be `ok`, if not the status will be `problem`. You can use this to trigger a notification, if there is a problem with your plant. Of course you can only monitor attributes of your plant, where the sensor is configured and is providing the data.
+If the sensor data is within the min/max values the status will be `ok`, if not the status will be `problem`. You can use this to trigger a notification, if there is a problem with your plant. Of course you can only monitor attributes of your plant, where the sensor is configured and is providing the data.
 
 ## Data Source
 

source/_components/remote.markdown

@@ -17,7 +17,7 @@ Keeps track which remotes are in your environment, their state and allows you to
 
 ### {% linkable_title Use the services %}
 
-Go the the **Developer Tools**, then to **Call Service** in the frontend, and choose `remote/turn_on`, `remote/turn_off`, or `remote/toggle` from the list of available services (**Available services:** on the left). Enter something like the sample below into the **Service Data** field and hit **Call Service**.
+Go to the **Developer Tools**, then to **Call Service** in the frontend, and choose `remote/turn_on`, `remote/turn_off`, or `remote/toggle` from the list of available services (**Available services:** on the left). Enter something like the sample below into the **Service Data** field and hit **Call Service**.
 
 ```json
 {"entity_id":"remote.family_room"}

source/_components/sensor.arest.markdown

@@ -34,7 +34,7 @@ sensor:
 Configuration variables:
 
 - **resource** (*Required*): IP address and schema of the device that is exposing an aREST API, e.g. http://192.168.1.10.
-- **name** (*Optional*): Let you overwrite the the name of the device. By default *name* from the device is used.
+- **name** (*Optional*): Let you overwrite the name of the device. By default *name* from the device is used.
 - **monitored_variables** array (*Optional*): List of exposed variables.
   - **[variable]** (*Required*): Name of the variable to monitor.
     - **name** (*Optional*): The name to use for the frontend.

source/_components/sensor.citybikes.markdown

@@ -28,8 +28,8 @@ Configuration options:
 
 - **name** (*Optional*): The base name of this group of monitored stations. The entity ID of every monitored station in this group will be prefixed with this base name, in addition to the network ID.
 - **network** (*Optional*):  The name of the bike sharing system to poll. Defaults to the system that operates in the monitored location.
-- **latitude** (*Optional*):  Latitude of the location, around which bike stations are monitored. Defaults to the latitude in your your `configuration.yaml` file.
-- **longitude** (*Optional*):  Longitude of the location, around which bike stations are monitored. Defaults to the longitude in your your `configuration.yaml` file.
+- **latitude** (*Optional*):  Latitude of the location, around which bike stations are monitored. Defaults to the latitude in your `configuration.yaml` file.
+- **longitude** (*Optional*):  Longitude of the location, around which bike stations are monitored. Defaults to the longitude in your `configuration.yaml` file.
 - **radius** (*Optional*):  The radius (in meters or feet, depending on the Home Assistant configuration) around the monitored location. Only stations closer than this distance will be monitored.
 - **stations** array (*Optional*): A list of specific stations to monitor. The list should contain station `ID`s or `UID`s, which can be obtained from the CityBikes API.
 

source/_components/sensor.dweet.markdown

@@ -29,7 +29,7 @@ Configuration variables:
 
 - **device** (*Required*): Identification of the device (also known as `thing`).
 - **value_template** (*Required*): The variable to extract a value from the content.
-- **name** (*Optional*): Let you overwrite the the name of the device in the frontend.
+- **name** (*Optional*): Let you overwrite the name of the device in the frontend.
 - **unit_of_measurement** (*Optional*): Defines the unit of measurement of the sensor, if any.
 
 ### {% linkable_title Full configuration sample %}

source/_components/sensor.loop_energy.markdown

@@ -14,11 +14,11 @@ ha_iot_class: "Cloud Push"
 ---
 
 
-Integrate your [Loop Energy](https://www.your-loop.com/) meter information into Home Assistant. To use this sensor you need the the client serial number and secret keys for your devices.
+Integrate your [Loop Energy](https://www.your-loop.com/) meter information into Home Assistant. To use this sensor you need the client serial number and secret keys for your devices.
 
 The library used to get the data isn't officially supported and the only way to get the keys is to log into loop energy's website and type a command into your browser console.
 
-To do this log into [Loop Energy](https://www.your-loop.com/). Once you're logged in you should be able see see your live readings on the web page.
+To do this log into [Loop Energy](https://www.your-loop.com/). Once you're logged in you should be able see your live readings on the web page.
 
 You can then open your browser's console window, how you do this varies by browser but in Chrome you click on `More Tools / Developer Tools' and click on the console window. You then type:
 

source/_components/sensor.snmp.markdown

@@ -31,7 +31,7 @@ Configuration variables:
 - **host** (*Required*): The IP address of your host, eg. `192.168.1.32`.
 - **baseoid** (*Required*): The OID where the information is located. It's advised to use the numerical notation.
 - **port** (*Option*): The SNMP port of your host. Defaults to `161`.
-- **community** (*Optional*): The SNMP community which is set for the device. Most devices have a default community set to to `public` with read-only permission (which is sufficient).
+- **community** (*Optional*): The SNMP community which is set for the device. Most devices have a default community set to `public` with read-only permission (which is sufficient).
 - **version** (*Optional*) version of SNMP protocol, `1` or `2c`. Defaults to `1`. Version `2c` is needed to read data from 64-bit counters.
 - **name** (*Optional*): Name of the SNMP sensor.
 - **unit_of_measurement** (*Optional*): Defines the unit of measurement of the sensor, if any.

source/_components/sensor.uber.markdown

@@ -30,7 +30,7 @@ sensor:
 Configuration variables:
 
 - **server_token** (*Required*): A server token obtained from [developer.uber.com](https://developer.uber.com) after [creating an app](https://developer.uber.com/dashboard/create).
-- **start_latitude** (*Optional*): The starting latitude for a trip. Defaults to the latitude in your your `configuration.yaml` file.
+- **start_latitude** (*Optional*): The starting latitude for a trip. Defaults to the latitude in your `configuration.yaml` file.
 - **start_longitude** (*Optional*): The starting longitude for a trip. Defaults to the longitude in your `configuration.yaml` file. 
 - **end_latitude** (*Optional*): The ending latitude for a trip. While `end_latitude` is optional, it is strongly recommended to provide an `end_latitude`/`end_longitude` when possible as you will get more accurate price and time estimates.
 - **end_longitude** (*Optional*): The ending longitude for a trip. While `end_longitude` is optional, it is strongly recommended to provide an `end_latitude`/`end_longitude` when possible as you will get more accurate price and time estimates.

source/_components/switch.arest.markdown

@@ -43,7 +43,7 @@ switch:
 Configuration variables:
 
 - **resource** (*Required*): IP address and schema of the device that is exposing an aREST API, eg. http://192.168.1.10 (no-trailing slash)
-- **name** (*Optional*): Let you overwrite the the name of the device. By default *name* from the device is used.
+- **name** (*Optional*): Let you overwrite the name of the device. By default *name* from the device is used.
 - **pins** array (*Optional*): An array with all used pins.
   - **name** (*Required*): The name of the pin to use in the frontend.
 

source/_components/switch.flux.markdown

@@ -14,9 +14,9 @@ logo: home-assistant.png
 
 The `flux` switch platform will change the temperature of your lights similar to the way flux works on your computer, using circadian rhythm. They will be bright during the day, and gradually fade to a red/orange at night.
 
-The component will update your lights based on the the time of day. It will only affect lights that are turned on and listed in the flux configuration.
+The component will update your lights based on the time of day. It will only affect lights that are turned on and listed in the flux configuration.
 
-During the day (in between `start time` and `sunset time`), it will fade the lights from the `start_colortemp` to the `sunset_colortemp`.  After sunset (between `sunset_time` and `stop_time`), the lights will fade from the the `sunset_colortemp` to the `stop_colortemp`. If the lights are still on after the `stop_time` it will continue to change the light to the `stop_colortemp` until the light is turned off. The fade effect is created by updating the lights every 30 seconds with a 30 second transition time.
+During the day (in between `start time` and `sunset time`), it will fade the lights from the `start_colortemp` to the `sunset_colortemp`.  After sunset (between `sunset_time` and `stop_time`), the lights will fade from the `sunset_colortemp` to the `stop_colortemp`. If the lights are still on after the `stop_time` it will continue to change the light to the `stop_colortemp` until the light is turned off. The fade effect is created by updating the lights every 30 seconds with a 30 second transition time.
 
 If you don't wish to have flux update on 30 second intervals, you can leave the switch turned off and use automation rules that call the service `switch.<name>_update` whenever you want the lights updated, where `<name>` equals the `name:` property in the switch configuration.
 

source/_components/switch.markdown

@@ -16,7 +16,7 @@ Keeps track which switches are in your environment, their state and allows you t
 
 ### {% linkable_title Use the services %}
 
-Go the the **Developer Tools**, then to **Call Service** in the frontend, and choose `switch/turn_on` or `switch/turn_off` from the list of available services (**Available services:** on the left). Enter something like the sample below into the **Service Data** field and hit **CALL SERVICE**.
+Go the **Developer Tools**, then to **Call Service** in the frontend, and choose `switch/turn_on` or `switch/turn_off` from the list of available services (**Available services:** on the left). Enter something like the sample below into the **Service Data** field and hit **CALL SERVICE**.
 
 ```json
 {"entity_id":"livingroom_pin2"}

source/_components/telegram_bot.webhooks.markdown

@@ -44,7 +44,7 @@ Configuration variables:
 - **proxy_params** (*Optional*): Proxy configuration parameters, as dict, if working behind a proxy (`username`, `password`, etc.)
 - **url** (*Optional*): Allow to overwrite the `base_url` from the [`http`](/components/http/) component for different configurations (`https://<public_url>:<port>`).
 
-To get your `chat_id` and `api_key` follow the instructions [here](/components/notify.telegram). As well as authorizing the chat, if you have added your bot to a group you will also need to authorize any user that will be interacting with the webhook. When an unauthorized user tries to interact with the webhook Home Assistant will raise an error ("Incoming message is not allowed"), you can easily obtain the the users id by looking in the "from" section of this error message.
+To get your `chat_id` and `api_key` follow the instructions [here](/components/notify.telegram). As well as authorizing the chat, if you have added your bot to a group you will also need to authorize any user that will be interacting with the webhook. When an unauthorized user tries to interact with the webhook Home Assistant will raise an error ("Incoming message is not allowed"), you can easily obtain the users id by looking in the "from" section of this error message.
 
 Full configuration sample:
 

source/_docs/installation/hassbian/common-tasks.markdown

@@ -25,7 +25,7 @@ Windows users start [Putty][ssh-putty], enter the IP address of the Raspberry Pi
 Optionally, starting with Windows 10 anniversary update, you can use the built-in '[Bash on Windows][bash-windows]' to use SSH if you have enabled Developer mode and have installed the "Windows Subsystem for Linux (beta)" feature.
 
 ### {% linkable_title Start/Stop/Restart Home Assistant %}
-Log in as the `pi` account account and execute the following commands:
+Log in as the `pi` account and execute the following commands:
 
 ```bash
 $ sudo systemctl stop home-assistant@homeassistant.service 

source/_docs/installation/synology.markdown

@@ -192,7 +192,7 @@ Make the daemon file executable:
 # chmod 777 /volume1/homeassistant/hass-daemon
 ```
 
-Update your firewall (if it is turned on on the Synology device):
+Update your firewall (if it is turned on the Synology device):
 
  - Go to your Synology control panel
  - Go to security 

source/_docs/tools/scripts.markdown

@@ -9,7 +9,7 @@ sharing: true
 footer: true
 ---
 
-The command-line and the frontend which simplify common tasks, are helping with migrations, and ensure that Home Assistant runs properly. Please do not confuse those with with Home Assistant's [script](/docs/scripts/) feature.
+The command-line and the frontend which simplify common tasks, are helping with migrations, and ensure that Home Assistant runs properly. Please do not confuse those with Home Assistant's [script](/docs/scripts/) feature.
 
 ### {% linkable_title Configuration check %}
 

source/_posts/2016-02-11-classifying-the-internet-of-things.markdown

@@ -88,7 +88,7 @@ Advantages:
 
 Disadvantages:
 
- - Home automation will assume the wrong state if the the command is not received correctly or if the device is controlled in any other way outside of the home automation system.
+ - Home automation will assume the wrong state if the command is not received correctly or if the device is controlled in any other way outside of the home automation system.
 
 ### {% linkable_title Polling the cloud %}
 These are devices that will only report their state to their own cloud backend. The cloud backend will allow reading the state but will not notify when a new state has arrived. This requires the home automation to check frequently if the state has been updated.

source/_posts/2017-02-25-config-panel-and-state-restoration.markdown

@@ -59,7 +59,7 @@ Thanks to [Fabian][@fabaff] we have a great re-organized documentation. Is it pe
 
 ## State restoration
 
-Ever have some input components or integrations and get annoyed with the fact that their state is lost after a restart? Don't worry any longer. [Johann][@kellerza] has added the foundation for state restoration to Home Assistant. For the initial release support has been added to to `input_select` and `input_boolean` components. We will be adding this to more integrations in the future.
+Ever have some input components or integrations and get annoyed with the fact that their state is lost after a restart? Don't worry any longer. [Johann][@kellerza] has added the foundation for state restoration to Home Assistant. For the initial release support has been added to `input_select` and `input_boolean` components. We will be adding this to more integrations in the future.
 
 ## Breaking changes to customize and Z-Wave "customize"
 

source/developers/development_environment.markdown

@@ -29,7 +29,7 @@ $ sudo apt-get install libssl-dev libxml2-dev libxslt1-dev libjpeg-dev libffi-de
 Different distributions have different package installation mechanisms and sometimes packages names as well. For example Centos would use: `sudo yum install epel-release && sudo yum install python34 python34-devel mysql-devel`
 </p>
 
-Additional dependencies exist if you you plan to perform Frontend Development, please read the [Frontend](https://home-assistant.io/developers/frontend/) section to learn more.
+Additional dependencies exist if you plan to perform Frontend Development, please read the [Frontend](https://home-assistant.io/developers/frontend/) section to learn more.
 
 #### {% linkable_title Developing on Windows %}