Update 02-the-basics.md

sea · sea · commit 373591663e7d · 2014-01-18T13:18:34.000-08:00
note: "For this book, we will focus on using Chrome and its developer tools for two reasons: Chrome has a a set of versatile and powerful tools, and focusing on the tools of one browser helps keep the instructions simple." you say this yet two paragraphs away you tell the reader they should also look at Firefox! maybe reword that paragraph from "You should" to "It's also good to familiarize yourself with", etc.

Line 69, I changed from "We learned that", which doesn't make sense with line 70 ("We learned that: the javascript console". Reword?)
diff --git a/chapters/02-the-basics.md b/chapters/02-the-basics.md
@@ -55,21 +55,21 @@ Type this into the console:
 console.error('this is an error');
 ```
 
-That's an error! Note how it shows up in red. Look in the bottom right corner of the browser. You'll see a little red circle with an x in the middle, and a number on its right side. That's a helpful little indicator of errors in your javascript, and any time something is wonky with your code that red circle will show up.
+That's an error! Note how it shows up in red. Look in the bottom right corner of the browser. You'll see a little red circle with an x in the middle, and a number on its right side. That's a helpful little indicator of errors in your javascript, and any time something is wonky with your code, that red circle will show up.
 
 With most errors you'll also be able to see a line number from your javascript file, which will help you pinpoint the offending code. We'll get into errors and debugging in more detail later in the book.
 
 ## More developer tools
-The javascript console is just one of the tools available for web development inside of Chrome. For this book we will focus on using Chrome and its developer tools for two reasons: Chrome has a a set of versatile and powerful tools, and focusing on the tools of one browser helps keep the instructions simple.
+The javascript console is just one of the tools available for web development inside of Chrome. For this book, we will focus on using Chrome and its developer tools for two reasons: Chrome has a a set of versatile and powerful tools, and focusing on the tools of one browser helps keep the instructions simple.
 
 Check out the [Chrome Developer Tools documentation](https://developers.google.com/chrome-developer-tools/) to learn more about all that Chrome has to offer for developers working with javascript, html, and css.
 
 You should also familiarize yourself with the developer tools in Firefox. Check out the [Mozilla Developer Network documentation for the Firefox developer tools](https://developer.mozilla.org/en-US/docs/Tools).
 
-## Recap! We learned that:
+## Recap! We learned:
 - the javascript console and learned that we can type in javascript!
-- we can use code like `console.log()` and `console.error()` to print information to the console.
-- Chrome has a lot of useful tools, and later in the book we'll learn how they can help with experimenting with code, auditing the performance of our site, investigating the information sent between the browser and the server, and more.
+- that we can use code like `console.log()` and `console.error()` to print information to the console
+- that Chrome has a lot of useful tools (later in the book, we'll learn how they can help with experimenting with code, auditing the performance of our site, investigating the information sent between the browser and the server, and more!)
 
 
 
