From 9df90afdd9617b1419fc1cd19a34f39d911a6e46 Mon Sep 17 00:00:00 2001
From: Nicolas St-Amour <stamoun@gmail.com>
Date: Wed, 16 Jan 2019 07:59:20 -0500
Subject: [PATCH] docs(coding-convention): if-statements examples not
 respecting coding convention (#6786)

---
 CodingConvention.md | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/CodingConvention.md b/CodingConvention.md
index 80f1e0127..826e49bd6 100644
--- a/CodingConvention.md
+++ b/CodingConvention.md
@@ -279,7 +279,7 @@ if (a) return "winning";
 
 ```TypeScript
 
-if(condition) {
+if (condition) {
     console.log("winning");
 }
 
@@ -293,15 +293,15 @@ if (!condition) {
 
 ```TypeScript
 
-if(condition === true) {
+if (condition === true) {
     console.log("losing");
 }
 
-if(condition !== true) {
+if (condition !== true) {
     console.log("losing");
 }
 
-if(condition !== false) {
+if (condition !== false) {
     console.log("losing");
 }
 
@@ -314,7 +314,7 @@ Do not use the **Yoda Conditions** when writing boolean expressions:
 
 ```TypeScript
 let num;
-if(num >= 0) {
+if (num >= 0) {
     console.log("winning");
 }
 ```
@@ -323,14 +323,14 @@ if(num >= 0) {
 
 ```TypeScript
 let num;
-if(0 <= num) {
+if (0 <= num) {
     console.log("losing");
 }
 ```
 
 **NOTE** It is OK to use constants on the left when comparing for a range.
 ```TypeScript
-if(0 <= num && num <= 100) {
+if (0 <= num && num <= 100) {
     console.log("winning");
 }
 ```