anchor.diff:  
   The following parameters are supported:
   
  -`input`:: 
  +`input`::
       The input to store, this can be a an array of strings or just
       a string. This field is mandatory.
   
  -`output`:: 
  +`output`::
       The string to return, if a suggestion matches. This is very
       useful to normalize outputs (i.e. have them always in the format
       `artist - songname`. This is optional.
   
  -`payload`:: 
  +`payload`::
       An arbitrary JSON object, which is simply returned in the
       suggest option. You could store data like the id of a document, in order
       to load it from elasticsearch without executing another search (which
       might not yield any results, if `input` and `output` differ strongly).
   
  -`weight`:: 
  +`weight`::
       A positive integer, which defines a weight and allows you to
       rank your suggestions. This field is optional.
   
  
positive.code: 
  Mapping supports the following parameters:
  
  `index_analyzer`:: 
      The index analyzer to use, defaults to `simple`.
  
  `search_analyzer`:: 
      The search analyzer to use, defaults to `simple`.
      In case you are wondering why we did not opt for the `standard`
      analyzer: We try to have easy to understand behaviour here, and if you
  
negative.code:     If disabled, you could find a field starting with `Foo Fighters`, if you
      suggest for `foof`.
  
  `preserve_position_increments`::
      Enables position increments, defaults
      to `true`. If disabled and using stopwords analyzer, you could get a
      field starting with `The Beatles`, if you suggest for `b`. *Note*: You
  