anchor.diff:  
   | _bare_ | `@Inject io.vertx.core.Vertx vertx` | _bare_ Vert.x instance, the API uses callbacks.
   
  -| RX Java 2 | `@Inject io.vertx.reactivex.core.Vertx vertx` | RX Java 2 Vert.x, the API uses RX Java 2 types.
  -
  -| _Axle_ | `@Inject io.vertx.axle.core.Vertx vertx` | Axle Vert.x, the API uses `CompletionStage` and `Reactive Streams`.
  +| https://smallrye.io/smallrye-mutiny/[Mutiny] | `@Inject io.vertx.mutiny.core.Vertx vertx` | The Mutiny API for Vert.x.
  +
  +| RX Java 2 | `@Inject io.vertx.reactivex.core.Vertx vertx` | RX Java 2 Vert.x, the API uses RX Java 2 types (deprecated).
  +
  +| _Axle_ | `@Inject io.vertx.axle.core.Vertx vertx` | Axle Vert.x, the API uses `CompletionStage` and `Reactive Streams` (deprecated).
   
   |===
   
  -TIP: You may inject any of the 3 flavors of `Vertx` as well as the `EventBus` in your Quarkus application beans: `bare`, `Axle`, `RxJava2`.
  +TIP: You may inject any of the 4 flavors of `Vertx` as well as the `EventBus` in your Quarkus application beans: `bare`, `Mutiny`, `Axle`, `RxJava2`.
   They are just shims and rely on a single _managed_ Vert.x instance.
   
   You will pick one or the other depending on your use cases.
   
   - `bare`: for advanced usage or if you have existing Vert.x code you want to reuse in your Quarkus application
  -- `Axle`: works well with Quarkus and MicroProfile APIs (`CompletionStage` for single results and `Publisher` for streams)
  -- `Rx Java 2`: when you need support for a wide range of data transformation operators on your streams
  -
  -The following snippets illustrate the difference between these 3 APIs:
  +- `mutiny`: Mutiny is an event-driven reactive programming API. It uses 2 types: `Uni` and `Multi`. This is the recommended API.
  +- `Axle`: works well with Quarkus and MicroProfile APIs (`CompletionStage` for single results and `Publisher` for streams) - deprecated, it is recommended to switch to Mutiny
  +- `Rx Java 2`: when you need support for a wide range of data transformation operators on your streams - deprecated, it is recommended to switch to Mutiny
  +
  +The following snippets illustrate the difference between these 4 APIs:
   
   [source, java]
   ----
  
positive.code: <dependency>
    <groupId>io.vertx</groupId>
    <artifactId>vertx-web-client</artifactId>
  </dependency>
  
  <!-- Axle API -->
  
negative.code: ----
  
  If you are familiar with Vert.x, you know that Vert.x provides different API models.
  For instance _bare_ Vert.x uses callbacks, the Mutiny variants uses `Uni` and `Multi`, the RX Java 2 version uses `Single`, `Maybe`, `Completable`, `Observable` and `Flowable`...
  
  Quarkus provides 4 Vert.x APIs:
  
  [options="header"]
  |===
  