anchor.diff:  
   A service broker can be renamed with the `rename-service-broker`
   command.
  -This name is used only by the Cloud Foundry operator to identify brokers, and
  +This name is used only by the <%= vars.platform_name %> operator to identify brokers, and
   has no relation to configuration of the broker itself.
   
   <pre class="terminal">
  
positive.code: 
  ## <a id='remove-broker'></a>Remove a Broker ##
  
  Removing a service broker will remove all services and plans in the broker's catalog from the Cloud Foundry Marketplace.
  
  <pre class="terminal">
  $ cf delete-service-broker mybrokername
  </pre>
  
  <p class="note"><strong>Note</strong>: Attempting to remove a service broker will fail if there are service instances for any service plan in its catalog. When planning to shut down or delete a broker, make sure to remove all service instances first. Failure to do so will leave <a href="./api.html#orphans">orphaned service instances</a> in the Cloud Foundry database. If a service broker has been shut down without first deleting service instances, you can remove the instances with the CLI; see <a href="#purge-service">Purge a Service</a>.</p>
  
  ### <a id='purge-service'></a>Purge a Service ###
  
  If a service broker has been shut down or removed without first deleting service instances from Cloud Foundry, you will be unable to remove the service broker or its services and plans from the Marketplace. In development environments, broker authors often destroy their broker deployments and need a way to clean up the Cloud Controller database.
  
  The following command will delete a service offering, all of its plans, as well as all associated service instances and bindings from the Cloud Controller database, without making any API calls to a service broker. Once all services for a broker have been purged, the broker can be removed normally.
  
  
negative.code: $ cf purge-service-offering service-test
  Warning: This operation assumes that the service broker responsible for this
  service offering is no longer available, and all service instances have been
  deleted, leaving orphan records in <%= vars.platform_name %>'s database. All knowledge of
  the service will be removed from <%= vars.platform_name %>, including service instances and
  service bindings. No attempt will be made to contact the service broker; running
  this command without destroying the service broker will cause orphan service
  instances. After running this command you may want to run either
  delete-service-auth-token or delete-service-broker to complete the cleanup.
  
  Really purge service offering service-test from <%= vars.platform_name %>? y
  OK
  </pre>
  
  