Skip to content

Commit 0b49172

Browse files
Apply suggestions from code review
Co-authored-by: John Downs <[email protected]>
1 parent fc8abb2 commit 0b49172

File tree

1 file changed

+2
-5
lines changed

1 file changed

+2
-5
lines changed

articles/reliability/reliability-app-service.md

Lines changed: 2 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ When you deploy App Service, you can provision multiple instances in an [App Ser
2727

2828
- Use premium v3/v4 App Service plans.
2929

30-
- [Enable zone redundancy](#availability-zone-support). To see requirements for enabling zone -redundancy, go to [Availability zone support requirements](#requirements).
30+
- [Enable zone redundancy](#availability-zone-support). To see requirements for enabling zone redundancy, go to [Availability zone support requirements](#requirements).
3131

3232
::: zone-end
3333

@@ -47,7 +47,7 @@ Microsoft-provided SDKs usually handle transient faults. Because you host your o
4747

4848
- **Use deployment slots.** App Service [deployment slots](/azure/app-service/deploy-staging-slots) enable zero-downtime deployments of your applications. Use deployment slots to minimize the effect of deployments and configuration changes for your users. Deployment slots also reduce the likelihood that your application restarts. Restarting the application causes a transient fault.
4949

50-
- **Avoid scaling up or scaling down.** Instead of scaling up or scaling down, select a tier and instance size that meet your performance requirements under typical load. Only scale out instances to handle changes in traffic volume. Scaling up and scaling down can trigger an application restart.
50+
- **Avoid scaling up or scaling down.** Scaling up and down require involve changing the CPU, memory, and other resources that are allocated to each instance. Scale-up and scale-down operations can trigger an application restart. Instead of scaling up or scaling down, select a tier and instance size that meet your performance requirements under typical load. You can scale out and scale in by dynamically adding and removing instances to handle changes in traffic volume.
5151

5252
## Availability zone support
5353

@@ -326,9 +326,6 @@ To deploy a new zone-redundant App Service plan, you must use either the [Premiu
326326
> [!NOTE]
327327
> If you use the Azure CLI to disable the `zoneRedundant` property, you should specify the `sku.capacity` property, otherwise the value defaults to 1.
328328
329-
> [!NOTE]
330-
> If you use the Azure CLI to disable the zoneRedundant property, you should specify the sku.capacity property. Otherwise, the value defaults to 1.
331-
332329
::: zone-end
333330
334331
::: zone pivot="premium,isolated"

0 commit comments

Comments
 (0)