Fix markdown issue

docs/why.md

@@ -45,6 +45,7 @@ ASP.NET MVC covers most of the pain points with building HTML forms that were de
 ChameleonForms was created to leverage the advantages of ASP.NET MVC while bridging the gap of the deficiencies described above. It's also designed to provide a lot of nice functionality to help make form development *better*.
 
 ChameleonForms:
+
 * Provides a first-class templating model that allows you to **quickly and easily define new form templates and swap them out**
 * Encourages you to specify the structure of your form in a way that provides a lot of **consistency within and across your forms**
 * Encourages a **minimum of repetition** - most of the time you only need to specify the property of the field you are outputting and it will work out everything else (label, validation HTML, field type based on model metadata, etc.)
@@ -69,4 +70,4 @@ At that point you have two problems:
 When this happens this is a good indicator that whatever solution you are using goes too far. Ideally, forms libraries should accept that you can't cover all cases and make it easy to opt out of using the library in the middle of a form. As explained above, addressing this is a core design element of ChameleonForms.
 
 ## Display Templates
-One aspect that hasn't been covered, which is somewhat unique to ASP.NET MVC is Display Templates. This is one area that ChameleonForms doesn't (currently - [see the backlog on Trello](https://trello.com/b/fSuyhwNZ)) cover in any way. This is actually a deliberate decision (to deprioritise that functionality) because we generally find that Display Templates aren't very useful - particularly with the terseness of Razor. Generally you will want more flexibility than Display Templates provide. If you find Display Templates useful and use them extensively then ChameleonForms might not be the right library for you (but we'd love to hear about your usecase so [please submit an issue](https://github.com/MRCollective/ChameleonForms/issues)!).
+One aspect that hasn't been covered, which is somewhat unique to ASP.NET MVC is Display Templates. This is one area that ChameleonForms doesn't (currently - [see the backlog on Trello](https://trello.com/b/fSuyhwNZ)) cover in any way. This is actually a deliberate decision (to deprioritise that functionality) because we generally find that Display Templates aren't very useful - particularly with the terseness of Razor. Generally you will want more flexibility than Display Templates provide. If you find Display Templates useful and use them extensively then ChameleonForms might not be the right library for you (but we'd love to hear about your usecase so [please submit an issue](https://github.com/MRCollective/ChameleonForms/issues)!).