feat(aim ga): updating number of filters needed for drop filters

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

@@ -20,7 +20,7 @@ When you disable `ai_monitoring.record_content.enabled`, event data containing e
 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 drop information before it enters NRDB, you need six 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 seven separate drop filters.
 
   <img
       title="Create a drop filter"
@@ -29,7 +29,7 @@ A single drop filter targets a specified attribute within one event type, but se
   />
 
 1. Go to <DoNotTranslate>**[one.newrelic.com](https://one.newrelic.com) > All capabilities > AI monitoring > Drop filters**</DoNotTranslate>, then click <DoNotTranslate>**Create drop filter**</DoNotTranslate>. 
-1. Create a filter name. Because one kind of data requires at least six drop filters, we recommend a naming convention that helps you track the events you're dropping data from. 
+1. Create a filter name. Because one kind of data requires at least seven drop filters, we recommend a naming convention that helps you track the events you're dropping data from. 
 1. Paste in the base NRQL query:
   ```sql
   SELECT <COLUMN> FROM <EVENT_TYPE> WHERE <COLUMN> RLIKE <REGEX>
@@ -62,7 +62,7 @@ In a typical AI interaction, a prompt or request undergoes certain processes (li
       src={aiDropFilterTable}
   />
 
-A complete set of drop filters for a piece of sensitive information should include queries for the six events provided in the drop filter table. Your drop filters correspond to event and column pairs in a given row. A few things to remember:
+A complete set of drop filters for a piece of sensitive information should include queries for the seven events provided in the drop filter table. For each event, you need to create separate filters for attributes when there are more than one. Your drop filters correspond to event and column pairs in a given row. A few things to remember:
 
 * The column `content` appears in the `LlmChatCompletionMessage` event and not in the `LlmEmbedding` event. 
 * The column `messages` only appears in `LlmFeedbackMessage` but not in `LlmTool`.