anchor.diff:  
   This section explores how Spring Cloud Contract Verifier with Stub Runner works.
   
  -==== A three second tour
  -
  +[[spring-cloud-contract-verifier-intro-three-second-tour]]
  +==== A Three-second Tour
  +
  +This very brief tour walks through using Spring Cloud Contract:
  +
  +* <<spring-cloud-contract-verifier-intro-three-second-tour-producer>>
  +* <<spring-cloud-contract-verifier-intro-three-second-tour-consumer>>
  +
  +You can find a somewhat longer tour
  +<<spring-cloud-contract-verifier-intro-three-minute-tour,here>>.
  +
  +[[spring-cloud-contract-verifier-intro-three-second-tour-producer]]
   ===== On the Producer Side
   
  -In order to start working with `Spring Cloud Contract`, add files with REST/ messaging contracts expressed in either
  -Groovy DSL or YAML to the contracts directory set by the
  -`contractsDslDir` property, by default `$rootDir/src/test/resources/contracts`.
  -
  -Then, add Spring Cloud Contract Verifier dependency and plugin to your build file:
  +To start working with Spring Cloud Contract, add files with `REST/` messaging contracts
  +expressed in either Groovy DSL or YAML to the contracts directory, which is set by the
  +`contractsDslDir` property. By default, it is `$rootDir/src/test/resources/contracts`.
  +
  +Then add the Spring Cloud Contract Verifier dependency and plugin to your build file, as
  +shown in the following example:
   
   [source,xml,indent=0]
   ----
   include::{introduction_url}/samples/standalone/dsl/http-server/pom.xml[tags=verifier_test_dependencies,indent=0]
   ----
  +
  +The following listing shows how to add the plugin, which should go in the build/plugins
  +portion of the file:
   
   [source,xml,indent=0]
   ----
  
positive.code: public class LoanApplicationServiceTests {
  ----
  
  Now in your integration test, you will be able to receive stubbed versions of HTTP responses or messages that are
  expected to be emitted by the collaborator service. You will see entries similar to theses in the build logs:
  
  [source,bash,indent=0]
  ----
  
negative.code: public class LoanApplicationServiceTests {
  ----
  
  TIP: Use the `REMOTE` `stubsMode` when downloading stubs from an online repository and
  `LOCAL` for offline work.
  
  Now, in your integration test, you can receive stubbed versions of HTTP responses or
  messages that are expected to be emitted by the collaborator service.
  
  [[spring-cloud-contract-verifier-intro-three-minute-tour]]
  ==== A Three-minute Tour
  
  This brief tour walks through using Spring Cloud Contract:
  
  * <<spring-cloud-contract-verifier-intro-three-minute-tour-producer>>
  * <<spring-cloud-contract-verifier-intro-three-minute-tour-consumer>>
  
  You can find an even more brief tour
  <<spring-cloud-contract-verifier-intro-three-second-tour,here>>.
  
  [[spring-cloud-contract-verifier-intro-three-minute-tour-producer]]
  ===== On the Producer Side
  
  To start working with `Spring Cloud Contract`, add files with `REST/` messaging contracts
  expressed in either Groovy DSL or YAML to the contracts directory, which is set by the
  `contractsDslDir` property. By default, it is `$rootDir/src/test/resources/contracts`.
  
  For the HTTP stubs, a contract defines what kind of response should be returned for a
  given request (taking into account the HTTP methods, URLs, headers, status codes, and so
  on). The following example shows how an HTTP stub contract in Groovy DSL:
  
  [source,groovy,indent=0]
  ----
  