From 09a32d3c5ca9b7f85fc4cd281a98c04901a80c26 Mon Sep 17 00:00:00 2001
From: c0ffeeca7 <38767475+c0ffeeca7@users.noreply.github.com>
Date: Mon, 26 May 2025 14:02:14 +0200
Subject: [PATCH] Remove links to common tasks for Core and Supervisor (#39238)

---
 source/_docs/configuration/splitting_configuration.markdown | 2 --
 source/_docs/configuration/troubleshooting.markdown         | 2 --
 source/_faq/component.markdown                              | 4 +---
 3 files changed, 1 insertion(+), 7 deletions(-)

diff --git a/source/_docs/configuration/splitting_configuration.markdown b/source/_docs/configuration/splitting_configuration.markdown
index 55ddb8a7aa8..99d4a507abf 100644
--- a/source/_docs/configuration/splitting_configuration.markdown
+++ b/source/_docs/configuration/splitting_configuration.markdown
@@ -229,8 +229,6 @@ If you have many configuration files, Home Assistant provides a CLI that allows
 
 - [Operating System](/common-tasks/os/#configuration-check)
 - [Container](/common-tasks/container/#configuration-check)
-- [Core](/common-tasks/core/#configuration-check)
-- [Supervised](/common-tasks/supervised/#configuration-check)
 
 ## Advanced usage
 
diff --git a/source/_docs/configuration/troubleshooting.markdown b/source/_docs/configuration/troubleshooting.markdown
index 30a4f7a7b0b..41107da42e7 100644
--- a/source/_docs/configuration/troubleshooting.markdown
+++ b/source/_docs/configuration/troubleshooting.markdown
@@ -26,8 +26,6 @@ One of the most common problems with Home Assistant is an invalid {% term "`conf
 - Home Assistant provides a CLI that allows you to see how it interprets them, each installation type has its own section in the common-tasks about this:
   - [Operating System](/common-tasks/os/#configuration-check)
   - [Container](/common-tasks/container/#configuration-check)
-  - [Core](/common-tasks/core/#configuration-check)
-  - [Supervised](/common-tasks/supervised/#configuration-check)
 
 - The configuration files, including {% term "`configuration.yaml`" %} must be UTF-8 encoded. If you see error like `'utf-8' codec can't decode byte`, edit the offending configuration and re-save it as UTF-8.
 - You can verify your configuration's {% term YAML %} structure using [this online YAML parser](https://yaml-online-parser.appspot.com/) or [YAML Validator](https://codebeautify.org/yaml-validator/).
diff --git a/source/_faq/component.markdown b/source/_faq/component.markdown
index 0c0dd67b607..4b5617563d0 100644
--- a/source/_faq/component.markdown
+++ b/source/_faq/component.markdown
@@ -9,6 +9,4 @@ When an integration does not show up, many different things can be the case. Bef
 If you have incorrect entries in your configuration files you can use the CLI script to check your configuration, each installation type has its own section in the common-tasks about this:
 
 - [Operating System](/common-tasks/os/#configuration-check)
-- [Container](/common-tasks/container/#configuration-check)
-- [Core](/common-tasks/core/#configuration-check)
-- [Supervised](/common-tasks/supervised/#configuration-check)
\ No newline at end of file
+- [Container](/common-tasks/container/#configuration-check)
\ No newline at end of file