anchor.diff:  
   [source,bash,indent=0]
   ----
  -    $ docker run -it --rm --link zookeeper:zookeeper debezium/kafka:0.2 create-topic -r 1 schema-changes.inventory
  +    $ docker run -it --rm --link zookeeper:zookeeper debezium/kafka:0.3 create-topic -r 1 schema-changes.inventory
   ----
   
   The command runs a container using version {debezium-docker-label} of the `debezium/kafka` image, uses `--rm` to tell Docker to remove the container when it stops, and links to the Zookeeper container so that the utility can find the Kafka broker(s). The command runs the `create-topic` utility, which by default create a topic with one partition - exactly what we want so that total order of all DDL statements is maintained. The `-r 1` argument specifies the topic should have 1 replica.
  
positive.code: :awestruct-layout: doc
  :linkattrs:
  :icons: font
  :debezium-version: 0.2.4
  :debezium-docker-label: 0.2
  
  This tutorial walks you through running Debezium {debezium-version} for change data capture (CDC). You will use Docker (1.9 or later) to start the Debezium services, run a MySQL database server with a simple example database, use Debezium to monitor the database, and see the resulting event streams respond as the data in the database changes.
  
  
negative.code: 
  [source,bash,indent=0]
  ----
      $ docker run -it --name connect -p 8083:8083 -e GROUP_ID=1 -e CONFIG_STORAGE_TOPIC=my-connect-configs -e OFFSET_STORAGE_TOPIC=my-connect-offsets -e ADVERTISED_HOST_NAME=$(echo $DOCKER_HOST | cut -f3  -d'/' | cut -f1 -d':') --link zookeeper:zookeeper --link kafka:kafka debezium/connect:0.3
  ----
  
  This creates a whole new container, and since we've intialized it with the same topic information the new service can connect to Kafka, read the previous service's configuration and start the registered connectors, which will continue where they last left off.
  