anchor.diff:  endif::community[]
   
   ifdef::product[]
  -{LinkServiceRegistryGetStart}[{registry-name-full}] provides several components that work with Avro:
  -endif::product[]
  -
  -* An Avro converter that you can specify in {prodname} connector configurations. This converter maps Kafka Connect schemas to Avro schemas. The converter then uses the Avro schemas to serialize the record keys and values into Avro's compact binary form.
  +{LinkServiceRegistryGetStart}[{registry-name-full}] provides the following components that work with Avro:
  +endif::product[]
  +
  +* An Avro converter that you can specify in {prodname} connector configurations. 
  +This converter maps Kafka Connect schemas to Avro schemas. 
  +The converter then uses the Avro schemas to serialize the record keys and values into Avro's compact binary form.
   
   * An API and schema registry that tracks:
   +
  -** Avro schemas that are used in Kafka topics
  -** Where the Avro converter sends the generated Avro schemas
  -
  -+
  -Since the Avro schemas are stored in this registry, each record needs to contain only a tiny _schema identifier_.
  +** Avro schemas that are used in Kafka topics.
  +** Where the Avro converter sends the generated Avro schemas.
  +
  ++
  +Because the Avro schemas are stored in this registry, each record needs to contain only a tiny _schema identifier_.
   This makes each record even smaller. For an I/O bound system like Kafka, this means more total throughput for producers and consumers.
   
  -* Avro _Serdes_ (serializers and deserializers) for Kafka producers and consumers. Kafka consumer applications that you write to consume change event records can use Avro Serdes to deserialize the change event records.
  +* Avro _Serdes_ (serializers and deserializers) for Kafka producers and consumers. 
  +Kafka consumer applications that you write to consume change event records can use Avro Serdes to deserialize the change event records.
   
   To use the {registry} with {prodname}, add {registry} converters and their dependencies to the Kafka Connect container image that you are using for running a {prodname} connector.
   
   [NOTE]
   ====
  -The {registry} project also provides a JSON converter. This converter combines the advantage of less verbose messages with human-readable JSON. Messages do not contain the schema information themselves, but only a schema ID.
  +The {registry} project also provides a JSON converter. 
  +This converter combines the advantage of less verbose messages with human-readable JSON. 
  +Messages do not contain the schema information themselves, but only a schema ID.
   ====
   
   // Type: concept
  
positive.code: [id="overview-of-deploying-a-debezium-connector-that-uses-avro-serialization"]
  == Deployment overview
  
  To deploy a {prodname} connector that uses Avro serialization, there are three main tasks: 
  
  ifdef::community[]
  . Deploy an link:https://github.com/Apicurio/apicurio-registry[{registry-name-full}] instance.
  
negative.code: oc logs $(oc get pods -o name -l strimzi.io/name=my-connect-cluster-connect)
  ----
  
  .. Review the log output to verify that the initial snapshot has been executed. 
  You should see something like the following lines: 
  +
  [source,shell,options="nowrap"]
  ----
  