Added some small info concerning third party integrations

src/content/docs/alerts/get-notified/incident-workflows.mdx

@@ -260,7 +260,9 @@ The issue notification log displays the following columns:
 2. <DNT>**Status:**</DNT> This column displays the status of the notification.
     * Sent: The notification was sent successfully from New Relic.
     * Failed: The notification was not sent successfully from New Relic.
-    * Deferred: The notification was sent successfully from New Relic but dropped by the vendor.
+    * Bounced: The receiving email server cannot or will not deliver the email. This usually happens because the email address is invalid or the email inbox is full. Bounced email addresses are dropped in future mailings.
+    * Dropped: Email client did not attempt to send the email because the email address has already bounced, because the address has unsubscribed from our emails, or because the address has marked our emails as spam.
+    * Deferred: The email didn't go through on the first attempt, due to temporary issues like connectivity. There will be another attempt, so a deferred notification can become successful or bounced later on.
 3. <DNT>**Destination:**</DNT> This column displays the destination type receiving the workflow notification (for example, Slack or email).
 4. <DNT>**Issue Name:**</DNT> This column displays the name of the issue that triggered the workflow notification.
 5. <DNT>**Trigger Event:**</DNT> This column displays the issue event that triggered the workflow notification. Clicking on the event will provide more information on how workflows are triggered.

src/content/docs/alerts/get-notified/notification-integrations.mdx

@@ -381,16 +381,17 @@ Click a test notification with default field values to see the Jira issue. If su
   This integration requires a REST API Key. PagerDuty has two types of REST API keys:
     * [General access key](https://support.pagerduty.com/docs/generating-api-keys#section-generating-a-general-access-rest-api-key): It includes all the permissions listed above and PagerDuty admins and account owners have access. [See PagerDuty instructions](https://support.pagerduty.com/docs/api-access-keys#generate-a-general-access-rest-api-key).
     * [Personal user tokens](https://support.pagerduty.com/docs/generating-api-keys#section-generating-a-personal-rest-api-key): If your account has advanced permissions, you can create unique personal REST API keys. Requests made using personal REST API keys are restricted to the user's permissions. If you choose to provide a user token API key, make sure it has the required permissions described above. [See PagerDuty instructions](https://support.pagerduty.com/docs/api-access-keys#generate-a-user-token-rest-api-key).
-    
+
   <Callout variant="tip">
       For personal user tokens, we recommend you use a dedicated integration user that does not belong to a real user.
   </Callout>
+  During the creation of an account level destination, we create a service integration. Do not delete this integration, as we use that key!
 
 
   ### Set up a destination [#set-up-pagerduty]
 
   To create a PagerDuty destination:
-    
+
     1. Go to <DNT>**[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Alerts**</DNT>, click <DNT>**Destinations**</DNT>, and then select <DNT>**PagerDuty**</DNT>.
     2. Enter the following information:
 
@@ -782,7 +783,9 @@ You can update ServiceNow attributes directly in the target table, such as **Inc
       alt="A screenshot completed authentication."
       src={accountsSlackAuthenticationCompleted}
     />
-
+  <Callout variant="important">
+    Each Slack workspace has a unique destination per New Relic account.
+  </Callout>
 ### Configure the Slack message template in workflows [#configure-slack-message-settings]
 
 <Callout variant="tip">