Fixed typos.

Author: alekdavis

README.md

@@ -5,7 +5,7 @@ This repo holds the [utils](utils.js) JavaScript class that can simplify and red
 The `utils` library is a simple JavaScript object that, when included in a collection folder's pre-request script, will be available to all scripts called after it. The object exposes various functions intended to make Postman tests shorter, simpler and more consistent.
 
 ## Usage
-To use the `utils` library, copy the [utils](utils.js) source code and paste it in the pre-request script of the test collection's root folder. Then you can call the `utils` functions from anywhere in the test code base.
+To use the `utils` library, copy the [utils.js](utils.js) source code and paste it in the pre-request script of the test collection's root folder. Then you can call the `utils` functions from anywhere in the test code base.
 
 The `utils` source code comments explain how to use the library, but a more detailed description is provided here.
 
@@ -27,7 +27,7 @@ The `utils` functions are logically grouped in nested classes (namespaces) and i
 * [**Primary test functions**](#primary-test-functions) for testing request results
 * [**Data validation functions**](#data-validation-functions) for checking data returned from requests
 * [**Trace functions**](#trace-functions) for trace logging
-* [**General purpose functions**](#general-purpose-functions) for miscellaneour operations
+* [**General purpose functions**](#general-purpose-functions) for miscellaneous operations
 
 ## Folder level functions
 Before we get to the overview of the folder level functions, let's summarize how folder scripts work. Folder scripts can be defined for pre-requests and post-requests. For each request in the test collection being executed, Postman first runs pre-request scripts defined in all request parent folders starting from the top level folder. Then Postman runs request's pre-request script, executes the request, and runs all post-request scripts defined in the parent folder just as it did with folder pre-requests. Finally, it runs request tests. And it is worth repeating: this logic gets executed for every request in the test collection. You may not need to run any scripts for any or all folders, which is fine: you simple do not add any code to them; but when you do, you may need to run the code once per test collection execution or for every request in the collection.