Minor updates for templates

Author: johndowns

articles/reliability/reliability-app-service.md

@@ -160,15 +160,15 @@ To prepare for availability zone failure, consider *over-provisioning* the capac
 
 ### Normal operations
 
-The following information describes what happens when you have a zone-redundant App Service plan and all availability zones are operational:
+This section describes what to expect when Azure App Service plans are configured for zone redundancy and all availability zones are operational.
 
 - **Traffic routing between zones:** During normal operations, traffic is routed between all of your available App Service plan instances across all availability zones.
 
 - **Data replication between zones:** During normal operations, any state stored in your application's file system is stored in zone-redundant storage, and is synchronously replicated between availability zones.
 
 ### Zone-down experience
 
-The following information describes what happens when you have a zone-redundant App Service plan and there's an availability zone outage:
+This section describes what to expect when an Azure App Service plan is configured for zone redundancy and there's an availability zone outage:
 
 - **Detection and response:** The App Service platform is responsible for detecting a failure in an availability zone and responding. You don't need to do anything to initiate a zone failover.
 

articles/reliability/reliability-bastion.md

@@ -90,7 +90,7 @@ There's no additional cost to use zone redundancy for Azure Bastion.
 
 ### Normal operations
 
-This section describes what to expect when Bastion resources are configured for zone redundancy and all availability zones are operational.
+This section describes what to expect when Azure Bastion resources are configured for availability zone support and all availability zones are operational.
 
 **Traffic routing between zones:** When you initiate an SSH or RDP session, it can be routed to an Azure Bastion instance in any of the availability zones you selected.
 
@@ -103,11 +103,13 @@ In most scenarios, the small amount of cross-zone latency isn't significant. How
 
 ### Zone-down experience
 
+This section describes what to expect when an Azure Bastion resource is configured for availability zone support and there's an availability zone outage.
+
 - **Detection and response:** When you use zone redundancy, Azure Bastion detects and responds to failures in an availability zone. You don't need to do anything to initiate an availability zone failover.
 
 - **Active requests:** When an availability zone is unavailable, any RDP or SSH connections in progress that use an Azure Bastion instance in the faulty availability zone are terminated and need to be retried.
 
-If the virtual machine you're connecting to isn't in the affected availability zone, the virtual machine continues to be accessible. See [Reliability in virtual machines: Zone down experience](./reliability-virtual-machines.md#zone-down-experience) for more information on the VM zone down experience.
+    If the virtual machine you're connecting to isn't in the affected availability zone, the virtual machine continues to be accessible. See [Reliability in virtual machines: Zone down experience](./reliability-virtual-machines.md#zone-down-experience) for more information on the VM zone down experience.
 
 - **Traffic rerouting:** When you use zone redundancy, new connections use Azure Bastion instances in the surviving availability zones. Overall, Azure Bastion remains operational.
 

articles/reliability/reliability-data-factory.md

@@ -119,6 +119,8 @@ This section describes what to expect when Azure Data Factory resources are conf
 
 ### Zone-down experience
 
+This section describes what to expect when Azure Data Factory resources are configured for zone redundancy and there's an availability zone outage.
+
 - **Detection and response.** The Azure Data Factory platform is responsible for detecting a failure in an availability zone and responding. You don't need to do anything to initiate a zone failover in your pipelines or other components.
 
 - **Active requests.** Any pipelines and triggers in progress continue to execute, and you won't notice a zone failure. However, activities in progress during a zone failure might fail and be restarted. It's important to design activities to be idempotent, which helps them to recover from zone failures as well as other faults. For more information, see [Transient faults](#transient-faults).

articles/reliability/reliability-logic-apps.md

@@ -179,7 +179,6 @@ To prepare for availability zone failure, consider *over-provisioning* the capac
 
 This section describes what to expect when Azure Logic Apps resources are configured for zone redundancy and all availability zones are operational.
 
-
 ::: zone pivot="consumption"
 
 **Traffic routing between zones:**  During normal operations, workflow invocations can use compute resources in any of the availability zones within the region.
@@ -194,6 +193,8 @@ This section describes what to expect when Azure Logic Apps resources are config
 
 ### Zone-down experience
 
+This section describes what to expect when Azure Logic Apps resources are configured for zone redundancy and there's an availability zone outage.
+
 - **Detection and response:** The Azure Logic Apps platform is responsible for detecting a failure in an availability zone. You don't need to do anything to initiate a zone failover.
 
 - **Active requests:** If an availability zone becomes unavailable, any in-progress workflow executions that run on a VM in the faulty availability zone are terminated. The Azure Logic Apps platform automatically resumes the workflow on another VM in a different availability zone. Due to this behavior, active workflows might experience some [transient faults](#transient-faults) or higher latency as new VMs are added to the remaining availability zones.