anchor.diff:  
   In the above example, `ctx._source` refers to the current source document that is about to be updated.
   
  -Note that as of this writing, updates can only be performed on a single document at a time. In the future, Elasticsearch will provide the ability to update multiple documents given a query condition (like an `SQL UPDATE-WHERE` statement).
  +Note that as of this writing, updates can only be performed on a single document at a time. In the future, Elasticsearch might provide the ability to update multiple documents given a query condition (like an `SQL UPDATE-WHERE` statement).
   
   === Deleting Documents
   
  
positive.code: }'
  --------------------------------------------------
  
  There are a many other aggregations capabilities that we won't go into detail here. The http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/search-aggregations.html[aggregations reference guide] is a great starting point if you want to do further experimentation.
  
  == Conclusion
  
  
negative.code: 
  If you come from a SQL background, the above is somewhat similar in concept to the `SQL SELECT FROM` field list.
  
  Now let's move on to the query part. Previously, we've seen how the `match_all` query is used to match all documents. Let's now introduce a new query called the <<query-dsl-match-query,`match` query>>, which can be thought of as a basic fielded search query (i.e. a search done against a specific field or set of fields).
  
  This example returns the account numbered 20:
  
  