anchor.diff:  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 v3-zdt-restart APP-NAME
  -```
  +* **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 `cf v3-zdt-push` command and its limitations. 
  +This section describes the beta rolling deployments and and their limitations. 
   
  -### <a id="deployment-process"></a>  cf v3-zdt-push Process
  +### <a id="deployment-process"></a>  Rolling Deployment Process
   
  -This section describes the process of pushing an app with `cf v3-zdt-push`. 
  +This section describes the process of pushing an app with a rolling deployment strategy. 
   
  -1. The `cf v3-zdt-push` command does the following:
  +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. 
  
positive.code: 	</tr>
  	<tr>
  		<td>Non-web processes</td>
  		<td>The <code>v3-zdt</code> commands only run web processes through the rolling update sequence described above. The commands restart worker and other non-web processes in bulk after updating all web processes.<br><br>
  		The CAPI v3 API introduces the concept of processes as runnable units of an app. Each app has a web process by default. You can specify additional processes with a procfile, and in some cases buildpacks create additional processes. For more information about processes, see the <a href="http://v3-apidocs.cloudfoundry.org/index.html#processes">Processes</a> section of the CAPI v3 documentation. 
  		</td>
  	</tr>
  	<tr>
  		<td>Quotas</td>
  		<td>Pushing updates to your app with a <code>v3-zdt</code> command creates an extra instance of your app. If there is not enough quota available, the deployment does not work. Administrators may need to increase quotas to account for rolling deployments.</td>
  	</tr>
  	<tr>
  		<td>Simultaneous apps when interrupting a push</td>
  		<td>If you run <code>v3-zdt-push</code> for an app before your previous <code>v3-zdt-push</code> 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>
  	<tr>
  		<td>SSH to app instances</td>
  
negative.code: 
  To deploy an app without incurring downtime, run the following command:
  
  * **cf CLI v7**:
  
  	```
  	cf push APP-NAME --strategy rolling
  	``` 
  * **cf CLI v6**:
  
  	```
  	cf v3-zdt-push APP-NAME
  	``` 
  <p class="note warning"><strong>Warning</strong>: Ensure that you understand the <a href="#limitations">Limitations</a> of this feature before running the command.</p>
  
  For more information about this command, see [How it Works](#how-it-works). 
  