anchor.diff:  
   - To ensure that HTTP and messaging stubs (used when developing the client) do exactly
   what the actual server-side implementation does.
  -- To promote the ATDD (acceptance test-driven developement) method and the microservices architectural style.
  +- To promote the ATDD (acceptance test-driven development) method, and the microservices architectural style.
   - To provide a way to publish changes in contracts that are immediately visible on both sides.
   - To generate boilerplate test code to be used on the server side.
   
  
positive.code: 
  Hopefully, this section provided some of the {project-full-name} basics and got you on your way
  to writing your own applications. If you are a task-oriented type of developer, you might
  want to jump over to https://spring.io and check out some of the
  https://spring.io/guides/[getting started] guides that solve specific "`How do I do that
  with Spring?`" problems. We also have {project-full-name}-specific
  "`<<howto.adoc#howto, how-to>>`" reference documentation.
  
negative.code: The {samples_code}/{standalone_samples_path}/http-server[server-side
  code is available here], and {samples_code}/{standalone_samples_path}/http-client[the client code  is available here].
  
  TIP: In this case, the producer owns the contracts. Physically, all the contracts are
  in the producer's repository.
  
  [[getting-started-cdc-technical-note]]
  