anchor.diff:  	</tr>
   	<tr>
   		<td>4</td>
  -		<td>Based on the type specified for the app, Cloud Controller configures a health check that runs periodically for each application instance.
  +		<td>Based on the type specified for the app, Cloud Controller configures a health check that runs periodically for each app 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 until the health check timeout has elapsed. The 2-second health check interval is not configurable.
  +		<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 elapses. The 2-second health check interval is not configurable.
   		</td>
   
   	</tr>
  
positive.code:         </tr>
  	<tr>
  		<td>7</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.</td>
  	</tr>
  	<tr>
  	   <td>8</td>
  		<td>When an app instance crashes, Diego immediately attempts to restart the app instance several times. After three failed restarts, CF waits thirty seconds before attempting another restart. The wait time doubles each restart until the ninth restart, and remains at that duration until the 200th restart. After the 200th restart, CF stops trying to restart the app instance.</td>
  	</tr>
  </table>
  
  
negative.code: <th>Then use this type of health check:</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>
  </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.</code>
  </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>
  </tr>
  </table>
  
  