anchor.diff:  -----------------------------
   // TESTRESPONSE[s/\.\.\./"took": $body.took,"timed_out": false,"_shards": $body._shards,"hits": $body.hits,/]
   
  -NOTE: The start `offset` of each bucket is calculated after the `time_zone`
  +NOTE: The start `offset` of each bucket is calculated after `time_zone`
   adjustments have been made.
   
  -==== Keyed Response
  -
  -Setting the `keyed` flag to `true` will associate a unique string key with each bucket and return the ranges as a hash rather than an array:
  +===== Keyed Response
  +
  +Setting the `keyed` flag to `true` associates a unique string key with each
  +bucket and returns the ranges as a hash rather than an array:
   
   [source,js]
   --------------------------------------------------
  
positive.code: // CONSOLE
  // TEST[setup:sales]
  
  Available expressions for interval: `year` (`1y`), `quarter` (`1q`), `month` (`1M`), `week` (`1w`),
  `day` (`1d`), `hour` (`1h`), `minute` (`1m`), `second` (`1s`)
  
  Time values can also be specified via abbreviations supported by <<time-units,time units>> parsing.
  Note that fractional time values are not supported, but you can address this by shifting to another
  time unit (e.g., `1.5h` could instead be specified as `90m`). Also note that time intervals larger than
  days do not support arbitrary values but can only be one unit large (e.g. `1y` is valid, `2y` is not).
  
  [source,js]
  --------------------------------------------------
  
negative.code: ---------------------------------
  // TESTRESPONSE[s/\.\.\./"took": $body.took,"timed_out": false,"_shards": $body._shards,"hits": $body.hits,/]
  
  If you specify a `time_zone` of `-01:00`, midnight in that timezone is one hour
  before midnight UTC:
  
  [source,js]
  ---------------------------------
  