anchor.diff:  
   The builder can be used to insert <<webflux-client-filter>>.
   
  -You can also customize URI building, set default headers, cookies, and more. Explore
  -the `WebClient.Builder` in your IDE.
  -
  -Note that you can also obtain a builder from an already existing `WebClient` instance
  -and create a modified version without affecting the original instance:
  +Explore the `WebClient.Builder` in your IDE for other options related to URI building,
  +default headers (and cookies), and more.
  +
  +After the `WebClient` is built, you can always obtain a new builder from it, in order to
  +build a new `WebClient`, based on, but without affecting the current instance:
   
   [source,java,intent=0]
   [subs="verbatim,quotes"]
  
positive.code: [[webflux-client-retrieve]]
  === Retrieve
  
  The `retrieve()` method is the easiest way to get a decoded response body:
  
  [source,java,intent=0]
  [subs="verbatim,quotes"]
  
negative.code: `spring-core` which provides pluggable support for reactive and async types. The registry
  has built-in support for RxJava and `CompletableFuture` but others can be registered.
  
  For functional endpoints, the `WebClient`, and other functional APIs, the general rule
  of thumb for WebFlux APIs applies:
  
  * `Flux` or `Mono` as return values -- use them to compose logic or pass to any Reactive
  Streams library (both are `Publisher` implementations).
  * Reactive Streams `Publisher` for input -- if a `Publisher` from another reactive library
  is provided it can only be treated as a stream with unknown semantics (0..N). If the
  semantics are known -- e.g. `io.reactivex.Single`, you can use `Mono.from(Publisher)` and
  pass that in instead of the raw `Publisher`.
  
  [NOTE]
  ====
  