jeans/home-assistant.io
jeans/home-assistant.io
1
0
Fork 0
mirror of https://github.com/home-assistant/home-assistant.io.git synced 2025-07-19 07:17:14 +00:00
Code Issues Packages Projects Releases Wiki Activity

Fixing some typos (#15194)

Browse Source
This commit is contained in:
Sam Welek 2020-10-12 12:55:52 +01:00 committed by GitHub
parent d58152e568
commit 75db96a083
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
8 changed files with 9 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
source/_docs/configuration/basic.markdown
View File

@ -27,7 +27,7 @@ homeassistant:
recordings: /mnt/recordings
```
NOTE: You will not be able to edit anything in Configuration -> General in the UI if you are using YAML configuration for any of the following: name, latitude, longitute, elevation, unit_system, temperature_unit, time_zone, external_url, internal_url.
NOTE: You will not be able to edit anything in Configuration -> General in the UI if you are using YAML configuration for any of the following: name, latitude, longitude, elevation, unit_system, temperature_unit, time_zone, external_url, internal_url.
{% configuration %}
name:

2
source/_docs/configuration/customizing-devices.markdown
View File

@ -53,7 +53,7 @@ device_class:
type: device_class
default: None
unit_of_measurement:
description: Defines the units of measurement, if any. This will also influence the graphical presentation in the history visualisation as continuous value. Sensors with missing `unit_of_measurement` are showing as discrete values.
description: Defines the units of measurement, if any. This will also influence the graphical presentation in the history visualization as continuous value. Sensors with missing `unit_of_measurement` are showing as discrete values.
required: false
type: string
default: None

2
source/_docs/z-wave/devices.markdown
View File

@ -38,7 +38,7 @@ From 2 April 2017 all newly approved Z-Wave devices will have to support the Sec
Your Z-Wave mesh network is built with the devices that are mains powered (whether directly, or via a USB adapter), these relay traffic for other nodes, building the network. These devices are always awake and you can query them, or send configuration changes, at any time.
Battery powered devices spend most of their time asleep, unable to relay traffic, to be queried, or receive changes. Changes sent while a device is asleep will be queued and sent the next time the device wakes. Details of the default wake interval, and how to manually wake the device (if supported) will be detailed in the devices's manual. Some battery powered devices (primarily locks and thermostats) support beaming (the *Beam* command class) that allows them to be remotely woken. This does require that all devices in the network responsible for relaying the commands between the controller and the device also support beaming.
Battery powered devices spend most of their time asleep, unable to relay traffic, to be queried, or receive changes. Changes sent while a device is asleep will be queued and sent the next time the device wakes. Details of the default wake interval, and how to manually wake the device (if supported) will be detailed in the device's manual. Some battery powered devices (primarily locks and thermostats) support beaming (the *Beam* command class) that allows them to be remotely woken. This does require that all devices in the network responsible for relaying the commands between the controller and the device also support beaming.
<div class='note'>

2
source/_integrations/traccar.markdown
View File

@ -159,7 +159,7 @@ device_tracker:
monitored_conditions: ['alarm', 'mycomputedattribute']
```
The parameter `event` allows you to import events from the traccar platform (https://www.traccar.org/documentation/events/) and fire them in your Home Assistant. It accepts a list of events to be monitored and imported and each event must be listed in lowercase snakecase. The events will be fired with the same event name defined in the abovementioned list preceded by the prefix `traccar_`. For example if you need to import the Traccar events `deviceOverspeed` and `deviceFuelDrop` in Home Assistant, you need to fill the `event` parameter with:
The parameter `event` allows you to import events from the traccar platform (https://www.traccar.org/documentation/events/) and fire them in your Home Assistant. It accepts a list of events to be monitored and imported and each event must be listed in lowercase snakecase. The events will be fired with the same event name defined in the aforementioned list preceded by the prefix `traccar_`. For example if you need to import the Traccar events `deviceOverspeed` and `deviceFuelDrop` in Home Assistant, you need to fill the `event` parameter with:
```yaml
device_tracker:

4
source/_integrations/transport_nsw.markdown
View File

@ -16,7 +16,7 @@ Prerequisite is a free API key from [Transport NSW](https://opendata.transport.n
In order to find your stop id, use the [Transport NSW stop finder](https://transportnsw.info/stop#/) and search for your stop. The URL will contain the stop id as a number.
You may also try going to Google maps and clicking on any bus/train/ferry stop. The pop up window shows the stop ID underneath the station name. For train stations the easist way to get a stop id for a platform is through [Transport NSW Info](https://transportnsw.info/).
You may also try going to Google maps and clicking on any bus/train/ferry stop. The pop up window shows the stop ID underneath the station name. For train stations the easiest way to get a stop id for a platform is through [Transport NSW Info](https://transportnsw.info/).
As a default the sensor picks up the next mode of transport leaving from a stop id.
@ -81,7 +81,7 @@ sensor:
api_key: 'YOUR API KEY'
```
The sensor returns n/a if no stop event is found within the next 24h. A `template` sensor can help building a more meaninful string.
The sensor returns n/a if no stop event is found within the next 24h. A `template` sensor can help building a more meaningful string.
{% raw %}
```yaml

2
source/_integrations/volvooncall.markdown
View File

@ -64,7 +64,7 @@ mutable:
default: true
type: boolean
name:
description: "Make it possible to provide a name for the vehicles. Note: Use all lower case letters when inputing your VIN number."
description: "Make it possible to provide a name for the vehicles. Note: Use all lower case letters when inputting your VIN number."
required: false
type: string
resources:

2
source/_integrations/xiaomi.markdown
View File

@ -35,7 +35,7 @@ Raspbian users: Don't forget to install `ffmpeg` support on your platform, other
</div>
<div class='note warning'>
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.
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 retrieves the video which was saved 1 minute earlier.
</div>
<div class='note warning'>

2
source/lovelace/badges.markdown
View File

@ -7,7 +7,7 @@ Badges are widgets that sit at the top of a Lovelace panel, above all the cards.
### State Label Badge
The State Label badge allows you to dislay a state badge. This badge supports [actions](/lovelace/actions/).
The State Label badge allows you to display a state badge. This badge supports [actions](/lovelace/actions/).
```yaml
type: state-label