From 4e417d84a17bb7a3bae982e15aa48398f4caf48f Mon Sep 17 00:00:00 2001
From: Dilan Tsasi <35239159+DilanTsasi@users.noreply.github.com>
Date: Mon, 17 Jun 2024 18:16:33 +0100
Subject: [PATCH] Update communication.md (#2221)

---
 docs/add-ons/communication.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/add-ons/communication.md b/docs/add-ons/communication.md
index 379047ab..39c88507 100644
--- a/docs/add-ons/communication.md
+++ b/docs/add-ons/communication.md
@@ -15,7 +15,7 @@ Use `supervisor` for communication with the internal API.
 
 ## Home Assistant Core
 
-An add-on can talk to the [Home Assistant Core API][core-api] using the internal proxy. This makes it very easy to communicate with the API without knowing the password, port or any other information about the Home Assistant instance. Using this URL: `http://supervisor/core/api` ensures that internal communication is redirected to the right place. The next step is to add `homeassistant_api: true` to the `config.yaml` file and read the environment variable `SUPERVISOR_TOKEN`. Use this as the Home Assistant Core [bearer token](/auth_api.md#making-authenticated-requests) when making requests.
+An add-on can talk to the [Home Assistant Core API][core-api] using the internal proxy. This makes it very easy to communicate with the API without knowing the password, port or any other information about the Home Assistant instance. Using this URL: `http://supervisor/core/api/` ensures that internal communication is redirected to the right place. The next step is to add `homeassistant_api: true` to the `config.yaml` file and read the environment variable `SUPERVISOR_TOKEN`. Use this as the Home Assistant Core [bearer token](/auth_api.md#making-authenticated-requests) when making requests.
 
 For example `curl -X GET -H "Authorization: Bearer ${SUPERVISOR_TOKEN}" -H "Content-Type: application/json" http://supervisor/core/api/config`