From 6e39c912952ebbfae4eb2fa6d74e73f978ce56ef Mon Sep 17 00:00:00 2001 From: Ryan Bonnell Date: Thu, 6 Feb 2025 12:15:08 -0800 Subject: [PATCH] Edit words --- docs/userguide/operation/webhooks.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/userguide/operation/webhooks.md b/docs/userguide/operation/webhooks.md index 58464c50..95ab6b88 100644 --- a/docs/userguide/operation/webhooks.md +++ b/docs/userguide/operation/webhooks.md @@ -139,10 +139,10 @@ than HTTP, such as AMQP or Kafka. It can be desirable for log events to be delivered to the destination system in a batch; the primary motivation for this is to amortize the -cost of a database transaction on the remote system by handle more than +cost of a database transaction on the remote system by handling more than one record per transaction. -You can implementing batching by setting the `batch_size` parameter +You can implement batching by setting the `batch_size` parameter to a value greater than 1. When you do this, the hook is run in a batch mode and it is expected to return a `connection` object that has a `send_batch` method rather than the `send` method shown in the example