anchor.diff:  
   <<search-facets, Facets>> provide a great way to aggregate data within a document set context.
   This context is defined by the executed query in combination with the different levels of filters that can be defined
  -(filtered queries, top level filters, and facet level filters). While powerful, their implementation is not designed
  +(filtered queries, top-level filters, and facet level filters). While powerful, their implementation is not designed
   from ground up to support complex aggregations and thus limited.
   
   .Are facets deprecated?
   **********************************
  -As the functionality facets offer is a subset of the the one offered by aggregations, over time, we would like to
  +As the functionality facets offer is a subset of the one offered by aggregations, over time, we would like to
   see users move to aggregations for all realtime data analytics. That said, we are well aware that such
   transitions/migrations take time, and for this reason we are keeping the facets around for the time being.
  -Nonetheless, facets are and should be considered deprecated and will likely be removed in one of the future major
  -releases.
  +Facets are not officially deprecated yet but are likely to be in the future.
   **********************************
   
   The aggregations module breaks the barriers the current facet implementation put in place. The new name ("Aggregations")
  -also indicate the intention here - a generic yet extremely powerful framework for building aggregations - any types of
  +also indicates the intention here - a generic yet extremely powerful framework for building aggregations - any types of
   aggregations.
   
   An aggregation can be seen as a _unit-of-work_ that builds analytic information over a set of documents. The context of
  -the execution defines what this document set is (e.g. a top level aggregation executes within the context of the executed
  +the execution defines what this document set is (e.g. a top-level aggregation executes within the context of the executed
   query/filters of the search request).
   
   There are many different types of aggregations, each with its own purpose and output. To better understand these types,
  
positive.code: }
  --------------------------------------------------
  
  The `aggregations` object (the key `aggs` can also be used) in the json holds the aggregations to be computed. Each aggregation
  is associated with a logical name that the user defines (e.g. if the aggregation computes the average price, then it'll
  make sense to name it `avg_price`). These logical names will also be used to uniquely identify the aggregations in the
  response. Each aggregation has a specific type (`<aggregation_type>` in the above snippet) and is typically the first
  key within the named aggregation body. Each type of aggregation define its own body, depending on the nature of the
  aggregation (eg. an `avg` aggregation on a specific field will define the field on which the avg will be calculated).
  At the same level of the aggregation type definition, one can optionally define a set of additional aggregations,
  though this only makes sense if the aggregation you defined is of a bucketing nature. In this scenario, the
  sub-aggregations you define on the bucketing aggregation level will be computed for all the buckets built by the
  bucketing aggregation. For example, if the you define a set of aggregations under the `range` aggregation, the
  sub-aggregations will be computed for each of the range buckets that are defined.
  
  [float]
  ==== Values Source
  
  Some aggregations work on values extracted from the aggregated documents. Typically, the values will be extracted from
  a sepcific document field which is set under the `field` settings for the aggrations. It is also possible to define a
  <<modules-scripting,`script`>> that will generate the values (per document).
  
  When both `field` and `script` settings are configured for the aggregation, the script will be treated as a
  
negative.code: include::aggregations/metrics.asciidoc[]
  
  include::aggregations/bucket.asciidoc[]
  