fixup! 8948d

Address code review comments

Author: bajtos

README.md

@@ -26,17 +26,17 @@ and then in modules implementing task queues and connection pools.
 $ npm install --save loopback-context cls-hooked
 ```
 
-Make sure you are running on a Node version supported by this module!
-Please check the output of `npm install` and make sure there are
-no `engine` related warnings.
+Make sure you are running on a Node.js version supported by this module
+(`^4.5`, `^5.10` or `^6.0`). When installing, check the output of `npm install`
+and make sure there are no `engine` related warnings.
 
 ## Usage
 
 ### Setup cls-hooked
 
 To minimize the likelihood of loosing context in your application, you should
 ensure that `cls-hooked` is loaded as the first module of your application, so
-that it can wrap certain Node APIs before any other modules start using these
+that it can wrap certain Node.js APIs before any other modules start using these
 APIs.
 
 Our recommended approach is to add `-r cls-hooked` to node's list of
@@ -125,7 +125,7 @@ chain (before the middleware that depends on
 invoked multiple times on the same request and returns immediately in
 subsequent runs.**
 
-Here’s sample code which uses a middleware function to place the currently
+Here is a snippet using a middleware function to place the currently
 authenticated user into the context so that remote methods may use it:
 
 **server/middleware/store-current-user.js**
@@ -158,7 +158,7 @@ module.exports = function(options) {
 {
   "initial": {
     "loopback-context#per-request": {}
-  }
+  },
   "auth": {
     "loopback#token": {}
   },