From 8e6c1fd53ba5e20434ff08fa8cbff7c9f1ffd8fe Mon Sep 17 00:00:00 2001
From: Victoria Xia <victoria.xia@confluent.io>
Date: Tue, 25 Apr 2023 15:31:24 -0700
Subject: [PATCH] MINOR: update docs note about spurious stream-stream join
 results

---
 docs/streams/core-concepts.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/streams/core-concepts.html b/docs/streams/core-concepts.html
index 884b39898ed9b..319c981cc3ecf 100644
--- a/docs/streams/core-concepts.html
+++ b/docs/streams/core-concepts.html
@@ -332,7 +332,7 @@ <h3 class="anchor-heading"><a id="streams_out_of_ordering" class="anchor-link"><
     </p>
 
     <ul>
-        <li> For Stream-Stream joins, all three types (inner, outer, left) handle out-of-order records correctly, but the resulted stream may contain unnecessary leftRecord-null for left joins, and leftRecord-null or null-rightRecord for outer joins. </li>
+        <li> For Stream-Stream joins, all three types (inner, outer, left) handle out-of-order records correctly. </li>
         <li> For Stream-Table joins, out-of-order records are not handled (i.e., Streams applications don't check for out-of-order records and just process all records in offset order), and hence it may produce unpredictable results. </li>
         <li> For Table-Table joins, out-of-order records are not handled (i.e., Streams applications don't check for out-of-order records and just process all records in offset order). However, the join result is a changelog stream and hence will be eventually consistent. </li>
     </ul>