anchor.diff:  
   [source,js]
   -----------------------------------
  -$ curl -XPUT "localhost:9200/_snapshot/my_backup/snapshot_1?wait_for_completion=true"
  ------------------------------------
  +PUT /_snapshot/my_backup/snapshot_1?wait_for_completion=true
  +-----------------------------------
  +// AUTOSENSE
   
   The `wait_for_completion` parameter specifies whether or not the request should return immediately after snapshot
   initialization (default) or wait for snapshot completion. During snapshot initialization, information about all
  
positive.code: 
  [source,shell]
  -----------------------------------
  $ curl -XGET "localhost:9200/_snapshot/my_backup/snapshot_1/_status"
  -----------------------------------
  
  While snapshot info method returns only basic information about the snapshot in progress, the snapshot status returns
  complete breakdown of the current state for each shard participating in the snapshot.
  
negative.code: 
  [source,js]
  -----------------------------------
  POST /_snapshot/my_backup/snapshot_1/_restore
  {
    "indices": "index_1,index_2",
    "ignore_unavailable": "true",
    "include_global_state": false,
    "rename_pattern": "index_(.+)",
    "rename_replacement": "restored_index_$1"
  }
  -----------------------------------
  // AUTOSENSE
  
  The restore operation can be performed on a functioning cluster. However, an existing index can be only restored if it's
  <<indices-open-close,closed>> and has the same number of shards as the index in the snapshot.
  