anchor.diff:  A syslog drain or a CLI tail can usually keep up with the flow of app
   logs.
   
  -## <a id='types'></a>Contents of a Log Line ##
  +
  +## <a id='types'></a> Contents of a Log Line
   
   Every log line contains four fields:
   
  
positive.code: 2016-06-14T13:44:38.14-0700 [CELL/0]     OUT Successfully created container
  </pre>
  
  ## <a id='writing'></a>Writing to the Log from Your App ##
  
  Your app must write logs to `stderr` or `stdout`.
  Both are typically buffered, and you should flush the buffer before delivering
  
negative.code: 
  Use **Ctrl-C** (^C) to exit the real-time stream.
  
  ### <a id="dump-log"></a> Dumping Logs
  
  Run `cf logs APP-NAME --recent` to display all the lines in the Loggregator buffer. Replace `APP-NAME` with the name of your app.
  
  ### <a id="filter"></a> Filtering Logs
  
  To view some subset of log output, run `cf logs APP-NAME` in conjunction with filtering commands of your choice. Replace `APP-NAME` with the name of your app.
  In the example below, `grep -v RTR` excludes all Router logs:
  