anchor.diff:  * `ORG`: The org where you want to deploy your apps.
   * `SPACE`: The space in the org where you want to deploy your apps.
   
  -The cf CLI prompts for credentials as needed. If you are a member of multiple orgs or spaces, `cf login` prompts you for which ones to log into. Otherwise it targets your org and space automatically.
  -
   <pre class="terminal">
   $ cf login -a https://api.example.com -u username<span>@</span>example.com
   API endpoint: https://api.example.com
  
positive.code: After you create a user-provided service instance, you bind it to an app with [cf bind-service](http://cli.cloudfoundry.org/en-US/cf/bind-service.html), 
  unbind it with [cf unbind-service](http://cli.cloudfoundry.org/en-US/cf/unbind-service.html), rename it with [cf rename-service](http://cli.cloudfoundry.org/en-US/cf/rename-service.html), and delete it with [cf delete-service](http://cli.cloudfoundry.org/en-US/cf/delete-service.html).
  
  ### <a id='user-uups'></a> The cf update-user-provided-service (uups) Command ###
  
  Use [cf update-user-provided-service](http://cli.cloudfoundry.org/en-US/cf/update-user-provided-service.html) (alias `cf uups`) to update one or more of the parameters for an existing user-provided service instance. 
  The `cf uups` command uses the same syntax as `cf cups` [above](#user-cups) to set parameter values. The `cf uups` command does not update any parameter values that you do not supply.
  
  ## <a id='return-codes'></a> cf CLI Return Codes ##
  
  The cf CLI uses exit codes, which help with scripting and confirming that a command has run successfully. For example, after you run a cf CLI command, you can retrieve its return code by running `echo $?` (on Windows, `echo %ERRORLEVEL%`). If the return code is `0`, the command was successful.
  
  ## <a id='help'></a> The cf help Command ##
  
  The [cf help](http://cli.cloudfoundry.org/en-US/cf) command lists the cf CLI commands and a brief description of each.
  Passing the `-h` flag to any command lists detailed help, including any aliases. For example, to see detailed help for `cf delete`, run:
  
negative.code: 
  </pre>
  
  ## <a id='login'></a> Log In With the API
  
  You can write a script to log in and set your target using the non-interactive [cf api](http://cli.cloudfoundry.org/en-US/cf/api.html), [cf auth](http://cli.cloudfoundry.org/en-US/cf/auth.html), and [cf target](http://cli.cloudfoundry.org/en-US/cf/target.html) commands.
  
  After you log in, the cf CLI saves a `config.json` file that contains your API endpoint, org, space values, and access token.
  
  If you change these settings, the `config.json` file is updated accordingly.
  
  By default, `config.json` is located in the `~/.cf` directory. The `CF_HOME` environment variable allows you to relocate the `config.json` file.
  
  ##<a id='i18n'></a> Localize the CLI
  
  The cf CLI translates terminal output into the language that you select. The default language is <code>en-US</code>. 
  
  The cf CLI supports the following languages:
  
  *  Chinese (simplified): <code>zh-Hans</code>
  *  Chinese (traditional): <code>zh-Hant</code>
  