Added note on grunt-contrib-watch

Author: b00gizm

01-express-nodemon/README.md

@@ -29,7 +29,7 @@ Run `fig build`. It will
 
 Run `fig up` to create and start the container. The app should then be running on your docker daemon on port 3030 (On OS X you can use `boot2docker ip` to find out the IP address).
 
-## Notes for boot2docker
+## Notes on boot2docker
 
 It [appears](https://github.com/boot2docker/boot2docker/issues/290) that boot2docker (OS X, Windows) currently does not automatically sync the system clock with the host system after a host resumes from sleep. This becomes a problem due to the way nodemon detects file changes. That might cause it to go bananas, if the clocks on both systems are "too much" out of sync. Until this is fixed, you might use [this workaround](https://github.com/boot2docker/boot2docker/issues/290#issuecomment-62384209) or simply do a manual sync via
 

02-express-redis-nodemon/README.md

@@ -31,7 +31,7 @@ Run `fig up` to create and start both `web` and `db` container. The app should t
 
 You should see a counter on the index page which will be incremented in Redis on every request. See [app/routes/index.js](https://github.com/b00giZm/fig-nodejs-examples/blob/master/02-express-redis-nodemon/app/routes/index.js) to learn how to conect to Redis via [enviroment variables](http://www.fig.sh/env.html) exposed to the `web` container.
 
-## Notes for boot2docker
+## Notes on boot2docker
 
 It [appears](https://github.com/boot2docker/boot2docker/issues/290) that boot2docker (OS X, Windows) currently does not automatically sync the system clock with the host system after a host resumes from sleep. This becomes a problem due to the way nodemon detects file changes. That might cause it to go bananas, if the clocks on both systems are "too much" out of sync. Until this is fixed, you might use [this workaround](https://github.com/boot2docker/boot2docker/issues/290#issuecomment-62384209) or simply do a manual sync via
 

03-express-gulp-watch/README.md

@@ -35,7 +35,7 @@ Run `fig up` to create and start the container. The app should then be running o
 
 Go ahead and change any SASS stylesheet inside app/public/sass, and watch it autmatically compile to CSS.
 
-## Notes for boot2docker
+## Notes on boot2docker
 
 It [appears](https://github.com/boot2docker/boot2docker/issues/290) that boot2docker (OS X, Windows) currently does not automatically sync the system clock with the host system after a host resumes from sleep. This becomes a problem due to the way nodemon detects file changes. That might cause it to go bananas, if the clocks on both systems are "too much" out of sync. Until this is fixed, you might use [this workaround](https://github.com/boot2docker/boot2docker/issues/290#issuecomment-62384209) or simply do a manual sync via
 

04-express-grunt-watch/README.md

@@ -36,7 +36,13 @@ Run `fig up` to create and start the container. The app should then be running o
 
 Go ahead and change any SASS stylesheet inside app/public/sass, and watch it autmatically compile to CSS.
 
-## Notes for boot2docker
+## Notes on `grunt-contrib-watch`
+
+For a "real real world" ;) application, you might consider [grunt-simple-watch](https://github.com/unbalanced/grunt-simple-watch) instead of [grunt-contrib-watch](https://github.com/gruntjs/grunt-contrib-sass), because, at least for my personal tests, it's a lot easier on the CPU when you have a non trivial amount of files to watch.
+
+For more information, please visit the [grunt-simple-watch repo](https://github.com/unbalanced/grunt-simple-watch).
+
+## Notes on boot2docker
 
 It [appears](https://github.com/boot2docker/boot2docker/issues/290) that boot2docker (OS X, Windows) currently does not automatically sync the system clock with the host system after a host resumes from sleep. This becomes a problem due to the way nodemon detects file changes. That might cause it to go bananas, if the clocks on both systems are "too much" out of sync. Until this is fixed, you might use [this workaround](https://github.com/boot2docker/boot2docker/issues/290#issuecomment-62384209) or simply do a manual sync via