anchor.diff:  --------------------------------------------------
   // CONSOLE
   +
  -The response should indicate that the status of the _elasticsearch_ cluster
  -is _green_ and it has three nodes:
  +The response should indicate that the status of the `elasticsearch` cluster
  +is `green` and it has three nodes:
   +
   [source,txt]
   --------------------------------------------------
  
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/_doc/_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: The additional nodes are assigned unique IDs. Because you're running all three
  nodes locally, they automatically join the cluster with the first node.
  
  . Use the cat health API to verify that your three-node cluster is up running.
  The cat APIs return information about your cluster and indices in a
  format that's easier to read than raw JSON.
  +
  You can interact directly with your cluster by submitting HTTP requests to
  