Skip to content

Commit d527970

Browse files
committed
edits
1 parent f523540 commit d527970

6 files changed

+8
-8
lines changed

articles/reliability/includes/app-service/reliability-architecture-overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,4 +17,4 @@ App Service provides the following redundancy features:
1717

1818
- **Scale units:** App Service runs on a platform infrastructure called *scale units*, also known as *stamps*. A scale unit includes all components needed to host and run App Service, including compute, storage, networking, and load balancing. Azure manages scale units to ensure balanced workload distribution, perform routine maintenance, and maintain overall platform reliability.
1919

20-
Some capabilities might only be applied on specific scale units. For example, some App Service scale units might support zone redundancy, while other scale units in the same region don't support it.
20+
Some capabilities might only be applied on specific scale units. For example, some App Service scale units might support zone redundancy, while other scale units in the same region don't.

articles/reliability/includes/app-service/reliability-architecture-plans.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,4 +7,4 @@
77
ms.custom: include file
88
---
99

10-
An App Service plan defines a set of compute resources that run your web apps. All web apps must run inside an App Service plan. You can scale an App Service plan to run on multiple VM *instances*, also called *workers*. These instances provide the compute resources that run your app code. A single App Service plan can host multiple apps. All apps run on the same shared set of VM instances.
10+
An App Service plan defines a set of compute resources that run your web apps. All web apps must run inside a plan. You can scale a plan to run on multiple VM *instances*, also called *workers*. These instances provide the compute resources that run your app code. A single App Service plan can host multiple apps. All apps run on the same shared set of VM instances.

articles/reliability/includes/app-service/reliability-normal-operations-include.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@
66
ms.author: anaharris
77
ms.custom: include file
88
---
9-
The following section describes what to expect when you configure App Service plans for zone redundancy and all availability zones are operational:
9+
Expect the following outcomes when you configure App Service plans for zone redundancy and all availability zones function properly:
1010

1111
- **Traffic routing between zones:** During normal operations, traffic is routed between all available App Service plan instances across all availability zones.
1212

articles/reliability/includes/app-service/reliability-zone-down-experience-include.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@
88
---
99
An availability zone outage might affect some aspects of App Service, even though the application continues to serve traffic. These behaviors include App Service plan scaling, application creation, application configuration, and application publishing.
1010

11-
The following section describes what to expect when you configure App Service plans for zone redundancy and one or more availability zones are unavailable:
11+
Expect the following outcomes when you configure App Service plans for zone redundancy and one or more availability zones are unavailable:
1212

1313
- **Detection and response:** The App Service platform automatically detects failures in an availability zone and initiates a response. No manual intervention is required to initiate a zone failover.
1414

articles/reliability/includes/reliability-transient-fault-description-include.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,6 +9,6 @@
99
ms.custom: include file
1010
---
1111

12-
Transient faults are short, intermittent failures in components. They occur frequently in a distributed environment like the cloud, and they're a normal part of operations. Transient faults correct themselves after a short period of time. It's important that your applications handle transient faults, usually by retrying affected requests.
12+
Transient faults are short, intermittent failures in components. They occur frequently in a distributed environment like the cloud, and they're a normal part of operations. Transient faults correct themselves after a short period of time. It's important that your applications can handle transient faults, usually by retrying affected requests.
1313

1414
All cloud-hosted applications should follow the Azure transient fault handling guidance when they communicate with any cloud-hosted APIs, databases, and other components. For more information, see [Recommendations for handling transient faults](/azure/well-architected/reliability/handle-transient-faults).

articles/reliability/reliability-app-service-environment.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ An environment provides the following key reliability benefits:
2121
- Enhanced network isolation for improved security and stability
2222
- The ability to deploy in your own virtual network for greater control over traffic routing and security policies
2323

24-
This article describes reliability support in an [App Service Environment](../app-service/environment/overview.md). It covers intra-regional resiliency via [availability zones](#availability-zone-support) and [multiple-region deployments](#multi-region-support).
24+
This article describes reliability support in [App Service Environment](../app-service/environment/overview.md). It covers intra-regional resiliency via [availability zones](#availability-zone-support) and [multiple-region deployments](#multi-region-support).
2525

2626
For more information about reliability support in App Service, see [Reliability in App Service](./reliability-app-service.md).
2727

@@ -39,7 +39,7 @@ After you create your environment, you can create one or more App Service plans.
3939

4040
[!INCLUDE [App Service reliability architecture - plan description](includes/app-service/reliability-architecture-plans.md)]
4141

42-
To use an App Service Environment, your plans must use the [Isolated v2 pricing tier](/azure/app-service/overview-hosting-plans#isolated-v2). The Isolated v2 pricing tier supports zone redundancy and is designed for high-scale, mission-critical applications.
42+
To use an App Service Environment, your plans must use the [Isolated v2 pricing tier](/azure/app-service/overview-hosting-plans#isolated-v2). This tier supports zone redundancy and high-scale, mission-critical applications.
4343

4444
[!INCLUDE [App Service reliability architecture overview](includes/app-service/reliability-architecture-overview.md)]
4545

@@ -55,7 +55,7 @@ To use an App Service Environment, your plans must use the [Isolated v2 pricing
5555

5656
You can configure your App Service Environment as *zone redundant*. You can also configure your App Service plans to be zone redundant, which distributes them across multiple availability zones.
5757

58-
You can enable or disable zone redundancy on each plan. Some plans in your environment can be zone redundant, while others aren't.
58+
You can enable or disable zone redundancy on each specific plan.
5959

6060
When you create a zone-redundant App Service plan in your environment, the instances of your App Service plan are distributed across the availability zones in the region. For more information, see [Instance distribution across zones](../reliability/reliability-app-service.md#instance-distribution-across-zones).
6161

0 commit comments

Comments
 (0)