Skip to content

Commit a773b34

Browse files
committed
fixing blocking issues
1 parent 816b266 commit a773b34

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/site-recovery/vmware-physical-azure-support-matrix.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ This article summarizes supported components and settings for disaster recovery
1616
- Follow our [tutorials](tutorial-prepare-azure.md) to try out disaster recovery.
1717

1818
> [!NOTE]
19-
> Site Recovery does not move or store customer data out of the target region, in which disaster recovery has been setup for the source machines. Customers may select a Recovery Services Vault from a different region if they so choose. The Recovery Services Vault contains metadata but no actual customer data.
19+
> Site Recovery does not move or store customer data out of the target region, in which disaster recovery has been set up for the source machines. Customers may select a Recovery Services Vault from a different region if they so choose. The Recovery Services Vault contains metadata but no actual customer data.
2020
2121
## Deployment scenarios
2222

@@ -356,7 +356,7 @@ As average churn on the disks increases, the number of disks that a storage acco
356356
V1 storage account | 600 disks | 300 disks
357357
V2 storage account | 1500 disks | 750 disks
358358

359-
Please note that the above limits are applicable to VMWare and Hyper-V scenarios only.
359+
Please note that the above limits are applicable to VMware and Hyper-V scenarios only.
360360

361361
## Vault tasks
362362

0 commit comments

Comments
 (0)