diff --git a/README.md b/README.md
index e9c3e047..a38c8647 100644
--- a/README.md
+++ b/README.md
@@ -64,99 +64,47 @@ workb();
The `DEBUG` environment variable is then used to enable these based on space or
comma-delimited names.
-Here are some examples:
-
-
-
-
-
-#### Windows command prompt notes
-
-##### CMD
-
-On Windows the environment variable is set using the `set` command.
-
-```cmd
-set DEBUG=*,-not_this
```
-
-Example:
-
-```cmd
-set DEBUG=* & node app.js
+$ DEBUG=* node examples/node/app.js
```
-##### PowerShell (VS Code default)
-
-PowerShell uses different syntax to set environment variables.
-
-```cmd
-$env:DEBUG = "*,-not_this"
-```
-
-Example:
-
-```cmd
-$env:DEBUG='app';node app.js
-```
-
-Then, run the program to be debugged as usual.
-
-npm script example:
-```js
- "windowsDebug": "@powershell -Command $env:DEBUG='*';node app.js",
-```
-
-## Namespace Colors
-
-Every debug instance has a color generated for it based on its namespace name.
-This helps when visually parsing the debug output to identify which debug instance
-a debug line belongs to.
-
-#### Node.js
-
-In Node.js, colors are enabled when stderr is a TTY. You also _should_ install
-the [`supports-color`](https://npmjs.org/supports-color) module alongside debug,
-otherwise debug will only use a small handful of basic colors.
-
-
-
-#### Web Browser
-
-Colors are also enabled on "Web Inspectors" that understand the `%c` formatting
-option. These are WebKit web inspectors, Firefox ([since version
-31](https://hacks.mozilla.org/2014/05/editable-box-model-multiple-selection-sublime-text-keys-much-more-firefox-developer-tools-episode-31/))
-and the Firebug plugin for Firefox (any version).
-
-
-
-
## Millisecond diff
When actively developing an application it can be useful to see when the time spent between one `debug()` call and the next. Suppose for example you invoke `debug()` before requesting a resource, and after as well, the "+NNNms" will show you how much time was spent between calls.
-
+```bash
+ $ DEBUG=* node examples/node/worker.js
+ worker:a doing lots of uninteresting work +0ms
+ worker:b doing some work + 0ms
+ http listening +23ms
+```
When stdout is not a TTY, `Date#toISOString()` is used, making it more useful for logging the debug information as shown below:
-
+```bash
+ $ DEBUG=* node examples/node/worker.js 2>&1 | cat
+ 2017-08-08T19:46:35.674Z worker:a doing lots of uninteresting work
+ 2017-08-08T19:46:35.678Z worker:b doing some work
+```
## Conventions
-If you're using this in one or more of your libraries, you _should_ use the name of your library so that developers may toggle debugging as desired without guessing names. If you have more than one debuggers you _should_ prefix them with your library name and use ":" to separate features. For example "bodyParser" from Connect would then be "connect:bodyParser". If you append a "*" to the end of your name, it will always be enabled regardless of the setting of the DEBUG environment variable. You can then use it for normal output as well as debug output.
+Use the name of your library so that developers may toggle debugging as desired without guessing names. If you have more than one debuggers prefix them with your library name and use ":" to separate features.
+
+Example for bodyParser from Connect
+```
+DEBUG=connect:bodyParser
+```
## Wildcards
-The `*` character may be used as a wildcard. Suppose for example your library has
-debuggers named "connect:bodyParser", "connect:compress", "connect:session",
-instead of listing all three with
-`DEBUG=connect:bodyParser,connect:compress,connect:session`, you may simply do
-`DEBUG=connect:*`, or to run everything using this module simply use `DEBUG=*`.
+The `*` character may be used as a wildcard
-You can also exclude specific debuggers by prefixing them with a "-" character.
-For example, `DEBUG=*,-connect:*` would include all debuggers except those
-starting with "connect:".
+Example for all from Connect
+```
+DEBUG=connect:*
+```
## Environment Variables