From 1104beb7dcf5ea878b7ba6555187fd2e9e10ccbe Mon Sep 17 00:00:00 2001
From: Danny Tsang <567982+dannytsang@users.noreply.github.com>
Date: Mon, 12 Dec 2022 15:59:04 +0000
Subject: [PATCH] Reworded introduction on conditions page. (#25256)

fixes undefined
---
 source/_docs/scripts/conditions.markdown | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/source/_docs/scripts/conditions.markdown b/source/_docs/scripts/conditions.markdown
index a51e0d891c2..c23eb0eec8d 100644
--- a/source/_docs/scripts/conditions.markdown
+++ b/source/_docs/scripts/conditions.markdown
@@ -5,7 +5,7 @@ toc: true
 no_toc: true
 ---
 
-Conditions can be used within a script or automation to prevent further execution. When a condition does not return true, the script or automation stops executing. A condition will look at the system at that moment. For example, a condition can test if a switch is currently turned on or off.
+Conditions can be used within a script or automation to prevent further execution. When a condition evaluates to true, the script or automation will be executed. If any other value is returned the script or automation stops executing. A condition will look at the system at that moment. For example, a condition can test if a switch is currently turned on or off.
 
 Unlike a trigger, which is always `or`, conditions are `and` by default - all conditions have to be true.