From ee930678cd5d62b2c72e9711d60257bfc111447f Mon Sep 17 00:00:00 2001
From: Hardik Sharma <44233098+shardic1@users.noreply.github.com>
Date: Fri, 21 Dec 2018 15:40:20 +0530
Subject: [PATCH] Edited some typos (#26118)

---
 guide/english/cplusplus/clean-code-guidelines/index.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/guide/english/cplusplus/clean-code-guidelines/index.md b/guide/english/cplusplus/clean-code-guidelines/index.md
index 2fe6fbfb67..d3bfce176a 100644
--- a/guide/english/cplusplus/clean-code-guidelines/index.md
+++ b/guide/english/cplusplus/clean-code-guidelines/index.md
@@ -34,15 +34,17 @@ int cucumber; // global variable "cucumber"
 
 ## Using goto, continue, etc.
 
+
 This is a usual discussion among programmers, just like global variables, these types of statements are usually considered bad practice.
 
 They are considered bad because they lead to ["spaghetti code"](https://en.wikipedia.org/wiki/Spaghetti_code). When we program we want a
+
 linear flow, when using those statements the flow is modified and lead to a "twisted and tangled" flow.
 
 Goto was used in the past when while, for, if functions, however, with the introduction of those structured programming was created.
 In general avoid using goto unless you are sure it will make your code cleaner and easier to read. An example might be using it in nested loops.
 
-The usage of break and continue are practically the same. Use them in switches and try to make functions with an only purpose so you only have one exit point.
+The usage of break and continue are practically the same. Use them in switches and try to make functions with the only purpose so you only have one exit point.
 
 ![img](https://imgs.xkcd.com/comics/goto.png)