Update load-balancer-standard-availability-zones.md

Author: anavinahar

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

@@ -199,7 +199,7 @@ Review [Azure cloud design patterns](https://docs.microsoft.com/azure/architectu
 
 ### <a name="zonalityguidance"></a> Zone-redundant versus zonal
 
-Zone-redundant can provide a simplicity with a zone-agnostic option and at the same time resilient option with a single IP address for the service.  It can reduce complexity in turn.  Zone-redundant also has mobility across zones, and can be safely used on resources in any zone.  Also, it's future proof in regions without availability zones, which can limit changes required once a region does gain availability zones.  The configuration syntax for a zone-redundant IP address or frontend succeeds in any region including those without availability zones: a zone is not specified within the zones: property of the resource.
+Zone-redundant ensure high availability by ensuring your Standard Load balancer public frontend is replicated across all zones.This means your deployment will not share fate with the health of a single zone. Zone-redundant also has mobility across zones and can be safely used on resources in any zone.
 
 Zonal can provide an explicit guarantee to a zone, explicitly sharing fate with the health of the zone. Creating a Load Balancer rule with a zonal IP address frontend or zonal internal Load Balancer frontend can be a desirable especially if your attached resource is a zonal virtual machine in the same zone.  Or perhaps your application requires explicit knowledge about which zone a resource is located in ahead of time and you wish to reason about availability in separate zones explicitly.  You can choose to expose multiple zonal frontends for an end-to-end service distributed across zones (that is, per zone zonal frontends for multiple zonal virtual machine scale sets).  And if your zonal frontends are public IP addresses, you can use these multiple zonal frontends for exposing your service with [Traffic Manager](../traffic-manager/traffic-manager-overview.md).  Or you can use multiple zonal frontends to gain per zone health and performance insights through third party monitoring solutions and expose the overall service with a zone-redundant frontend. You should only serve zonal resources with zonal frontends aligned to the same zone and avoid potentially harmful cross-zone scenarios for zonal resources.  Zonal resources only exist in regions where availability zones exist.