anchor.diff:  <tr>
     <td>service_plans</td>
     <td>array of objects</td>
  -  <td>A list of service plan objects to created along as part of this service
  -	(see POST /v2/service_plans for list of fields).</td>
  +  <td>A list of service plan objects to created along as part of this service; see <a href="#catalog-create-plan">Creating a new plan in the catalog</a>.</td>
   </tr>
   </tbody>
   </table>
  
positive.code: In this case, the broker is responsible for removing the bindings and instances
  that don’t exist anymore in the Cloud Controller.
  There are the Cloud Controller endpoints for getting a list of bindings and
  instances, and the broker should use these to find orphans and prune them.
negative.code: <tr>
    <td>extra</td>
    <td>string</td>
    <td>JSON-encoded-string of extra data to be used by frontend clients. For more information see <a href="catalog-metadata.html">Catalog Metadata</a>.</td>
  </tr>
  <tr>
    <td>unique_id</td>
  