new normal operations section

Author: anaharris-ms

articles/reliability/reliability-app-service.md

@@ -150,9 +150,9 @@ Zone redundancy can only be configured when you create a new App Service plan. I
 
 To prepare for availability zone failure, consider *over-provisioning* the capacity of your integration runtime. Over-provisioning allows the solution to tolerate some degree of capacity loss and still continue to function without degraded performance. To learn more about over-provisioning, see [Manage capacity with over-provisioning](./concept-redundancy-replication-backup.md#manage-capacity-with-over-provisioning).
 
-### Traffic routing between zones
+### Normal operations
 
-During normal operations, traffic is routed between all of your available App Service plan instances across all availability zones.
+**Traffic routing between zones:** During normal operations, traffic is routed between all of your available App Service plan instances across all availability zones.
 
 ### Zone-down experience
 

articles/reliability/reliability-bastion.md

@@ -88,9 +88,9 @@ There's no additional cost to use zone redundancy for Azure Bastion.
 
 **Migration:** It's not possible to change the availability zone configuration of an existing Azure Bastion resource. Instead, you need to create an Azure Bastion resource with the new configuration and delete the old one.
 
-### Traffic routing between zones
+### Normal operations
 
-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.
+**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.
 
 If you configure zone redundancy on Azure Bastion, a session might be sent to an Azure Bastion instance in an availability zone that's different from the virtual machine you're connecting to. In the following diagram, a request from the user is sent to an Azure Bastion instance in zone 2, although the virtual machine is in zone 1:
 

articles/reliability/reliability-data-factory.md

@@ -111,9 +111,9 @@ Zone-redundant Azure Data Factory resources can be deployed in [any region that
 - *Azure-SSIS integration runtime* requires you to explicitly configure the number of nodes that you use. To prepare for availability zone failure, consider *over-provisioning* the capacity of your integration runtime. Over-provisioning allows the solution to tolerate some degree of capacity loss and still continue to function without degraded performance. To learn more about over-provisioning, see [Manage capacity with over-provisioning](./concept-redundancy-replication-backup.md#manage-capacity-with-over-provisioning).
 - *Self-hosted integration runtime* requires you to configure your own capacity and scaling. Consider over-provisioning when you deploy a self-hosted integration runtime.
 
-### Traffic routing between zones
+### Normal operations
 
-During normal operations, Azure Data Factory automatically distributes pipeline activities, triggers, and other work among healthy instances in each availability zone.
+**Traffic routing between zones:** During normal operations, Azure Data Factory automatically distributes pipeline activities, triggers, and other work among healthy instances in each availability zone.
 
 ### Zone-down experience
 

articles/reliability/reliability-logic-apps.md

@@ -175,17 +175,18 @@ To prepare for availability zone failure, consider *over-provisioning* the capac
 
 ::: zone-end
 
-### Traffic routing between zones
+### Normal operations
+
 
 ::: zone pivot="consumption"
 
-During normal operations, workflow invocations can use compute resources in any of the availability zones within the region.
+**Traffic routing between zones:**  During normal operations, workflow invocations can use compute resources in any of the availability zones within the region.
 
 ::: zone-end
 
 ::: zone pivot="standard-workflow-service-plan,standard-app-service-environment"
 
-During normal operations, workflow invocations are spread among all your available plan instances across all availability zones.
+**Traffic routing between zones:**  During normal operations, workflow invocations are spread among all your available plan instances across all availability zones.
 
 ::: zone-end