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: 
  This section provides the following:
  
  - A procedure for labeling an app, package, and droplet with a Git commit SHA. See [Manually Label Objects](#manual).
  - A script that automates the procedure. See [Automate Labeling Objects](#example-script).
  
  Labeling your app and related resources with a Git commit SHA allows you to track which version of your code is running on <%= vars.app_runtime_abbr %>.  
  
  For more information about app packages and droplets, see the [CAPI documentation](https://v3-apidocs.cloudfoundry.org/version/3.68.0/index.html).
  
  
negative.code: 
  To label an app, droplet, and package with a Git commit SHA:
  
  1. Run:
  
      ```
      cf app APP_NAME --guid
      ```
      Where `APP_NAME` is the name of the app.
  
  1. Record the app GUID you retrieved in the previous step,
  
  1. Return the GUID of the droplet and package associated with the app by running:
  
      ```
      cf curl /v3/apps/APP-GUID/droplets/current
      ```
      Where `APP-GUID` is the GUID of the app.
  
  1. Record the GUID of the droplet and package:
      * The droplet GUID is the value for the `"guid"` key.
      * The package GUID is the end of the `"href"` URL for the `"package"` key.
      <br>
      <br>
      For example, the droplet and package GUIDs are highlighted in blue in the following output:
      <pre class='terminal'>
      {
        "guid": "<span class='guid'>fd35633f-5c5c-4e4e-a5a9-0722c970a9d2</span>",
  