anchor.diff:  
   ## <a id='dea-configuration'></a>DEA Configuration ##
   
  -
  -DEA behavior is configured in `dea.yml`.
  +DEA behavior is configured in the `dea.yml` file.
   
   The following is a partial list of the keys that the DEA reads from the YAML file:
   
  -* `logging` --- A [Steno configuration](http://github.com/cloudfoundry/steno#from-yaml-file).
  -* `nats_uri` --- A URI of the form `nats://host:port` that the DEA uses to connect to NATS.
  -* `warden_socket` --- The path to a unix domain socket that the DEA uses to communicate to a Warden server.
  -
  +* `logging`: A [Steno configuration](http://github.com/cloudfoundry/steno#from-yaml-file)
  +* `nats_uri`: A URI of the form `nats://host:port` that the DEA uses to connect to NATS
  +* `warden_socket`: The path to a UNIX domain socket that the DEA uses to communicate to a Warden server.
   
   A sample `dea.yml` file follows:
   
   <p class="note"><strong>Note</strong>: See <a href='https://github.com/cloudfoundry/dea_ng/blob/master/lib/dea/config.rb'>https://github.com/cloudfoundry/dea_ng/blob/master/lib/dea/config.rb</a> for optional configuration keys.</p>
   
  -
   ```yaml
   
   # See src/lib/dea/config.rb for optional config values.
   
  -# Base directory for dea, application directories, dea temp files, etc. are all relative to this.
  +# Base directory for dea. Application directories, DEA temp files, etc. are all relative to this.
   base_dir: /tmp/dea_ng
   
   logging:
  
positive.code: #   after_start: path/to/script
  #   before_stop: path/to/script
  #   after_stop: path/to/script
  ## <a id='run-standalone'></a>Running the DEA Standalone ##
  
  ```
  
  When you contribute to the DEA, it is useful to run it as a standalone component. This section has instructions for doing so on Vagrant 1.1x.
  
  Refer to the [Vagrant documentation](http://docs.vagrantup.com/v2/installation/index.html) for instructions on installing Vagrant.
  
  Follow these steps to set up DEA to run locally on your computer:
  
  <pre class="terminal">
  $ git clone http://github.com/cloudfoundry/dea_ng
  
negative.code: 
  The DEA also checks for a `AppState` object for the application.
  
  ## <a id='usage'></a>Usage ##
  
  You can run the `dea` executable at the command line by passing the path to the DEA configuration file:
  
  <pre class="terminal">
  $ bin/dea config/dea.yml
  