anchor.diff:  There are a variety of ingest options for {es}, but in the end they all
   do the same thing: put JSON documents into an {es} index.
   
  -You can do this directly with a simple POST request that identifies
  -the index you want to add the document to and specifies one or more
  +You can do this directly with a simple PUT request that specifies
  +the index you want to add the document, a unique document ID, and one or more
   `"field": "value"` pairs in the request body:
   
   [source,js]
  
positive.code: --------------------------------------------------
  // NOTCONSOLE
  
  For the curious, this data was generated using http://www.json-generator.com/[`www.json-generator.com/`], so please ignore the actual values and semantics of the data as these are all randomly generated.
  
  You can download the sample dataset (accounts.json) from https://github.com/elastic/elasticsearch/blob/master/docs/src/test/resources/accounts.json?raw=true[here]. Extract it to our current directory and let's load it into our cluster as follows:
  
  [source,sh]
  --------------------------------------------------
  curl -H "Content-Type: application/json" -XPOST "localhost:9200/bank/_bulk?pretty&refresh" --data-binary "@accounts.json"
  curl "localhost:9200/_cat/indices?v"
  --------------------------------------------------
  // NOTCONSOLE
  
  ////
  This replicates the above in a document-testing friendly way but isn't visible
  in the docs:
  
  [source,js]
  --------------------------------------------------
  GET /_cat/indices?v
  
negative.code: --------------------------------------------------
  // TESTRESPONSE[s/128.6kb/\\d+(\\.\\d+)?[mk]?b/]
  // TESTRESPONSE[s/l7sSYV2cQXmu6_4rJWVIww/.+/ non_json]
  
  [[getting-started-search]]
  == Start searching
  