From 0ab7ef6eb96973b40f678294b59bddce25dfdedf Mon Sep 17 00:00:00 2001
From: Serge Petrenko <35663196+sergepetrenko@users.noreply.github.com>
Date: Wed, 13 Dec 2023 10:46:52 +0300
Subject: [PATCH] changelog: reword gh-9235 changelog

Follow-up #9235

NO_DOC=changelog
NO_TEST=changelog

Co-authored-by: Kseniia Antonova <73473519+xuniq@users.noreply.github.com>
---
 .../gh-9235-assertion_in_box_wait_limbo_acked.md       | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/changelogs/unreleased/gh-9235-assertion_in_box_wait_limbo_acked.md b/changelogs/unreleased/gh-9235-assertion_in_box_wait_limbo_acked.md
index fd2db3bd3e..4201301bd0 100644
--- a/changelogs/unreleased/gh-9235-assertion_in_box_wait_limbo_acked.md
+++ b/changelogs/unreleased/gh-9235-assertion_in_box_wait_limbo_acked.md
@@ -2,8 +2,8 @@
 
 * Fixed a bug when the assertion in `box_wait_limbo_acked` would fail. The
   assertion is that the lsn of the last entry in limbo is always positive after
-  `wal_sync`. What happened in the release build before the patch? If the
-  `replication_synchro_quorum` is set too high on the replica, then it will never
-  be reached. After the timeout is triggered, the user will receive a `TimedOut`
-  error. If `replication_synchro_quorum` <= number of instances in the replica
-  set, the program will immediately stop with a `Segmentation fault` (gh-9235).
+  `wal_sync`. Before the patch, if the `replication_synchro_quorum` was set too
+  high on the replica, it would never be reached. After the timeout was
+  triggered, the user received a `TimedOut` error. If the quorum was greater
+  than or equal to the number of instances in the replica set, the program
+  immediately stopped with a segmentation fault (gh-9235).
-- 
GitLab