anchor.diff:  in <<web-reactive.adoc#webflux-client-builder-maxinmemorysize, WebClient.Builder>>.
   
   For <<webflux-codecs-multipart,Multipart parsing>> the `maxInMemorySize` property limits
  -the size of non-file parts. For file parts it determines the threshold at which the part
  +the size of non-file parts. For file parts, it determines the threshold at which the part
   is written to disk. For file parts written to disk, there is an additional
   `maxDiskUsagePerPart` property to limit the amount of disk space per part. There is also
   a `maxParts` property to limit the overall number of parts in a multipart request.
  -To configure all 3 in WebFlux, you'll need to supply a pre-configured instance of
  +To configure all three in WebFlux, you'll need to supply a pre-configured instance of
   `MultipartHttpMessageReader` to `ServerCodecConfigurer`.
   
   
  
positive.code: === `HttpHandler`
  
  {api-spring-framework}/http/server/reactive/HttpHandler.html[HttpHandler]
  is a simple contract with a single method to handle a request and response. It is
  intentionally minimal, and its main, and only purpose is to be a minimal abstraction
  over different HTTP server APIs.
  
  The following table describes the supported server APIs:
  
negative.code: [[webflux-form-data]]
  ==== Form Data
  
  `ServerWebExchange` exposes the following method for accessing form data:
  
  [source,java,indent=0,subs="verbatim,quotes",role="primary"]
  .Java
  