anchor.diff:  
   ==== Payload
   
  -The payload is the message content or value and is what is consumed by observes of the Kafka topic.
  +The payload is the message content or value and is what is consumed by consumers of the Kafka topic.
   
   [TIP]
   ====
  
positive.code: 
  The aggregate type is a string-based value that is used to append to the Kafka topic name and also assists in routing of the given message inside the Outbox Event Router SMT.
  In this example, we use `Order` and when using the default configuration of the SMT, messages would be found in the `outbox.event.Order` topic.
  Please see the `route.topic.replacement` in the link:documentation/reference/1.1/configuration/outbox-event-router.html#configuration-options[SMT configuration options].
  
  ==== Type
  
  
negative.code: ----
  
  If you enabled SQL logging or check the row count of the outbox table, you might find it unusual that after saving the order that a record is inserted into the outbox table but then is immediately deleted.
  This is the default behavior since rows are not required to be retained for Debezium to pick up the change.
  
  If row retention is required, this can be configured using a link:/documentation/reference/1.1/integrations/outbox.html#_runtime_configuration_options[run-time configuration option].
  In order to enable row retention, add the following configuration to the `application.properties` file.
  
  [source,properties]
  