anchor.diff:  
   Elasticsearch provides the ability to update multiple documents given a query condition (like an `SQL UPDATE-WHERE` statement). See {ref}/docs-update-by-query.html[`docs-update-by-query` API]
   
  +[[getting-started-delete-documents]]
   === Deleting Documents
   
   Deleting a document is fairly straightforward. This example shows how to delete our previous customer with the ID of 2:
  
positive.code: 
  Also note the line marked http with information about the HTTP address (`192.168.8.112`) and port (`9200`) that our node is reachable from. By default, Elasticsearch uses port `9200` to provide access to its REST API. This port is configurable if necessary.
  
  == Exploring Your Cluster
  
  [float]
  
negative.code: 
  You might also notice that the customer index has a yellow health tagged to it. Recall from our previous discussion that yellow means that some replicas are not (yet) allocated. The reason this happens for this index is because Elasticsearch by default created one replica for this index. Since we only have one node running at the moment, that one replica cannot yet be allocated (for high availability) until a later point in time when another node joins the cluster. Once that replica gets allocated onto a second node, the health status for this index will turn to green.
  
  [[getting-started-query-document]]
  === Index and Query a Document
  
  Let's now put something into our customer index. We'll index a simple customer document into the customer index, with an ID of 1 as follows:
  