anchor.diff:  ---------------------------
   
   Usually we recommend using the same `analyzer` at index time and at search
  -time. In the case of the `edge_ngram` tokenizer, the advice is different.  It
  +time. In the case of the `edge_ngram` tokenizer, the advice is different. It
   only makes sense to use the `edge_ngram` tokenizer at index time, to ensure
  -that partial words are available for matching in the index.  At search time,
  +that partial words are available for matching in the index. At search time,
   just search for the terms the user has typed in, for instance: `Quick Fo`.
   
  -Below is an example of how to set up a field for _search-as-you-type_:
  +Below is an example of how to set up a field for _search-as-you-type_.
  +
  +Note that the `max_gram` value for the index analyzer is `10`, which limits
  +indexed terms to 10 characters. Search terms are not truncated, meaning that
  +search terms longer than 10 characters may not match any indexed terms.
   
   [source,console]
   -----------------------------------
  
positive.code: * `punctuation` -- for example `!` or `"`
  * `symbol` --      for example `$` or `√`
  
  [float]
  === Example configuration
  
  
negative.code: 
  The `edge_ngram` tokenizer accepts the following parameters:
  
  `min_gram`::
      Minimum length of characters in a gram.  Defaults to `1`.
  
  `max_gram`::
  +
  --
  Maximum length of characters in a gram.  Defaults to `2`.
  
  See <<max-gram-limits>>.
  --
  
  `token_chars`::
  
  