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: 
  == Using HTTPS
  
  Vert.x web client can be configured to use HTTPS in exactly the same way as the Vert.x {@link io.vertx.core.http.HttpClient}.
  
  You can specify the behavior per request
  
  
negative.code: 
  == Handling http responses
  
  When the Web Client sends a request you always deal with a single async result {@link io.vertx.ext.web.client.HttpResponse}.
  
  On a success result the callback happens after the response has been received
  
  