updates per e.w.

src/content/docs/ai-monitoring/drop-sensitive-data.mdx

@@ -12,17 +12,15 @@ You have two options for dropping sensitive AI data before you send it to New Re
 
 ## Disable `ai.monitoring.record_content_enabled` [#disable-event]
 
-When you disable `ai_monitoring.record_content.enabled`, event data containing end user prompts and AI responses won't be sent to NRDB. This is a good option if you want to drop the entire event in the data ingest pipeline.
-
-You can read more about agent configurations at our [AI monitoring configuration doc](/docs/ai-monitoring/customize-agent-ai-monitoring).
+When you disable `ai_monitoring.record_content.enabled`, event data containing end user prompts and AI responses won’t be sent to NRDB. You can read more about agent configurations at our [AI monitoring configuration doc](/docs/ai-monitoring/customize-agent-ai-monitoring).
 
 ## Create drop filters [#create-filter]
 
 <Callout variant="caution">
 Use caution when deciding to drop data. The data you drop is not recoverable. Before using this feature, [review your data compliance responsibilities](#responsibilities).  
 </Callout>
 
-A single drop filter targets a specified attribute within one event type, but sensitive information from a single AI interaction is stored in multiple events. To ensure that information is completely dropped before it enters NRDB, you need four separate drop filters.
+A single drop filter targets a specified attribute within one event type, but sensitive information from a single AI interaction is stored in multiple events. To drop information before it enters NRDB, you need six separate drop filters.
 
   <img
       title="Create a drop filter"
@@ -236,7 +234,7 @@ New Relic can't guarantee that this functionality completely resolves your data
 * Review your drop filters and confirm they're accurately identifying and discarding the data you want dropped.
 * Check that your drop filters are still dropping sensitive information after you've created them. 
 
-While drop filters ensure that personal information about your end users aren't stored in NRDB, creating the rules themselves imply the kinds of data you maintain, including the format of your data or systems. This is important when determining control permissions for certain users in your org, as certain permissions let users view and edit all information in the rules you create.
+While drop filters help ensure that personal information about your end users aren't stored in NRDB, creating the rules themselves imply the kinds of data you maintain, including the format of your data or systems. This is important when determining control permissions for certain users in your org, as certain permissions let users view and edit all information in the rules you create.
 
 ## What's next? [#whats-next]