diff --git a/content/v2.0/monitor-alert/_index.md b/content/v2.0/monitor-alert/_index.md
index ad72da7b7..cd52ba5b2 100644
--- a/content/v2.0/monitor-alert/_index.md
+++ b/content/v2.0/monitor-alert/_index.md
@@ -9,7 +9,6 @@ menu:
     name: Monitor & alert
 weight: 6
 v2.0/tags: [monitor, alert, checks, notification, endpoints]
-cloud_all: true
 ---
 
 Monitor your time series data and send alerts by creating checks, notification
diff --git a/content/v2.0/monitor-alert/checks/_index.md b/content/v2.0/monitor-alert/checks/_index.md
index 490bb8645..2c84bb054 100644
--- a/content/v2.0/monitor-alert/checks/_index.md
+++ b/content/v2.0/monitor-alert/checks/_index.md
@@ -11,7 +11,6 @@ v2.0/tags: [monitor, checks, notifications, alert]
 related:
   - /v2.0/monitor-alert/notification-rules/
   - /v2.0/monitor-alert/notification-endpoints/
-cloud_all: true
 ---
 
 Checks in InfluxDB query data and apply a status or level to each data point based on specified conditions.
diff --git a/content/v2.0/monitor-alert/checks/create.md b/content/v2.0/monitor-alert/checks/create.md
index 41631062b..c2b8964f1 100644
--- a/content/v2.0/monitor-alert/checks/create.md
+++ b/content/v2.0/monitor-alert/checks/create.md
@@ -10,7 +10,6 @@ weight: 201
 related:
   - /v2.0/monitor-alert/notification-rules/
   - /v2.0/monitor-alert/notification-endpoints/
-cloud_all: true
 ---
 
 Create a check in the InfluxDB user interface (UI).
diff --git a/content/v2.0/monitor-alert/checks/delete.md b/content/v2.0/monitor-alert/checks/delete.md
index 3d42b1bac..8e884679f 100644
--- a/content/v2.0/monitor-alert/checks/delete.md
+++ b/content/v2.0/monitor-alert/checks/delete.md
@@ -10,7 +10,6 @@ weight: 204
 related:
   - /v2.0/monitor-alert/notification-rules/
   - /v2.0/monitor-alert/notification-endpoints/
-cloud_all: true
 ---
 
 If you no longer need a check, use the InfluxDB user interface (UI) to delete it.
diff --git a/content/v2.0/monitor-alert/checks/update.md b/content/v2.0/monitor-alert/checks/update.md
index 935509b05..d2c9af61c 100644
--- a/content/v2.0/monitor-alert/checks/update.md
+++ b/content/v2.0/monitor-alert/checks/update.md
@@ -10,7 +10,6 @@ weight: 203
 related:
   - /v2.0/monitor-alert/notification-rules/
   - /v2.0/monitor-alert/notification-endpoints/
-cloud_all: true
 ---
 
 Update checks in the InfluxDB user interface (UI).
diff --git a/content/v2.0/monitor-alert/checks/view.md b/content/v2.0/monitor-alert/checks/view.md
index b27e7a202..a41f90713 100644
--- a/content/v2.0/monitor-alert/checks/view.md
+++ b/content/v2.0/monitor-alert/checks/view.md
@@ -10,7 +10,6 @@ weight: 202
 related:
   - /v2.0/monitor-alert/notification-rules/
   - /v2.0/monitor-alert/notification-endpoints/
-cloud_all: true
 ---
 
 View check details and statuses and notifications generated by checks in the InfluxDB user interface (UI).
diff --git a/content/v2.0/monitor-alert/notification-endpoints/_index.md b/content/v2.0/monitor-alert/notification-endpoints/_index.md
index 2362d0f5e..f3d6fef42 100644
--- a/content/v2.0/monitor-alert/notification-endpoints/_index.md
+++ b/content/v2.0/monitor-alert/notification-endpoints/_index.md
@@ -11,7 +11,6 @@ weight: 102
 related:
   - /v2.0/monitor-alert/checks/
   - /v2.0/monitor-alert/notification-rules/
-cloud_all: true
 ---
 
 Notification endpoints store information to connect to a third party service.
