anchor.diff:  
   Mapping supports the following parameters:
   
  -`index_analyzer`:: 
  +`index_analyzer`::
       The index analyzer to use, defaults to `simple`.
   
  -`search_analyzer`:: 
  +`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
  
positive.code: 
  The following parameters are supported:
  
  `input`:: 
      The input to store, this can be a an array of strings or just
      a string. This field is mandatory.
  
  `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`:: 
      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`:: 
      A positive integer, which defines a weight and allows you to
      rank your suggestions. This field is optional.
  
  
negative.code:     bloating the underlying datastructure. The most usecases won't be influenced
      by the default value since prefix completions hardly grow beyond prefixes longer
      than a handful of characters.
  
  ==== Indexing
  
  [source,js]
  --------------------------------------------------
  curl -X PUT 'localhost:9200/music/song/1?refresh=true' -d '{
      "name" : "Nevermind",
      "suggest" : {
          "input": [ "Nevermind", "Nirvana" ],
          "output": "Nirvana - Nevermind",
          "payload" : { "artistId" : 2321 },
  