From 46e078fce1f3578c34ece2bcb747d7225b11a874 Mon Sep 17 00:00:00 2001 From: rompic Date: Mon, 26 May 2025 21:48:50 +0200 Subject: [PATCH] chore: typos and consistant spelling of Home Assistant (#563) --- docs/akkudoktoreos/introduction.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/akkudoktoreos/introduction.md b/docs/akkudoktoreos/introduction.md index 55c9742..5d9da2e 100644 --- a/docs/akkudoktoreos/introduction.md +++ b/docs/akkudoktoreos/introduction.md @@ -161,7 +161,7 @@ corresponding sources can be easily integrated into a flow. In Home Assistant you could use an automation to prepare the input payload for EOS and then use the RESTful integration to call EOS. Based on this concept there is already a -home assistand add-on created by [Duetting](#duetting-solution). +Home Assistant add-on created by [Duetting](#duetting-solution). The plan created by EOS must also be executed via the chosen integration solution, with the respective devices receiving their instructions according to the plan.