anchor.diff:  // CONSOLE
   // TEST[continued]
   
  -The previous method can also be used in combination with <<docs-reindex-change-name, change the name of a field>>
  -to only load the existing data into the new index, but also rename fields if needed.
  +The previous method can also be used in conjunction with <<docs-reindex-change-name, change the name of a field>>
  +to load only the existing data into the new index and rename any fields if needed.
   
   [float]
   === Extracting a random subset of an index
   
  -Reindex can be used to extract a random subset of an index for testing:
  +`_reindex` can be used to extract a random subset of an index for testing:
   
   [source,js]
   ----------------------------------------------------------------
  
positive.code: 
  The advantage of this API is that it integrates with `wait_for_completion=false`
  to transparently return the status of completed tasks. If the task is completed
  and `wait_for_completion=false` was set on it them it'll come back with a
  `results` or an `error` field. The cost of this feature is the document that
  `wait_for_completion=false` creates at `.tasks/task/${taskId}`. It is up to
  you to delete that document.
  
negative.code: 
  `index` and `type` in `source` can both be lists, allowing you to copy from
  lots of sources in one request. This will copy documents from the `_doc` and
  `post` types in the `twitter` and `blog` index. The copied documents would include the 
  `post` type in the `twitter` index and the `_doc` type in the `blog` index. For more 
  specific parameters, you can use `query`.
  
  The Reindex API makes no effort to handle ID collisions. For such issues, the target index 
  will remain valid, but it's not easy to predict which document will survive because 
  the iteration order isn't well defined.
  
  [source,js]
  --------------------------------------------------
  