fixes

Author: iliakan

1-js/01-getting-started/2-code-editors/article.md

@@ -1,6 +1,6 @@
 # Code editors
 
-The code editor is the place where a programmer spends most his time. 
+A code editor is the place where a programmer spends most of his time. 
 
 There are two archetypes: IDE and lightweight editors. Many people feel comfortable choosing one tool of each type.
 
@@ -32,7 +32,7 @@ They are mainly used to instantly open and edit a file.
 
 The main difference between a "lightweight editor" and an "IDE" is that IDE works on a project-level, so it loads much more data on start, analyzes the project structure if needed and so on. A lightweight editor is much faster if we need only one file.
 
-In practice, lightweight editors may have a lot of plugins including directory-level syntax analyzers and autocompleters, so there's no strict border between a lightweight editor and an IDE. 
+In practice, lightweight editors may have a lot of plugins including directory-level syntax analyzers and autocompleters, so there's no strict border between a lightweight editor and an IDE.
 
 The following options deserve your attention:
 

1-js/01-getting-started/3-devtools/article.md

@@ -1,18 +1,12 @@
 # Developer console
 
-And the one more thing before we get down to coding.
-
 A code is error-prone. You are quite likely to have errors... Oh what I'm talking? You are *absolutely* going to make errors, at least if you're a human, not a [robot](https://en.wikipedia.org/wiki/Bender_(Futurama)).
 
 But in the browser, a user doesn't see the errors by default. So, if something goes wrong in the script, we won't see what's broken and can't fix it.
 
 To see errors and get a lot of other useful information about scripts, browsers have embedded "developer tools".
 
-**Most often developers lean towards Chrome or Firefox for the development.**
-
-Other browsers also provide developer tools, but are usually in a "catching-up" position, compared to Chrome/Firefox which are the best. 
-
-Sometimes, it may be required to switch to another browser, if a problem is browser-specific, but that's rare.
+Most often developers lean towards Chrome or Firefox for the development, because developer tools are best there. Other browsers also provide developer tools, sometimes with special features, but usually are in "catching-up" position. So most people have a "favorite" browser and switch to others if a problem is browser-specific.
 
 Developer tools are really powerful, there are many features. Here, for the start, we'll learn how to open them, look at errors and run JavaScript commands.
 
@@ -34,10 +28,10 @@ It looks somewhat like this:
 
 The exact look depends on your Chrome version. It changes from time to time, but should be similar.
 
-- Here we can see the red-colored error message. In this case the script contains a "lalala" command, which was put there just because it is unknown.
+- Here we can see the red-colored error message. In this case the script contains an unknown "lalala" command.
 - On the right, there is a clickable link to the source `bug.html:12` with the line number where the error has occured.
 
-Below the error message there is a blue `>` symbol. It marks a "command line" where we can type JavaScript commands and press enter to run them (`key:Shift+Enter` to input multiline commands).
+Below the error message there is a blue `>` symbol. It marks a "command line" where we can type JavaScript commands and press `key:Enter` to run them (`key:Shift+Enter` to input multiline commands).
 
 Now we can see errors and that's enough for the start. We'll be back to developer tools later and cover debugging more in-depth in the chapter <info:debugging-chrome>.
 
@@ -46,21 +40,21 @@ Now we can see errors and that's enough for the start. We'll be back to develope
 
 Most other browsers use `key:F12` to open developer tools.
 
-The look & feel of them is quite similar, once we know how to use one of them (can start with Chrome), can easily switch to another.
+The look & feel of them is quite similar. Once you know how to use one of them (can start with Chrome), you can easily switch to another.
 
 ## Safari
 
-Safari (if you use Mac, not Windows/Linux) is a little bit special here. We need to enable the "Develop menu" first.
+Safari (Mac browser, not supported for Windows/Linux) is a little bit special here. We need to enable the "Develop menu" first.
 
-There's a checkbox for that at the bottom of the "Advanced" pane of the preferences:
+Open Preferences and go to "Advanced" pane. There's a checkbox at the bottom of it:
 
 ![safari](safari.png)
 
-Now `key:Cmd+Opt+C` can toggle the console. Also note that the new top menu item has appeared with many useful options.
+Now `key:Cmd+Opt+C` can toggle the console. Also note that the new top menu item named "Develop" has appeared. It has many commands and options.
 
 ## Summary
 
-  - Developer tools allow us to see errors, run commands, examine variables and much more.
+- Developer tools allow us to see errors, run commands, examine variables and much more.
 - They can be opened with `key:F12` for most browsers under Windows. Chrome for Mac needs `key:Cmd+Opt+J`, Safari: `key:Cmd+Opt+C` (need to enable first).
 
-Now we have the environment ready. In the next section we get down to JavaScript.
+Now we have the environment ready. In the next section we get down to JavaScript.