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: 
  ### <a id="health_check_uri"></a> Health Check HTTP Endpoints
  
  Only used by `http` type, this configuration specifies the path portion of a URI that must be served by the app and return `HTTP 200` when the app is healthy.
  
  ## <a id="setting_health_checks"></a> How to Configure the Health Check for Your Application
  
  Use the [Cloud Controller API](https://apidocs.cloudfoundry.org/251/apps/creating_an_app.html) to configure a health check type, application start timeout, and HTTP endpoint for your app. 
  
  Use the cf CLI [cf push](http://cli.cloudfoundry.org/en-US/cf/push.html) command to configure the health check type while creating or updating an application, or [cf set-health-check](http://cli.cloudfoundry.org/en-US/cf/set-health-check.html) to configure an existing application.
  With `cf push`, use command line options `-u` to set the health check type and `-t` to configure the timeout. Alternatively, you can specify the type in the `health-check-type` field of your [application manifest](./manifest.html#health-check-type) file, and in case of the <code>http</code> health check type, the endpoint in the `health-check-http-endpoint` field.
  
  You can change the health check configuration of a deployed app, but you must restart the app for the changes to take effect.
  
negative.code: 
  <strong><%= modified_date %></strong>
  
  This topic describes how to configure health checks for your applications in Cloud Foundry.
  
  ## <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.
  
  Developers can configure a health check for an application using the Cloud Foundry Command Line Interface (cf CLI) or by specifying the `health-check-http-endpoint` and `health-check-type` fields in an application manifest. 
  
  To configure a health check using the cf CLI, follow the instructions in the [Configure Health Checks](#setting_health_checks) section below. For more information about using an application manifest to configure a health check, see the [health-check-http-endpoint](manifest.html#health-check-http-endpoint) and [health-check-type](manifest.html#health-check-type) sections of the <em>Deploying with Application Manifest</em> topic.
  
  Application health checks function as part of the app lifecycle managed by [Diego architecture](../../concepts/diego/diego-architecture.html).
  
  ## <a id="setting_health_checks"></a> Configure Health Checks
  
  To configure a health check while creating or updating an application, use the [cf push](http://cli.cloudfoundry.org/en-US/cf/push.html) command:
  
  <pre class="terminal">
  $ cf push YOUR-APP -u HEALTH-CHECK-TYPE -t HEALTH-CHECK-TIMEOUT
  </pre>
  
  Replace the placeholders in the example command above as follows:
  
  * `HEALTH-CHECK-TYPE`: Valid health check types are `port`, `process`, and `http`. See the [Health Check Types](#types) section below for more information.
  * `HEALTH-CHECK-TIMEOUT`: The timeout is the amount of time allowed to elapse between starting up an application and the first healthy response. See the [Health Check Timeouts](#health_check_timeout) section for more information.
  
  <p class="note"><strong>Note</strong>: The health check configuration you provide with <code>cf push</code> overrides any configuration in the application manifest.</p>
  
  To configure a health check for an existing application or to add a custom HTTP endpoint, use the [cf set-health-check](http://cli.cloudfoundry.org/en-US/cf/set-health-check.html) command:
  
  <pre class="terminal">
  $ cf set-health-check YOUR-APP HEALTH-CHECK-TYPE --endpoint CUSTOM-HTTP-ENDPOINT
  </pre>
  
  Replace the placeholders in the example command above as follows:
  
  * `HEALTH-CHECK-TYPE`: Valid health check types are `port`, `process`, and `http`. See the [Health Check Types](#types) section below for more information.
  * `CUSTOM-HTTP-ENDPOINT`: A `http` health check defaults to using `/` as its endpoint, but you can specify a custom endpoint. See the [Health Check HTTP Endpoints](#health_check_uri) section below for more information.
  
  <p class="note"><strong>Note</strong>: You can change the health check configuration of a deployed app with <code>cf set-health-check</code>, but you must restart the app for the changes to take effect.</p>
  
  ##<a id='understand-healthchecks'></a> Understand Health Checks
  
  ###<a id='healthcheck-lifecycle'></a> Health Check Lifecycle
  
  The following table describes how application health checks work in Cloud Foundry.
  
  