anchor.diff:  * unified error handling
   * form submissions
   
  -The web client does not deprecate the Vert.x Core {@link io.vertx.core.http.HttpClient}, indeed it is based on
  +The Web Client does not deprecate the Vert.x Core {@link io.vertx.core.http.HttpClient}, indeed it is based on
   this client and inherits its configuration and great features like pooling, HTTP/2 support, pipelining support, etc...
   The {@link io.vertx.core.http.HttpClient} should be used when fine grained control over the HTTP
   requests/responses is necessary.
   
  -The web client does not provide a WebSocket API, the Vert.x Core {@link io.vertx.core.http.HttpClient} should
  +The Web Client does not provide a WebSocket API, the Vert.x Core {@link io.vertx.core.http.HttpClient} should
   be used. It also does not handle cookies at the moment.
   
  -== Using the web client
  +== Using the Web Client
   
   To use Vert.x Web Client, add the following dependency to the _dependencies_ section of your build descriptor:
   
  
positive.code: 
  Sending a single buffer is useful but often you don't want to load fully the content in memory because
  it may be too large or you want to handle many concurrent requests and want to use just the minimum
  for each request. For this purpose the web client can send `ReadStream<Buffer>` (e.g a
  {@link io.vertx.core.file.AsyncFile} is a ReadStream<Buffer>`) with the {@link io.vertx.ext.web.client.HttpRequest#sendStream} method
  
  [source,$lang]
  
negative.code: {@link examples.WebClientExamples#sendStreamChunked(io.vertx.ext.web.client.WebClient, io.vertx.core.streams.ReadStream)}
  ----
  
  The Web Client takes care of setting up the transfer pump for you. Since the length of the stream is not know
  the request will use chunked transfer encoding .
  
  When you know the size of the stream, you shall specify before using the `content-length` header
  