anchor.diff:  uaac curl https://notifications.user.example.com/templates -X GET
   ```
   
  -
   ## <a id='associate'></a> Associate a Custom Template with a Notification
   
  -In this example, the `system-going-down` notification belonging to the `notifications-admin` client is associated with the template ID `E3710280-954B-4147-B7E2-AF5BF62772B5`. This is the template ID of the template we created in the previous section.
  +In this example, the `system-going-down` notification belonging to the `notifications-admin` client
  +is associated with the template ID `E3710280-954B-4147-B7E2-AF5BF62772B5`. This is the template ID
  +of the template we created in the previous section.
   
   Associating a template with a notification requires the `notifications.manage` scope.
   
  
positive.code: owner: Notifications
  ---
  
  This topic describes how to use the Notifications Service, including how to create a client, obtain a token, register notifications, create a custom template, and send notifications to your users.
  
  <%= vars.notifications_api_1 %>
  
  
  ## <a id='prereqs'></a> Prerequisites
  
  
negative.code:     ```
      uaac token client get notifications-admin
      ```
      <p class='note'><strong>Note:</strong> Stay logged in to this client to follow the examples in
      this topic.</p>
  
  For more information about UAA scopes, see 
  [User Account and Authentication (UAA) Server](../concepts/architecture/uaa.html).
  
  ## <a id='registering'></a> Register Notifications
  
  <p class='note'><strong>Note:</strong> To register notifications, you must have the
  <code>notifications.manage</code> scope on the client. To set critical notifications, you must have
  the <code>critical_notifications.write</code> scope.</p>
  
  You must register a notification before sending it. Using the token `notifications-admin` from the
  previous step, the following example registers two notifications with the following properties:
  
  ```
  uaac curl https://notifications.user.example.com/notifications -X PUT --data '{  "source_name": "Cloud Ops Team",
  