From d326b7c4b5ceed9c47991b6b129d545730ab97a7 Mon Sep 17 00:00:00 2001
From: Meysam Hadeli <35596795+meysamhadeli@users.noreply.github.com>
Date: Sat, 18 Jun 2022 01:38:25 +0430
Subject: [PATCH] Update README.md

---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 4a85f70..2e6541d 100644
--- a/README.md
+++ b/README.md
@@ -27,7 +27,7 @@ Booking Microservices is a Sample application for booking ticket. This applicati
 - Correct `separation of bounded contexts` for each microservice.
 - Communication between bounded contexts through asynchronous `MessageBus` and `events`.
 - Communication internally between our microservices with `gRPC` synchronously.
-- Simple `CQRS` implementation and Event Driven Architecture with using `SqlServer` in `write side` and `MongoDB` in `read side`. I use an `internal processor` for `syncing read side and write` side without event sourcing. In booking microservice, I also use `event store` to store all historical state of aggregate.
+- Simple `CQRS` implementation and Event Driven Architecture with using `SqlServer` in `write side` and `MongoDB` in `read side`. I use an `internal processor` for syncing `read side` and `write side` without event sourcing. In booking microservice, I also use `event store` to store all historical state of aggregate.
 - Using `Inbox Pattern` for guaranty message Idempotency for receiver microservice and `Exactly-once Delivery pattern` and using `Outbox Pattern` for ensuring about any message `lost and At-Least one Delivery` rule.
 - Implementing various types of testing like `Unit Testing`, `Integration Testing`.
 - Using `Health Check` for reporting the health of app infrastructure components.