From 13e3f6c9cb72a04d1359bf572dc924f150ce70c9 Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Fri, 22 Jul 2016 15:20:59 +0200 Subject: [PATCH] Minor update --- source/_topics/splitting_configuration.markdown | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source/_topics/splitting_configuration.markdown b/source/_topics/splitting_configuration.markdown index 7b613d780c5..91cb7b823bc 100644 --- a/source/_topics/splitting_configuration.markdown +++ b/source/_topics/splitting_configuration.markdown @@ -22,7 +22,7 @@ In this lighter version we will still need what could be called the core snippet ```yaml homeassistant: # Name of the location where Home Assistant is running - name: My Hass Instance + name: My Home Assistant Instance # Location required to calculate the time the sun rises and sets latitude: 37 longitude: -121 @@ -69,7 +69,7 @@ As with the core snippet, indentation makes a difference. The component headers While some of these components can technically be moved to a separate file they are so small or "one off's" where splitting them off is superfluous. Also, you'll notice the # symbol (hash/pound). This represents a "comment" as far as the commands are interpreted. Put another way, any line prefixed with a `#` will be ignored. This makes breaking up files for human readability really convenient, not to mention turning off features while leaving the entry intact. (Look at the `zigbee:` entry above and the b entry further down) -Now, lets assume that a blank file has been created in the hass configuration directory for each of the following: +Now, lets assume that a blank file has been created in the Home Assistant configuration directory for each of the following: ```text automation.yaml