docs(vol-restore): added a doc for volume restore from a snapshot

reference/storage-class-parameters.md

@@ -49,7 +49,7 @@ The `agents.core.capacity.thin` spec present in the Mayastor helm chart consists
 {% hint style="info" %}
 Note:
 1. By default, the volumes are provisioned as `thick`. 
-2. For a pool of a particular size, say 10 Gigabytes, a volume > 10 Gigabytes cannot be created, as Mayastor 2.4.0 does not support pool expansion.
+2. For a pool of a particular size, say 10 Gigabytes, a volume > 10 Gigabytes cannot be created, as Mayastor currently does not support pool expansion.
 3. The replicas for a given volume can be either all thick or all thin. Same volume cannot have a combination of thick and thin replicas
 {% endhint %}
 
@@ -77,8 +77,8 @@ By default, the `stsAffinityGroup` feature is disabled. To enable it, modify the
 
 ## "cloneFsIdAsVolumeId"
 
-`cloneFsIdAsVolumeId` is a setting for volume clones with two options: `true` and `false`. By default, it is set to `false`.
-- When set to `true`, the created clone/restore's filesystem `uuid` will be set to the new volume `uuid`. This is important because some file systems, like XFS, don't allow duplicate filesystem `uuid` on the same machine by default.
+`cloneFsIdAsVolumeId` is a setting for volume clones/restores with two options: `true` and `false`. By default, it is set to `false`.
+- When set to `true`, the created clone/restore's filesystem `uuid` will be set to the restore volume's `uuid`. This is important because some file systems, like XFS, don't allow duplicate filesystem `uuid` on the same machine by default.
 - When set to `false`, the created clone/restore's filesystem `uuid` will be same as the orignal volume `uuid`, but it will be mounted using the `nouuid` flag to bypass duplicate `uuid` validation.