anchor.diff:  
   By default, {prodname} delivers every data change event that it receives to the Kafka broker.
   However, in many cases, you might be interested in only a subset of the events emitted by the producer. 
  -To enable you to process only the records that are relevant to you, {prodname} provides the `Filter` simple message transform (SMT).
  +To enable you to process only the records that are relevant to you, {prodname} provides the _filter_ simple message transform (SMT).
   
   Configure this transformation in the {prodname} connector's Kafka Connect configuration.
  -By configuring the `Filter` SMT, you can specify the events that you are interested in by defining filter conditions based on business rules.
  -As the `Filter` SMT processes the event stream, it evaluates each event against the configured filter conditions.
  +By configuring the filter SMT, you can specify the events that you are interested in by defining filter conditions based on business rules.
  +As the filter SMT processes the event stream, it evaluates each event against the configured filter conditions.
   Only events that meet the criteria of the filter conditions are passed to the broker.
   
  -Although Kafka Connect provides its own link:https://cwiki.apache.org/confluence/display/KAFKA/KIP-66%3A+Single+Message+Transforms+for+Kafka+Connect[Simple Message Transforms] (SMT) to encode filtering logic,
  -it has the following drawbacks:
  +The filter SMT supports scripting languages that integrate with https://jcp.org/en/jsr/detail?id=223[JSR 223] (Scripting for the Java(TM) Platform).
   
  -* It is necessary to compile the transformation upfront and deploy it to Kafka Connect.
  +Kafka Connect provides its own link:https://cwiki.apache.org/confluence/display/KAFKA/KIP-66%3A+Single+Message+Transforms+for+Kafka+Connect[Simple Message Transforms] (SMT) to encode filtering logic.
  +However, the following drawbacks apply to using the generic SMT:
  +
  +* It is necessary to compile the transformation up front and deploy it to Kafka Connect.
   * Every change needs code recompilation and redeployment, leading to inflexible operations.
   
  -The `Filter` SMT supports scripting languages that integrate with https://jcp.org/en/jsr/detail?id=223[JSR 223] (Scripting for the Java(TM) Platform).
   
   // Type: concept
   // ModuleID: example-of-configuring-filter-conditions
   // Title: Example of configuring filter conditions 
   == Example
   
  -To filter change event records, configure the `Filter` transformation in the Kafka Connect configuration for the {prodname} connector.
  -Configuration of the `Filter` SMT requires you to specify a regular expression that defines the filtering criteria. 
  +To filter change event records, configure the filter transformation in the Kafka Connect configuration for the {prodname} connector.
  +Configuration of the filter SMT requires you to specify a regular expression that defines the filtering criteria. 
   
   For example, you might add the following configuration in a `.properties` file:name: value
   
  
positive.code: 
  |[[filter-topic-regex]]<<filter-topic-regex, `topic.regex`>>
  |
  |An optional regular expression that determines whether the filter logic is applied to an event based on name of the Kafka topic where the event is routed. 
  If 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 destination topic does not match the value in `topic.regex`, the SMT passes the event to the topic unmodified.
  
  |[[filter-language]]<<filter-language, `language`>>
  |
  
negative.code: 
  // Type: reference
  // ModuleID: 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.
  
  .filter SMT configuration options
  [cols="30%a,25%a,45%a"]
  |===
  |Property
  