From 2cbf74204a88ce31be427a27ecd7156e534ed332 Mon Sep 17 00:00:00 2001
From: Stefan <37924749+stefanroelofs@users.noreply.github.com>
Date: Fri, 2 Oct 2020 10:43:32 +0200
Subject: [PATCH] Update templating.markdown (#14704)

Fixed broken link
---
 source/_docs/automation/templating.markdown | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/source/_docs/automation/templating.markdown b/source/_docs/automation/templating.markdown
index 58d0aee93cf..aeb9c9f02d5 100644
--- a/source/_docs/automation/templating.markdown
+++ b/source/_docs/automation/templating.markdown
@@ -64,7 +64,7 @@ Remembering these simple rules will help save you from many headaches and endles
 
 ## Trigger State Object
 
-Knowing how to access the [state object](/docs/configuration/state_object/) of a trigger entity can be useful in automations. Here are a few ways to access the [`state`](#state), [`numeric_state`](#numeric_state) and [`template`](#template) triggers:
+Knowing how to access the [state object](/docs/configuration/state_object/) of a trigger entity can be useful in automations. Here are a few ways to access the [`state`](#state), [`numeric state`](#numeric-state) and [`template`](#template) triggers:
 
 * `trigger.from_state` will return the **previous** [state object](/docs/configuration/state_object/) of the entity.
 * `trigger.to_state` will return the **new** [state object](/docs/configuration/state_object/) that triggered trigger.