diff --git a/src/content/docs/new-relic-control/pipeline-control/cloud-rules-api.mdx b/src/content/docs/new-relic-control/pipeline-control/cloud-rules-api.mdx
index d2b019cebb9..baaed9667a4 100644
--- a/src/content/docs/new-relic-control/pipeline-control/cloud-rules-api.mdx
+++ b/src/content/docs/new-relic-control/pipeline-control/cloud-rules-api.mdx
@@ -18,7 +18,7 @@ There are two categories of rules you can create:
     ```sql
     DELETE dropAttr1, dropAttr2 FROM DATA_TYPE (WHERE OPTIONAL_FILTER)
     ```
-  * For this type of rule, you must pass in a non-empty list of **raw** attributes names in the `SELECT` clause.
+  * For this type of rule, you must pass in a non-empty list of **raw** attributes names in the `DELETE` clause.
 
 <Callout variant="tip">
     Pipeline Control cloud rules only apply to data that arrives from the moment you create the rule, they don't delete data that's [already been ingested](/docs/telemetry-data-platform/ingest-manage-data/manage-data/manage-data-retention#data-deletion).