From dca90a22d62d6469aa0dca23dcea1112aa9185ce Mon Sep 17 00:00:00 2001 From: Mark Herwege Date: Tue, 17 Mar 2026 13:31:00 +0100 Subject: [PATCH] Correct rule action to rule language (#2657) Signed-off-by: Mark Herwege --- tutorials/getting_started/rules_introduction.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/tutorials/getting_started/rules_introduction.md b/tutorials/getting_started/rules_introduction.md index 26986effa..0b80acc38 100644 --- a/tutorials/getting_started/rules_introduction.md +++ b/tutorials/getting_started/rules_introduction.md @@ -93,12 +93,12 @@ When run manually, the conditions are ignored. If triggers define when the rule runs and conditions define what must be true for the rule to run, the actions define the rule's behaviors. There are four categories of Actions. -| Action | Purpose | -|-----------------|---------------------------------------------------------| -| Item Action | to command or update an Item | -| Other Rules | to cause another rule to run | -| Audio and Voice | to cause TTS or an audio file to play on an audio sink | -| Script Action | to execute some code written in a supported rule action | +| Action | Purpose | +|-----------------|-----------------------------------------------------------| +| Item Action | to command or update an Item | +| Other Rules | to cause another rule to run | +| Audio and Voice | to cause TTS or an audio file to play on an audio sink | +| Script Action | to execute some code written in a supported rule language | ### A Note on Rule Languages