Apply suggestions from code review

Author: anaharris-ms

articles/reliability/reliability-logic-apps.md

@@ -171,7 +171,20 @@ Consumption logic app workflows automatically support zone redundancy, so no con
 
 ### Capacity planning and management
 
-To prepare for availability zone failure, you should over-provision capacity of service to ensure that the solution can tolerate 1/3 loss of capacity and continue to function without degraded performance during zone-wide outages. Since the platform spreads VMs across three zones and you need to account for at least the failure of one zone, multiply peak workload instance count by a factor of zones/(zones-1), or 3/2. For example, if your typical peak workload requires four instances, you should provision six instances: (2/3 * 6 instances) = 4 instances.
+To prepare for availability zone failure, you should over-provision capacity of service. Over-provisioning allows the solution to tolerate 30% capacity loss and still continue to function without degraded performance. 
+
+To calculate how many instances to over-provision, it's important to know that the platform spreads VMs across three zones and you need to account for at least the failure of one zone.  
+
+Follow these steps to find out how many instances you should provision:
+
+1. Determine the number of instances your peak workload requires. In this example, we use two scenarios. One is with 3 instances and one is with 4.
+2. Retrieve the over-provision instance count by multiplying the peak workload instance count by a factor of [(zones/(zones-1)]:
+
+| Peak workload instance count | Factor of  [(zones/(zones-1)]|Formula| Instances to provision (Rounded) |
+|-------|---------|---------|--------|
+|3|3/2 or 1.5|(3 x 1.5 = 4.5)|5 instances|
+|4|3/2 or 1.5|(4 x 1.5 = 4.5)|6 instances|
+
 
 ::: zone-end