anchor.diff:   });
   ----
   
  -If you remember the architecture, the quote generator also provides a HTTP endpoint returning the last values of the
  -quotes (but, you are going to work on it). But this service is not explicitly published in the service discovery.
  -It's because Kubernetes is taking care of this part. The Vert.x service discovery interacts with Kubernetes
  +If you remember the architecture, the quote generator also provides an HTTP endpoint returning the last values of the
  +quotes (but, you are going to work on it). Note that this service is not explicitly published in the service discovery.
  +That's because Kubernetes is taking care of this part. The Vert.x service discovery interacts with Kubernetes
   _services_, so all Kubernetes services can be retrieved by Vert.x.
   
   ### The quote REST endpoint
   
   It's time for you to develop some parts of the application (I know you have pins and needles in your fingers). Open the
  -`RestQuoteAPIVerticle`. It's a verticle class extending `AbstractVerticle`. In the `start` method you need to:
  -
  -1. Receive the an event bus _market_ messages to collect the last quotations (in the `quotes` map)
  -2. Handle HTTP requests to return the list of quotes, or a single quote if the `name` (query) param is set.
  +`RestQuoteAPIVerticle` file. It's a verticle class extending `AbstractVerticle`. In the `start` method you need to:
  +
  +1. Receive the event bus _market_ messages to collect the last quotations (in the `quotes` map)
  +2. Handle HTTP requests to return the list of quotes or a single quote if the `name` (query) param is set.
   
   In this example we are using streams (`Flowable`). Streams are an important part of reactive programming and
  -architecture. So it's important to understand how they work and how we manipulate them.
  +architecture. So, it's important to understand how they work and how we manipulate them.
   
   Let's do that....
   
  
positive.code: 2. Compile the java code and process resources (if any)
  3. Build a _fat-jar_
  
  A _fat-jar_ (also called _uber_ jar or _shaded_ jar) is a convenient way to package a Vert.x application. It creates a
  _über-jar_ containing your application and all its dependencies, including Vert.x. Then, to launch it, you just need
  to use `java -jar ....`, without having to handle the `CLASSPATH`. Wait, I told you that Vert.x does not dictate a
  type of packaging. It's true, fat jars are convenient, but it's not the only way, you can use plain (not fat) jars,
  OSGi bundles...
  
  The `pom.xml` file also contains a set of properties used to configure the application:
  
negative.code: 
  The first action is about observing the stream of _market_ messages. This is done using
  `vertx.eventBus().<JsonObject>consumer(GeneratorConfigVerticle.ADDRESS).toFlowable()`. We now have the stream of
  messages, but we need to extract the JSON body and populate the `quotes` map. Implement the missing logic that extracts the
   body of the message (with the `body()` method), and then puts `name -> quote` in the `quotes` map.
  
  [.assignment]
  ****
  