anchor.diff:          }
         }'
       ```
  -
       Where:
       * `RESOURCE-ENDPOINT` is the CAPI endpoint for the type of resource you want to label, such as `apps` or `organizations`.
       * `GUID` is the GUID of the resource you want to label.
       * `ANNOTATION-KEY` is the key for the label.
       * `ANNOTATION-VALUE` is the corresponding value for the annotation key.
   
  -    For example, the following command provides a `contacts` annotation for an app.
  -
  -    <pre class="terminal">
  -    $ cf curl v3/apps/1cb006ee-fb05-47e1-b541-c34179ddc446 \
  -      -X PATCH \
  -      -d '{
  -        "metadata": {
  -          "annotations": {
  -            "contacts": "Bill tel(1111111) email(bill@fixme), Bob tel(222222) pager(3333333#555) email(bob@fixme)"
  -          }
  -        }
  -      }'
  -    </pre>
  -
   ### <a id="update"></a> Update Metadata for a Resource
   
  -To update metadata for a resource, follow the procedure for adding metadata and provide a new value for an existing key. See [Add Metadata to a Resource](#add) above.
  +To update metadata for a resource, follow the procedure for adding metadata and provide a new value for an existing key. For more information, see [Add Metadata to a Resource](#add).
   
   ### <a id="remove"></a> Remove Metadata from a Resource
   
  -To remove metadata from a resource, follow the procedure for adding metadata and provide a `null` value for an existing key. See [Add Metadata to a Resource](#add) above.
  +To remove metadata from a resource, follow the procedure for adding metadata and provide a `null` value for an existing key. For more information, see [Add Metadata to a Resource](#add).
   
   ### <a id="view"></a> View Metadata for a Resource
   
  
positive.code:     ```
      cf curl /v3/RESOURCE-ENDPOINT/GUID
      ```
  
      Where:
      * `RESOURCE-ENDPOINT` is the CAPI endpoint for the type of resource you want to view, such as `apps` or `organizations`.
      * `GUID` is the GUID of the resource you want to view.
  
      For example:
  
      <pre class="terminal">
      $ cf curl /v3/apps/1cb006ee-fb05-47e1-b541-c34179ddc446
  
      {
        "guid": "1cb006ee-fb05-47e1-b541-c34179ddc446",
        "name": "my_app",
        "state": "STOPPED",
        "created_at": "2016-03-17T21:41:30Z",
        "updated_at": "2016-06-08T16:41:26Z",
        "lifecycle": {
          "type": "buildpack",
          "data": {
            "buildpacks": ["java_buildpack"],
            "stack": "cflinuxfs3"
          }
        },
        "relationships": {
          "space": {
            "data": {
              "guid": "2f35885d-0c9d-4423-83ad-fd05066f8576"
            }
          }
        },
        "links": {
        		. . .
          }
        },
        "metadata": {
          "labels": {
            "environment": "production"
          },
          "annotations": {
            "contacts": "Bill tel(1111111) email(bill@fixme), Bob tel(222222) pager(3333333#555) email(bob@fixme)"
          }
        }
      }
      </pre>
  
  ### <a id="query"></a> List Resources by Querying Labels
  
  To list resources by querying label metadata:
  
negative.code: 		<ul>
  			<li>DNS subdomain format, with at least one <code>.</code></li>
  			<li>Must end with <code>/</code></li>
  		</ul>
    </td>
  </tr>
  <tr>
  	<td>Key Name</td>
  	<td>1-63</td>
  	<td>
      <ul>
  			<li>Alphanumeric ( \[a-z0-9A-Z\] )</li>
  			<li><code>-</code></li>
  			<li><code>_</code></li>
  			<li><code>.</code></li>
  		</ul>
    </td>
  	<td>Must begin and end with an alphanumeric character</td>
  </tr>
  <tr>
  	<td>Value</td>
  	<td>0-5000</td>
  	<td><em>None (that is, any unicode character is allowed)</em></td>
  	<td><em>N/A</em></td>
  </tr>
  </table>
  
  ### <a id="prefix"></a> Metadata Key Prefixes
  
  You can ensure a label or annotation key is easily differentiated from other keys by using a prefix. A prefix is a namespacing pattern that helps you more clearly identify resources. Prefixes are in DNS subdomain format. For example, `prefix.example.com`.
  
  Consider an example in which you have two scanner tools: one for security and one for compliance. Both tools use a `scanned` label or annotation. You can disambiguate between the two tools using a prefix. The security tool can prefix a label or annotation with `security.example.com/scanned` and the compliance tool can prefix a label or annotation with `compliance.example.com/scanned`.
  
  