From e120931fcec3bfd7acd6b56ab26f21adec206850 Mon Sep 17 00:00:00 2001
From: ayeshanasir <43529436+ayeshanasir@users.noreply.github.com>
Date: Thu, 22 Aug 2019 01:16:25 -0400
Subject: [PATCH] Fixed a small typo.

---
 1-js/03-code-quality/01-debugging-chrome/article.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/1-js/03-code-quality/01-debugging-chrome/article.md b/1-js/03-code-quality/01-debugging-chrome/article.md
index 331319b6..c777ae69 100644
--- a/1-js/03-code-quality/01-debugging-chrome/article.md
+++ b/1-js/03-code-quality/01-debugging-chrome/article.md
@@ -2,7 +2,7 @@
 
 Before writing more complex code, let's talk about debugging.
 
-[Debugging](https://en.wikipedia.org/wiki/Debugging) is the process of finding and fixing errors within a script. All modern browsers and most other environments support debugging tools -- a special UI in developer tools that enable debugging much easier. It also allows to trace the code step by step to see what exactly is going on.
+[Debugging](https://en.wikipedia.org/wiki/Debugging) is the process of finding and fixing errors within a script. All modern browsers and most other environments support debugging tools -- a special UI in developer tools that makes debugging much easier. It also allows to trace the code step by step to see what exactly is going on.
 
 We'll be using Chrome here, because it has enough features, most other browsers have a similar process`.