diff --git a/content/rancher/v2.x/en/cluster-admin/tools/alerts/default-alerts/_index.md b/content/rancher/v2.x/en/cluster-admin/tools/alerts/default-alerts/_index.md
index 63ad50061d8..13277b3fbc4 100644
--- a/content/rancher/v2.x/en/cluster-admin/tools/alerts/default-alerts/_index.md
+++ b/content/rancher/v2.x/en/cluster-admin/tools/alerts/default-alerts/_index.md
@@ -54,9 +54,4 @@ Alerts can be triggered based on node metrics. Each computing resource in a Kube
 | Node disk is running full within 24 hours | A critical alert is triggered if the disk space on the node is expected to run out in the next 24 hours based on the disk growth over the last 6 hours. |
 
 # Project-level Alerts
-When you enable monitoring for the project, some project-level alerts are provided.
-
-| Alert | Explanation |
-|-------|-------------|
-| Less than half workload available | A critical alert is triggered if less than half of a workload is available, based on workloads where the key is `app` and the value is `workload`. |
-| Memory usage close to the quota | A warning alert is triggered if the workload's memory usage exceeds the memory resource quota that is set for the workload. You can see the memory limit in the Rancher UI if you go to the workload under the **Security & Host Config** tab. |
\ No newline at end of file
+When you enable monitoring for the project, some project-level alerts are provided. For details, refer to the [section on project-level alerts.]({{<baseurl>}}/rancher/v2.x/en/project-admin/tools/alerts/#default-project-level-alerts)
\ No newline at end of file
diff --git a/content/rancher/v2.x/en/project-admin/tools/alerts/_index.md b/content/rancher/v2.x/en/project-admin/tools/alerts/_index.md
index d68b22c393b..4d07d7ac8cf 100644
--- a/content/rancher/v2.x/en/project-admin/tools/alerts/_index.md
+++ b/content/rancher/v2.x/en/project-admin/tools/alerts/_index.md
@@ -9,6 +9,13 @@ Alerts are sets of rules, chosen by you, to monitor for specific events.
 
 Only [administrators]({{< baseurl >}}/rancher/v2.x/en/admin-settings/rbac/global-permissions/), [cluster owners or members]({{< baseurl >}}/rancher/v2.x/en/admin-settings/rbac/cluster-project-roles/#cluster-roles), or [project owners]({{< baseurl >}}/rancher/v2.x/en/admin-settings/rbac/cluster-project-roles/#project-roles) can manage project alerts.
 
+This section covers the following topics:
+
+- [Alerts scope](#alerts-scope)
+- [Default project-level alerts](#default-project-level-alerts)
+- [Adding project alerts](#adding-project-alerts)
+- [Managing project alerts](#managing-project-alerts)
+
 ## Alerts Scope
 
  The scope for alerts can be set at either the [cluster level]({{< baseurl >}}/rancher/v2.x/en/cluster-admin/tools/alerts/) or project level.
@@ -20,6 +27,17 @@ At the project level, Rancher monitors specific deployments and sends alerts for
 * Pod status
 * The Prometheus expression cross the thresholds
 
+## Default Project-level Alerts
+
+When you enable monitoring for the project, some project-level alerts are provided.
+
+| Alert | Explanation |
+|-------|-------------|
+| Less than half workload available | A critical alert is triggered if less than half of a workload is available, based on workloads where the key is `app` and the value is `workload`. |
+| Memory usage close to the quota | A warning alert is triggered if the workload's memory usage exceeds the memory resource quota that is set for the workload. You can see the memory limit in the Rancher UI if you go to the workload under the **Security & Host Config** tab. |
+
+For information on other default alerts, refer to the section on [cluster-level alerts.]({{<baseurl>}}/rancher/v2.x/en/cluster-admin/tools/alerts/default-alerts)
+
 ## Adding Project Alerts
 
 >**Prerequisite:** Before you can receive project alerts, you must [add a notifier]({{< baseurl >}}/rancher/v2.x/en/cluster-admin/tools/notifiers/#adding-notifiers).
@@ -31,6 +49,7 @@ At the project level, Rancher monitors specific deployments and sends alerts for
 1. Enter a **Name** for the alert that describes its purpose, you could group alert rules for the different purpose.
 
 1. Based on the type of alert you want to create, complete one of the instruction subsets below.
+
 {{% accordion id="pod" label="Pod Alerts" %}}
 This alert type monitors for the status of a specific pod.
 
@@ -153,7 +172,7 @@ If you enable [project monitoring]({{< baseurl >}}/rancher/v2.x/en/project-admin
 
 **Result:** Your alert is configured. A notification is sent when the alert is triggered.
 
-#### Managing Project Alerts
+## Managing Project Alerts
 
 To manage project alerts, browse to the project that alerts you want to manage. Then select **Tools > Alerts**. In versions prior to v2.2.0, you can choose **Resources > Alerts**. You can:
 
@@ -161,4 +180,4 @@ To manage project alerts, browse to the project that alerts you want to manage.
 - Edit alert settings
 - Delete unnecessary alerts
 - Mute firing alerts
-- Unmute muted alerts
+- Unmute muted alerts
\ No newline at end of file