anchor.diff:  }
   --------------------------------------------------
   
  -On top of this also a mapping type can be associated with this query. This allows to control how certain queries
  -like range queries, shape filters and other query & filters that rely on mapping settings get constructed. This is
  +On top of this, also a mapping type can be associated with this query. This allows to control how certain queries
  +like range queries, shape filters, and other query & filters that rely on mapping settings get constructed. This is
   important since the percolate queries are indexed into the `.percolator` type, and the queries / filters that rely on
  -mapping settings would yield unexpected behaviour. Note by default field names do get resolved in a smart manner,
  -but in certain cases with multiple types this can lead to unexpected behaviour, so being explicit about it will help.
  +mapping settings would yield unexpected behaviour. Note: By default, field names do get resolved in a smart manner,
  +but in certain cases with multiple types this can lead to unexpected behavior, so being explicit about it will help.
   
   [source,js]
   --------------------------------------------------
  
positive.code: }
  --------------------------------------------------
  
  In the above example the range query gets really parsed into a Lucene numeric range query, based on the settings for
  the field `created_at` in the type `tweet`.
  
  Just as with any other type, the `.percolator` type has a mapping, which you can configure via the mappings apis.
  The default percolate mapping doesn't index the query field and only stores it.
  
  Because `.percolate` is a type it also has a mapping. By default the following mapping is active:
  
  
negative.code: * `percolate_preference` - Which shard to prefer when executing the percolate request.
  * `version` - Enables a version check. If the fetched document's version isn't equal to the specified version then the request fails with a version conflict and the percolation request is aborted.
  
  Internally the percolate API will issue a GET request for fetching the `_source` of the document to percolate.
  For this feature to work, the `_source` for documents to be percolated needs to be stored.
  
  [float]
  ==== Example
  