Merge pull request #594 from gratiaa/patch-4

[PR] Fix typos

Author: iliakan

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

@@ -4,11 +4,11 @@ Code is prone to errors. You are quite likely to make errors... Oh, what am I ta
 
 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".
+To see errors and get a lot of other useful information about scripts, "developer tools" have been embedded in browsers.
 
-Most often developers lean towards Chrome or Firefox for development, because those browsers have the best developer tools. Other browsers also provide developer tools, sometimes with special features, but are usually playing "catch-up" to Chrome or Firefox. So most people have a "favorite" browser and switch to others if a problem is browser-specific.
+Most often developers lean towards Chrome or Firefox for development because those browsers have the best developer tools. Other browsers also provide developer tools, sometimes with special features, but are usually playing "catch-up" to Chrome or Firefox. 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. To start, we'll learn how to open them, look at errors and run JavaScript commands.
+Developer tools are potent; there are many features. To start, we'll learn how to open them, look at errors and run JavaScript commands.
 
 ## Google Chrome
 
@@ -24,21 +24,21 @@ It looks somewhat like this:
 
 ![chrome](chrome.png)
 
-The exact look of developer tools depends on your version of Chrome. It changes from time to time, but should be similar.
+The exact look of developer tools depends on your version of Chrome. 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 an unknown "lalala" command.
+- 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 occurred.
 
-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 multi-line commands).
+Below the error message, there is a blue `>` symbol. It marks a "command line" where we can type JavaScript commands. Press `key:Enter` to run them (`key:Shift+Enter` to input multi-line 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>.
+Now we can see errors, and that's enough for a start. We'll be back to developer tools later and cover debugging more in-depth in the chapter <info:debugging-chrome>.
 
 
-## Firefox, Edge and others
+## Firefox, Edge, and others
 
 Most other browsers use `key:F12` to open developer tools.
 
-The look & feel of them is quite similar. Once you know how to use one of them (you can start with Chrome), you can easily switch to another.
+The look & feel of them is quite similar. Once you know how to use one of those tools (you can start with Chrome), you can easily switch to another.
 
 ## Safari
 
@@ -48,11 +48,11 @@ Open Preferences and go to "Advanced" pane. There's a checkbox at the bottom:
 
 ![safari](safari.png)
 
-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.
+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.
 - 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'll get down to JavaScript.
+Now we have the environment ready. In the next section, we'll get down to JavaScript.