From c59eca32c0e51a370d96657a16c1a7096f75df6a Mon Sep 17 00:00:00 2001
From: hvolmer <5054691+hvolmer@users.noreply.github.com>
Date: Tue, 11 Feb 2020 19:16:50 -0700
Subject: [PATCH] Updated Essentials Architecture (markdown)

---
 Essentials-Architecture.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/Essentials-Architecture.md b/Essentials-Architecture.md
index c2120dc..be3c669 100644
--- a/Essentials-Architecture.md
+++ b/Essentials-Architecture.md
@@ -83,7 +83,7 @@ At startup, the configuration file is read, and a ReadyEvent is fired. Upon bein
 
 For example, a `DeviceConfig` object:
 
-```
+```chasrp
 namespace PepperDash.Essentials.Core.Config
 {
     public class DeviceConfig
@@ -123,7 +123,7 @@ This ordering ensures that all devices are at least present before building tie
 
 In each device/room step, a device factory process is called. We call subsequent device factory methods in the various libraries that make up Essentials until one of them returns a functional device.  This allows us to break up the factory process into individual libraries, and not have a huge master list of types and build procedures.  Here's part of the code:
 
-```
+```csharp
 // Try local factories first
 var newDev = DeviceFactory.GetDevice(devConf);