anchor.diff:  ./mvnw clean install -DskipTests
   ----
   
  -In the logs we'll see something like this:
  +In the logs, you see something like this:
   
   [source,bash,indent=0]
   ----
  
positive.code: 	}
  ----
  
  This is because the builder is passed through callbacks to initalize it, so the SSL validation can be set up
  in the client at that point. This will happen automatically in your test if you are using the
  `@AutoConfigureWireMock` annotation (or the stub runner). If you are using the JUnit `@Rule` approach you need
  to add the `@AutoConfigureHttpClient` annotation as well:
  
  [source,java,indent=0]
  ----
  
negative.code: 	}
  ----
  
  The WireMock API is rich. You can match headers, query parameters, and request body by
  regex as well as by JSON path. These features can be used to create stubs with a wider
  range of parameters. The above example generates a stub resembling the following example:
  
  .post-resource.json
  [source,json]
  