From aba08e271435dc6c5852488f7129b92df167095e Mon Sep 17 00:00:00 2001
From: dougiteixeira <31328123+dougiteixeira@users.noreply.github.com>
Date: Wed, 10 Jul 2024 18:49:29 -0300
Subject: [PATCH] Add config flow for image platform in Template (#33668)

---
 source/_integrations/template.markdown | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/source/_integrations/template.markdown b/source/_integrations/template.markdown
index 51d75b3678a..f914bf51bab 100644
--- a/source/_integrations/template.markdown
+++ b/source/_integrations/template.markdown
@@ -49,9 +49,9 @@ Sensors, binary (on/off) sensors, buttons, images, numbers and selects are cover
 - [Vacuum](/integrations/vacuum.template/)
 - [Weather](/integrations/weather.template/)
 
-Sensor and binary sensor can be configured using [UI](#ui-configuration) or [YAML](#yaml-configuration) file.
+Sensor, binary sensor and image can be configured using [UI](#ui-configuration) or [YAML](#yaml-configuration) file.
 
-Button, image, number, and select template entities are defined in your YAML configuration files under the `template:` key and cannot be configured via the UI. You can define multiple configuration blocks as a list. Each block defines sensor/binary sensor/number/select entities and can contain an optional update trigger.
+Button, number, and select template entities are defined in your YAML configuration files under the `template:` key and cannot be configured via the UI. You can define multiple configuration blocks as a list. Each block defines sensor/binary sensor/number/select entities and can contain an optional update trigger.
 
 _For old sensor/binary sensor configuration format, [see below](#legacy-binary-sensor-configuration-format)._