feat(README): polish and add new Matrix chat link (#248)

Author: ar3s3ru

README.md

@@ -45,14 +45,36 @@
         <img alt="GitHub license"
         src="https://img.shields.io/github/license/eventually-rs/eventually-rs?style=flat-square">
     </a>
+    <!-- Matrix -->
+    <a href="https://matrix.to/#/#get-eventually:matrix.org">
+        <img alt="Matrix Chat"
+        src="https://img.shields.io/matrix/get-eventually:matrix.org?logo=matrix&style=flat-square">
+    </a>
 </div>
 
 <br />
 
 
 Collection of traits and other utilities to help you build your Event-sourced applications in Rust.
 
-> :warning: **version 0.5.0 is under active develoment**: Breaking changes are expected. If you are using `Eventually` as a git dependency you should use a pinned version.
+## Installation
+
+> ⚠️ **v0.5.0 is under active development**: Breaking changes are expected. If you are using `eventually` as a git dependency you should use a pinned version!
+
+Add `eventually` into your project dependencies:
+
+```toml
+[dependencies]
+eventually = { version = "0.5.0", features = ["full"], git = "https://github.com/get-eventually/eventually-rs" }
+```
+
+### Note on semantic versioning
+
+This library is **actively being developed**, and prior to `v1` release the following [Semantic versioning]()
+is being adopted:
+
+* Breaking changes are tagged with a new `MINOR` release
+* New features, patches and documentation are tagged with a new `PATCH` release
 
 ## What is Event Sourcing?
 
@@ -62,7 +84,7 @@ From [eventstore.com](https://eventstore.com/) introduction:
 
 >Event Sourcing is an architectural pattern that is gaining popularity as a method for building modern systems. Unlike traditional databases which only store and update the current state of data, event-sourced systems store all changes as an immutable series of events in the order that they occurred and current state is derived from that event log.
 
-## How does `eventually` support Event Sourcing?
+## How does `eventually-rs` support Event Sourcing?
 
 `eventually` exposes all the necessary abstraction to model your
 Domain Entities (in lingo, _Aggregates_) using Domain Events, and
@@ -73,40 +95,20 @@ For more information, [check out the crate documentation](https://docs.rs/eventu
 You can also take a look at the [`bank-accounting`](https://github.com/get-eventually/eventually-rs/tree/main/examples/bank-accounting) example,
 showcasing Event-sourced application for a generic (and simple) Bank Accounting bounded context.
 
-All other questions are more than welcome on our [Gitter chat](https://gitter.im/eventually-rs/community).
-
 ### Event Store backends
 
-`eventually` provides the necessary abstractions for modeling and interacting
+`eventually-rs` provides the necessary abstractions for modeling and interacting
 with an Event Store.
 
 These are the following officially-supported backend implementations:
-* [`eventually::inmemory::EventStore`](): simple inmemory Event Store implementation, using `std::collections::HashMap`,
-* [`eventually-postgres`](./eventually-postgres): Event Store implementation for PostgreSQL databases,
-* [`eventually-redis`](./eventually-redis): Event Store implementation for Redis stores.
-
-## Installation
-
-Add `eventually` into your project dependencies:
-
-```toml
-[dependencies]
-eventually = { version = "0.4.0", features = ["full"] }
-```
-
-### Note on semantic versioning
-
-This library is **actively being developed**, and prior to `v1` release the following [Semantic versioning]()
-is being adopted:
-
-* Breaking changes are tagged with a new `MINOR` release
-* New features, patches and documentation are tagged with a new `PATCH` release
+* [`eventually::event::store::InMemory`](./eventually/src/event/store.rs): simple inmemory Event Store implementation, using `std::collections::HashMap`,
+* [`eventually-postgres`](./eventually-postgres): Event Store and Aggregate Root Repository implementations for PostgreSQL databases.
 
 ## Contributing
 
-You want to contribute to `eventually` but you don't know where to start?
+You want to contribute to `eventually-rs` but you don't know where to start?
 
-First of all, thank you for considering contributing :heart:
+First of all, thank you for considering contributing ❤️
 
 You can head over our [`CONTRIBUTING`](./CONTRIBUTING.md) section to know
 how to contribute to the project, and — in case you don't have a clear idea what