anchor.diff:  service instance is no longer available or is not responding with a 200 or 410,
   and the service instance has been deleted, leaving orphan records in Cloud
   Foundry's database. All knowledge of the service instance will be removed from
  -Cloud Foundry, including service bindings and service keys.
  -
  -Really purge service instance mysql-dev from Cloud Foundry?> y
  +<%= vars.platform_name %>, including service bindings and service keys.
  +
  +Really purge service instance mysql-dev from <%= vars.platform_name %>?> y
   Purging service mysql-dev...
   OK
   </pre>
  
positive.code: 
  ### <a id='multiple-brokers'></a>Multiple Brokers, Services, Plans ###
  
  Many service brokers may be added to a Cloud Foundry instance, each offering
  many services and plans.
  The following constraints should be kept in mind:
  
  - It is not possible to have multiple brokers with the same name
  - Prior to Cloud Foundry API (CAPI) v1.71, the service ID and plan IDs of each service advertised by the broker must be unique across Cloud Foundry.
  - With Cloud Foundry API (CAPI) v1.71 or later, the service ID and plan IDs of each service advertised by the broker must be unique only within the broker and can overlap ids defined in other brokers
  - GUIDs are recommended for the service ID and plan IDs of each service.
  
      
  <div class="note"><strong>Note</strong>: 
  If your deployment uses Cloud Foundry API (CAPI) v1.71 or later, you can add multiple brokers with the same URL. In this case, the brokers must have different names. CAPI v1.70 and earlier do not support this feature.
  </div>
  
  See [Possible Errors](#possible-errors) below for error messages and what do to
  
negative.code: encrypted in Cloud Controller database, and used by the Cloud Controller to
  authenticate with the broker when making all API calls.
  Your service broker should validate the username and password sent in every
  request; otherwise, anyone could curl your broker to delete service instances. When the broker is registered with an URL having the scheme `https`, Cloud Controller will make all calls to the broker over HTTPS.
  
  As of cf-release 229, CC API 2.47.0, <%= vars.platform_name %> supports two types of brokers: _standard brokers_ and _space-scoped brokers_. A list of their differences follows:
  
  **Standard Brokers**
  
  