anchor.diff:  
   ## <a id='user-provided'></a> User-Provided Service Instances ##
   
  -The cf CLI has three ways of creating and updating user-provided service instances: interactively, non-interactively, and in conjunction 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).
  -
  -Once created, user-provided service instances can be bound to an app with `cf bind-service`, unbound with `cf unbind-service`, renamed with `cf rename-service`, and deleted with `cf delete-service`.
  -
  -### <a id='user-cups'></a>The cf create-user-provided-service Command ###
  -
  -The alias for `create-user-provided-service` is `cups`.
  -
  -To create a service instance in interactive mode, use the `-p` option with a comma-separated list of parameter names.
  -The cf CLI then prompts you for each parameter in turn.
  -
  -  <pre class="terminal">cf cups SERVICE_INSTANCE -p host, port, dbname, username, password</pre>
  -
  -To create a service instance non-interactively, use the `-p` option with a JSON hash of parameter keys and values.
  -
  -  <pre class="terminal">cf cups SERVICE_INSTANCE -p '{"username":"admin","password":"pa55woRD"}'</pre>
  -
  -To create a service instance that drains information to third-party log management software, use the `-l SYSLOG_DRAIN_URL` option.
  -
  -  <pre class="terminal">cf cups SERVICE_INSTANCE -l syslog://example.com:514</pre>
  -
  -### <a id='user-uups'></a> The cf update-user-provided-service Command ###
  -
  -The alias for `update-user-provided-service` is `uups`.
  -Use `cf update-user-provided-service` to update one or more of the attributes for a user-provided service instance.
  -Attributes that you do not supply are not updated.
  -
  -To update a service instance non-interactively, use the `-p` option with a JSON hash of parameter keys and values.
  -
  -  <pre class="terminal">cf uups SERVICE_INSTANCE -p '{"username":"USERNAME","password":"PASSWORD"}'</pre>
  -
  -To update a service instance that drains information to third-party log management software, use the `-l SYSLOG_DRAIN_URL` option.
  -
  -  <pre class="terminal">cf uups SERVICE_INSTANCE -l syslog://example.com:514</pre>
  -
  +To create or update a user-provided service instance, you need to supply basic parameters. For example a database service might require a username, password, host, port, and database name.
  +
  +The cf CLI has three ways of supplying these parameters to create or update an instance of a service: interactively, non-interactively, and in conjunction 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).
  +
  +You create a service instance with `cf cups` and update one with `cf uups` as described below. 
  +
  +### <a id='user-cups'></a>The cf create-user-provided-service (cups) Command ###
  +
  +Use [cf create-user-provided-service](./cf-help.html#services) (alias `cf cups`) creates a new service instance.
  +
  +**Interactive** --- For example, to create a service instance for a database service, 
  +this command prompts for the parameters specified in a comma-separated list after the `-p` flag.  
  +
  +  <pre class="terminal">$ cf cups sql-service-instance -p "host, port, dbname, username, password"
  +host> mysql.example.com
  +port> 1433
  +dbname> mysqldb
  +username> admin
  +password> Pa55w0rd
  +Creating user provided service sql-service-instance in org example-org / space development as username@example.com...
  +OK
  +</pre>
  +
  +**Non-interactive** --- This example resembles the one above except that you pass in parameters and their values as a JSON hash, bound by single quotes.
  +
  +  <pre class="terminal">$ cf cups sql-service-instance -p '{"host":"mysql.example.com", "port":"1433", "dbname":"mysqldb", "username":"admin","password":"pa55woRD"}'
  +  Creating user provided service sql-service-instance in org example-org / space development as username<span>@</span>example.com...
  +OK
  +</pre>
  +
  +**Third-party** --- This example creates a service instance that drains information to third-party log management software using the `-l SYSLOG_DRAIN_URL` option. 
  +For specific log service instructions, see the [Service-Specific Instructions for Streaming Application Logs](../devguide/services/log-management-thirdparty-svc.html) topic.
  +
  +  <pre class="terminal">$ cf cups mylog -l syslog://logs4.example.com:25258
  +Creating user provided service mylog in org example-org / space development as username<span>@</span>example.com...
  +OK
  +</pre>
  +
  +After you create a user-provided service instance, you bind it to an app with [cf bind-service](./cf-help.html#services), 
  +unbind it with [cf unbind-service](./cf-help.html#services), rename it with [cf rename-service](./cf-help.html#services), and delete it with [cf delete-service](./cf-help.html#services).
  +
  +### <a id='user-uups'></a> The cf update-user-provided-service (uups) Command ###
  +
  +Use [cf update-user-provided-service](./cf-help.html#services) (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 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.
  +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 $?`. If the return code is `0`, the command was successful.
   
   ## <a id='help'></a> The cf help Command ##
   
  
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:
  