anchor.diff:  }
   --------------------------------------------------
   // AUTOSENSE
  -<1> The first term in the next array element will be 50 terms apart from the
  +<1> The first term in the next array element will be 0 terms apart from the
       last term in the previous array element.
  -<2> The phrase query no longer matches our document.
  +<2> The phrase query matches our document which is weird, but its what we asked
  +    for in the mapping.
   
   TIP: The `position_increment_gap` setting is allowed to have different settings
   for fields of the same name in the same index.  Its value can be updated on
   existing fields using the <<indices-put-mapping,PUT mapping API>>.
  -
  
positive.code: <<mapping-index,Analyzed>> string fields take term <<index-options,positions>>
  into account, in order to be able to support
  <<query-dsl-match-query-phrase,proximity or phrase queries>>.
  When indexing an array of strings, each string of the array is indexed
  directly after the previous one, almost as though all the strings in the array
  had been concatenated into one big string.
  
  This can result in matches from phrase queries spanning two array elements.
  For instance:
  
  [source,js]
  --------------------------------------------------
  
negative.code:         }
      }
  }
  
  GET /my_index/groups/_search
  {
      "query": {
          "match_phrase": {
              "names": "Abraham Lincoln",
              "slop": 101 <2>
          }
      }
  }
  --------------------------------------------------
  // AUTOSENSE
  <1> This phrase query doesn't match our document which is totally expected.
  <2> This phrase query matches our document, even though `Abraham` and `Lincoln`
      are in separate strings, because `slop` > `position_increment_gap`.
  
  
  The `position_increment_gap` can be specified in the mapping.  For instance:
  
  [source,js]
  --------------------------------------------------
  