diff --git a/source/_posts/2015-02-28-home-assistant-migrating-to-yaml.markdown b/source/_posts/2015-02-28-home-assistant-migrating-to-yaml.markdown
index fdc468a2812..d2e5fa1ff38 100644
--- a/source/_posts/2015-02-28-home-assistant-migrating-to-yaml.markdown
+++ b/source/_posts/2015-02-28-home-assistant-migrating-to-yaml.markdown
@@ -2,8 +2,8 @@
 layout: post
 title: "Home Assistant moving to YAML"
 description: "Configuration will now be more flexible"
-date: 2015-02-28 20:38:00 +0100
-date_formatted: February 28, 2015
+date: 2015-03-01 20:38:00 +0100
+date_formatted: March 1, 2015
 author: "Theodor Lindquist"
 comments: true
 ---
@@ -13,6 +13,6 @@ YAML allows the use of lists, which should make the configuration file a bit mor
 
 The new file is named configuration.yaml and if it can't be found in your config directory, Home Assistant will instead try to find the old configuration file, home-assistant.conf.
 
-The home-assistant.conf.example has been replaced with an updated configuration.yaml.example.
+The home-assistant.conf.example has been replaced with an updated [configuration.yaml.example](https://github.com/balloob/home-assistant/blob/dev/config/configuration.yaml.example).
 
-Users of Home Assistant should migrate as the old configuration format will be depicted.
+Users of Home Assistant should migrate as the old configuration format is deprecated.