More clarity for snapshotfilter

Author: Phil-Jensen

articles/azure-netapp-files/azacsnap-cmd-ref-restore.md

@@ -31,7 +31,7 @@ Doing a volume restore from a snapshot is done using the `azacsnap -c restore` c
 
 The `-c restore` command has the following options:
 
-- `--restore snaptovol` Creates a new volume based on a volume snapshot. This command creates a new "cloned" volume based on the volumes in the configuration file, by default using the latest volume snapshot as the base to create the new volume.  It is possible to select a snapshot to clone, by using the additional option `--snapshotfilter <Snapshot Name>`.  This command does not interrupt the storage replication from primary to secondary. Instead clones of the snapshot are created at the same location and recommended filesystem mountpoints of the cloned volumes are presented. This command should be run on the Azure Large Instance system **in the DR region** (that is, the target fail-over system).
+- `--restore snaptovol` Creates a new volume based on a volume snapshot. This command creates a new "cloned" volume for each volume in the configuration file, by default using the latest volume snapshot as the base to create the new volume.  For data volumes it's possible to select a snapshot to clone by using the option `--snapshotfilter <Snapshot Name>`, this will only complete if ALL data volumes have that same snapshot.  This command does not interrupt the storage replication from primary to secondary. Instead clones of the snapshot are created at the same location and recommended filesystem mountpoints of the cloned volumes are presented. This command should be run on the Azure Large Instance system **in the DR region** (that is, the target fail-over system).
 
 - `--restore revertvolume` Reverts the target volume to a prior state based on a volume snapshot.  Using this command as part of DR Failover into the paired DR region. This command **stops** storage replication from the primary site to the secondary site, and reverts the target DR volume(s) to their latest available snapshot on the DR volumes along with recommended filesystem mountpoints for the reverted DR volumes. This command should be run on the Azure Large Instance system **in the DR region** (that is, the target fail-over system).