Skip to content

Commit 2b5d3c0

Browse files
mnoorenbergheLandrash
mnoorenberghe
authored and
Landrash
committed
Fix over 100 typos/spelling mistakes :P (home-assistant#1483)
* Fix a bunch of typos/spelling mistakes * Removed extra spaces from emulated_hue * Correct device type. of binary_sensor.enocean.markdown
1 parent 455325f commit 2b5d3c0

File tree

78 files changed

+101
-101
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

78 files changed

+101
-101
lines changed

‎source/_components/alarm_control_panel.concord232.markdown

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -25,5 +25,5 @@ alarm_control_panel:
2525
Configuration variables:
2626
2727
- **host** (*Optional*): The host where the concord232 server process is running. Defaults to localhost.
28-
- **port** (*Optional*): The port where the Alarm panel ist listening. Defaults to 5007.
28+
- **port** (*Optional*): The port where the Alarm panel is listening. Defaults to 5007.
2929

‎source/_components/alarm_control_panel.nx584.markdown

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -25,5 +25,5 @@ alarm_control_panel:
2525
Configuration variables:
2626
2727
- **host** (*Optional*): The host where the nx584 server process is running. Defaults to `localhost`.
28-
- **port** (*Optional*): The port where the Alarm panel ist listening. Defaults to `5007`.
28+
- **port** (*Optional*): The port where the Alarm panel is listening. Defaults to `5007`.
2929

‎source/_components/binary_sensor.concord232.markdown

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -25,5 +25,5 @@ binary_sensor:
2525
Configuration variables:
2626
2727
- **host** (*Optional*): The host where the concord232 server process is running. Defaults to `localhost`.
28-
- **port** (*Optional*): The port where the Alarm panel ist listening. Defaults to 5007.
28+
- **port** (*Optional*): The port where the Alarm panel is listening. Defaults to 5007.
2929

‎source/_components/binary_sensor.enocean.markdown

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ ha_release: 0.21
1313
ha_iot_class: "Local Push"
1414
---
1515

16-
This can typically be one of those batteryless wall switches. Currently only one type has been tested: Eltako FT55. Other devices will most likely not work without changing the Home Asisstant code.
16+
This can typically be one of those batteryless wall switches. Currently only one type has been tested: Eltako FT55. Other devices will most likely not work without changing the Home Assistant code.
1717

1818
To use your EnOcean device, you first have to set up your [EnOcean hub](/components/enocean/) and then add the following to your `configuration.yaml` file:
1919

@@ -27,5 +27,5 @@ binary_sensor:
2727
Configuration variables:
2828
2929
- **id** (*Required*): The ID of the device. This is the 4 bytes long number written on the dimmer.
30-
- **name** (*Optional*): An identifier for the Ligh in the frontend.
30+
- **name** (*Optional*): An identifier for the switch in the frontend.
3131
- **sensor_class** (*Optional*): The [type/class](/components/binary_sensor/) of the sensor to set the icon in the frontend.

‎source/_components/binary_sensor.modbus.markdown

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -34,5 +34,5 @@ Configuration variables:
3434
3535
- **coils** array (*Required*): The array contains a list of coils to read from.
3636
- **name** (*Required*): Name of the sensor.
37-
- **slave** (*Required*): The number of the slave (Optional for tcp and upd Modbus).
37+
- **slave** (*Required*): The number of the slave (Optional for TCP and UDP Modbus).
3838
- **coil** (*Required*): Coil number.

‎source/_components/binary_sensor.netatmo.markdown

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -40,7 +40,7 @@ Configuration variables:
4040
4141
- **home** (*Optional*): Will use the cameras of this home only.
4242
- **timeout** (*Optional*): The binary sensors will reflect the events from the last X minutes (default: 15)
43-
- **cameras** array (*Optional*): Cameras to use. Multiple enties allowed.
43+
- **cameras** array (*Optional*): Cameras to use. Multiple entities allowed.
4444
- 'camera_name': Name of the camera to display.
4545
- **monitored_conditions** array (*Optional*): List of monitored conditions.
4646
- 'Someone known'

‎source/_components/binary_sensor.rest.markdown

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -54,7 +54,7 @@ Configuration variables:
5454
- **name** (*Optional*): Name of the REST binary sensor.
5555
- **sensor_class** (*Optional*): The [type/class](/components/binary_sensor/) of the sensor to set the icon in the frontend.
5656
- **value_template** (*Optional*): Defines a [template](/topics/templating/) to extract the value.
57-
- **payload** (*Optional*): The payload to send with a POST request. Usualy formed as a dictionary.
57+
- **payload** (*Optional*): The payload to send with a POST request. Usually formed as a dictionary.
5858
- **verify_ssl** (*Optional*): Verify the certification of the endpoint. Default to True.
5959
- **authentication** (*Optional*): Type of the HTTP authentication. `basic` or `digest`.
6060
- **username** (*Optional*): The username for accessing the REST endpoint.

‎source/_components/binary_sensor.trend.markdown

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ Configuration variables:
3333
- **sensor_class** (*Optional*): The [type/class](/components/binary_sensor/) of the sensor to set the icon in the frontend.
3434
- **entity_id** (*Required*): The entity that this sensor tracks.
3535
- **attribute** (*Optional*): The attribute of the entity that this sensor tracks. If no attribute is specified then the sensor will track the state.
36-
- **invert** (*Optional*): Invert the result (so `true` means decending rather than ascending)
36+
- **invert** (*Optional*): Invert the result (so `true` means descending rather than ascending)
3737

3838
## {% linkable_title Examples %}
3939

‎source/_components/binary_sensor.zigbee.markdown

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -27,8 +27,8 @@ binary_sensor:
2727
2828
Configuration variables:
2929
30-
- **name** (*Required*): The name you wouldd like to give the binary sensor in Home Assistant.
30+
- **name** (*Required*): The name you would like to give the binary sensor in Home Assistant.
3131
- **pin** (*Required*): The number identifying which pin to use.
32-
- **address** (*Optional*): The long 64bit address of the remote ZigBee device whose digital input pin you'd like to sample. Do not include this variable if you want to sample the local ZigBee device's pins.
32+
- **address** (*Optional*): The long 64-bit address of the remote ZigBee device whose digital input pin you'd like to sample. Do not include this variable if you want to sample the local ZigBee device's pins.
3333
- **on_state** (*Optional*): Either `high` (default) or `low`, depicting whether the binary sensor is considered `on` when the pin is `high` or `low`.
3434

‎source/_components/camera.ffmpeg.markdown

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ ha_release: 0.26
1313
---
1414

1515

16-
The `ffmpeg` platform allows you to use any video feed as a camera in Home Assistant via [FFmpeg](http://www.ffmpeg.org/). This video source must support multiple simultaenous reads, because for every concurrent Home Assistant user, a connection will be made to the source every 10 seconds. Normally this should not be a problem.
16+
The `ffmpeg` platform allows you to use any video feed as a camera in Home Assistant via [FFmpeg](http://www.ffmpeg.org/). This video source must support multiple simultaneous reads, because for every concurrent Home Assistant user, a connection will be made to the source every 10 seconds. Normally this should not be a problem.
1717

1818
To enable your FFmpeg feed in your installation, add the following to your `configuration.yaml` file:
1919

‎source/_components/camera.netatmo.markdown

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ camera:
3131
Configuration variables:
3232
3333
- **home** (*Optional*): Will display the cameras of this home only.
34-
- **cameras** array (*Optional*): Cameras to use. Multiple enties allowed.
34+
- **cameras** array (*Optional*): Cameras to use. Multiple entities allowed.
3535
- **camera_name**: Name of the camera to display.
3636
3737
If **home** and **cameras** are not provided, all cameras will be displayed. For more control over your cameras check the configuration sample below.

‎source/_components/camera.synology.markdown

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ Configuration variables:
3131
- **url** (*Required*): The URL to your synology, including port.
3232
- **username** (*Required*): The username for accessing surveillance station.
3333
- **password** (*Required*): The password for accessing surveillance station.
34-
- **whitelist** (*Optional*): A list of which cameras you want to add, the names must be the same as in Surveillance Station. If omited all cameras are added.
34+
- **whitelist** (*Optional*): A list of which cameras you want to add, the names must be the same as in Surveillance Station. If omitted all cameras are added.
3535
- **verify_ssl** (*Optional*): True to require a valid certificate, False to disable certificate checking. Defaults to `True`.
3636

3737
A full sample configuration for the `synology` platform is shown below:

‎source/_components/climate.generic_thermostat.markdown

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ Configuration variables:
3131
- **target_sensor** (*Required*): `entity_id` for a temperature sensor, target_sensor.state must be temperature.
3232
- **min_temp** (*Optional*): Set minimum set point available (default: 7)
3333
- **max_temp** (*Optional*): Set maximum set point available (default: 35)
34-
- **target_temp** (*Optional*): Set intital target temperature. Failure to set this variable will result in target temperature being set to null on startup.
34+
- **target_temp** (*Optional*): Set initial target temperature. Failure to set this variable will result in target temperature being set to null on startup.
3535
- **ac_mode** (*Optional*): Set the switch specified in the *heater* option to be treated as a cooling device instead of a heating device.
3636
- **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.
3737

‎source/_components/climate.heatmiser.markdown

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -38,4 +38,4 @@ Configuration variables:
3838
- **port** (*Required*): The port that the interface is listening on.
3939
- **tstats** (*Required*): A list of thermostats activated on the gateway.
4040
- **id** (*Required*): The id of the thermostat as configured on the device itself
41-
- **name** (*Required*): A friendly name for the themostat
41+
- **name** (*Required*): A friendly name for the thermostat

‎source/_components/climate.proliphix.markdown

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ climate:
3131
3232
Configuration variables:
3333
34-
- **host** (*Required*): Adress of your thermostat, eg. 192.168.1.32
34+
- **host** (*Required*): Address of your thermostat, eg. 192.168.1.32
3535
- **username** (*Required*): Username for the thermostat.
3636
- **password** (*Required*): Password for the thermostat.
3737

‎source/_components/climate.radiotherm.markdown

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ ha_category: Climate
1414

1515
The `radiotherm` climate platform let you control a thermostat from [Radio Thermostat](http://www.radiothermostat.com/).
1616

17-
The underlaying library supports:
17+
The underlying library supports:
1818

1919
- CT50 V1.09
2020
- CT50 V1.88
@@ -36,7 +36,7 @@ Configuration variables:
3636

3737
Temperature settings from Home Assistant will be sent to thermostat and then hold at that temperature. Set to `False` if you set a thermostat schedule on the thermostat itself and just want Home Assistant to send temporary temperature changes.
3838

39-
Multiple thermostats could be assigned by using `host:` if auto-detetion is not used.
39+
Multiple thermostats could be assigned by using `host:` if auto-detection is not used.
4040

4141
```yaml
4242
climate:

‎source/_components/demo.markdown

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ ha_category: Other
1212
---
1313

1414

15-
The `demo` platform allows you to use components which are providing a demo of their implementation. The demo entities are dummies but show you how the acutal platform looks like. This way you can run own demonstration instance like the online [Home Assistant demo](https://home-assistant.io/demo/) or `hass --demo-mode` but combined with your own real/functional platforms.
15+
The `demo` platform allows you to use components which are providing a demo of their implementation. The demo entities are dummies but show you how the actual platform looks like. This way you can run own demonstration instance like the online [Home Assistant demo](https://home-assistant.io/demo/) or `hass --demo-mode` but combined with your own real/functional platforms.
1616

1717
Available demo platforms:
1818

‎source/_components/device_tracker.bluetooth_tracker.markdown

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -23,6 +23,6 @@ device_tracker:
2323
- platform: bluetooth_tracker
2424
```
2525
26-
In some cases it can be that your device is not discovered. In that case let your phone scan for BT devices while you restart Home Assistant. Just hit `Scan` on your phone all the time until Home Assisstant is fully restarted and the device should appear in `known_devices.yaml`.
26+
In some cases it can be that your device is not discovered. In that case let your phone scan for BT devices while you restart Home Assistant. Just hit `Scan` on your phone all the time until Home Assistant is fully restarted and the device should appear in `known_devices.yaml`.
2727

2828
For additional configuration variables check the [Device tracker page](/components/device_tracker/).

‎source/_components/device_tracker.owntracks.markdown

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,7 @@ Configuration variables:
3232
- **waypoints** (*Optional*): Owntracks users can define [waypoints](http://owntracks.org/booklet/features/waypoints/) (a.k.a regions) which are similar in spirit to Home Assistant zones. If this configuration variable is `True`, the Owntracks users who are in `waypoint_whitelist` can export waypoints from the device and Home Assistant will import them as zone definitions. Defaults to `True`.
3333
- **waypoint_whitelist** (*Optional*): A list of user names (as defined for [Owntracks](https://home-assistant.io/components/device_tracker.owntracks/)) who can export their waypoints from Owntracks to Home Assistant. Defaults to all users who are connected to Home Assistant via Owntracks.
3434

35-
A full sample configuration for the `owntracks` plaftfrom is shown below:
35+
A full sample configuration for the `owntracks` platform is shown below:
3636

3737
```yaml
3838
# Example configuration.yaml entry

‎source/_components/device_tracker.tplink.markdown

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ ha_release: pre 0.7
1616
The `tplink` platform allows you to detect presence by looking at connected devices to a [TP-Link](https://www.tp-link.com) device. This includes the ArcherC9 line.
1717

1818
<p class='note'>
19-
TP-Link devices typically only allow one login at a time to the admin console. This component will count torwards your one allowed login. Depending on how aggressively you configure device_tracker you may not be able to access the admin console of your TP-Link device without first stopping Home Assistant (and waiting a few minutes for the session to timeout) before you'll be able to login.
19+
TP-Link devices typically only allow one login at a time to the admin console. This component will count towards your one allowed login. Depending on how aggressively you configure device_tracker you may not be able to access the admin console of your TP-Link device without first stopping Home Assistant (and waiting a few minutes for the session to timeout) before you'll be able to login.
2020
</p>
2121

2222

@@ -38,7 +38,7 @@ Configuration variables:
3838
For Archer C9 models running firmware version 150811 or later please use the encrypted password you can retrieve like this:
3939
4040
1. Go to the login page of your router. (default: 192.168.0.1)
41-
2. Type in the password you use to login into the passsword field.
41+
2. Type in the password you use to login into the password field.
4242
3. Click somewhere else on the page so that the password field is not selected anymore.
4343
4. Open the JavaScript console of your browser (usually by pressing F12 and then clicking on "Console").
4444
5. Type ```document.getElementById("login-password").value;```.

‎source/_components/ecobee.markdown

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -54,7 +54,7 @@ ecobee:
5454
5555
Configuration variables:
5656
57-
- **api_key** (*Required*): Your ecobee API key. This is only needed for the inital setup of the component. Once registered it can be removed. If you revoke the key in the ecobee portal you will need to update this again and remove the ecobee.conf file in the `.homeassistant` configuration path.
57+
- **api_key** (*Required*): Your ecobee API key. This is only needed for the initial setup of the component. Once registered it can be removed. If you revoke the key in the ecobee portal you will need to update this again and remove the ecobee.conf file in the `.homeassistant` configuration path.
5858
- **hold_temp** (*Optional*): True/False whether or not to hold changes indefinitely (True) or until the next scheduled event. Defaults to `False`.
5959

6060
<p class='img'>

‎source/_components/emoncms_history.markdown

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -35,4 +35,4 @@ Configuration variables:
3535
- **url** (*Required*): The root URL of your Emoncms installation. (Use https://emoncms.org for the cloud based version)
3636
- **inputnode** (*Required*): Input node that will be used inside emoncms. Please make sure you use a dedicated, not used before, node for this component!
3737
- **whitelist** (*Required*): List of entity IDs you want to publish.
38-
- **scan_interval** (*Optional*): Defines, in seconds, how reguarly the states of the whitelisted entities are being gathered and send to emoncms. Default is 30 seconds.
38+
- **scan_interval** (*Optional*): Defines, in seconds, how regularly the states of the whitelisted entities are being gathered and send to emoncms. Default is 30 seconds.

‎source/_components/emulated_hue.markdown

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ The `emulated_hue` component provides a virtual Philips Hue bridge, written enti
1616
entities. The driving use case behind this functionality is to allow Home Assistant to work with an Amazon Echo with no set up cost outside of configuration changes.
1717

1818
<p class='note'>
19-
It is recommended to assign a static IP address to the computer running Home Assistant. This is because the Amazon Echo discovers devices by IP addresss, and if the IP changes, the Echo won't be able to control it. This is easiest done from your router, see your router's manual for details.
19+
It is recommended to assign a static IP address to the computer running Home Assistant. This is because the Amazon Echo discovers devices by IP addresses, and if the IP changes, the Echo won't be able to control it. This is easiest done from your router, see your router's manual for details.
2020
</p>
2121

2222
### {% linkable_title Configuration %}
@@ -41,7 +41,7 @@ Configuration variables:
4141
- `script`
4242
- `scene`
4343

44-
- **expose_by_default** (*Optional*): Whether or not entities should be exposed via the bridge by default instead of explicitly (see the 'emulated_hue' customization below). If not specified, this defaults to true. Warning: If you have a lot of devices (more than 49 total across all exposed domains), you should be careful with this opton. Exposing more devices than Alexa supports can result in it not seeing any of them. If you are having trouble getting any devices to show up, try disabling this, and explicitly exposing just a few devices at a time to see if that fixes it.
44+
- **expose_by_default** (*Optional*): Whether or not entities should be exposed via the bridge by default instead of explicitly (see the 'emulated_hue' customization below). If not specified, this defaults to true. Warning: If you have a lot of devices (more than 49 total across all exposed domains), you should be careful with this option. Exposing more devices than Alexa supports can result in it not seeing any of them. If you are having trouble getting any devices to show up, try disabling this, and explicitly exposing just a few devices at a time to see if that fixes it.
4545

4646
- **exposed_domains** (*Optional*): The domains that are exposed by default if `expose_by_default` is set to true. If not specified, this defaults to the following list:
4747
- `switch`

‎source/_components/ffmpeg.markdown

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ ha_category: Hub
1414
The FFmpeg component allows other Home Assistant components to process video and audio streams. This component supports all FFmpeg versions since 3.0.0; if you have a older version, please update.
1515

1616
<p class='note'>
17-
You need the `ffmpeg` binary in your system path. On Debian 8 or Raspbian (Jessie) you can install it from [debian-backports](https://backports.debian.org/Instructions/). If you want [hardware acceleration](https://trac.ffmpeg.org/wiki/HWAccelIntro) support on a Raspberry Pi, you will need to build from source by yourself. Windows binaries are avilable on the [FFmpeg](http://www.ffmpeg.org/) website.
17+
You need the `ffmpeg` binary in your system path. On Debian 8 or Raspbian (Jessie) you can install it from [debian-backports](https://backports.debian.org/Instructions/). If you want [hardware acceleration](https://trac.ffmpeg.org/wiki/HWAccelIntro) support on a Raspberry Pi, you will need to build from source by yourself. Windows binaries are available on the [FFmpeg](http://www.ffmpeg.org/) website.
1818
</p>
1919

2020
To set it up, add the following information to your `configuration.yaml` file:

‎source/_components/hdmi_cec.markdown

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -40,7 +40,7 @@ $ ln -s /usr/local/lib/python3.4/dist-packages/cec /srv/hass/hass_venv/lib/pytho
4040
```
4141

4242
<p class='note'>If after symlinking and adding `hdmi_cec:` to your configuration you are getting the following error in your logs,
43-
`* failed to open vchiq instance` you will also need to add the user account Home Asssistant runs under, to the `video` group. To add the Home Assistant user account to the `video` group, run the following command. `$ usermod -a -G video <hass_user_account>`
43+
`* failed to open vchiq instance` you will also need to add the user account Home Assistant runs under, to the `video` group. To add the Home Assistant user account to the `video` group, run the following command. `$ usermod -a -G video <hass_user_account>`
4444
</p>
4545

4646
## {% linkable_title Testing your installation %}

0 commit comments

Comments
 (0)