From e6b28a38eca1b1fade65ae5cb5d2fce6037801a5 Mon Sep 17 00:00:00 2001 From: Ilya Kantor Date: Tue, 15 Jan 2019 15:29:41 +0300 Subject: [PATCH] fixes --- 1-js/03-code-quality/02-coding-style/article.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/1-js/03-code-quality/02-coding-style/article.md b/1-js/03-code-quality/02-coding-style/article.md index accc407c..290028a8 100644 --- a/1-js/03-code-quality/02-coding-style/article.md +++ b/1-js/03-code-quality/02-coding-style/article.md @@ -255,7 +255,7 @@ That's because when reading code, we first want to know *what it does*. If the c A style guide contains general rules about "how to write" code, e.g. which quotes to use, how many spaces to indent, where to put line breaks, etc. A lot of minor things. -When all members of a team use the same style guide the code tends looks uniform, regardless of which team member wrote it. +When all members of a team use the same style guide, the code looks uniform, regardless of which team member wrote it. Of course, a team can always write their own style guide. Most of the time though, there's no need to. There are many existing tried and true options to choose from, so adopting one of these is usually your best bet.