Skip to content

Commit c243212

Browse files
committed
resolving blocker
1 parent 8d3ac90 commit c243212

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

articles/event-hubs/event-hubs-business-continuity-outages-disasters.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ ms.date: 5/13/2025
88
ms.custom: references_regions
99
---
1010

11-
# Best practices for insulating Azure Event Hubs Applications Against Outages and Disasters
11+
# Best practices for insulating Azure Event Hubs applications against outages and disasters
1212

1313
Mission-critical applications must operate continuously, even in the presence of planned maintenance or unplanned outages or disasters. Resilience against disastrous outages of data processing resources is a requirement for many enterprises and, in some cases, mandated by industry regulations. This article describes techniques you can use to protect Event Hubs applications during planned maintenance or against potential service outages or disasters.
1414

articles/event-hubs/geo-replication.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -124,7 +124,7 @@ Here are some cases where a promotion of a secondary to primary may be triggered
124124

125125
* Performance Issues: If the primary region is experiencing performance issues that impact the availability or reliability of your Event Hubs, promoting the secondary region can help mitigate these issues.
126126

127-
It is recommended to occasionally test failover mechanisms to ensure the business continuity plan is effeective, and your applications can seamlessly switch to the secondary region when needed.
127+
It is recommended to occasionally test failover mechanisms to ensure the business continuity plan is effective, and your applications can seamlessly switch to the secondary region when needed.
128128

129129
## Monitoring data replication
130130
Users can monitor the progress of the replication job by monitoring the replication lag metric in Application Metrics logs.

0 commit comments

Comments
 (0)