anchor.diff:  in the mapping), it will be used, otherwise, the actual `_source` will
   be loaded and the relevant field will be extracted from it.
   
  -If `term_vector` information is provided by setting `term_vector` to 
  -`with_positions_offsets` in the mapping then the fast vector 
  +If `term_vector` information is provided by setting `term_vector` to
  +`with_positions_offsets` in the mapping then the fast vector
   highlighter will be used instead of the plain highlighter.  The fast vector highlighter:
   
   * Is faster especially for large fields (> `1MB`)
  -* Can be customized with `boundary_chars`, `boundary_max_scan`, and 
  +* Can be customized with `boundary_chars`, `boundary_max_scan`, and
    `fragment_offset` (see below)
  -* Requires setting `term_vector` to `with_positions_offsets` which 
  +* Requires setting `term_vector` to `with_positions_offsets` which
     increases the size of the index
   
   Here is an example of setting the `content` field to allow for
  
positive.code:     }
  }
  --------------------------------------------------
  
  It is also possible to highlight against a query other than the search
  query by setting `highlight_query`.  This is especially useful if you
  
negative.code: highlighting framework. For implementation details you can check
  `ScoreOrderFragmentsBuilder.java` class.
  
  [[highlighting-settings]]
  ==== Global Settings
  
  