Minor edits.

Author: TimShererWithAquent

articles/logic-apps/create-replication-tasks-azure-resources.md

@@ -5,7 +5,7 @@ services: logic-apps
 ms.suite: integration
 ms.reviewer: estfan, azla
 ms.topic: how-to
-ms.date: 11/16/2025
+ms.date: 01/26/2026
 ms.custom: sfi-image-nochange
 #Customer intent: As a developer responsible for Azure services, I want to know how to implement replication in case of communication problems to keep my services available.
 ---
@@ -75,7 +75,7 @@ For information about replication and federation in Azure Event Hubs, see:
 
 The following diagram shows the topology and replication task workflow between Service Bus queues:
 
-:::image type="content" source="media/create-replication-tasks-azure-resources/replication-topology-service-bus-queues.png" alt-text="Diagram show topology for replication task powered by Logic App (Standard) workflow between Service Bus queues.":::
+:::image type="content" source="media/create-replication-tasks-azure-resources/replication-topology-service-bus-queues.png" alt-text="Diagram shows topology for replication task powered by Logic App (Standard) workflow between Service Bus queues.":::
 
 For information about replication and federation in Azure Service Bus, see:
 
@@ -202,7 +202,7 @@ The examples in this section use 800 as the default value for the prefetch count
 |-------|-------------|
 | **Maximum bursts** | The *maximum* number of elastic workers to scale out under load. If your underlying app requires instances beyond the *always ready instances* in the next table row, your app can continue to scale out until the number of instances hits the maximum burst limit. To change this value, see [Edit hosting plan scale-out settings](#edit-plan-scale-out-settings) later in this article. <br>**Note**: Any instances beyond your plan size are billed *only* when they're running and allocated to you on a per-second basis. The platform makes a best effort to scale out your app to the defined maximum limit. <br>**Tip**: As a recommendation, select a maximum value that's higher than you might need so that the platform can scale out to handle a larger load. Unused instances aren't billed. <br>For more information, see the following documentation. The Workflow Standard plan shares some aspects with the Azure Functions Premium plan: <br>- [Premium plan settings](../azure-functions/functions-premium-plan.md#plan-and-sku-settings) <br>- [What is cloud bursting](https://azure.microsoft.com/overview/what-is-cloud-bursting/)? |
 | **Always ready instances** | The minimum number of instances that are always ready and warm for hosting your app. The minimum number is always 1. To change this value, see [Edit hosting plan scale-out settings](#edit-plan-scale-out-settings) later in this article. <br>**Note**: Any instances beyond your plan size are billed *whether or not* they're running when allocated to you. <br>For more information, see the following documentation. The Workflow Standard plan shares some aspects with the Azure Functions Premium plan: [Always ready instances](../azure-functions/functions-premium-plan.md#always-ready-instances). |
-| **Prefetch count** | The default value for `AzureFunctionsJobHost__extensions__serviceBus__prefetchCount` app setting in your logic app resource that determines the prefetch count used by the underlying `ServiceBusProcessor` class. To add or specify a different value for this app setting, see [Manage app settings - local.settings.json](edit-app-settings-host-settings.md?tabs=azure-portal#manage-app-settings), for example: <br>- **Name**: `AzureFunctionsJobHost__extensions__serviceBus__eventProcessorOptions__prefetchCount` <br>- **Value**: `800` (no maximum limit) <br>For more information about the `prefetchCount` property, see: <br>- [Azure Service Bus bindings for Azure Functions](../azure-functions/functions-bindings-service-bus.md) <br>- [ServiceBusProcessor.PrefetchCount property](/dotnet/api/azure.messaging.servicebus.servicebusprocessor.prefetchcount) <br>- [ServiceBusProcessor Class](/dotnet/api/azure.messaging.servicebus.servicebusprocessor) |
+| **Prefetch count** | The default value for `AzureFunctionsJobHost__extensions__serviceBus__prefetchCount` app setting in your logic app resource that determines the prefetch count used by the underlying `ServiceBusProcessor` class. To add or specify a different value for this app setting, see [Manage app settings - local.settings.json](edit-app-settings-host-settings.md?tabs=azure-portal#manage-app-settings), for example: <br>- **Name**: `AzureFunctionsJobHost__extensions__serviceBus__prefetchCount` <br>- **Value**: `800` (no maximum limit) <br>For more information about the `prefetchCount` property, see: <br>- [Azure Service Bus bindings for Azure Functions](../azure-functions/functions-bindings-service-bus.md) <br>- [ServiceBusProcessor.PrefetchCount property](/dotnet/api/azure.messaging.servicebus.servicebusprocessor.prefetchcount) <br>- [ServiceBusProcessor Class](/dotnet/api/azure.messaging.servicebus.servicebusprocessor) |
 | **Maximum message count** | The default value for the `AzureFunctionsJobHost__extensions__serviceBus__batchOptions__maxMessageCount` app setting in your logic app resource that determines the maximum number of messages to send when triggered. To add or specify a different value for this app setting, review [Manage app settings - local.settings.json](edit-app-settings-host-settings.md?tabs=azure-portal#manage-app-settings), for example: <br>- **Name**: `AzureFunctionsJobHost__extensions__serviceBus__batchOptions__maxMessageCount` <br>- **Value**: `800` (no maximum limit) <br>For more information about the `maxMessageCount` property, see [Azure Service Bus bindings for Azure Functions](../azure-functions/functions-bindings-service-bus.md).|
 
 ## Prerequisites