Skip to content

Commit 8594587

Browse files
committed
Grammar
1 parent a7fec74 commit 8594587

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/storage/common/storage-failover-private-endpoints.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ ms.subservice: common
1414
---
1515
# Failover Considerations for Storage Accounts with Private Endpoints
1616

17-
Storage accounts work different than many other Azure services when it comes to high availability configurations. They don't often use a secondary instance deployed by the customer for resiliency. Instead,storage accounts configured to be [geo-redundant](./storage-account-overview.md#types-of-storage-accounts) replicates to another region, based on [regional pairs](/azure/reliability/cross-region-replication-azure). When necessary, the storage account can fail over to this replicated copy, and operate in the secondary region.
17+
Storage accounts work different than many other Azure services when it comes to high availability configurations. They don't often use a secondary instance deployed by the customer for resiliency. Instead, storage accounts configured to be [geo-redundant](./storage-account-overview.md#types-of-storage-accounts) replicate to another region, based on [regional pairs](/azure/reliability/cross-region-replication-azure). When necessary, the storage account can fail over to this replicated copy, and operate in the secondary region.
1818

1919
This feature means that customers don't need to plan to have a second storage account already running in their second region. You could have multiple storage accounts and use customer managed operations to move data between them, but that is an uncommon pattern.
2020

0 commit comments

Comments
 (0)