anchor.diff:  
   
   [float]
  -=== Changing index settings during restore
  +==== Changing index settings during restore
   
   Most of index settings can be overridden during the restore process. For example, the following command will restore
   the index `index_1` without creating any replicas while switching back to default refresh interval:
  
positive.code: }'
  -----------------------------------
  
  
  [float]
  === Snapshot status
  
negative.code: -----------------------------------
  
  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.
  The restore operation automatically opens restored indices if they were closed and creates new indices if they
  didn't exist in the cluster. If cluster state is restored, the restored templates that don't currently exist in the
  cluster are added and existing templates with the same name are replaced by the restored templates. The restored
  persistent settings are added to the existing persistent settings.
  
  [float]
  ==== Partial restore
  
  By default, the entire restore operation will fail if one or more indices participating in the operation don't have
  snapshots of all shards available. It can occur if some shards failed to snapshot for example. It is still possible to
  