anchor.diff:    <td>Service instance has been created. The expected response body is below.</td>
   </tr>
   <tr>
  -  <td>409 Conflict</td>
  -  <td>Should be returned if the requested service instance already exists. The expected response body is "{}"</td>
  -</tr>
  -<tr>
     <td>200 OK</td>
     <td>
       May be returned if the service instance already exists and the requested parameters are identical to the existing service instance.
       The expected response body is below.
     </td>
   </tr>
  -</tbody>
  -</table>
  -
  -All other status codes will be interpreted as an error and Cloud Controller will inform the user that the provision failed.
  -
  -We have chosen to require empty JSON in the response for future compatibility; it will be easier to add fields in the
  -future if JSON is expected rather than to support the cases when a JSON body may or may not be returned.
  -
  -##### Body #####
  +<tr>
  +  <td>409 Conflict</td>
  +  <td>Should be returned if the requested service instance already exists. The expected response body is "{}"</td>
  +</tr>
  +</tbody>
  +</table>
  +
  +Responses with any other status code will be interpreted as a failure. Brokers can include a user-facing message in the `description` field; for details see [Broker Errors](#broker-errors).
  +
  +##### Body #####
  +
  +All responses must include valid JSON in the body. This is for future compatibility; it will be easier to add fields in the future if JSON is expected rather than to support the cases when a JSON body may or may not be returned.
  +
  +For success responses, the following fields are valid.
   
   <table border="1" class="nice">
   <thead>
  
positive.code: 
  ### Response ###
  
  <table>
  <thead>
  <tr>
    <th>Status Code</th>
  
negative.code: </tbody>
  </table>
  
  Responses with any other status code will be interpreted as a failure and the binding will remain in the Cloud Controller database. Brokers can include a user-facing message in the `description` field; for details see [Broker Errors](#broker-errors).
  
  ##### Body #####
  
  All responses must include valid JSON in the body. This is for future compatibility; it will be easier to add fields in the future if JSON is expected rather than to support the cases when a JSON body may or may not be returned.
  
  For a success response, the expected response body is `"{}"`.
  
  ## <a id='deprovisioning'></a>Deprovisioning ##
  
  