anchor.diff:  are distributed proportionally to each sub-request. Combine that with the point
   above about distribution being uneven and you should conclude that the using
   `size` with `slices` might not result in exactly `size` documents being
  -`_delete_by_query`ed.
  -* Each sub-requests gets a slightly different snapshot of the source index
  +deleted.
  +* Each sub-request gets a slightly different snapshot of the source index
   though these are all taken at approximately the same time.
   
   [float]
  
positive.code: [[docs-delete-by-query-automatic-slice]]
  ==== Automatic slicing
  
  You can also let delete-by-query automatically parallelize using
  <<sliced-scroll>> to slice on `_uid`. Use `slices` to specify the number of
  slices to use:
  
  [source,js]
  
negative.code: == Delete By Query API
  
  The simplest usage of `_delete_by_query` just performs a deletion on every
  document that matches a query. Here is the API:
  
  [source,js]
  --------------------------------------------------
  