anchor.diff:  |===
   ifdef::community[]
   == Distributed tracing
  -The extension has support for the distributed tracing.
  +The extension has support for distributed tracing.
   See link:/documentation/reference/integrations/tracing[tracing documentation] for more details.
   endif::community[]
  
positive.code: 
  The delegate `Converter` implementation is specified by the `delegate.converter.type` option.
  If any extra configuration options are needed by the converter, they can also be specified, such as the disablement of schemas shown above using `schemas.enable=false`.
  
  // Type: concept
  // Title: Emitting additional fields in {prodname} outbox messages
  
negative.code: == Options for applying the transformation selectively
  
  In addition to the change event messages that a {prodname} connector emits when a database change occurs, the connector also emits other types of messages, including heartbeat messages, and metadata messages about schema changes and transactions.
  Because the structure of these other messages differs from the structure of the change event messages that the SMT is designed to process, it's best to configure the connector to selectively apply the SMT, so that it processes only the intended data change messages.
  You can use one of the following methods to configure the connector to apply the SMT selectively:
  
  * {link-prefix}:{link-smt-predicates}#applying-transformation-selectively[Configure an SMT predicate for the transformation].
  * Use the xref:outbox-event-router-property-route-topic-regex[route.topic.regex] configuration option for the SMT.
  
  ifdef::community[]
  // Type: concept
  // Title: Using Avro as the payload format in {prodname} outbox messages
  // ModuleID: using-avro-as-the-payload-format-in-debezium-outbox-messages
  