From 384d295edbb92004b39f9dcab4f3be87d68b0cd3 Mon Sep 17 00:00:00 2001
From: tssdavey <54796226+tssdavey@users.noreply.github.com>
Date: Fri, 3 Jan 2025 12:07:40 +0000
Subject: [PATCH] Update reliability-app-service.md

---
 articles/reliability/reliability-app-service.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/articles/reliability/reliability-app-service.md b/articles/reliability/reliability-app-service.md
index 847ccb8343095..987d6e395d03b 100644
--- a/articles/reliability/reliability-app-service.md
+++ b/articles/reliability/reliability-app-service.md
@@ -103,7 +103,7 @@ Applications that are deployed in a zone-redundant App Service plan continue to
 
 ::: zone pivot="premium"
 
-When you're using App Service Premium v2 or Premium v3 plans, there's no additional cost associated with enabling availability zones as long as you have three or more instances in your App Service plan. You'll be charged based on your App Service plan SKU, the capacity you specify, and any instances you scale to based on your autoscale criteria. If you enable availability zones but specify a capacity less than three, the platform enforces a minimum instance count of three and charges you for those three instances.
+When you're using App Service Premium v2 or Premium v3 plans, there's no additional cost associated with enabling availability zones as long as you have three or more instances in your App Service plan. You'll be charged based on your App Service plan SKU, the capacity you specify, and any instances you scale to based on your autoscale criteria.
 
 ::: zone-end