update readme

Author: Zakk Fleischmann

readme.md

@@ -1,21 +1,12 @@
 # JavaScript Checkpoint
-Fork and clone this repository and complete the three sections below. Make at least one commit for each section. When finished, push your commits to your forked repository and submit a Pull Request back to the original repository.
 
-**IMPORTANT**: Make sure to use the `var` keyword for **ALL** variable declarations (for testing purposes). **DO NOT** use `const` or `let`.
-
-## Fundamentals
-Follow the prompts and write your code in `fundamentals.js`
+Fork and clone this repository and complete the three sections below. Make at least one commit for each section. When you finish, push your commits to your forked repository. Wait to make your Pull Request until the end of the hour.
 
-## Higher-Order Functions
-Follow the prompts and write your code in `hof.js`
-
-
-## OOJS
-Follow the prompts and write your code in `oojs.js`
+**IMPORTANT**: Make sure to use the `var` keyword for **ALL** variable declarations (for testing purposes). **DO NOT** use `const` or `let`.
 
 ## Pro Tip: Test Your Code
 
-You should first test your code's functionality in the browser console via the included `index.html` file.  
+You should first test your code's functionality in the browser console with the included `index.html` file.
 
 Once you think your code is correct, you can run the tests that will evaluate your solutions to double-check them.
 
@@ -30,3 +21,15 @@ Then call the test runner each time you want to check your code...
 ```bash
  $ npm test
 ```
+
+This will execute a set of automated tests to check that your code is fulfilling each prompt.
+
+## Fundamentals
+Follow the prompts and write your code in `fundamentals.js`
+
+## Higher-Order Functions
+Follow the prompts and write your code in `hof.js`
+
+## OOJS
+Follow the prompts and write your code in `oojs.js`
+