Update layout syntax in readme

README.md

@@ -129,7 +129,7 @@ like:
 		"tpl/layout"  //import tpl/layout namespace
 	)
 
-	var layout *layout.Base //Use layout package's **base struct** for layout
+	layout := layout.Base //Use layout package's **Base func** for layout
 	var user *models.User //1st template param
 	var blog *models.Blog //2nd template param
 }
@@ -176,11 +176,13 @@ The syntax for declaring layout is a bit tricky, in the example mentioned above:
 		"tpl/layout"
 	)
 
-	var layout *layout.Base //Use layout package's **base struct** for layout
+	layout := layout.Base //Use layout package's **base func** for layout
 }
 ```
 
-`"tpl/layout"` **is** a the layout package namespace, and the `layout` variable refers to `"layout.Base"` structure, which should be generated by `tpl/layout/base.gohtml`.
+`"tpl/layout"` **is** a the layout package namespace, and the `layout` variable refers to `"layout.Base"` func, which should be generated by `tpl/layout/base.gohtml`.
+
+> Must use `layout` as the variable name
 
 ### Package / Variable convention
 
@@ -220,6 +222,7 @@ It's just a usual gorazor template, but:
 * First param must be `var body string` (As it's always required, maybe we could remove it in future?)
 * All params **must be** string, each param is considered as a **section**, the variable name is the **section name**.
 * Under `layout` package, i.e. within "layout" folder.
+  * Optionally, use `isLayout := true` to declare a template as layout
 
 A template using such layout `tpl/index.gohtml` may look like:
 
@@ -229,7 +232,7 @@ A template using such layout `tpl/index.gohtml` may look like:
 		"tpl/layout"
 	)
 
-	var layout *layout.Base
+	layout := layout.Base
 }
 
 @section footer {
@@ -239,6 +242,18 @@ A template using such layout `tpl/index.gohtml` may look like:
 <h2>Welcome to homepage</h2>
 ```
 
+It's also possible to use import alias:
+
+```html
+@{
+	import (
+		share "tpl/layout"
+	)
+
+	layout := share.Base
+}
+```
+
 With the page, the page content will be treated as the `body` section in layout.
 
 The other section content need to be wrapped with