anchor.diff:  	<tr>
   		<th>Limitation</th>
   		<th>Description</th>
  +	</tr>
  +	<tr>
  +		<td>SSH to app instances</td>
  +		<td>Pushing updates to your app with a <code>v3-zdt</code> command causes the new web
  +			process and app GUID to mismatch. <code>cf ssh</code> does not handle this
  +			scenario. You must use the <code>cf v3-ssh</code> command instead.</td>
   	</tr>
   	<tr>
   		<td>Multiple app versions</td>
  
positive.code: 	1. Creates a droplet with the updated app package
  	1. Creates a deployment with the new droplet and any new configuration. 
  		* This starts a new process with one instance that shares the route with the old process. 
  		* At this point, if you run `cf app` on your app, you see a `web` process and a `web-deployment-DEPLOYMENT-UUID` process.
  		* For more information about the deployment object, see the [Deployments](http://v3-apidocs.cloudfoundry.org/index.html#deployments) section of the CAPI v3 docs. 
  1. Once the command creates the deployment, the `cc_deployment_updater` BOSH job runs in the background, updating deployments as follows:
  	1. Adds another instance of the new web process and removes an instance from the old web process. 
  
negative.code: 		<td>Simultaneous apps when interrupting a push</td>
  		<td>If you push app before your previous push command for the same app has completed, your first push gets interrupted. Until the last deployment completes, there may be many versions of the app running at once. Eventually, the app runs the code from your most recent push.</td>
  	</tr>
  </table>
  