anchor.diff:  This means that the total number of samples in all data series is constant, and consequently
   the size of this data structure is also constant (because the size of the moving window is fixed, and
   older samples are replaced by newer ones). This arrangement is referred to as a
  -round-robin database, and Solr uses implementation of this concept provided by RRD4j library.
  +round-robin database, and Solr uses implementation of this concept provided by the https://github.com/rrd4j/rrd4j[RRD4j] library.
   
   === Storage
   Databases created with RRD4j are compact - for the time series specified above the total size
  -of data is ca. 11kB for each of the primary time series, including its resampled data. Each database may contain
  +of data is around 11kB for each of the primary time series, including its resampled data. Each database may contain
   several primary time series ("datasources" in RRD4j parlance) and their re-sampled versions (called
   "archives").
   
   This data is updated in memory and then periodically stored in the `.system`
   collection in the form of Solr documents with a binary `data_bin` field, each document
   containing data of one full database. This method of storage is much more compact and generates less
  -update operations than storing each data point in a separate Solr document. Metrics history API allows retrieving
  +update operations than storing each data point in a separate Solr document. The Metrics History API allows retrieving
   detailed data from each database, including retrieval of all individual datapoints.
   
   Databases are identified primarily by their corresponding metric registry name, so for databases that
   keep track of aggregated metrics this will be e.g., `solr.jvm`, `solr.node`, `solr.collection.gettingstarted`.
   For databases with non-aggregated metrics the name consists of the registry name, optionally with a node name
   to identify databases with the same name coming from different nodes. For example, per-node databases are
  -name like this: `solr.jvm.localhost:8983_solr`, `solr.node.localhost:7574_solr`, but per-replica names are
  +named like this: `solr.jvm.localhost:8983_solr`, `solr.node.localhost:7574_solr`, but per-replica names are
   already unique across the cluster so they are named like this: `solr.core.gettingstarted.shard1.replica_n1`.
   
  -=== Collected metrics
  +=== Collected Metrics
   Currently the following selected metrics are tracked:
   
   * Non-aggregated `solr.core` and aggregated `solr.collection` metrics:
  
positive.code: Each section also contains a `lastModified` element, which contains the last modification time when the
  database was update. All timestamps returned from this API correspond to Unix epoch time in seconds.
  
  === Database status (`action=status`)
  This call provides detailed status of the selected database.
  
  The following parameters are supported:
  
  `name`:: string, required: database name
  
  Example:
  [source,bash]
  
negative.code:       "syncPeriod" : 300
      }
    }
  }
  ----
  
  