anchor.diff:  
   Spring Cloud Sleuth implements a distributed tracing solution for http://cloud.spring.io[Spring Cloud].
   
  -=== Terminology
  +=== Terminologyc
   
   Spring Cloud Sleuth borrows http://research.google.com/pubs/pub36356.html[Dapper's] terminology.
   
  
positive.code:   other target branch in the main project).
  * When writing a commit message please follow http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html[these conventions],
    if you are fixing an existing issue please add `Fixes gh-XXXX` at the end of the commit
    message (where XXXX is the issue number).
negative.code: 
  1. Optionally run https://github.com/openzipkin/zipkin[Zipkin], e.g. via docker compose (there's a `docker-compose.yml` in https://github.com/spring-cloud-incubator/spring-cloud-sleuth[Spring Cloud Sleuth], or in https://github.com/openzipkin/docker-zipkin[Docker Zipkin]
  7. Run the zipkin sample application (and set `sample.zipkin.enabled=false` if you have no collector running)
  8. Hit `http://localhost:3380`, `http://localhost:3380/call`, `http://localhost:3380/async` for some interesting sample traces (the app calls back to itself).
  9. Goto `http://localhost:8082` for zipkin web (8080 if running locally from source, the host is the docker host, so if you are using boot2docker it will be different)
  
  NOTE: You can see the zipkin spans without the UI (in logs) if you run the sample with `sample.zipkin.enabled=false`.
  