From 82daad46d137e3775fb86a7c923f0c75b31d1ab0 Mon Sep 17 00:00:00 2001
From: SvenPittelkow <76539523+SvenPittelkow@users.noreply.github.com>
Date: Mon, 9 Dec 2024 06:35:42 +0100
Subject: [PATCH] Update voice_remote_local_assistant.markdown (#36232)

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

diff --git a/source/voice_control/voice_remote_local_assistant.markdown b/source/voice_control/voice_remote_local_assistant.markdown
index 671c577e80f5..2a347ccbcadc 100644
--- a/source/voice_control/voice_remote_local_assistant.markdown
+++ b/source/voice_control/voice_remote_local_assistant.markdown
@@ -13,7 +13,7 @@ related:
     title: Best practices with Assist
 ---
 
-The simplest and most effective way to use Assist is to leverage the voice providers (for speech-to-text and test-to-speech) included in [Home Assistant Cloud](/voice_control/voice_remote_cloud_assistant/) 
+The simplest and most effective way to use Assist is to leverage the voice providers (for speech-to-text and text-to-speech) included in [Home Assistant Cloud](/voice_control/voice_remote_cloud_assistant/) 
 
 If you are interested in setting up a fully local voice assistant, follow this setup:
 
@@ -95,4 +95,4 @@ The options are also documented in the add-on itself. Go to the {% my supervisor
 Also be sure to check the specific tutorial for [using Piper in Automations](voice_control/using_tts_in_automation/)
 
 ## Next steps
-Once the pipeline is configured, you are ready to jump into the basic conversation setup in Best Practices
\ No newline at end of file
+Once the pipeline is configured, you are ready to jump into the basic conversation setup in Best Practices