diff --git a/docs/cse/rules/rules-status.md b/docs/cse/rules/rules-status.md
index 73407d6a88..6fb78ef8d6 100644
--- a/docs/cse/rules/rules-status.md
+++ b/docs/cse/rules/rules-status.md
@@ -75,12 +75,6 @@ Sometimes there may be a problem creating a baseline for a [first seen rule](/do
 
 Limits are set on how often a rule fires so that the system is not overloaded. For example, if a rule fires too many signals in an hour, it can cause performance problems for all rule processes. If a rule exceeds a limit, its rule status changes from Active to Failed and the rule is disabled. 
 
-| Type | Limit |
-| :-- | :-- |
-| Signals per hour | 100K |
-| Signals per 24 hours | 1M |
-
-<!-- For DOCS-72 - Rule limits
 | Type | Limit |
 | :-- | :-- |
 | Total allowed custom rules of each [rule type](/docs/cse/rules/about-cse-rules/#rule-types) | 100 - Tier 1 <br/>200 - Tier 2<br/>500 - Tier 3 |
@@ -98,8 +92,6 @@ Limits are set on how often a rule fires so that the system is not overloaded. F
 Rule limits can be higher if you are in a higher tenant tier level. If you have questions about what your tenant tier level is, contact your Sumo Logic account representative or [contact Sumo Logic Support](https://support.sumologic.com/support/s/).
 :::
 
--->
-
 ## Query for rule status changes
 
 You can query audit logs for rule status changes. For more information about querying audit logs, see [Cloud SIEM Audit Logging](/docs/cse/administration/cse-audit-logging/) and [Cloud SIEM audit log definitions](/docs/manage/security/audit-indexes/documentation-audit-log-definitions/#cloud-siem-audit-log-definitions).