anchor.diff:  To implement the outbox pattern in a {prodname} application, configure a {prodname} connector to: 
   
   * Capture changes in an outbox table
  -* Apply the {prodname} `outbox.EventRouter` single message transformation (SMT)
  +* Apply the {prodname} outbox event router single message transformation (SMT)
   
   A {prodname} connector that is configured to apply the outbox SMT should capture changes in only an outbox table. A connector can capture changes in more than one outbox table only if each outbox table has the same structure.  
   
   ifdef::community[]
   [NOTE]
   ====
  -The `outbox.EventRouter` SMT is under active development. The structure of the emitted message or other details might change as development progresses.
  +The outbox event router SMT is under active development. The structure of the emitted message or other details might change as development progresses.
   ====
   endif::community[]
   
  
positive.code: }
  ----
  
  This example of a {prodname} outbox message is based on the {link-prefix}:{link-outbox-event-router}#outbox-event-router-configuration-options[default `outbox.EventRouter` configuration], which assumes an outbox table structure and event routing based on aggregates. To customize behavior, the `outbox.EventRouter` SMT provides numerous {link-prefix}:{link-outbox-event-router}#outbox-event-router-configuration-options[configuration options].
  
  // Type: concept
  // Title: Outbox table structure expected by {prodname} outbox event router SMT
  // ModuleID: outbox-table-structure-expected-by-debezium-outbox-eventrouter-smt
  [[basic-outbox-table]]
  == Basic outbox table
  
  To apply the default `outbox.EventRouter` SMT configuration, your outbox table is assumed to have the following columns: 
  
  [source]
  ----
  
negative.code: [[avro-as-payload-format]]
  == Using Avro as the payload format
  
  The outbox event router SMT supports arbitrary payload formats. The `payload` column value in an outbox table is passed on transparently. An alternative to working with JSON is to use Avro.
  This can be beneficial for message format governance and for ensuring that outbox event schemas evolve in a backwards-compatible way.
  
  How a source application produces Avro formatted content for outbox message payloads is out of the scope of this documentation.
  