anchor.diff:  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 <<api-annotations, Metrics Annotations>> or using the `MetricRegistry` object directly.
  +Metrics can be added to or retrieved from the registry either using the `@Metric` annotation
  +(see <<api-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 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`
  +* 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 any more specific
  +media type like `application/json`.
  ++
  +NOTE: Future versions may allow for more export formats that are triggered by their specific media type. The Prometheus
  +text format will stay as fall-back.
   
   Formats are detailed below.
   
  
positive.code: 
  The value of the counter must be the value of `getCount()`.
  
  *Note:* Implementors must not convert the unit of Counters or append the unit suffix to the metric.
  
  .Example Prometheus text format for a Counter.
  [source, ruby]
  
negative.code: 
  == REST endpoints
  
  This section describes the REST-api, that monitoring agents would use to retrieve the collected metrics.
  (Java-) methods mentioned refer to the respective Objects in the Java API. See also <<app-metrics-api>>
  
  === JSON format
  
  