anchor.diff:  
   
   [[explicit-field-order]]
  -===== Explicitly ordering highlighted fields
  +[float]
  +=== Explicitly order highlighted fields
   Elasticsearch highlights the fields in the order that they are sent, but per the
   JSON spec, objects are unordered.  If you need to be explicit about the order
   in which fields are highlighted specify the `fields` as an array:
  
positive.code: // CONSOLE
  // TEST[setup:twitter]
  
  {es} supports three highlighters:
  
  [[unified-highlighter]]
  * The `unified` highlighter uses the Lucene Unified Highlighter. This
  highlighter breaks the text into sentences and uses the BM25 algorithm to score
  individual sentences as if they were documents in the corpus. It also supports
  accurate phrase and multi-term (fuzzy, prefix, regex) highlighting. This is the
  default highlighter.
  
  [[plain-highlighter]]
  * The `plain` highlighter uses the standard Lucene highlighter. It attempts to
  reflect the query matching logic in terms of understanding word importance and
  any word positioning criteria in phrase queries.
  +
  [WARNING]
  The `plain` highlighter works best for highlighting simple query matches in a
  single field. To accurately reflect query logic, it creates a tiny in-memory
  
negative.code: 
  pre_tags:: Use in conjunction with `post_tags` to define the HTML tags
  to use for the highlighted text. By default, highlighted text is wrapped
  in `<em>` and `</em>` tags. Specify as an array of strings.
  
  post_tags:: Use in conjunction with `pre_tags` to define the HTML tags
  to use for the highlighted text. By default, highlighted text is wrapped
  