From d42dd3babdf1bdc09a167e7b79540c7e28b8a27c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Jan=20Kucha=C5=99?= <honza.kuchar@grifart.cz>
Date: Tue, 6 Aug 2019 14:37:05 +0200
Subject: [PATCH] Update README.md

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

diff --git a/README.md b/README.md
index f160781..772b7d7 100644
--- a/README.md
+++ b/README.md
@@ -16,7 +16,7 @@ From architectonical perspective it is equavalent to microservices approach. The
 
 Technically you save tons of hours of maintainace cost of managing microservices. Because there is still one app, but with many independent modules. They have clear boundaries and explicitly defined dependencies. And when you break this boundary, you get an exception. 
 
-So if needed you can easily turn already defined modules into microservices later. Only thig that is missing there is serialization & networking stack. This can be easily solved by adding RPC layer between modules. 
+So if needed you can easily turn already defined modules into microservices later. Only part that is missing here is a serialization & networking stack. This can be easily solved by adding RPC layer between modules that are extracted into microservices.
 
 
 **More resources:**
-- 
GitLab