anchor.diff:  
   The following example shows what a CloudEvents change event record emitted by a PostgreSQL connector looks like. In this example, the PostgreSQL connector is configured to use JSON as the CloudEvents format envelope and also as the `data` format.  
   
  -[source,json,indent=0]
  +[source,json,indent=0,subs="attributes"]
   ----
   {
     "id" : "name:test_server;lsn:29274832;txId:565",   <1>
  
positive.code:   "datacontenttype" : "application/avro",            <1>
    "dataschema" : "http://my-registry/schemas/ids/1", <2>
    "iodebeziumop" : "r",
    "iodebeziumversion" : "1.1.0-SNAPSHOT",
    "iodebeziumconnector" : "postgresql",
    "iodebeziumname" : "test_server",
    "iodebeziumtsms" : "1578924258597",
  
negative.code: // Title: Example of configuring `CloudEventsConverter`
  == Example configuration
  
  Configure `io.debezium.converters.CloudEventsConverter` in your {prodname} connector configuration. Following is an example of configuring `CloudEventsConverter` to emit change event records that:
  
  * Use JSON as the envelope
  * Use the schema registry at \http://schema-registry:8081 to serialize the `data` attribute as binary Avro data
  
  In this example, you could omit the specification of `serializer.type` because `json` is the default. 
  
  