anchor.diff:  previous snapshots is loaded into the memory, which means that in large repositories it may take several seconds (or
   even minutes) for this command to return even if the `wait_for_completion` parameter is set to `false`.
   
  -By default snapshot of all open and started indices in the cluster is created. This behavior can be changed by
  +By default a snapshot of all open and started indices in the cluster is created. This behavior can be changed by
   specifying the list of indices in the body of the snapshot request.
   
   [source,js]
  
positive.code: changed since the last snapshot. That allows multiple snapshots to be preserved in the repository in a compact form.
  Snapshotting process is executed in non-blocking fashion. All indexing and searching operation can continue to be
  executed against the index that is being snapshotted. However, a snapshot represents the point-in-time view of the index
  at the moment when snapshot was created, so no records that were added to the index after snapshot process had started
  will be present in the snapshot. The snapshot process starts immediately for the primary shards that has been started
  and are not relocating at the moment. Before version 1.2.0, the snapshot operation fails if the cluster has any relocating or
  initializing primaries of indices participating in the snapshot. Starting with version 1.2.0, Elasticsearch waits for
  
negative.code: }'
  -----------------------------------
  
  Once a repository is registered, its information can be obtained using the following command:
  
  [source,js]
  -----------------------------------
  