From fc14b5d413fa66f91ea7bb043a3b8f59f7ff6b14 Mon Sep 17 00:00:00 2001
From: c0ffeeca7 <38767475+c0ffeeca7@users.noreply.github.com>
Date: Mon, 26 May 2025 12:35:55 +0200
Subject: [PATCH] Secrets remove core specific steps (#39188)

---
 source/_docs/blueprint/selectors.markdown   |  5 +++--
 source/_docs/configuration/secrets.markdown | 12 ++----------
 2 files changed, 5 insertions(+), 12 deletions(-)

diff --git a/source/_docs/blueprint/selectors.markdown b/source/_docs/blueprint/selectors.markdown
index b6cef9cc50f..33a582dc92b 100644
--- a/source/_docs/blueprint/selectors.markdown
+++ b/source/_docs/blueprint/selectors.markdown
@@ -83,7 +83,7 @@ The output of this selector is a list of actions. For example:
 
 ## Add-on selector
 
-This can only be used on Home Assistant Operating System installation. For Home Assistant Container installations, an error will be displayed.
+This can only be used on a {% term "Home Assistant Operating System" %} installation. For {% term "Home Assistant Container" %} installations, an error will be displayed.
 
 The add-on selector allows the user to input an add-on slug.
 On the user interface, it will list all installed add-ons and use the slug of the
@@ -275,7 +275,8 @@ assist_pipeline:
 
 ## Backup location selector
 
-This can only be used on an installation with a Home Assistant Operating System. For {% term "Home Assistant Container" %} installations, an error
+This can only be used on an installation with a {% term "Home Assistant Operating System" %}. For {% term "Home Assistant Container" %} installations, an error
+
 will be displayed.
 
 The backup location selector shows a list of places a backup could go, depending
diff --git a/source/_docs/configuration/secrets.markdown b/source/_docs/configuration/secrets.markdown
index d7130f254df..25092080c1f 100644
--- a/source/_docs/configuration/secrets.markdown
+++ b/source/_docs/configuration/secrets.markdown
@@ -51,20 +51,12 @@ When you start splitting your configuration into multiple files, you might end u
 - A `secrets.yaml` located in the same folder as the {% term YAML %} file referencing the secret,
 - next, parent folders will be searched for a `secrets.yaml` file with the secret, stopping at the folder with the main {% term "`configuration.yaml`" %}.
 
-To see where secrets are being loaded from, you can either add an option to your `secrets.yaml` file or use the `check_config` script. The latter is only available for {% term "Home Assistant Core" %} installations given it's available through [`hass`](/docs/tools/hass/).
+To see where secrets are being loaded from, you can add an option to your `secrets.yaml` file.
 
-*Option 1*: Print where secrets are retrieved from to the Home Assistant log by adding the following to `secrets.yaml`:
+Print where secrets are retrieved from to the Home Assistant log by adding the following to `secrets.yaml`:
 
 ```yaml
 logger: debug
 ```
 
 This will not print the actual secret's value to the log.
-
-*Option 2*: For Home Assistant Core installations, you can also view where secrets are retrieved from and the contents of all `secrets.yaml` files using the [`check_config` script](/docs/tools/check_config/) from the command line:
-
-```bash
-hass --script check_config --secrets
-```
-
-This will print all your secrets.