Update README [ci skip]

Author: n-rodriguez

README.md

@@ -672,7 +672,7 @@ In the end, it's up to the developer which model(s), scope(s), relationship(s)
 (or else) to employ inside the datatable class to retrieve records from the
 database.
 
-## Pro Tips
+## ProTips™
 
 ### Create a master parent class
 

doc/migrate.md

@@ -12,6 +12,8 @@ class PostDatatable < ApplicationDatatable
 end
 ```
 
+**Note :** This is now in the [ProTips™](https://github.com/jbox-web/ajax-datatables-rails#protips) section of the documentation.
+
 2) To mitigate the second change (The `view_context` is no longer injected in Datatables)
 
 Update the `ApplicationDatatable` class :
@@ -30,9 +32,20 @@ end
 and update your controllers :
 
 ```ruby
+# before
+respond_to do |format|
+  format.json { render json: UserDatatable.new(view_context) }
+end
+
+# after
 respond_to do |format|
   format.json { render json: UserDatatable.new(params, view_context: view_context) }
 end
+
+# if you need to inject some options
+respond_to do |format|
+  format.json { render json: UserDatatable.new(params, view_context: view_context, my: 'options') }
+end
 ```
 
 This way, you can still use `def_delegators` in your datatables [as in the documentation](https://github.com/jbox-web/ajax-datatables-rails#using-view-helpers).