anchor.diff:  
   == Coverage for tests not using @QuarkusTest
   
  -The Quarkus automatic Jacoco config will only work for tests that are annotated with `@QuarkusTest`. If you want to check
  -the coverage of other tests as well then you will need to fall back to the Jacoco maven plugin.
  -
  -In addition to including the `quarkus-jacoco` extension in your pom you will need the following config:
  +The Quarkus automatic JaCoCo config will only work for tests that are annotated with `@QuarkusTest`. If you want to check
  +the coverage of other tests as well then you will need to fall back to the JaCoCo maven plugin.
  +
  +In addition to including the `quarkus-jacoco` extension in your `pom.xml` you will need the following config:
   
   [role="primary asciidoc-tabs-target-sync-cli asciidoc-tabs-target-sync-maven"]
   .pom.xml
  
positive.code:     @GET
      @Produces(MediaType.TEXT_PLAIN)
      @Path("/greeting/{name}")
      public String greeting(@PathParam("name") String name) {
          return service.greeting(name);
      }
  
  
negative.code: 
  == Setting coverage thresholds
  
  You can set thresholds for code coverage using the JaCoCo Maven plugin. Note the element `<dataFile>${project.build.directory}/jacoco-quarkus.exec</dataFile>`.
  You must set it matching your choice for `quarkus.jacoco.data-file`.
  
  [role="primary asciidoc-tabs-target-sync-cli asciidoc-tabs-target-sync-maven"]
  