anchor.diff:  --------------------------------------------------
   
   [float]
  -=== Percolate api
  -
  -The percolate api executes in a distributed manner, meaning it executes on all shards an index points to.
  +=== Percolate API
  +
  +The percolate API executes in a distributed manner, meaning it executes on all shards an index points to.
   
   .Required options
   * `index` - The index that contains the `.percolator` type. This can also be an alias.
   * `type` - The type of the document to be percolated. The mapping of that type is used to parse document.
  -* `doc` - The actual document to percolate. Unlike the other two options this needs to be specified in the request body. Note this isn't required when percolating an existing document.
  +* `doc` - The actual document to percolate. Unlike the other two options this needs to be specified in the request body. Note: This isn't required when percolating an existing document.
   
   [source,js]
   --------------------------------------------------
  
positive.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 need to be stored.
  
  [float]
  ==== Example
  
negative.code: that the percolate request only gets executed on the shard where the routing value is partitioned to. This means that
  the percolate request only gets executed on one shard instead of all shards. Multiple values can be specified as a
  comma separated string, in that case the request can be be executed on more than one shard.
  * `preference` - Controls which shard replicas are preferred to execute the request on. Works the same as in the search API.
  * `ignore_unavailable` - Controls if missing concrete indices should silently be ignored. Same as is in the search API.
  * `percolate_format` - If `ids` is specified then the matches array in the percolate response will contain a string
  array of the matching ids instead of an array of objects. This can be useful to reduce the amount of data being send
  back to the client. Obviously if there are to percolator queries with same id from different indices there is no way
  