anchor.diff:  	</tr>
   </table>
   
  -## <a id="health_check_configuration"></a>Application Health Check Configuration
  -
  -This section provides information on the configuration of application health checks.
  -
   ### <a id="types"></a> Health Check Types
   
  -The following table describes the types of health checks available for apps and recommended circumstances in which to use them:
  +The following table describes the types of health checks available for applications and recommended circumstances in which to use them:
   
   <table>
   <tr>
  -<th>If your app:</th>
  -<th>Then use this type of health check:</th>
  +<th>Health Check Type</th>
  +<th>Recommended Use Case</th>
  +<th>Explanation</th>
   </tr>
   <tr>
  -<td>Can provide an <code>HTTP 200</code> response</td>
  -<td><code>http</code>: The <code>http</code> health check performs a GET request to the configured http endpoint. When the health check receives an <code>HTTP 200</code> response, the app is declared healthy. We recommend using the <code>http</code> health check type whenever possible. A healthy HTTP response ensures that the web app is ready to serve HTTP requests. The configured endpoint must respond within 1 second to be considered healthy.</td>
  +<td><code>http</code></td>
  +<td>The app can provide an <code>HTTP 200</code> response.</td>
  +<td>The <code>http</code> health check performs a GET request to the configured http endpoint. When the health check receives an <code>HTTP 200</code> response, the app is declared healthy. We recommend using the <code>http</code> health check type whenever possible. A healthy HTTP response ensures that the web app is ready to serve HTTP requests. The configured endpoint must respond within 1 second to be considered healthy.</td>
   </tr>
   <tr>
  -<td>Can receive TCP connections (including HTTP web applications)
  -</td>
  -<td>
  -<code>port</code>: A health check makes a TCP connection to the port or ports configured for the app. For applications with multiple ports, a health check monitors each port. If you do not specify a health check type for your app, then the monitoring process defaults to a <code>port</code> health check. The TCP connection must be established within 1 second to be considered healthy.
  +<td><code>port</code></td>
  +<td>The app can receive TCP connections (including HTTP web applications).</td>
  +<td>A health check makes a TCP connection to the port or ports configured for the app. For applications with multiple ports, a health check monitors each port. If you do not specify a health check type for your app, then the monitoring process defaults to a <code>port</code> health check. The TCP connection must be established within 1 second to be considered healthy.
   </td>
   </tr>
   <tr>
  -<td>Does not support TCP connections (for example, a worker)</td>
  -<td><code>process</code>: For a <code>process</code> health check, Diego ensures that any process declared for the app stays running. If the process exits, Diego stops and deletes the app instance.</td>
  +<td><code>process</code></td>
  +<td>The app does not support TCP connections (for example, a worker).</td>
  +<td> For a <code>process</code> health check, Diego ensures that any process declared for the app stays running. If the process exits, Diego stops and deletes the app instance.</td>
   </tr>
   </table>
   
  
positive.code: 
  <strong><%= modified_date %></strong>
  
  ## <a id="about_health_checks"></a> Overview
  
  An application health check is a monitoring process that continually checks the status of a running Cloud Foundry app.
  
  When deploying an app, a developer can configure the health check type and a timeout for starting the app. Valid health check types are `port`, `process`, and `http`. For type `http`, the developer can also configure an endpoint for the application health check.
  
  Application health checks function as part of the app lifecycle managed by [Diego architecture](../../concepts/diego/diego-architecture.html).
  
  ### <a id="health_checks_work"></a>How Application Health Checks Work
  
  The following table describes how application health checks work in Cloud Foundry.
  
  
negative.code: 
  ### <a id="health_check_uri"></a> Health Check HTTP Endpoints
  
  Only used by `http` type, the `--endpoint` flag of the `cf set-health-check` command specifies the path portion of a URI that must be served by the app and return `HTTP 200` when the app is healthy.
  
  
  