From d3385dca21e0d17df84c5cf1b6e75c015b235be9 Mon Sep 17 00:00:00 2001 From: Jacob Snyder Date: Wed, 9 Nov 2022 00:04:58 -0800 Subject: [PATCH] Fix "Developer Tools -> Services" link (#24867) --- source/_docs/automation/basics.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_docs/automation/basics.markdown b/source/_docs/automation/basics.markdown index 4ae74ca7de0..e49a1655874 100644 --- a/source/_docs/automation/basics.markdown +++ b/source/_docs/automation/basics.markdown @@ -37,7 +37,7 @@ Automation rules interact directly with the internal state of Home Assistant, so State changes can be used as the source of triggers and the current state can be used in conditions. -Actions are all about calling *services*. To explore the available *services* open the **{% my developer_states title="Developer Tools -> Services" %}**. *Services* allow changing anything. For example turn on a light, run a script or enable a scene. Each *service* has a domain and a name. For example the *service* {% my developer_call_service service="light.turn_on" %} is capable of turning on any light in your system. Parameters can be passed to a *service* to indicate, for example, which device to activate or which color to use. +Actions are all about calling *services*. To explore the available *services* open the **{% my developer_services title="Developer Tools -> Services" %}**. *Services* allow changing anything. For example turn on a light, run a script or enable a scene. Each *service* has a domain and a name. For example the *service* {% my developer_call_service service="light.turn_on" %} is capable of turning on any light in your system. Parameters can be passed to a *service* to indicate, for example, which device to activate or which color to use. ## Creating automations