Merge pull request #1 from Kurczok/patch-3

grammatical changes

Author: hadrysmateusz

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

@@ -1,12 +1,12 @@
 # Developer console
 
-A code is prone to errors. You are quite likely to have errors... Oh, what am I talking about? You are *absolutely* going to make errors, at least if you're a human, not a [robot](https://en.wikipedia.org/wiki/Bender_(Futurama)).
+Code is prone to errors. You are quite likely to have errors... Oh, what am I talking about? 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, because those browsers have the best developer tools. Other browsers also provide developer tools, sometimes with special features, but are usually playing "catching-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 "catching-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.
 
@@ -18,7 +18,7 @@ Open the page [bug.html](bug.html).
 
 There's an error in the JavaScript code on it. It's hidden from a regular visitor's eyes, so let's open developer tools to see it.
 
-Press the key `key:F12` or, if you're on Mac, then `key:Cmd+Opt+J`.
+Press `key:F12` or, if you're on Mac, then `key:Cmd+Opt+J`.
 
 The developer tools will open on the Console tab by default.
 
@@ -40,13 +40,13 @@ 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 you know how to use one of them (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 them (ypu can start with Chrome), you can easily switch to another.
 
 ## Safari
 
-Safari (Mac browser, not supported for Windows/Linux) is a little bit special here. We need to enable the "Develop menu" first.
+Safari (Mac browser, not supported by Windows/Linux) is a little bit special here. We need to enable the "Develop menu" first.
 
-Open Preferences and go to "Advanced" pane. There's a checkbox at the bottom of it:
+Open Preferences and go to "Advanced" pane. There's a checkbox at the bottom:
 
 ![safari](safari.png)