anchor.diff:  
   ^1^ The implementation is expected to convert the result returned by the `Histogram` into the base unit (if known). The `<unit>` represents the base metric unit and is named according to  <<prometheus_units>>.
   
  -^2^ The `summary` type is a complex metric type for Prometheus which consists of multiple quantile values.
  +^2^ The `summary` type is a complex metric type for Prometheus which consists of the count and multiple quantile values.
   
   .Example Prometheus text format for a Histogram with unit bytes.
   [source, ruby]
   ----
  -# TYPE application:file_sizes_count counter
  -# HELP application:file_sizes_count Users file size
  -application:file_sizes_count 2037
   # TYPE application:file_sizes_mean_bytes gauge
   application:file_sizes_mean_bytes 4738.231
   # TYPE application:file_sizes_max_bytes gauge
  
positive.code: .Example Prometheus text format for a Meter
  [source, ruby]
  ----
  # TYPE application:requests_count counter
  # HELP application:requests_count Tracks the number of requests to the server
  application:requests_count 29382
  # TYPE application:requests_rate_per_second gauge
  application:requests_rate_per_second 12.223
  # TYPE application:requests_one_min_rate_per_second gauge
  
negative.code: 
  ^1^ The implementation is expected to convert the result returned by the `Timer` into seconds
  
  ^2^ The `summary` type is a complex metric type for Prometheus which consists of the count and multiple quantile values.
  
  .Example Prometheus text format for a Timer
  [source, ruby]
  ----
  # TYPE application:response_time_rate_per_second gauge
  application:response_time_rate_per_second  0.004292520715985437
  # TYPE application:response_time_one_min_rate_per_second gauge
  