anchor.diff:  
   #### <a id='interactive'></a> Supply Parameters Interactively
   
  -To supply parameters interactively, list parameters in a comma-separated list after the `-p` flag. 
  -
  -The following example creates a service instance for a database service:  
  -
  -<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>
  +This procedure describes how to create a new service instance by supplying parameters interactively:
  +
  +To supply parameters interactively:
  +
  +1. Log in to the cf CLI:
  +
  +    ```
  +    cf login
  +    ```
  +
  +1. List parameters in a comma-separated list after the `-p` flag:
  +
  +    ```
  +    cf cups MY-SERVICE -p "MY-PARAMETER, MY-SECOND-PARAMETER, MY-THIRD-PARAMETER"
  +    ```
  +    Where:
  +    * `MY-SERVICE` is the name of the service to create.
  +    * `MY-PARAMETER`, `MY-SECOND-PARAMETER`, and `MY-THIRD-PARAMETER` are parameters such as username, password, host, port, and database name.
  +
  +    For example:  
  +
  +    <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>
   
   #### <a id='non-interactive'></a> Supply Parameters Non-Interactively
   
  -To supply parameters non-interactively, pass parameters and their values in as a JSON hash, bound by single quotes, after the `-p` tag. 
  -
  -The following example is a non-interactive version of the `cf cups` example in [Supply Parameters Interactively](#interactive):
  -
  -<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>
  +This procedure describes how to create a new service instance by supplying parameters non-interactively:
  +
  +To supply parameters non-interactively:
  +
  +1. Log in to the cf CLI:
  +
  +    ```
  +    cf login
  +    ```
  +
  +1. Pass parameters and their values in as a JSON hash, bound by single quotes, after the `-p` tag.
  +
  +    ```
  +    cf cups MY-SERVICE -p '{"host":"HOSTNAME", "port":"PORT"}'
  +    ``` 
  +    Where:
  +    * `MY-SERVICE` is the name of the service to create. 
  +    * `HOSTNAME` and `PORT` are service parameters.
  +
  +    For example: 
  +    <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>
   
   
   #### <a id='third-party'></a> Supply Parameters Through a Third-Party
   
  -To create a service instance that sends data to a third-party, use the `-l` option followed by the external destination URL. 
  -
  -The following example creates a service instance that sends log information to the syslog drain URL of a third-party log management service. 
  -
   For specific log service instructions, see [Service-Specific Instructions for Streaming Application Logs](https://docs.cloudfoundry.org/devguide/services/log-management-thirdparty-svc.html).
   
  -<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>
  +To create a service instance that sends data to a third-party:
  +
  +1. Log in to the cf CLI:
  +
  +    ```
  +    cf login
  +    ```
  +1. Create a service instance that sends data to a third-party:
  +
  +    ```
  +    cf cups MY-SERVICE -l THIRD-PARTY-DESTINATION-URL
  +    ```
  +    Where:
  +    * `MY-SERVICE` is the name of the service to create.
  +    * `THIRD-PARTY-DESTINATION-URL` is the external URL of the third-party service.
  +
  +    For example, the following command creates a service instance that sends log information to the syslog drain URL of a third-party log management service: 
  +
  +    <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>
   
   ### <a id='bind-unbind'></a> Bind and Unbind Service Instances
   
  
positive.code: 
  ## <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 , cf auth, and [cf target](http://cli.cloudfoundry.org/en-US/cf/target.html) commands.
  
  [cf api](http://cli.cloudfoundry.org/en-US/cf/api.html)
  [cf auth](http://cli.cloudfoundry.org/en-US/cf/auth.html)
  
  After you log in, the cf CLI saves a `config.json` file that contains your API endpoint, org, space values, and access token.
  
  
negative.code: 
  For more information, see [update-user-provided-service](http://cli.cloudfoundry.org/en-US/cf/update-user-provided-service.html) in the _Cloud Foundry CLI Reference Guide_.
  
  <p class="note"><b>Note:</b> The <code>cf uups</code> command does not update any parameter values that you do not supply.</p>
  
  ## <a id='return-codes'></a> Retrieve cf CLI Return Codes
  
  