From aac7568ee19a173f1584799aa96d2b6de2214441 Mon Sep 17 00:00:00 2001 From: Pratyush Mohapatra Date: Sun, 23 Oct 2016 00:25:49 +0530 Subject: [PATCH] added a word to fix grammar --- source/getting-started/automation-condition.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/getting-started/automation-condition.markdown b/source/getting-started/automation-condition.markdown index 8c54c6861aa2..c242cc0ce736 100644 --- a/source/getting-started/automation-condition.markdown +++ b/source/getting-started/automation-condition.markdown @@ -9,7 +9,7 @@ sharing: true footer: true --- -Conditions are an optional part of an automation rule and be used to prevent an action from happening when triggered. Conditions look very similar to triggers but are very different. A trigger will look at events happening in the system while a condition only looks at how the system looks right now. A trigger can observe that a switch is being turned on. A condition can only see if a switch is currently on or off. +Conditions are an optional part of an automation rule and can be used to prevent an action from happening when triggered. Conditions look very similar to triggers but are very different. A trigger will look at events happening in the system while a condition only looks at how the system looks right now. A trigger can observe that a switch is being turned on. A condition can only see if a switch is currently on or off. The available conditions for an automation are the same as for the script syntax. So see that page for a [full list of available conditions][script-condition].