anchor.diff:  
   ### <a id="limitations"></a>  Limitations
   
  -The following table describes the limitations to consider when using the beta `v3-zdt-push` command. 
  +The following table describes the limitations to consider when using the rolling deployments. 
   
   <table>
   	<tr>
  
positive.code: 
  To stop the deployment of an app that you pushed, run the following command:
  
  <p class="note"><strong>Note</strong>: The <code>v3-cancel-zdt-push</code> command is designed to revert the app to its original state as quickly as possible, and does not guarantee zero downtime.</p>
  
  ```
  cf v3-cancel-zdt-push APP-NAME
  ```
  
  This reverts the app to its state from before the deployment started by doing the following:
  
  
negative.code: Restart your app without downtime using the following command. 
  This is useful when applying configuration updates that require a restart, such as environment variables or service bindings. 
  
  * **cf CLI v7**:
  
  	```
  	cf restart APP-NAME --strategy rolling
  	```
  * **cf CLI v6**:
  
  	```
  	cf v3-zdt-restart APP-NAME
  	```
  
  ## <a id="how-it-works"></a> How It Works
  
  This section describes the beta rolling deployments and and their limitations. 
  
  ### <a id="deployment-process"></a>  Rolling Deployment Process
  
  This section describes the process of pushing an app with a rolling deployment strategy. 
  
  1. The `cf push APP-NAME --strategy rolling` command does the following:
  	1. Stages the updated app package
  	1. Creates a droplet with the updated app package
  	1. Creates a deployment with the new droplet and any new configuration. 
  