From 938121e85727e838590fdf6b7f28253c54725ab3 Mon Sep 17 00:00:00 2001
From: c0ffeeca7 <38767475+c0ffeeca7@users.noreply.github.com>
Date: Thu, 6 Jun 2024 09:42:39 +0200
Subject: [PATCH] Replace VS Code by correct name, Studio Code Server (#33103)

---
 source/_docs/configuration.markdown           | 4 ++--
 source/_docs/troubleshooting_general.markdown | 2 +-
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/source/_docs/configuration.markdown b/source/_docs/configuration.markdown
index 0ac7b292c1a..080fb014545 100644
--- a/source/_docs/configuration.markdown
+++ b/source/_docs/configuration.markdown
@@ -40,11 +40,11 @@ File access depends on your [installation method](/installation/#advanced-instal
 
    - [Configure file access on the Operating System](/common-tasks/os/#configuring-access-to-files):
      - If you are unsure which option to choose, install the [file editor add-on](/common-tasks/os/#installing-and-using-the-file-editor-add-on).
-     - Alternatively, use the [VS Code add-on](/common-tasks/os/#installing-and-using-the-visual-studio-code-vsc-add-on). This editor offers live syntax checking and auto-fill of various Home Assistant entities. But it looks more complex than the file editor.
+     - Alternatively, use the [Studio Code Server add-on](/common-tasks/os/#installing-and-using-the-visual-studio-code-vsc-add-on). This editor offers live syntax checking and auto-fill of various Home Assistant entities. But it looks more complex than the file editor.
      - If you prefer to use a file editor on your computer, use the [Samba add-on](/common-tasks/os/#installing-and-using-the-samba-add-on).
    - [Configure file access on Supervised](/common-tasks/supervised/#configuring-access-to-files):
      - Using the [File editor add-on](/common-tasks/supervised/#installing-and-using-the-file-editor-add-on).
-     - Using the [VS Code add-on](/common-tasks/supervised/#installing-and-using-the-visual-studio-code-vsc-add-on).
+     - Using the [Studio Code Server add-on](/common-tasks/supervised/#installing-and-using-the-visual-studio-code-vsc-add-on).
      - Using the [Samba add-on](/common-tasks/supervised/#installing-and-using-the-samba-add-on).
 
 2. To look up the path to your configuration directory, go to {% my system_health title="**Settings** > **System** > **Repairs**" %}.
diff --git a/source/_docs/troubleshooting_general.markdown b/source/_docs/troubleshooting_general.markdown
index 859adac0b23..46fb8379d41 100644
--- a/source/_docs/troubleshooting_general.markdown
+++ b/source/_docs/troubleshooting_general.markdown
@@ -32,7 +32,7 @@ Recovery mode loads a minimum set of integrations to allow troubleshooting the c
 
 You need to identify the issue in the configuration files and fix it there. The issue could be caused by something as simple as an invalid YAML file.
 
-- If you are running {% term "Home Assistant Operating System" %}, you can install an add-on such as VS code to edit the configuration file if needed.
+- If you are running {% term "Home Assistant Operating System" %}, you can install an add-on such as Studio Code Server to edit the configuration file if needed.
 - If you are still logged in, you can [edit your configuration](/docs/configuration/#editing-configurationyaml).
   - In the Home Assistant user interface, open the add-on you usually use and edit the configuration file.
 - Restart Home Assistant.