Fix formatting

Author: ttorble

articles/azure-netapp-files/cross-region-replication-introduction.md

@@ -76,8 +76,8 @@ Cross-region replication supports three replication schedules: 10 minutes, hourl
 * For the hourly replication schedule, the typical RPO is less than two hours.  
 * For the daily replication schedule, the typical RPO is less than two days.  
 
->[IMPORTANT]
->[Large volumes](azure-netapp-files-understand-storage-hierarchy.md#large-volumes) for cross-region replication do not support the 10-minute replication schedule. 
+> [!IMPORTANT]
+> [Large volumes](azure-netapp-files-understand-storage-hierarchy.md#large-volumes) for cross-region replication do not support the 10-minute replication schedule. 
 
 Recovery Time Objective (RTO), or the maximum tolerable business application downtime, is determined by factors in bringing up the application and providing access to the data at the second site. The storage portion of the RTO for breaking the peering relationship to activate the destination volume and provide read and write data access in the second site is expected to be complete within a minute.
 

articles/azure-netapp-files/cross-zone-replication-introduction.md

@@ -60,8 +60,8 @@ Cross-zone replication supports three replication schedules: 10 minutes, hourly,
 * For the hourly replication schedule, the typical RPO is less than two hours. 
 * For the daily replication schedule, the typical RPO is less than two days. 
 
->[IMPORTANT]
->[Large volumes](azure-netapp-files-understand-storage-hierarchy.md#large-volumes) for cross-zone replication do not support the 10-minute replication schedule. 
+> [!IMPORTANT]
+> [Large volumes](azure-netapp-files-understand-storage-hierarchy.md#large-volumes) for cross-zone replication do not support the 10-minute replication schedule. 
 
 Recovery Time Objective (RTO), or the maximum tolerable business application downtime, is determined by factors in bringing up the application and providing access to the data at the second site. The storage portion of the RTO for breaking the peering relationship to activate the destination volume and provide read and write data access in the second site is expected to be complete within a minute.