anchor.diff:  
   * `-c` --- Start command for the application.
   * `-d` --- Domain, for example, example.com.
  -* `-f` --- replaces `--manifest`
  +* `-f` --- Path to manifest. 
   * `-i` --- Number of instances of the application to run.
   * `-m` --- Memory limit, for example, 256, 1G, 1024M, and so on.
   * `-n` --- Hostname, for example, `my-subdomain`.
  
positive.code: * `-t` --- Timeout to start in seconds.
  * `--no-hostname` --- Map the root domain to this application.
  * `--no-manifest` --- Ignore manifests if they exist.
  * `--no-route` --- Do not map a route to this application, also removes existing routes from previous pushes of this app.
  * `--no-start` --- Do not start the application after pushing.
  
  <p class ="note"><strong>Note</strong>: To push a sample app, see the <a href="../../buildpacks/">Buildpacks</a> topic and choose to deploy a Java or Ruby sample app.</p>
  
  ## <a id='user-provided'></a> User-Provided Service Instances ##
  
  
negative.code: 
  ## <a id='return-codes'></a> cf CLI Return Codes ##
  
  The cf CLI uses exit codes, which is helpful for scripting and for confirming that a command has run successfully. For example, run `echo $?` in the terminal. If the return code is `0`, the command was successful. 
  
  ## <a id='help'></a> Run cf help ##
  
  