anchor.diff:  
   [source,js]
   ----
  -PUT twitter?include_type_name=true <1>
  +PUT twitter
   {
     "mappings": {
       "_doc": {
         "properties": {
  -        "type": { "type": "keyword" }, <2>
  +        "type": { "type": "keyword" }, <1>
           "name": { "type": "text" },
           "user_name": { "type": "keyword" },
           "email": { "type": "keyword" },
  
positive.code: an index that doesn't exist yet, the template is always honored. This is
  usually not a problem due to the fact that typeless index calls work on typed
  indices.
  
negative.code: }
  --------------------------------------------------
  // TESTRESPONSE
  
  Similarly, the `get` and `delete` APIs use the path `{index}/_doc/{id}`:
  
  [source,js]
  --------------------------------------------------
  GET index/_doc/1
  --------------------------------------------------
  // CONSOLE
  // TEST[continued]
  
  For API paths that contain both a type and endpoint name like `_update`,
  in 7.0 the endpoint will immediately follow the index name:
  
  [source,js]
  --------------------------------------------------
  POST index/_update/1
  {
      "doc" : {
          "foo" : "qux"
      }
  }
  
  GET /index/_source/1
  --------------------------------------------------
  // CONSOLE
  // TEST[continued]
  
  Types should also no longer appear in the body of requests. The following
  example of bulk indexing omits the type both in the URL, and in the individual
  bulk commands:
  
  [source,js]
  --------------------------------------------------
  POST _bulk
  { "index" : { "_index" : "index", "_id" : "3" } }
  { "foo" : "baz" }
  { "index" : { "_index" : "index", "_id" : "4" } }
  { "foo" : "qux" }
  --------------------------------------------------
  // CONSOLE
  
  [float]
  ==== Search APIs
  
  When calling a search API such `_search`, `_msearch`, or `_explain`, types
  should not be included in the URL. Additionally, the `_type` field should not
  be used in queries, aggregations, or scripts.
  
  [float]
  ==== Types in responses
  
  The document and search APIs will continue to return a `_type` key in
  responses, to avoid breaks to response parsing. However, the key is
  considered deprecated and should no longer be referenced. Types will
  be completely removed from responses in 8.0.
  
  Note that when a deprecated typed API is used, the index's mapping type will be
  returned as normal, but that typeless APIs will return the dummy type `_doc`
  in the response. For example, the following typeless `get` call will always
  return `_doc` as the type, even if the mapping has a custom type name like
  `my_type`:
  
  [source,js]
  --------------------------------------------------
  PUT index/my_type/1
  {
    "foo": "baz"
  }
  
  GET index/_doc/1
  --------------------------------------------------
  // CONSOLE
  
  [source,js]
  --------------------------------------------------
  {
      "_index" : "index",
      "_type" : "_doc",
      "_id" : "1",
      "_version" : 1,
      "_seq_no" : 0,
      "_primary_term" : 1,
      "found": true,
      "_source" : {
          "foo" : "baz"
      }
  }
  --------------------------------------------------
  // TESTRESPONSE
  
  [float]
  ==== Index templates
  
  It is recommended to make index templates typeless before upgrading to 7.0 by
  re-adding them with `include_type_name` set to `false`.
  