anchor.diff:  OpenAPI document.
   
   The easiest way to get started is via the <<Annotations>>, since
  -they augment (not replace) the existing JAX-RS annotations, meaning that application
  +they augment (not replace) the existing JAX-RS annotations.  Using annotations means
   developers don't have to re-write the portions of the OpenAPI document that are
  -already covered by the JAX-RS framework (eg: the HTTP method of an operation).
  +already covered by the JAX-RS framework (e.g. the HTTP method of an operation).
   
   Another way to document your APIs is via <<Static OpenAPI files>>.  This
  -is specially adopted by enterprises that want to lock-in the contract of the API
  +is often adopted by enterprises that want to lock-in the contract of the API
   before any code is written.  In this case, we refer to the OpenAPI document as the
  -"source of truth", by which the client and provider must abide to.
  -
  -The MP OpenAPI specification also provides a <<Programming model>> that allows
  -application developers to provide a bootstrap or complete OpenAPI model tree.
  +"source of truth", by which the client and provider must abide.
  +
  +The MP OpenAPI specification also defines a <<Programming model>> that allows
  +application developers to provide a bootstrap (or complete) OpenAPI model tree.
   
   Lastly, a <<Filter>> is described which can update different parts of the OpenAPI
   document during various processing stages independently of which documentation
  
positive.code: The https://github.com/eclipse/microprofile-open-api/blob/master/api/src/main/java/org/eclipse/microprofile/openapi/OASModelReader.java[OASModelReader] interface allows application developers to bootstrap the OpenAPI model tree
  used by the processing framework.  To use it, simply create an implementation of
  this interface and register it using the `mp.openapi.model.reader` configuration
  key, where the value is the qualified name of the reader.
  
  .Sample META-INF/microprofile-config.properties
  [code,property]
  
negative.code: `Accept` header.
  
  === Query parameters
  No query parameters are required for the `/openapi` endpoint.  However, one
  suggested but optional query parameter for vendors to support is `format`,
  where the value can be either `json` or `yaml`, to facilitate the toggle between
  the default `yaml` format and `json` format.
  
  === Context root behaviour
  Vendors are required to ensure that the combination of each global https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#serverObject[server]
  