anchor.diff:      cf v3-zdt-push APP-NAME
       ```
       Where `APP-NAME` is the name that you want to give your app.
  -    <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 
  +    <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:**
  
positive.code:   </tr>
    <tr>
      <td>V3 APIs</td>
      <td>During a rolling deploy for an app requests to <a href="https://v3-apidocs.cloudfoundry.org/version/3.109.0/index.html#scale-a-process">scale a process</a>
      or <a href="https://v3-apidocs.cloudfoundry.org/version/3.109.0/index.html#update-a-process">update a process</a> V3 APIs will fail with an error message
      like <code>Cannot scale this process while a deployment is in flight.</code>.</td>
    </tr>
  </table>
  
  
negative.code:     cf v3-zdt-restart APP-NAME
      ```
      Where `APP-NAME` is the name of the app.
      <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:**
  