anchor.diff:  
   ## <a id='update-broker'></a>Update a Broker ##
   
  -Updating a broker is how to applying changes a broker author has made to cloud controller. Similar to adding a broker, update causes cloud controller to fetch and validate the catalog from a broker, and update the cloud controller database with any changes found in the catalog.
  +Updating a broker to apply changes a broker author has made to cloud controller.
  +Similar to adding a broker, updating causes cloud controller to fetch and validate the catalog from a broker, and update the cloud controller database with any changes found in the catalog.
   
   Update also provides a means to change the basic auth credentials cloud controller should use to authenticate with a broker, as well as the URL controller uses for the location of the broker's API endpoints.
   
  
positive.code: 
  ## <a id='remove-broker'></a>Removing a Broker ##
  
  Attempting to remove a service broker will fail if there are service instances for any service plan in the catalog. When planning to shut down or delete a broker, make sure that you remove all service instances before you shut it down. Failure to do so will leave [orphaned service instances](api.html#orphans).
  
  With `cf`:
  <pre class="terminal">
  
negative.code: 
  ### <a id='list-services'></a>List Services ###
  
  New service plans are private by default. To make plans available to end users, see [Make Plans Public](#make-plans-public).
  .**Note**: instances of private plans can not be provisioned until either the plans are made public or are the plans are made available to an organization.
  
  `cf` allows an admin to see service plans before they are available to end users.
  
  