diff --git a/source/_docs/automation/action.markdown b/source/_docs/automation/action.markdown index e44f4f8ea62..ca876ce108d 100644 --- a/source/_docs/automation/action.markdown +++ b/source/_docs/automation/action.markdown @@ -3,11 +3,11 @@ title: "Automation actions" description: "Automations result in action." --- -The action of an automation rule is what is being executed when a rule fires. The action part follows the [script syntax](/docs/scripts/) which can be used to interact with anything via services or events. +The action of an automation rule is what is being executed when a rule fires. The action part follows the [script syntax](/docs/scripts/) which can be used to interact with anything via other actions or events. -For {% term services %}, you can specify the `entity_id` that it should apply to and optional service parameters (to specify for example the brightness). +For actions, you can specify the `entity_id` that it should apply to and optional parameters (to specify for example the brightness). -You can also call the {% term service %} to activate [a scene](/integrations/scene/) which will allow you to define how you want your devices to be and have Home Assistant call the right services. +You can also perform the action to activate [a scene](/integrations/scene/) which will allow you to define how you want your devices to be and have Home Assistant perform the right action. {% raw %} @@ -48,7 +48,7 @@ automation 2: {% endraw %} -Conditions can also be part of an action. You can combine multiple service calls and conditions in a single action, and they will be processed in the order you put them in. If the result of a condition is false, the action will stop there so any service calls after that condition will not be executed. +Conditions can also be part of an action. You can combine multiple actions and conditions in a single action, and they will be processed in the order you put them in. If the result of a condition is false, the action will stop there so any action after that condition will not be executed. ```yaml automation: