anchor.diff:  
   Running a Node.js REPL is similar to running a browser REPL. In order to specify
   a REPL which uses a different JavaScript evaluation environment you supply
  -`--repl-env` or `-re` for short. This value defaults to the browser REPL but in
  +`--repl-env`. This value defaults to the browser REPL but in
   this case we want to specify `node`.
   
   [source,bash]
   ----
  -clj -m cljs.main -re node
  -----
  -
  -On Windows:
  -
  -[source,bash]
  -----
  -java -cp "cljs.jar;src" -m cljs.main -re node
  +clj -m cljs.main --repl-env node
  +----
  +
  +On Windows:
  +
  +[source,bash]
  +----
  +java -cp "cljs.jar;src" -m cljs.main --repl-env node
   ----
   
   All the previously described REPL interactions for the browser should
  
positive.code: (.getElementById js/document "app")
  ----
  
  Let's look a bit closer at the flags we've used here. `-m`, short
  for `--main`, invokes a _Clojure_ function, in this case `cljs.main`. The
  `cljs.main` function supports a variety of command line arguments to specify
  common tasks. We're using `-c` for `--compile` to specify that we want to
  compile the `hello-world.core` namespace. This is followed by `-r` for `--repl`
  to say that we want a REPL to launch immediately when compilation completes.
  
  Change your `src/hello_world/core.cljs` source file to look like the following:
  
  
negative.code: elimination.
  
  You can test that this file still works by running the built in simple web
  server via the `--serve` flag:
  
  [source,bash]
  ----
  clj -m cljs.main --serve
  ----
  
  On Windows:
  
  [source,bash]
  ----
  java -cp "cljs.jar;src" -m cljs.main --serve
  ----
  
  `-s` is for `--serve`. This command does not start a REPL, so a browser window
  