acrolinx edits

Author: ggailey777

includes/messaging-replicator-functions.md

@@ -13,7 +13,7 @@ ms.custom: include file
 
 A replication task receives events from a source and forwards them to a target. Most replication tasks will forward events unchanged and at most perform mapping between metadata structures if the source and target protocols differ.
 
-Replication tasks are generally stateless, meaning that they do not share state or other side-effects across sequential or parallel executions of a task. That is also true for batching and chaining, which can both be implemented on top of the existing state of a stream.
+Replication tasks are generally stateless, meaning that they don't share state or other side-effects across sequential or parallel executions of a task. That is also true for batching and chaining, which can both be implemented on top of the existing state of a stream.
 
 This makes replication tasks different from aggregation tasks, which are generally stateful, and are the domain of analytics frameworks and services like [Azure Stream Analytics](../articles/stream-analytics/stream-analytics-introduction.md).
 
@@ -40,13 +40,13 @@ With Azure Functions Premium, multiple replication applications can share the sa
 
 Whenever available, you should prefer the batch-oriented triggers over triggers that deliver individual events or messages and you should always obtain the complete event or message structure rather than rely on Azure Function's [parameter binding expressions](../articles/azure-functions/functions-bindings-expressions-patterns.md).
 
-The name of the function should reflect the pair of source and target you are connecting, and you should prefix references to connection strings or other configuration elements in the application configuration files with that name.
+The name of the function should reflect the pair of source and target you're connecting, and you should prefix references to connection strings or other configuration elements in the application configuration files with that name.
 
 ### Data and metadata mapping
 
-Once you've decided on a pair of input trigger and output binding, you will have to perform some mapping between the different event or message types, unless the type of your trigger and the output is the same.
+Once you've decided on a pair of input trigger and output binding, you'll have to perform some mapping between the different event or message types, unless the type of your trigger and the output is the same.
 
-For simple replication tasks that copy messages between Event Hubs and Service Bus, you do not have to write your own code, but can lean on a [utility library that is provided](https://github.com/Azure-Samples/azure-messaging-replication-dotnet/tree/main/src/Azure.Messaging.Replication) with the replication samples.
+For simple replication tasks that copy messages between Event Hubs and Service Bus, you don't have to write your own code, but can lean on a [utility library that is provided](https://github.com/Azure-Samples/azure-messaging-replication-dotnet/tree/main/src/Azure.Messaging.Replication) with the replication samples.
 
 ### Retry policy
 
@@ -80,7 +80,7 @@ Replication applications that must access Event Hubs bound to an Azure virtual n
 
 The [samples repository](https://github.com/Azure-Samples/azure-messaging-replication-dotnet/) contains several examples of replication tasks that copy events between Event Hubs and/or between Service Bus entities.
 
-For copying event between Event Hubs, you use an Event Hub Trigger with an Event Hub output binding:
+For copying event data between event hubs, you use an Event Hubs Trigger with an Event Hubs output binding:
 
 ```csharp
 [FunctionName("telemetry")]
@@ -112,9 +112,9 @@ The helper methods can make it easy to replicate between Event Hubs and Service
 
 | Source      | Target      | Entry Point |
 |-------------|-------------|------------------------------------------------------------------------
-| Event Hub   | Event Hub   | `Azure.Messaging.Replication.EventHubReplicationTasks.ForwardToEventHub`
-| Event Hub   | Service Bus | `Azure.Messaging.Replication.EventHubReplicationTasks.ForwardToServiceBus`
-| Service Bus | Event Hub   | `Azure.Messaging.Replication.ServiceBusReplicationTasks.ForwardToEventHub`
+| Event Hubs   | Event Hubs   | `Azure.Messaging.Replication.EventHubReplicationTasks.ForwardToEventHub`
+| Event Hubs   | Service Bus | `Azure.Messaging.Replication.EventHubReplicationTasks.ForwardToServiceBus`
+| Service Bus | Event Hubs   | `Azure.Messaging.Replication.ServiceBusReplicationTasks.ForwardToEventHub`
 | Service Bus | Service Bus | `Azure.Messaging.Replication.ServiceBusReplicationTasks.ForwardToServiceBus`
 
 ### Monitoring