README.md in access-granted-1.0.2 vs README.md in access-granted-1.0.3

@@ -46,10 +46,12 @@
 Roles are defined using blocks (or by passing custom classes to keep things tidy).
 
 **Order of the roles is VERY important**, because they are being traversed in the top-to-bottom order.
 At the top you must have an admin or other important role giving the user top permissions, and as you go down you define less-privileged roles.
 
+**I recommend starting your adventure by reading my [blog post about AccessGranted](http://blog.chaps.io/2015/11/13/role-based-authorization-in-rails.html), where I demonstrate its abilities on a real life example.**
+
 ### 1. Defining access policy
 
 Let's start with a complete example of what can be achieved:
 
 ```ruby
@@ -222,10 +224,10 @@
 #### Checking permissions in views
 
 Usually you don't want to show "Create" buttons for people who can't create something.
 You can hide any part of the page from users without permissions like this:
 
-```html
+```erb
 # app/views/categories/index.html.erb
 
 <% if can? :create, Category %>
   <%= link_to "Create new category", new_category_path %>
 <% end %>