From 722a00b4ec566724eb90aaed91e7b0e511690f2e Mon Sep 17 00:00:00 2001 From: Jay Zhang Date: Mon, 7 Oct 2019 14:36:14 +0800 Subject: [PATCH] docs: fix grammar --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index d4bec86..841c4cb 100644 --- a/README.md +++ b/README.md @@ -2,7 +2,7 @@ This is my understanding of how to structure `Go` project layout. The most important part is how to organize your `Go` code into packages. ## Motivation -A good project layout will make your source code **easier to understand, easier to test, and eaiser to maintain**. +A good project layout will make your source code **easy to understand, easy to test, and easy to maintain**. [Kat Zien](https://github.com/katzien/) has a very good summary([Slides](https://github.com/katzien/talks/tree/master/how-do-you-structure-your-apps/gopherconuk-2018-08-03)) for this, so I'd like to refer it directly as below: ### Questions, decisions