diff --git a/content/v2.0/monitor-alert/notification-endpoints/create.md b/content/v2.0/monitor-alert/notification-endpoints/create.md
index d692eaafa..829158886 100644
--- a/content/v2.0/monitor-alert/notification-endpoints/create.md
+++ b/content/v2.0/monitor-alert/notification-endpoints/create.md
@@ -10,7 +10,6 @@ weight: 201
 related:
   - /v2.0/monitor-alert/checks/
   - /v2.0/monitor-alert/notification-rules/
-cloud_all: true
 ---
 
 To send notifications about changes in your data, start by creating a notification endpoint to a third party service. After creating notification endpoints, [create notification rules](/v2.0/monitor-alert/notification-rules/create) to send alerts to third party services on [check statuses](/v2.0/monitor-alert/checks/create).
@@ -26,11 +25,11 @@ To send notifications about changes in your data, start by creating a notificati
     The following endpoints are available for InfluxDB 2.0 OSS, the InfluxDB Cloud 2.0 Free Plan,
     and the InfluxDB Cloud 2.0 Pay As You Go (PAYG) Plan:
 
-    | Endpoint      | OSS      | Free Plan _(Cloud)_      | PAYG Plan _(Cloud)_          |
-    |:--------      |:--------:|:-------------------:     |:----------------------------:|
-    | **Slack**     | _Coming_ | **{{< icon "check" >}}** | **{{< icon "check" >}}**     |
-    | **PagerDuty** | _Coming_ |                          | **{{< icon "check" >}}**     |
-    | **HTTP**      | _Coming_ |                          | **{{< icon "check" >}}**     |
+    | Endpoint      | OSS                      | Free Plan _(Cloud)_      | PAYG Plan _(Cloud)_          |
+    |:--------      |:--------:                |:-------------------:     |:----------------------------:|
+    | **Slack**     | **{{< icon "check" >}}** | **{{< icon "check" >}}** | **{{< icon "check" >}}**     |
+    | **PagerDuty** | **{{< icon "check" >}}** |                          | **{{< icon "check" >}}**     |
+    | **HTTP**      | **{{< icon "check" >}}** |                          | **{{< icon "check" >}}**     |
 
 4.  In the **Name** and **Description** fields, enter a name and description for the endpoint.
 5.  Enter enter information to connect to the endpoint:
