From 1ee342d83b3c32c05de3732246e745f560b3b779 Mon Sep 17 00:00:00 2001 From: Dan Atkinson Date: Wed, 14 Mar 2012 14:58:12 +0000 Subject: [PATCH] * Seperated 'Howto' into 'How to'. * Added periods to the second list as the first item has them. I guess I'm anally retentive like that. :) --- README.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index 982002c8..d8e468e3 100644 --- a/README.md +++ b/README.md @@ -11,10 +11,10 @@ Liquid is a template engine which was written with very specific requirements: ## Why you should use Liquid * You want to allow your users to edit the appearance of your application but don't want them to run **insecure code on your server**. -* You want to render templates directly from the database -* You like smarty (PHP) style template engines -* You need a template engine which does HTML just as well as emails -* You don't like the markup of your current templating engine +* You want to render templates directly from the database. +* You like smarty (PHP) style template engines. +* You need a template engine which does HTML just as well as emails. +* You don't like the markup of your current templating engine. ## What does it look like? @@ -31,7 +31,7 @@ Liquid is a template engine which was written with very specific requirements: ``` -## Howto use Liquid +## How to use Liquid Liquid supports a very simple API based around the Liquid::Template class. For standard use you can just pass it the content of a file and call render with a parameters hash.