anchor.diff:  better way to structure your code. For this, Vert.x provides _verticles_ - a simple agent-like model. Verticles are
   single-threaded classes interacting using asynchronous messages.
   
  -Open the `vertx-exercises/src/main/java/io/vertx/workshop/exercise/Exercise2.java`. In the `main` method, deploy the
  +Open the `vertx-exercises/src/main/java/io/vertx/workshop/exercise/Exercise2.java` file. In the `main` method, deploy the
   `Exercise2Verticle`. Then, implement the missing functionnality in the verticle class (`Exercise2Verticle.java`).
   
  -Run and check the result as in the previous exercise. Emit the request several time in a raw to check that your
  +Run and check the result as in the previous exercise. Emit the request several time in a row to check that your
   verticle is always executed by the same thread.
   
   [.assignment]
  
positive.code: 
  ### Exercise 5 - Request Reply and Composing actions
  
  Let's now mix the HTTP server and the event bus. A first verticle create the HTTP server, but to response to the
  request, it sends a message to another verticle and _waits_ for a reply. This reply is used as response to the HTTP
  request. This introduce the `request-reply` delivery mechanism of the event bus. This exercices is composed by a
  _main` class (`io.vertx.workshop.exercise.Exercise5`) and two verticles: `io.vertx.workshop.exercise
  .Exercise5HttpVerticle` and `io.vertx.workshop.exercise.Exercise5ProcessorVerticle`.
  
  
negative.code: ----
  ****
  
  Then, open the `vertx-exercises/src/main/java/io/vertx/workshop/exercise/Exercise4ReceiverVerticle.java` file and follow the instructions to receive
  the messages sent by the other verticle. To achieve this, register a `consumer` on the `greetings` address and
  implement the `Handler` to process the received messages.
  
  