anchor.diff:  <tbody>
   <tr>
     <td>services*</td>
  -  <td>array-of-objects</td>
  -  <td>Schema of service objects defined below:</td>
  +  <td>array-of-service-objects</td>
  +  <td>Schema of service objects defined below.</td>
  +</tr>
  +
  +<h5> Service Objects </h5>
  +
  +<table border="1" class="nice">
  +<thead>
  +<tr>
  +  <th>Response field</th>
  +  <th>Type</th>
  +  <th>Description</th>
  +</tr>
  +</thead>
  +<tbody>
  +<tr>
  +  <td>&nbsp;&nbsp;&nbsp;name*</td>
  +  <td>string</td>
  +  <td>The CLI-friendly name of the service that will appear in the catalog. All lowercase, no spaces.</td>
   </tr>
   <tr>
     <td>&nbsp;&nbsp;&nbsp;id*</td>
     <td>string</td>
     <td>An identifier used to correlate this service in future requests to the catalog. This must be unique within Cloud Foundry, using a GUID is recommended. </td>
  -</tr>
  -<tr>
  -  <td>&nbsp;&nbsp;&nbsp;name*</td>
  -  <td>string</td>
  -  <td>The CLI-friendly name of the service that will appear in the catalog. All lowercase, no spaces.</td>
   </tr>
   <tr>
     <td>&nbsp;&nbsp;&nbsp;description*</td>
  
positive.code: 
  ### Request ###
  
  ##### Route #####
  `GET /v2/catalog`
  
  ##### cURL #####
  <pre class="terminal">
   $ curl -H "X-Broker-API-Version: 2.8" http://username:password@broker-url/v2/catalog
  </pre>
  
negative.code:   <td>A list of metadata for a service offering. For more information, see <a href="catalog-metadata.html">Service Metadata</a>.</td>
  </tr>
  <tr>
    <td>&nbsp;&nbsp;&nbsp;dashboard_client</td>
    <td>object</td>
    <td>Contains the data necessary to activate the <a href="dashboard-sso.html">Dashboard SSO feature</a> for this service</td>
  </tr>
  <tr>
    <td>&nbsp;&nbsp;&nbsp;plan_updateable</td>
    <td>boolean</td>
  