@@ -40,7 +39,7 @@ To send notifications about changes in your data, start by creating a notificati
     - For Slack, create an [Incoming WebHook](https://api.slack.com/incoming-webhooks#posting_with_webhooks) in Slack, and then enter your webHook URL in the **Slack Incoming WebHook URL** field.
 
     - For PagerDuty:
-      - [Create a new service](https://support.pagerduty.com/docs/services-and-integrations#section-create-a-new-service), [add an integration for your service](https://support.pagerduty.com/docs/services-and-integrations#section-add-integrations-to-an-existing-service), and then enter the PagerDuty integration key for your new service in the **Routing Key** field. 
+      - [Create a new service](https://support.pagerduty.com/docs/services-and-integrations#section-create-a-new-service), [add an integration for your service](https://support.pagerduty.com/docs/services-and-integrations#section-add-integrations-to-an-existing-service), and then enter the PagerDuty integration key for your new service in the **Routing Key** field.
       - The **Client URL** provides a useful link in your PagerDuty notification. Enter any URL that you'd like to use to investigate issues. This URL is sent as the `client_url` property in the PagerDuty trigger event. By default, the **Client URL** is set to your Monitoring & Alerting History page, and the following included in the PagerDuty trigger event: `"client_url": "https://twodotoh.a.influxcloud.net/orgs/<your-org-ID>/alert-history”`
 
 6. Click **Create Notification Endpoint**.
diff --git a/content/v2.0/monitor-alert/notification-endpoints/delete.md b/content/v2.0/monitor-alert/notification-endpoints/delete.md
index 88d2448b0..24a0dc71b 100644
--- a/content/v2.0/monitor-alert/notification-endpoints/delete.md
+++ b/content/v2.0/monitor-alert/notification-endpoints/delete.md
@@ -10,7 +10,6 @@ weight: 204
 related:
   - /v2.0/monitor-alert/checks/
   - /v2.0/monitor-alert/notification-rules/
-cloud_all: true
 ---
 
 If notifications are no longer sent to an endpoint, complete the steps below to delete the endpoint, and then [update notification rules](/v2.0/monitor-alert/notification-rules/update) with a new notification endpoint as needed.
diff --git a/content/v2.0/monitor-alert/notification-endpoints/update.md b/content/v2.0/monitor-alert/notification-endpoints/update.md
index a35ff0011..d2624e5e4 100644
--- a/content/v2.0/monitor-alert/notification-endpoints/update.md
+++ b/content/v2.0/monitor-alert/notification-endpoints/update.md
@@ -10,7 +10,6 @@ weight: 203
 related:
   - /v2.0/monitor-alert/checks/
   - /v2.0/monitor-alert/notification-rules/
-cloud_all: true
 ---
 
 To update the notification endpoint details, complete the procedures below as needed. To update the notification endpoint selected for a notification rule, see [update notification rules](/v2.0/monitor-alert/notification-rules/update/).
diff --git a/content/v2.0/monitor-alert/notification-endpoints/view.md b/content/v2.0/monitor-alert/notification-endpoints/view.md
index a4c5342d9..982fa4c42 100644
--- a/content/v2.0/monitor-alert/notification-endpoints/view.md
+++ b/content/v2.0/monitor-alert/notification-endpoints/view.md
@@ -11,7 +11,6 @@ weight: 202
 related:
   - /v2.0/monitor-alert/checks/
   - /v2.0/monitor-alert/notification-rules/
-cloud_all: true
 ---
 
 View notification endpoint details and history in the InfluxDB user interface (UI).
diff --git a/content/v2.0/monitor-alert/notification-rules/_index.md b/content/v2.0/monitor-alert/notification-rules/_index.md
index 0b7115605..bc99a9114 100644
--- a/content/v2.0/monitor-alert/notification-rules/_index.md
+++ b/content/v2.0/monitor-alert/notification-rules/_index.md
@@ -10,7 +10,6 @@ menu:
 related:
   - /v2.0/monitor-alert/checks/
   - /v2.0/monitor-alert/notification-endpoints/
-cloud_all: true
 ---
 
 The following articles provide information on managing your notification rules:
diff --git a/content/v2.0/monitor-alert/notification-rules/create.md b/content/v2.0/monitor-alert/notification-rules/create.md
index 5bed355ea..471f65aff 100644
--- a/content/v2.0/monitor-alert/notification-rules/create.md
+++ b/content/v2.0/monitor-alert/notification-rules/create.md
@@ -9,7 +9,6 @@ menu:
 related:
   - /v2.0/monitor-alert/checks/
   - /v2.0/monitor-alert/notification-endpoints/
-cloud_all: true
 ---
 
 Once you've set up checks and notification endpoints, create notification rules to alert you.
diff --git a/content/v2.0/monitor-alert/notification-rules/delete.md b/content/v2.0/monitor-alert/notification-rules/delete.md
index 7ebfca923..dea28950d 100644
--- a/content/v2.0/monitor-alert/notification-rules/delete.md
+++ b/content/v2.0/monitor-alert/notification-rules/delete.md
@@ -9,7 +9,6 @@ menu:
 related:
   - /v2.0/monitor-alert/checks/
   - /v2.0/monitor-alert/notification-endpoints/
-cloud_all: true
 ---
 
 ## Delete a notification rule in the UI
diff --git a/content/v2.0/monitor-alert/notification-rules/update.md b/content/v2.0/monitor-alert/notification-rules/update.md
index 7b9960fb5..f88a832d0 100644
--- a/content/v2.0/monitor-alert/notification-rules/update.md
+++ b/content/v2.0/monitor-alert/notification-rules/update.md
@@ -9,7 +9,6 @@ menu:
 related:
   - /v2.0/monitor-alert/checks/
   - /v2.0/monitor-alert/notification-endpoints/
-cloud_all: true
 ---
 
 ## Add a label to notification rules
diff --git a/content/v2.0/monitor-alert/notification-rules/view.md b/content/v2.0/monitor-alert/notification-rules/view.md
index 5dad401c4..bbbcbe130 100644
--- a/content/v2.0/monitor-alert/notification-rules/view.md
+++ b/content/v2.0/monitor-alert/notification-rules/view.md
@@ -9,7 +9,6 @@ menu:
 related:
   - /v2.0/monitor-alert/checks/
   - /v2.0/monitor-alert/notification-endpoints/
-cloud_all: true
 ---
 
 View notification rule details and statuses and notifications generated by notification rules in the InfluxDB user interface (UI).