From 897aad07f56edadd892db253935345e2cacde152 Mon Sep 17 00:00:00 2001 From: Hillary Fraley Date: Tue, 4 Oct 2016 15:02:27 -0400 Subject: [PATCH] Fixed a couple typos and format inconsistencies (#1112) --- source/developers/architecture.markdown | 16 +++++++++------- 1 file changed, 9 insertions(+), 7 deletions(-) diff --git a/source/developers/architecture.markdown b/source/developers/architecture.markdown index 5bebf0a0d30..70912917a7c 100644 --- a/source/developers/architecture.markdown +++ b/source/developers/architecture.markdown @@ -9,7 +9,9 @@ sharing: true footer: true --- -Before we dive into the Home Assistant architecture, it is important to get a clear overview of the home automation landscape as a whole. This will allow us to show how the different parts of Home Assistant fit in the picture. For a more lengthy discussion about what each part in this overview is responsible for, check out our blog. A tl;dr version of the blog: +Before we dive into the Home Assistant architecture, let's get a clear overview of the home automation landscape as a whole. This way, we can show how the different parts of Home Assistant fit into the picture. + +For more information about each part in this overview, check out our blog. Here's the tl;dr version of the blog: * Home Control is responsible for collecting information and controlling devices. * Home Automation triggers commands based on user configurations. @@ -20,15 +22,15 @@ Before we dive into the Home Assistant architecture, it is important to get a cl Home Automation landscape - Overview of the home automation landscape. + Overview of the home automation landscape

-The Home Assistant core is responsible for Home Control. It has four parts to make this possible: +The Home Assistant core is responsible for Home Control. Home Assistant has four parts to make this possible: - * The **Event Bus** facilitates the firing and listening of events. This is the beating heart of Home Assistant. - * The **State Machine** keeps track of the states of things. It fires a `state_changed` event when a state has been changed. - * The **Service Registry** listens on the event bus for `call_service` events and allows other code to register services. - * The **Timer** will send a `time_changed` event every 1 second on the event bus. + * **Event Bus**: facilitates the firing and listening of events--the beating heart of Home Assistant. + * **State Machine**: keeps track of the states of things and fires a `state_changed` event when a state has been changed. + * **Service Registry**: listens on the event bus for `call_service` events and allows other code to register services. + * **Timer**: sends a `time_changed` event every 1 second on the event bus.