From a8fa3f6f38c7cac20360b6b7c9ccfc7372a9d967 Mon Sep 17 00:00:00 2001
From: LavredisG <90918919+LavredisG@users.noreply.github.com>
Date: Fri, 15 Dec 2023 14:11:33 +0200
Subject: [PATCH] Update Transactions.md

- Removed 'semantics' after EoS since S already stands for that.
---
 docs/Transactions.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/Transactions.md b/docs/Transactions.md
index d7158b3d2..bc617055b 100644
--- a/docs/Transactions.md
+++ b/docs/Transactions.md
@@ -47,7 +47,7 @@ try {
 
 ### Choosing a `transactionalId`
 
-The `transactionalId` allows Kafka to fence out zombie instances by rejecting writes from producers with the same `transactionalId`, allowing only writes from the most recently registered producer. To ensure EoS semantics in a stream processing application, it is important that the `transactionalId` is always the same for a given input topic and partition in the read-process-write cycle.
+The `transactionalId` allows Kafka to fence out zombie instances by rejecting writes from producers with the same `transactionalId`, allowing only writes from the most recently registered producer. To ensure EoS in a stream processing application, it is important that the `transactionalId` is always the same for a given input topic and partition in the read-process-write cycle.
 
 The simplest way to achieve this is to encode the topic and partition in the `transactionalId` itself such as the scheme: `"myapp-producer-" + topic + "-" + partition`.