anchor.diff:  
   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:
  +example. The following configuration file is what I once used at gravatar.com
  +to keep the mongrels running:
   
   ```ruby
   RAILS_ROOT = "/Users/tom/dev/gravatar2"
  
positive.code: There are two ways that god can monitor your process. The first and better way
  is with process events. Not every system supports it, but those that do will
  automatically use it. With events, god will know immediately when a process
  exits. For those systems without events support, god will use a polling
  mechanism. The output you will see in this section will show both ways.
  
  After starting god, you should see some output like the following:
  
  
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
  