From 34f47ae067e6ec5dedff415ee03d4016cd03a9c4 Mon Sep 17 00:00:00 2001 From: Dawid Nowak Date: Mon, 18 Dec 2023 08:29:42 +0100 Subject: [PATCH] splitting_configuration: fixed filename (#30363) for the explanation to be consistent with the example --- source/_docs/configuration/splitting_configuration.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_docs/configuration/splitting_configuration.markdown b/source/_docs/configuration/splitting_configuration.markdown index 2f3e7bd30c1..f5558c53bc7 100644 --- a/source/_docs/configuration/splitting_configuration.markdown +++ b/source/_docs/configuration/splitting_configuration.markdown @@ -29,7 +29,7 @@ homeassistant: Note that each line after `homeassistant:` is indented two (2) spaces. Since the configuration files in Home Assistant are based on the YAML language, indentation and spacing are important. Also note that seemingly strange entry under `customize:`. -`!include filename.yaml` is the statement that tells Home Assistant to insert the contents of `filename.yaml` at that point. This is how we are going to break a monolithic and hard to read file (when it gets big) into more manageable chunks. +`!include customize.yaml` is the statement that tells Home Assistant to insert the contents of `customize.yaml` at that point. This is how we are going to break a monolithic and hard to read file (when it gets big) into more manageable chunks. Now before we start splitting out the different components, let's look at the other integrations (in our example) that will stay in the base file: