anchor.diff:  
   ### <a id="dump-log"></a> Dumping Logs
   
  -To display all the lines in the Loggregator buffer, run `cf logs APP-NAME --recent` and replace `APP-NAME` with the name of your app.
  +To display all of the lines in the Loggregator buffer, run `cf logs APP-NAME --recent`, where `APP-NAME` is 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 Gorouter 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 Gorouter logs:
   
   <pre class="terminal">
   $ cf logs spring-music --recent | grep -v RTR
  
positive.code: 
  #### <a id="traceid"></a> Zipkin Trace Logging
  
  If Zipkin trace logging is enabled in <%= vars.app_runtime_abbr %>, then Gorouter access log messages contain Zipkin HTTP headers.
  
  The following is an example access log message containing Zipkin headers:
  
  
negative.code: 2016-06-14T13:44:38.14-0700 [CELL/0]     OUT Successfully created container
  </pre>
  
  The Diego Cell also emits a CELL log message when an app instance exceeds the `max_log_lines_per_second` limit, which
  is configured on the platform.
  
  For example:
  
  