anchor.diff:  
   == Gist
   
  -Lot of developers use gist to store some snippets of their code, you can now use the gist macro to integrate those snippets in your post.
  +Developers use gist to store code snippets, and with {release} you can now use the gist macro to integrate those snippets in your post.
   
  -For example with the gist https://gist.github.com/anthonny/7786310 the usage will be:
  +For example with the gist https://gist.github.com/anthonny/7786310 the usage is as follows:
   
   image::https://cloud.githubusercontent.com/assets/2006548/16184313/bf71edac-36bb-11e6-8acc-bcc779964fbc.png[]
   
  -
   == Editor Validation for Blog Posts
   
  -In versions prior to {release}, if you didn't have a level 1 heading starting your blog post, you were not able to save your blog post. The error that displayed as a result of this was not clear, which caused frustration for some users.
  +In versions prior to {release}, if you didn't have a Level 1 heading starting your blog post, you were not able to save your blog post. The error that displayed as a result of this was not clear, which caused frustration for some users.
   
  -In {release}, the editor now has basic validation built into the editor, where if you don't start your blog with a Level 1 heading, there are no Preview or Save buttons in the editor. This is a visual clue to you to check your blog structure. 
  +In {release}, the editor now has basic validation built-in.
  +If you don't start your blog with a Level 1 heading, there are no Preview or Save buttons in the editor. This is a visual clue to check your blog structure. 
   
   If you want some tips on writing successful blog posts with HubPress, check out the _Writers' Guide_ in your repository.
   
  
positive.code: 
  Then you have to create a pull request with the listed changes and merge it.
  
  THe last action is to log in your HubPress administration, go to the *Settings* page and *Save*, it will rebuild all your blog with the last changes. And voilà!
  
  == Themes
  
  
negative.code: 
  What we noticed is that the theme folders used a mixture of upper and lower case, which made it tricky to set the theme correctly in the Admin console.
  
  In {release} *all theme names have been changed to lowercase*. 
  This is breaking change, and you will need to check that the theme you've chosen in the Settings are lowercase.
  
  Refer to the folder names in the `/themes` folder in your repository, or in the `Administration.adoc` Admin Guide. 
  
  