From ab20ddd9ab453b106acf492ad951fefb78c45c7d Mon Sep 17 00:00:00 2001 From: Ilya Kantor Date: Wed, 7 Aug 2019 22:37:38 +0300 Subject: [PATCH] minor --- 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 586209b5..562ceeee 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 script that prevent correct operation of application. 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 enable 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`.