From 836137488d3a7250dfa6773bfb63551cb8e61a9e Mon Sep 17 00:00:00 2001 From: Brent Guffens Date: Fri, 19 Jan 2018 13:59:05 +0100 Subject: [PATCH] Curly braces section improvement --- 1-js/03-code-quality/02-coding-style/article.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) 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 2ea6fb7b95..c05f459c50 100644 --- a/1-js/03-code-quality/02-coding-style/article.md +++ b/1-js/03-code-quality/02-coding-style/article.md @@ -42,9 +42,9 @@ Now let's discuss the rules and reasons for them in detail. Nothing is "carved in stone" here. Everything is optional and can be changed: these are coding rules, not religious dogmas. -### Figure brackets +### Curly braces -In most JavaScript projects figure brackets are written on the same line, not on the new line. A so-called "egyptian" style. There's also a space before an opening bracket. +In most JavaScript projects curly braces are written on the same line as the corresponding keyword, not on the new line, a so-called "Egyptian" style. There's also a space before an opening bracket. Like this: