From 01a741cfe7197de8330b44f1e64b095fdc0c6fa9 Mon Sep 17 00:00:00 2001
From: Yuta Azumi <37298463+YA21@users.noreply.github.com>
Date: Sat, 23 Jan 2021 15:52:32 +0900
Subject: [PATCH] Update thincomponents.japanese.md

---
 sections/projectstructre/thincomponents.japanese.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/sections/projectstructre/thincomponents.japanese.md b/sections/projectstructre/thincomponents.japanese.md
index 72671a23..7d5535b6 100644
--- a/sections/projectstructre/thincomponents.japanese.md
+++ b/sections/projectstructre/thincomponents.japanese.md
@@ -8,9 +8,9 @@ For medium sized apps and above, monoliths are really bad - one big software wit
 
 <br/><br/>
 
-### ブログ Quote: "Scaling requires scaling of the entire application"
+### Blog Quote: "Scaling requires scaling of the entire application"
 
- From the ブログ MartinFowler.com
+ From the blog MartinFowler.com
 
  > Monolithic applications can be successful, but increasingly people are feeling frustrations with them - especially as more applications are being deployed to the cloud. Change cycles are tied together - a change made to a small part of the application requires the entire monolith to be rebuilt and deployed. Over time it's often hard to keep a good modular structure, making it harder to keep changes that ought to only affect one module within that module. Scaling requires scaling of the entire application rather than parts of it that require greater resource.