Skip to content

Commit 7c5faff

Browse files
authored
Merge pull request #114434 from asudbring/lbzoneart
Fixed Typo
2 parents 9862c7e + 0fdc3a2 commit 7c5faff

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/load-balancer/load-balancer-standard-availability-zones.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -98,7 +98,7 @@ Load balancer is flexible in the context of availability zones. You can choose t
9898

9999
Load Balancer makes it simple to have a single IP as a zone-redundant frontend. A zone-redundant IP address can serve a zonal resource in any zone. The IP can survive one or more zone failures as long as one zone remains healthy within the region. Instead, a zonal frontend is a reduction of the service to a single zone and shares fate with the respective zone.
100100

101-
Zone-redundancy doesn't imply hitless datapath or control plane; its data plane. Zone-redundant flows can use any zones and a customer's flows will use all healthy zones in a region. In a zone failure, traffic flows using healthy zones aren't affected.
101+
Zone-redundancy doesn't imply hitless datapath or control plane; it's data plane. Zone-redundant flows can use any zones and a customer's flows will use all healthy zones in a region. In a zone failure, traffic flows using healthy zones aren't affected.
102102

103103
Traffic flows using a zone at the time of zone failure may be affected but applications can recover. Traffic continues in the healthy zones within the region upon retransmission when Azure has converged around the zone failure.
104104

0 commit comments

Comments
 (0)