anchor.diff:      ```
       Where `APP-NAME` is the name of the app. 
   
  -    <p class="note"><strong>Note</strong>: When you provide an app name at the command line, <code>cf push</code> uses that app name whether or not there is a different app name in the manifest. If the manifest describes multiple apps, you can push a single app by providing its name at the command line; the cf CLI does not push the others. Use these behaviors for testing.</p>
  +
  +### <a id='push-path'></a> Push an App Using a Manifest 
  +
  +You can provide a path to a manifest file when you push an app. The manifest file may include information such as the name of the app, disk limit, and number of instances. You can use a manifest file rather than adding flags to the `cf push` command. 
  +
  +`cf push` locates the `manifest.yml` file in the current working
  +directory by default. Or, you can provide a path to the manifest with the `-f` flag.
  +
  +For more information, see [push](http://cli.cloudfoundry.org/en-US/cf/push.html) in the _Cloud Foundry CLI Reference Guide_. 
  +
  +<p class="note"><strong>Note</strong>: When you provide an app name at the command line, <code>cf push</code> uses that app name whether or not there is a different app name in the manifest. If the manifest describes multiple apps, you can push a single app by providing its name at the command line; the cf CLI does not push the others. Use these behaviors for testing.</p> 
   
   
   ### <a id='push-buildpack'></a> Push an App with a Buildpack
   
  -When you push an app and specify a buildpack with the <code>-b</code> flag, the app remains permanently linked to that buildpack. To use the app with a different buildpack, you must delete the app and re-push it.
  -
  -For more information about available buildpacks, see the <a href="https://docs.cloudfoundry.org/buildpacks/">Buildpacks</a> topic.
  +You can specify a buildpack when you push an app with the `-b` flag. If you use the `-b` flag to specify a buildpack, the app remains permanently linked to that buildpack. To use the app with a different buildpack, you must delete the app and then push it again.
  +
  +For more information about available buildpacks, see [Buildpacks](https://docs.cloudfoundry.org/buildpacks/).
   
   The following example pushes an app called `my-awesome-app` to the URL `http://my-awesome-app.example.com` and specifies the Ruby buildpack with the `-b` flag:
   
  
positive.code: <p class="note"><strong>Note</strong>: If you are not a <%=vars.product_short%> admin, you see this message when you try to run these commands:
  <code>error code: 10003, message: You are not authorized to perform the requested action</code></p>
  
  ### <a id='multi-origin'></a> Set or Unset Users with Identical Usernames in Multiple Origins
  
  If a username corresponds to multiple accounts from different user stores, such as both the internal UAA store and an external SAML or LDAP store, the `cf set-org-role` 
  and the `cf unset-org-role` commands above return the following error:
  
negative.code: * Non-interactively 
  * With third-party log management software as described in [RFC 6587](http://tools.ietf.org/html/rfc6587). When used with third-party logging, the cf CLI sends data formatted according to [RFC 5424](http://tools.ietf.org/html/rfc5424).
  
  ### <a id='user-cups'></a> Create a Service Instance
  
  To create a new service instance, use `cf create-user-provided-service` or `cf cups`. See [create-user-provided-service` or `cf cups`. See [cf cups](http://cli.cloudfoundry.org/en-US/cf/](http://cli.cloudfoundry.org/en-US/cf/create-user-provided-service.html) in the _Cloud Foundry CLI Reference Guide_.
  
  You can do one of the following to create a service instance:
  
  * **To supply service instance parameters interactively:**
  * **To supply service instance parameters to `cf cups` non-interactively:**
  * 
  
  
  **To supply service instance parameters interactively:** Specify parameters in a comma-separated list after the `-p` flag. This example command-line session creates a service instance for a database service.  
  
  