anchor.diff:  http://docs.oracle.com/javase/7/docs/api/java/util/regex/Pattern.html#UNICODE_CHARACTER_CLASS[`UNICODE_CHARACTER_CLASS`] and
   http://docs.oracle.com/javase/7/docs/api/java/util/regex/Pattern.html#UNIX_LINES[`UNIX_LINES`]
   
  -==== Execution hint
  +===== Execution hint
   
   There are two mechanisms by which terms aggregations can be executed: either by using field values directly in order to aggregate
   data per-bucket (`map`), or by using ordinals of the field values instead of the values themselves (`ordinals`). Although the
  
positive.code: NOTE:   `shard_size` cannot be smaller than `size` (as it doesn't make much sense). When it is, elasticsearch will
          override it and reset it to be equal to `size`.
  
  ==== Minimum document count
  
  It is possible to only return terms that match more than a configured number of hits using the `min_doc_count` option:
  
  
negative.code: Like most design decisions, this is the basis of a trade-off in which we have chosen to provide fast performance at the cost of some (typically small) inaccuracies.
  However, the `size` and `shard size` settings covered in the next section provide tools to help control the accuracy levels. 
  
  ==== Parameters
  
  
  ===== Size & Shard Size
  
  The `size` parameter can be set to define how many term buckets should be returned out of the overall terms list. By
  default, the node coordinating the search process will request each shard to provide its own top term buckets
  