anchor.diff:  
   ## <a id='prereqs'></a> Prerequisites
   
  -Before you can use the Notifications Service:
  +Before you can use the Notifications Service you must:
   
  -* Install [<%= vars.app_runtime_full  %>](<%= vars.product_url %>).
  -* You must have `admin` permissions on your Cloud Foundry instance. <%= vars.asg_notifications_prereq  %>
  +* Install [<%= vars.app_runtime_full %>](<%= vars.product_url %>) (<%= vars.app_runtime_abbr %>).
  +
  +* Have `admin` permissions on your <%= vars.app_runtime_abbr %> instance. <%= vars.asg_notifications_prereq %>
  +
   * Install the [Cloud Foundry Command Line Interface (cf CLI)](https://github.com/cloudfoundry/cli) and [User Account and Authorization Server (UAAC)](https://rubygems.org/gems/cf-uaac) command line tools.
   
   
   ## <a id='create-client'></a> Create a Client and Get a Token
   
  -To interact with the Notifications Service, you must create UAA scopes: 
  +To interact with the Notifications Service, you must create UAA scopes.
   
  -1. Use `uaac target uaa.YOUR-DOMAIN` to target your UAA server:
  -    <pre class="terminal">
  -    $ uaac target uaa.example.com
  -    </pre>
  +To create UAA scopes: 
  +
  +1. Target your UAA server by running:
  +    
  +    ```
  +    aac target uaa.YOUR-DOMAIN
  +    ```
  +    Where `YOUR-DOMAIN` is the domain of your UAA server URL.
   
   1. <%= vars.uaa_admin_client_creds %>
   
  -1. Use `uaac token client get admin -s ADMIN-CLIENT-SECRET` to authenticate and obtain an access token for the admin client from the UAA server. UAAC stores the token in `~/.uaac.yml`.
  -    <pre class="terminal">
  -    $ uaac token client get admin -s MyAdminPassword
  -    </pre>
  +1. Authenticate and obtain an access token for the admin client from the UAA server by running: 
  +    
  +    ```
  +    uaac token client get admin -s ADMIN-CLIENT-SECRET
  +    ```
  +    Where `ADMIN-CLIENT-SECRET` is the admin client secret.
  +    <br><br>
  +    UAAC stores the token in `~/.uaac.yml`.
   
  -1. Create a `notifications-admin` client with the required scopes:
  -    <pre class='terminal'>
  -    $ uaac client add notifications-admin --authorized\_grant\_types client\_credentials --authorities \
  +1. Create a `notifications-admin` client with the required scopes by running:
  +    
  +    ```
  +    uaac client add notifications-admin --authorized\_grant\_types client\_credentials --authorities \
           notifications.manage,notifications.write,notification\_templates.write,notification\_templates.read,critical\_notifications.write
  -    </pre>
  -    * `notifications.write`: send a notification. For example, you can send notifications to a user, space, or everyone in the system. 
  -    * `notifications.manage`: update notifications and assign templates for that notification.
  -    * (Optional) `notification_templates.write`: create a custom template for a notification. 
  -    * (Optional) `notification_templates.read`: check which templates are saved in the database.
  +    ```
  +    * `notifications.write`: Send a notification. For example, you can send notifications to a user, space, or everyone in the system. 
  +    * `notifications.manage`: Update notifications and assign templates for that notification.
  +    * (Optional) `notification_templates.write`: Create a custom template for a notification. 
  +    * (Optional) `notification_templates.read`: Check which templates are saved in the database.
   
  -1. Log in using your newly created client:
  -    <pre class='terminal'>
  -    $ uaac token client get notifications-admin
  -    </pre>
  -
  +1. Log in using your newly created client by running:
  +    
  +    ```
  +    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).
  
positive.code: * A UAA scope
  * An email address
  
  For more information, see the [Notifications V1 Documentation](https://github.com/cloudfoundry-incubator/notifications/blob/master/V1_API.md) on GitHub.
  
  The following example sends the `system-going-down` notification described above to all users in the system:
  
  <pre class='terminal'>
  $ uaac curl https://notifications.user.example.com/everyone -X POST --data \
  '{"kind_id":"system-going-down","text":"The system is going down while we upgrade our storage","html":"<strong>THE SYSTEM IS DOWN</strong><p>The system is going down while we upgrade our storage</p>","subject":"Upgrade to Storage","reply_to":"no-reply@example.com"}'
  </pre>
  
negative.code: 
  A template is made up of a name, a subject, a text representation of the template you are sending for mail clients that do not support HTML, and an HTML version of the template. 
  
  The system provides a default template for all notifications, but you can create a custom template by running: 
  
  ```
  uaac curl https://notifications.user.example.com/templates -X POST --data \
  '{"name":"site-maintenance","subject":"Maintenance: {{.Subject}}","text":"The site has gone down for maintenance. More information to follow {{.Text}}","html":"<p>The site has gone down for maintenance. More information to follow {{.HTML}}"}'
  ```
  
  Variables that take the form `{{.}}` interpolate data provided in the send step before a notification is sent. Data that you can insert into a template during the send step include `{{.Text}}`, `{{.HTML}}`, and `{{.Subject}}`.
  
  This `curl` command returns a unique template ID that can be used in subsequent calls to refer to your custom template. The result looks similar to:
  
  ```
  {"template-id": "E3710280-954B-4147-B7E2-AF5BF62772B5"}
  ```
  
  Check all of your saved templates by running:
  
  ```
  uaac curl https://notifications.user.example.com/templates -X GET
  ```
  
  
  ## <a id='associate'></a> Associate a Custom Template with a Notification
  