CRR/CZR removing consideration: Config vol replication for source vol created from snapshot

Removing from the CRR considerations: 
•	Configuring volume replication for source volumes created from snapshot isn't supported at this time.

Removing from CZR considerations:
•	At this time, you can't configure volume replication for source volumes created from snapshot with cross-zone replication.

Author: b-hchen

articles/azure-netapp-files/cross-region-replication-requirements-considerations.md

@@ -30,7 +30,6 @@ This article describes requirements and considerations about [using the volume c
 * See [resource limits](azure-netapp-files-resource-limits.md) for the maximum number of cross-region replication destination volumes. You can open a support ticket to [request a limit increase](azure-netapp-files-resource-limits.md#request-limit-increase) in the default quota of replication destination volumes (per subscription in a region).
 * There can be a delay up to five minutes for the interface to reflect a newly added snapshot on the source volume.  
 * Cascading and fan in/out topologies aren't supported.
-* Configuring volume replication for source volumes created from snapshot isn't supported at this time.
 * After you set up cross-region replication, the replication process creates *SnapMirror snapshots* to provide references between the source volume and the destination volume. SnapMirror snapshots are cycled automatically when a new one is created for every incremental transfer. You can't delete SnapMirror snapshots until replication relationship and volume is deleted. 
 * You can't mount a dual-protocol volume until you [authorize replication from the source volume](cross-region-replication-create-peering.md#authorize-replication-from-the-source-volume) and the initial [transfer](cross-region-replication-display-health-status.md#display-replication-status) happens.
 * You can delete manual snapshots on the source volume of a replication relationship when the replication relationship is active or broken, and also after the replication relationship is deleted. You can't delete manual snapshots for the destination volume until the replication relationship is broken.