anchor.diff:  an overall view if the same metric has different metadata.
   
   === Metric Registry
  -<TO DO>
  +The `MetricRegistry` stores the metrics and metadata information.
  +There is one `MetricRegistry` instance for each of the scopes listed in <<scopes>>.
  +
  +Metrics can be added to or retrieved from the registry either using the <<annotations, Metrics Annotations>> or using the `MetricRegistry` object directly.
   
   [[rest-api]]
   === Exposing metrics via REST API
   
  -Data is exposed via REST over HTTP under the `/metrics` base path in two default data formats for `GET` requests:
  -
  -* JSON format.
  -* Prometheus text format.
  +Data is exposed via REST over HTTP under the `/metrics` base path in two different data formats for `GET` requests:
  +
  +* JSON format - used when the HTTP Accept header matches `application/json`
  +* Prometheus text format - default response format when the HTTP Accept header does not match `application/json`
   
   Formats are detailed below.
   
  
positive.code: ----
  <1> Metric names are turned from camel case into snake_case.
  <2> The description goes into the HELP line
  <3> Metric names gets the base unit of the family appended with `_` and defined labels. Values are scaled accordingly
  
  ===== Translation rules for metric names
  
  Prometheus text format does not allow for all characters and adds the base unit of a family to the name.
  
  
negative.code: import org.eclipse.microprofile.metrics.Counter;
  import org.eclipse.microprofile.metrics.annotation.Metric;
  
  public class Colours {
  
    @Inject
    @Metric
  