docs(readme,blog): fix markdown linting errors

Author: trollixx

README.md

@@ -1,16 +1,21 @@
-# zealdocs.github.io
-https://zealdocs.org/: web documentation for [Zeal, an offline documentation browser][zeal].
+# zealdocs.github.io / zealdocs.org
+
+This repository contains source code the [Zeal][zeal] homepage.
 
 ## Development
+
 To build this static site, you need the following dependencies:
+
 - `jekyll` (`v3.1.6` from Ubuntu 18.04 works correctly)
 
 To perform a one-off build, run:
+
 ```sh
 jekyll build
 ```
 
 To build any time a source code file changes and locally host the results at `http://127.0.0.1:4000/`, run:
+
 ```sh
 jekyll serve
 ```

_posts/2015-05-01-post-0.1-release-thoughts.md

@@ -11,11 +11,11 @@ I've instantly fell in love in Dash's quick search functionality which allows ea
 
 While I don't really spend much time on developing Zeal nowadays, all the hard work is mostly done by [@trollixx](https://github.com/trollixx), but I try to support him when I can, and we talk a lot about potential long term goals for Zeal. Some of possibilities from the top of my head:
 
- - Tons of new features to implement, like [full text search](https://github.com/zealdocs/zeal/issues/280), [docsets versioning](https://github.com/zealdocs/zeal/issues/208), [autogenerated docs](https://github.com/zealdocs/zeal/issues/143), [support for Dash's user contributed docs](https://github.com/zealdocs/zeal/issues/170), and more.
- - Spend more time on community, which could involve Twitter posts, writing blog with status updates and release plans, improving the website, etc.
- - Possibly derive some business model which would allow funding Zeal's development - note there was *no* money involved in Zeal's development yet! The ideas include supporting software businesses' documentation needs, or selling books from Zeal's UI... However, the plan is to always keep Zeal an open source project.
- - Build a backend servers infrastructure for things like cross-device settings synchronization, crash reporting, history, statistics.
- - Create a community of developers where everyone can contribute to documentation and help others, a bit like StackExchange, but more centered on documentation.
+- Tons of new features to implement, like [full text search](https://github.com/zealdocs/zeal/issues/280), [docsets versioning](https://github.com/zealdocs/zeal/issues/208), [autogenerated docs](https://github.com/zealdocs/zeal/issues/143), [support for Dash's user contributed docs](https://github.com/zealdocs/zeal/issues/170), and more.
+- Spend more time on community, which could involve Twitter posts, writing blog with status updates and release plans, improving the website, etc.
+- Possibly derive some business model which would allow funding Zeal's development - note there was *no* money involved in Zeal's development yet! The ideas include supporting software businesses' documentation needs, or selling books from Zeal's UI... However, the plan is to always keep Zeal an open source project.
+- Build a backend servers infrastructure for things like cross-device settings synchronization, crash reporting, history, statistics.
+- Create a community of developers where everyone can contribute to documentation and help others, a bit like StackExchange, but more centered on documentation.
 
 This is all obviously very far-fetched, and requires lots of effort to implement even part of the ideas, but I think it's a very exciting project to take part in!