From de4845d18939c91a8e8898d763e2e93328b7853e Mon Sep 17 00:00:00 2001
From: Karlie Meads <68717336+karliemeads@users.noreply.github.com>
Date: Mon, 16 Jan 2023 15:41:02 -0500
Subject: [PATCH] Update documentation to reflect intuitive behaviour of an
 action being disabled (#25794)

---
 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 b45a3ae4087..00d0c66cce3 100644
--- a/source/_docs/scripts/conditions.markdown
+++ b/source/_docs/scripts/conditions.markdown
@@ -681,7 +681,7 @@ Every individual condition can be disabled, without removing it.
 To do so, add `enabled: false` to the condition configuration.
 
 This can be useful if you want to temporarily disable a condition, for example,
-for testing. A disabled condition will always pass.
+for testing. A disabled condition will behave as if it were removed.
 
 For example: