anchor.diff:  
   * `Response Time` is the total time it takes for the request to go through the Gorouter to the app
      and for the response to travel back through the Gorouter.
  -   This includes the time the request spends traversing the network to the app and back again to the Gorouter.
  +   This includes the time that the request spends traversing the network to the app and back again to the Gorouter.
      It also includes the time the app spends forming a response.
   
  -* `GoRouter Time` is the total time it takes for the request to go through the Gorouter
  +* `Gorouter Time` is the total time it takes for the request to go through the Gorouter
      initially plus the time it takes for the response to travel back through the Gorouter.
      This does not include the time the request spends traversing the network to the app.
      This also does not include the time the app spends forming a response.
   
  -* `X-CF-RouterError` is populated if the Gorouter encounters an error. This can
  -   help distinguish if a non-2xx response code is due to an error in the Gorouter
  -   or the backend. For more information on the possible Router Error causes go to
  -   the [#router-errors](#router-errors) section.
  +* `X-Cf-RouterError` is populated if the Gorouter encounters an error. The returned values can
  +   help distinguish whether a non-2xx response code is due to an error in the Gorouter
  +   or the backend. For more information on the possible errors, see
  +   the [Router Errors](#router-errors) section.
   
   ##### <a id="router-errors"></a> Router Errors
   
  -The value of the `X-Cf-Routererror` header can be one of the following:
  +The following table lists possible values of the `X-Cf-RouterError` header:
   
   <table>
     <tr>
  
positive.code: 
  Gorouter generates an access log in the following format when it receives a request:
  
  `<Request Host> - [<Start Date>] "<Request Method> <Request URL> <Request Protocol>" <Status Code> <Bytes Received> <Bytes Sent> "<Referer>" "<User-Agent>" <Remote Address> <Backend Address> x_forwarded_for:"<X-Forwarded-For>" x_forwarded_proto:"<X-Forwarded-Proto>" vcap_request_id:<X-Vcap-Request-ID> response_time:<Response Time> gorouter_time:<GoRouter Time> app_id:<Application ID> app_index:<Application Index> x_cf_routererror:<X-Cf-RouterError> <Extra Headers>`
  
  Gorouter access logs are also redirected to syslog.
  
  
negative.code:   </tr>
    <tr>
      <td><code>invalid_cf_app_instance_header</code></td>
      <td>The provided value for the <code>X-Cf-App-Instance</code> header does not match the required format of <code>APP_GUID:INSTANCE_ID</code>.</td>
    </tr>
    <tr>
      <td><code>empty_host</code></td>
      <td>The value for the <code>Host</code> header is empty, or the <code>Host</code> header is equivalent to the remote address. Some load balancers optimistically set the <code>Host</code> header value to their IP address when there is no value present.</td>
    </tr>
    <tr>
      <td><code>unknown_route</code></td>
      <td>The desired route does not exist in the Gorouter's route table.</td>
    </tr>
    <tr>
      <td><code>no_endpoints</code></td>
  