anchor.diff:  
   // Type: reference
   // ModuleID: options-for-configuring-filter-transformation
  -// Title: Options for configuring `Filter` transformation
  +// Title: Options for configuring filter transformation
   [[filter-configuration-options]]
   == Configuration options
   
  -The following table lists the configuration options for the `Filter` SMT.
  +The following table lists the configuration options for the filter SMT.
   
  -.'Filter' configuration options
  +.filter SMT configuration options
   [cols="30%a,25%a,45%a"]
   |===
   |Property
  
positive.code: [TIP]
  ====
  The {prodname} MongoDB connector emits the `after` and `patch` fields not as structures but as serialized JSON documents.
  When you use the `Filter` SMT with the MongoDB connector, you should first unwind the field by applying the {link-prefix}:{link-mongodb-event-flattening}[`ExtractNewDocumentState`] SMT.
  
  As an alternative, you can use a JSON parser in the expression.
  To use a JSON parser when Groovy is the expression language, add the `groovy-json` artifact to the classpath, and add an expression such as `(new groovy.json.JsonSlurper()).parseText(value.after).last_name == 'Kretchmar'`.
  
negative.code: 
  |[[filter-topic-regex]]<<filter-topic-regex, `topic.regex`>>
  |
  |An optional regular expression that evaluates the name of the destination topic for an event to determine whether to apply filtering logic. 
  If the name of the destination topic matches the value in `topic.regex`, the transformation applies the filter logic before it passes the event to the topic.
  If the name of the topic does not match the value in `topic.regex`, the SMT passes the event to the topic unmodified.
  
  |[[filter-language]]<<filter-language, `language`>>
  |
  