anchor.diff:  2016-11-23T16:04:01.49-0800 [RTR/0]      OUT www.example.com - [24/11/2016:00:04:01.227 +0000] "GET / HTTP/1.1" 200 0 109 "-" "curl/7.43.0" 10.0.2.150:4070 10.0.48.66:60815 x_forwarded_for:"198.51.100.120" x_forwarded_proto:"http" vcap_request_id:87f9d899-c7a4-46cd-7b76-4ec35ce9921b response_time:0.263000966 app_id:8e5d6451-b369-4423-bce8-3a7a9e479dbb app_index:0 x_b3_traceid:"2d5610bf5e0f7241" x_b3_spanid:"2d5610bf5e0f7241" x_b3_parentspanid:"-"
   </pre>
   
  -For more information about Zipkin tracing, see [Zipkin Tracking in HTTP Headers](../../concepts/http-routing.html#zipkin-headers) in _HTTP Routing_.
  +For more information about Zipkin tracing,
  +see [Zipkin Tracking in HTTP Headers](../../concepts/http-routing.html#zipkin-headers) in _HTTP Routing_.
   
   ### <a id='lgr'></a> LGR
   
  -Loggregator emits LGR to indicate problems with the logging process. Examples include `can't reach syslog drain url` and `dropped log messages due to high rate`.
  +Loggregator emits LGR to indicate problems with the logging process. Examples include `can't reach syslog drain url`
  +and `dropped log messages due to high rate`.
   
   ### <a id='app'></a> APP
   
  
positive.code: 
  ### <a id='stg'></a> STG
  
  The Diego Cell or the Droplet Execution Agent emits STG logs when staging or restaging an app. These actions implement the desired state requested by the user. After the droplet has been uploaded, STG messages end and CELL messages begin. For STG, the instance index is almost always 0.
  
  For example:
  
  
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:
  
  