anchor.diff:      <pre class="terminal">
       $ cf config --locale pt-BR
       </pre> 
  +    <p class='note'><strong>Note</strong>: Localization with <code>cf config --locale</code> affects only messages that the cf CLI generates. </p>
   
   1. Confirm the language change:
   
       ```
       cf help
       ```
  +    
       For example:
   
       <pre class="terminal">
  
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>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 `set` and `unset` role commands above return an error:
  `The user exists in multiple origins. Specify an origin for the requested user from: ‘uaa’, ‘other’`
  
  To resolve this ambiguity, the operator can construct a `curl` command that uses the CF API to perform the desired role-management function. For an example, see the [PUT v2/organizations/:guid/auditors](http://apidocs.cloudfoundry.org/280/organizations/associate_auditor_with_the_organization_by_username.html) API function.
  
  ## <a id='push'></a>Push
  
  The [cf push](http://cli.cloudfoundry.org/en-US/cf/push.html) command pushes a new app or syncs changes to an existing app.
  
  If you do not provide a hostname (also known as subdomain), `cf push` routes your app to a URL of the form `APPNAME.DOMAIN` based on the name of your app and your default domain. 
  If you want to map a different route to your app, see the [Routes and Domains](https://docs.cloudfoundry.org/devguide/deploy-apps/routes-domains.html) topic for information about creating routes. 
  
  The `cf push` command supports many options that determine how and where the app instances are deployed. For details about the `cf push` command, see the [push](http://cli.cloudfoundry.org/en-US/cf/push.html) page in the Cloud Foundry CLI Reference Guide.
  
  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.
  
  <p class="note"><strong>Note</strong>: 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.</p>
  
  <pre class="terminal">
  $ cf push my-awesome-app -b ruby_buildpack
  
negative.code:        ...
      </pre>
  
  
  ## <a id='user-roles'></a> Manage Users and Roles
  
  The cf CLI includes commands that list users and assign roles in orgs and spaces. For more information, see [Orgs, Spaces, Roles, and Permissions](https://docs.cloudfoundry.org/concepts/roles.html).
  
  ### <a id='listing-users'></a> List Users
  
  The following commands list users in an org or a space:
  
  * `cf org-users`. See [org-users](http://cli.cloudfoundry.org/en-US/cf/org-users.html) in the _Cloud Foundry CLI Reference Guide_
  
  * `cf space-users`. See [space-users](http://cli.cloudfoundry.org/en-US/cf/space-users.html) in the _Cloud Foundry CLI Reference Guide_.
  
  The following example shows the cf CLI output for listing the users of an org:
  
  <pre class="terminal">
  $ cf org-users example-org
  