From d0aac4a8abe33f32d93233cd691de8e5fded3040 Mon Sep 17 00:00:00 2001
From: ChaseCares <13863948+ChaseCares@users.noreply.github.com>
Date: Wed, 30 Jun 2021 23:03:32 -0700
Subject: [PATCH] Update climate.mqtt.markdown (#18358)

fixed typo
---
 source/_integrations/climate.mqtt.markdown | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/source/_integrations/climate.mqtt.markdown b/source/_integrations/climate.mqtt.markdown
index 228a061b090..abb5cc6f07d 100644
--- a/source/_integrations/climate.mqtt.markdown
+++ b/source/_integrations/climate.mqtt.markdown
@@ -363,7 +363,7 @@ If a property works in *optimistic mode* (when the corresponding state topic is
 
 #### Using Templates
 
-For all `*_state_topic`s, a template can be specified that will be used to render the incoming payloads on these topics. Also, a default template that applies to all state topis can be specified as `value_template`. This can be useful if you received payloads are e.g., in JSON format. Since in JSON, a quoted string (e.g., `"foo"`) is just a string, this can also be used for unquoting.
+For all `*_state_topic`s, a template can be specified that will be used to render the incoming payloads on these topics. Also, a default template that applies to all state topics can be specified as `value_template`. This can be useful if you received payloads are e.g., in JSON format. Since in JSON, a quoted string (e.g., `"foo"`) is just a string, this can also be used for unquoting.
 
 Say you receive the operation mode `"auto"` via your `mode_state_topic`, but the mode is actually called just `auto`, here's what you could do: