anchor.diff:  	</tr>
   	<tr>
   		<td>3</td>
  -		<td>Cloud Controller stages, starts, and runs the app. 
  +		<td>Cloud Controller stages, starts, and runs the app.
   		</td>
   	</tr>
   	<tr>
   		<td>4</td>
  -		<td>Based on the type specified for the app, Cloud Controller configures a health check that runs periodically for the application instance.
  +		<td>Based on the type specified for the app, Cloud Controller configures a health check that runs periodically for each application instance.
   		</td>
   	</tr>
   	<tr>
   		<td>5</td>
  -		<td>When Diego starts an app instance, the application health check runs every 2 seconds until a response indicates that the app instance is healthy or that the health check timeout has elapsed. 
  +		<td>When Diego starts an app instance, the application health check runs every 2 seconds until a response indicates that the app instance is healthy or until the health check timeout has elapsed.
   		</td>
   
   	</tr>
   	<tr>
   	   <td>6</td>
  -		<td>The health check continues to monitor each running app instance. When an app instance becomes healthy, its route is advertised, if applicable.
  +		<td>When an app instance becomes healthy, its route is advertised, if applicable. Subsequent health checks are run every 30 seconds once the app becomes healthy.
   		</td>
  -    </tr>
  -    <tr>
  +        </tr>
  +	<tr>
   		<td>7</td>
  -		<td>After an app instance is declared healthy, the health check runs every 30 seconds. Each health check has a TCP connection or HTTP connection timeout of 1 second.
  -		</td>
  -	</tr>
  -	<tr>
  -		<td>8</td>
  -		<td>If a previously healthy app instance fails a health check, Diego then considers that particular instance to be unhealthy. As a result, Diego stops that instance, tears down the instance, and then reschedules it. The teardown of the app instance is reported back to the Cloud Controller as a crash event. When an app instance crashes, Diego immediately attempts to restart the app instance several times. If the app instance continues to crash, then an exponential back off is applied to the restart attempts.</td>
  +		<td>If a previously healthy app instance fails a health check, Diego then considers that particular instance to be unhealthy. As a result, Diego tears down the instance, and then reschedules it. The teardown of the app instance is reported back to the Cloud Controller as a crash event. When an app instance crashes, Diego immediately attempts to restart the app instance several times. If the app instance continues to crash, then an exponential back off is applied to the restart attempts.</td>
   	</tr>
   </table>
   
  
positive.code: 
  ### <a id="health_check_timeout"></a> Health Check Timeouts
  
  The value configured for the health check timeout is the amount of time allowed to elapse between starting up an app and the first healthy response from the app. If the health check does not receive a healthy response within the configured timeout, then the app is declared unhealthy. 
  
  <%=vars.app_healthcheck_timeout%>
  
  
negative.code: 
  ## <a id="setting_health_checks"></a> How to Configure the Health Check for Your Application
  
  You can configure a health check type, application start timeout and HTTP endpoint for your application by using the [Cloud Controller API](https://apidocs.cloudfoundry.org/251/apps/creating_an_app.html).
  
  To set the type of health check for your application, you can specify a value in the `health-check-type` field of your [application manifest](./manifest.html#health-check-type) file.
  
  