diff --git a/source/_docs/automation/trigger.markdown b/source/_docs/automation/trigger.markdown index 748ff6313d0..02db1fb64ed 100644 --- a/source/_docs/automation/trigger.markdown +++ b/source/_docs/automation/trigger.markdown @@ -78,13 +78,12 @@ automation:

Listing above and below together means the numeric_state has to be between the two values. -In the example above, a numeric_state that goes to 17.1-24.9 (from 17 or below, or 25 or above) -would fire this trigger. +In the example above, a numeric_state that goes to 17.1-24.9 (from 17 or below, or 25 or above) would fire this trigger.

### {% linkable_title State trigger %} -Triggers when the state of a given entity changes. If only entity_id is given trigger will activate for all state changes, even if only state attributes change. +Triggers when the state of a given entity changes. If only `entity_id` is given trigger will activate for all state changes, even if only state attributes change. ```yaml automation: @@ -183,7 +182,7 @@ automation 3: ### {% linkable_title Zone trigger %} -Zone triggers can trigger when an entity is entering or leaving the zone. For zone automation to work, you need to have setup a device tracker platform that supports reporting GPS coordinates. This includes [GPS Logger](/components/device_tracker.gpslogger/), the [OwnTracks platform](/components/device_tracker.owntracks/), and the [iCloud platform](/components/device_tracker.icloud/). +Zone triggers can trigger when an entity is entering or leaving the zone. For zone automation to work, you need to have setup a device tracker platform that supports reporting GPS coordinates. This includes [GPS Logger](/components/device_tracker.gpslogger/), the [OwnTracks platform](/components/device_tracker.owntracks/) and the [iCloud platform](/components/device_tracker.icloud/). ```yaml automation: