From baf954931ef90b124fefc65b8ed60ac6a4549c0b Mon Sep 17 00:00:00 2001
From: Neshar89 <37742994+Neshar89@users.noreply.github.com>
Date: Wed, 28 Nov 2018 13:56:23 +0100
Subject: [PATCH] Added Colon to Examples (#25152)

---
 guide/english/agile/code-smells/index.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/guide/english/agile/code-smells/index.md b/guide/english/agile/code-smells/index.md
index 8e63c844d5..0517bb9ca1 100644
--- a/guide/english/agile/code-smells/index.md
+++ b/guide/english/agile/code-smells/index.md
@@ -7,7 +7,7 @@ A Code Smell in computer programming is a surface indication that there might be
 
 It is important to understand that smelly code works, but is not of good quality.
 
-#### Examples
+#### Examples:
 1. Duplicated code - Blocks of code that have been replicated across the code base. This may indicate that you need to generalize the code into a function and call it in two places, or it may be that the way the code works in one place is completely unrelated to the way it works in another place, despite having been copied.
 2. Large classes - Classes having too many lines of code. This may indicate that the class is trying to do too many things, and needs to be broken up into smaller classes.
 3. [Magic numbers](https://en.wikipedia.org/wiki/Magic_number_(programming)) - Variables (or `if` statements) scattered in the code that hold numeric values with no apparent meaning.