anchor.diff:  ```
   
   Ctrl-C out of the foregrounded god instance. Notice that your current `simple`
  -server will continue to run. Start god again with the same command from
  -before. Now instead of starting the `simple` process, it will notice that one
  -is already running and simply switch to the `up` state.
  +server will continue to run. Start god again with the same command as before.
  +Now instead of starting the `simple` process, it will notice that one is
  +already running and simply switch to the `up` state.
   
   ```terminal
   # Events
  
positive.code: 
  Now that you've seen how to get started quickly, let's see how to use the more
  powerful aspects of god. Once again, the best way to learn will be through an
  example. The following configuration file is what I once used at <a
  href="http://site.gravatar.com/">gravatar.com</a> to keep the mongrels
  running:
  
  ```ruby
  RAILS_ROOT = "/Users/tom/dev/gravatar2"
  
negative.code: 
  Here I've specified a `:memory_max` option to the `keepalive` command. Now if
  the process memory usage goes above 150 megabytes, god will restart it.
  Similarly, by setting the `:cpu_max`, god will restart my process if its CPU
  usage goes over 50%. By default these properties will be checked every 30
  seconds and will be acted upon if there is an overage for three out of any
  five checks. This prevents the process from getting restarted for temporary
  