anchor.diff:  }
   --------------------------------
   
  -<1> Setting `type` to `custom` tells Elasticsearch that we are defining a custom analyzer.
  -    Compare this to how <<configuring-analyzers,built-in analyzers can be configured>>:
  -    `type` will be set to the name of the built-in analyzer, like
  -    <<analysis-standard-analyzer,`standard`>> or <<analysis-simple-analyzer,`simple`>>.
  +<1> For `custom` analyzers, use a `type` of `custom` or omit the `type`
  +parameter.
   
   /////////////////////
   
  
positive.code:     "analysis": {
        "analyzer": {
          "my_custom_analyzer": { <1>
            "type": "custom",
            "char_filter": [
              "emoticons"
            ],
  
negative.code: 
  <1> Assigns the index a default custom analyzer, `my_custom_analyzer`. This
  analyzer uses a custom tokenizer, character filter, and token filter that
  are defined later in the request. This analyzer also omits the `type` parameter.
  <2> Defines the custom `punctuation` tokenizer.
  <3> Defines the custom `emoticons` character filter.
  <4> Defines the custom `english_stop` token filter.
  