anchor.diff:  
   The [cf push](./cf-help.html#apps) 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](..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 entry](./cf-help.html#apps) in the Apps section of the Cloud Foundry CLI Reference Guide.
  +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](../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](./cf-help.html#apps) entry in the Apps section of the Cloud Foundry CLI Reference Guide.
   
   The following example pushes an application called `my-awesome-app` using the Ruby buildpack to the URL `http://my-awesome-app.example.com`: 
   
  
positive.code:    ...
  </pre>
  
  <p class='note'><strong>Note</strong>: Localization affects only messages that the cf CLI generates. </p>
  
  ## <a id='login'></a>Login ##
  
  Use [cf login](./cf-help.html#getting-started) to log into <%= vars.product_short %>. The `cf login` command uses the following syntax to specify a target API endpoint, an [org](#domains-etc), and a [space](#domains-etc): <code>$ cf login [-a API_URL] [-u USERNAME] [-p PASSWORD] [-o ORG] [-s SPACE] </code>.  
  
  * `API_URL`: This is your API endpoint, <%=vars.api_endpoint%>.
  * `USERNAME`: Your username.
  * `PASSWORD`: Your password. <%=vars.pcf_rec%> discourages using the `-p` option, which may record your password in your shell history. 
  * `ORG`: The org (organization) 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 http://api.example.com -u username@example.com
  API endpoint: https://api.example.com
  
  Password>
  
negative.code: 
  <pre class="terminal">
  $ cf org-users example-org
  Getting users in org example-org as username<span>@</span>example.com...
  
  ORG MANAGER
    username<span>@</span>example.com
  
  BILLING MANAGER
    huey<span>@</span>example.com
    dewey<span>@</span>example.com
  
  ORG AUDITOR
    louie<span>@</span>example.com
  </pre>
  
  <strong>Commands for managing roles.</strong> These commands require <%=vars.product_short%> admin permissions and take username, org or space, and role as arguments:
  