increment version

README.md

@@ -4,18 +4,18 @@
 
 Supports `Event` and `Snapshot` storage providers like EventStore/Redis or SQL Server. Built with dependency injection in mind and seamlessly integrates with AspNetCore.
 
-## Give a star :star: if you appreciate the effort
+### Give a star :star: if you appreciate the effort
 
 ## What is Event Sourcing?
 
 > Use an append-only store to record the full series of events that describe actions taken on data in a domain, rather than storing just the current state.
 
 Start here [https://dasith.me/2016/12/02/event-sourcing-examined-part-1-of-3/](https://dasith.me/2016/12/02/event-sourcing-examined-part-1-of-3/)
 
-## What does NEventLite solve? :goal_net:
+## :goal_net: What does NEventLite solve?
 NEventLite makes it easier to implement the event sourcing pattern in your .NET project. The library is opinionated and introduces some patterns to manage the life cycle of your [Aggregates](https://martinfowler.com/bliki/DDD_Aggregate.html) in an event sourced system. It will manage Creating, Loading, Mutating and Persisting Aggregates and Events.
 
-## What doesn't it solve? :warning:
+## :warning: What doesn't it solve?
 
 NEventLite is **not a framework** that manages your application end to end. It doesn't enforce ports and adapters pattern or any of the application level concerns. The aim is to do one thing (Manage aggregate lifecycle) and do that well. If you need to implement command and event handlers you can have a look at something like [SimpleMediator](https://github.com/dasiths/SimpleMediator) or [Brighter](https://github.com/BrighterCommand/Brighter) and NEventLite will complement them nicely.
 

appveyor.yml

@@ -1,4 +1,4 @@
-version: 2.0.{build}
+version: 2.1.{build}
 pull_requests:
   do_not_increment_build_number: true
 branches: