anchor.diff:      ```
       Where `APP-NAME` is the name of the app.
   
  -* **cf CLI v6**:
  -
  -  1. Run:
  -
  -    ```
  -    cf restart APP-NAME
  +* **cf CLI v6:**
  +
  +1. Run:
  +
  +    ```
  +    cf v3-zdt-restart APP-NAME
       ```
       Where `APP-NAME` is the name of the app.
  -
  -* **CAPI v3**:
  +    <p class='note'><strong>Note:</strong> This command is experimental and unsupported. Consider upgrading to cf CLI v7 to use a supported version of this command. To upgrade to cf CLI v7, see <a href="../cf-cli/v7.html#install">Install cf CLI v7</a> in <em>Upgrading to cf CLI v7</em>.</p>
  +
  +* **CAPI V3:**
   
   1. Run:
   
  
positive.code:           }
          }
        }'
      </pre>
      Where `APP-GUID` is the app GUID that you recorded in the previous step. This app GUID is a
      unique identifier for your app.
  
  1. Upload the package bits by running the following `curl` command with
  `POST /v3/packages/PACKAGE-GUID/upload`.
  
      <pre>
      cf curl /v3/packages/PACKAGE-GUID/upload \
      -X POST \
      -F bits=@"YOUR-PACKAGED-APP" \
      </pre>
      Where:
      * `PACKAGE-GUID` is the package GUID that you recorded in the previous step.
      * `YOUR-PACKAGED-APP` is your app packaged in a file such as `.zip`.
  
  1. Create the build by running the following `curl` command with `POST /v3/builds`. Record the
  droplet guid from the output.
  
      <pre>
      cf curl /v3/builds \
        -X POST \
        -H "Content-type: application/json" \
  
negative.code: 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.
        * 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 multiple `web` processes.
      <br>
      For more information about the deployment object, see the [Deployments](http://v3-apidocs.cloudfoundry.org/index.html#deployments) section of the CAPI V3 documentation.
  
  1. After the command creates the deployment, the `cc_deployment_updater` BOSH job runs in the
  background, updating deployments as follows:
  