Update Rule Priority for span attribute filters

There was a question as to whether all or any rules needed to match for a filter to be applied. This aims to make that more clear.

src/content/docs/distributed-tracing/infinite-tracing/infinite-tracing-configure-span-attribute-trace-filter.mdx

@@ -43,6 +43,6 @@ When you add a custom rule, it takes effect immediately for that trace observer.
 
 ## Rule Priority
 
-When a trace has spans with attributes that match both **Keep** and **Discard** filter rules, the trace is discarded.
+Each rule is evaluated independently. If any rule matches, its observer action, **Keep** or **Discard**, is carried out. When a trace has spans with attributes that match both **Keep** and **Discard** filter rules, the trace is discarded. 
 
 For example, suppose you don't want to save some expected errors that have a certain phrase in the error message. You could create a **Discard** filter rule that targets the error message while still retaining all other traces with an error.