reviewer's comments applied_2

doc/reference/configuration/configuration_reference.rst

@@ -4152,19 +4152,15 @@ autoexpel full example
 
     **Since:** :doc:`3.3.0 </release/3.3.0>`
 
-    The ``replication.synchro_queue_max_size`` option controls the maximum size of the synchronous transaction queue on a master node.
-    This parameter ensures that the queue does not grow indefinitely, potentially impacting performance and resource usage.
+    The maximum size of the synchronous transaction queue on a master node, in bytes.
+    This parameter ensures that the queue does not grow indefinitely, potentially impacting performance and resource usage, and applies only to the master node.
 
-    The size is measured in bytes, with a value of 0 disabling the limit (unlimited queue, as in earlier versions).
-
-    .. NOTE::
-
-        Applies only to the master node.
+    The ``0`` value disables the limit.
 
 
     If the synchronous queue reaches the configured size limit, new transactions attempting to enter the queue are discarded.
     In such cases, the system returns an error to the user:
-    “The synchronous transaction queue is full.”
+    ``The synchronous transaction queue is full.``
 
     This size limitation does not apply during the recovery process. Transactions processed during recovery are unaffected by the queue size limit.
 
@@ -4195,21 +4191,6 @@ autoexpel full example
         replication:
             synchro_queue_max_size: 33554432  # Limit set to 32 MB
 
-
-    .. code-block:: lua
-
-        box.cfg{
-          replication_synchro_queue_max_size = 33554432  -- Limit set to 32 MB
-        }
-
-
-    .. hint::
-
-	- Ensure the ``synchro_queue_max_size`` value is sufficient for the expected transaction workload to avoid unnecessary rejections.
-	- Setting the limit to 0 removes any restrictions but may result in unbounded queue growth.
-	- Monitor the queue size using ``box.info.synchro.queue.size`` to adjust the limit if needed.
-
-
     |
     | Type: integer
     | Default: 16777216 (16 MB)