anchor.diff:  --------------------------------------------------
   // CONSOLE
   
  -Or by building a custom transient analyzer out of tokenizers,
  -token filters and char filters. Token filters can use the shorter 'filter'
  -parameter name:
  -
  -[source,js]
  ---------------------------------------------------
  -GET _analyze
  +[[analyze-api-custom-analyzer-ex]]
  +===== Custom analyzer
  +
  +You can use the analyze API to test a custom transient analyzer built from
  +tokenizers, token filters, and char filters. Token filters use the `filter`
  +parameter:
  +
  +[source,js]
  +--------------------------------------------------
  +GET /_analyze
   {
     "tokenizer" : "keyword",
     "filter" : ["lowercase"],
  
positive.code: [[indices-analyze]]
  === Analyze
  
  Performs the analysis process on a text and return the tokens breakdown
  of the text.
  
  Can be used without specifying an index against one of the many built in
  analyzers:
  
  [source,js]
  --------------------------------------------------
  GET _analyze
  {
    "analyzer" : "standard",
    "text" : "this is a test"
  }
  --------------------------------------------------
  // CONSOLE
  
  If text parameter is provided as array of strings, it is analyzed as a multi-valued field.
  
  [source,js]
  --------------------------------------------------
  GET _analyze
  {
    "analyzer" : "standard",
    "text" : ["this is a test", "the second text"]
  
negative.code: Will cause the analysis to happen based on the analyzer configured in the
  mapping for `obj1.field1` (and if not, the default index analyzer).
  
  [[analyze-api-normalizer-ex]]
  ===== Normalizer
  
  A `normalizer` can be provided for keyword field with normalizer associated with the `analyze_sample` index.
  
  [source,js]
  --------------------------------------------------
  GET /analyze_sample/_analyze
  {
    "normalizer" : "my_normalizer",
    "text" : "BaR"
  