From c8a2501283282daf601930096378cb3a80fe4981 Mon Sep 17 00:00:00 2001 From: akmhmgc Date: Mon, 1 Jan 2024 22:26:48 +0900 Subject: [PATCH] chore: fix trivial typo --- _data/tutorials.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_data/tutorials.yaml b/_data/tutorials.yaml index 648cf124a1..85d01c74f9 100644 --- a/_data/tutorials.yaml +++ b/_data/tutorials.yaml @@ -1077,7 +1077,7 @@ multiple-event-types: You have distinct but related event types and you want to produce them to the same topic, but you also want to maintain topic-name subject constraints. Why produce different events to the same topic? One reason would be you have low-traffic - topics and you'd like to consolodate them to reduce overhead for the brokers. + topics and you'd like to consolidate them to reduce overhead for the brokers. Or you need to get the exact order of different events and by producing them to the same topic you are guaranteed correct ordering per-partition.