Clarify Drop Filters wording on Data Clean-up page

[claude]

Requested by Ashley Wang · Slack thread

Before / After

Two small wording changes to the Drop Filters section of the Data Clean-up page (docs/data-governance/data-clean-up.mdx).

Intro sentence

• Before: "Drop Filters let you stop unwanted events from being ingested and stored into Mixpanel going forward."
• After: "Drop Filters let you permanently stop unwanted events from being ingested and stored into Mixpanel going forward."

Last bullet of "You might find this useful if you:"

• Before: "Want to stop ingesting high-volume events that aren't being queried"
• After: "Have malformed or deprecated events you no longer intend to send"

How

Inserted the word "permanently" into the section's opening sentence to emphasize that dropped events are never stored, and replaced the final use-case bullet so the list reflects malformed/deprecated events rather than high-volume ones. The other two bullets and the rest of the paragraph are unchanged.

---

Generated by Claude Code

[greptile-apps]

Confidence Score: 5/5

The PR appears safe to merge.

No blocking failures remain.

Important Files Changed

Filename	Overview
docs/data-governance/data-clean-up.mdx	Updates one Drop Filters use-case example without changing documented behavior.

_{Reviews (2): Last reviewed commit: "Revert 'permanently' wording per review ..." | Re-trigger Greptile}

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
mixpanel-docs	🟢 Ready	View Preview	Jul 24, 2026, 9:54 AM

💡 Tip: Enable Workflows to automatically generate PRs for you.

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
mixpanel-docs	🟡 Building	–	Jul 24, 2026, 9:51 AM

💡 Tip: Enable Workflows to automatically generate PRs for you.