From ee6c986c9f9f8ed7b0628229e53ad37171505113 Mon Sep 17 00:00:00 2001 From: Warren James Date: Tue, 9 Jan 2024 14:53:05 -0500 Subject: [PATCH] strengthen wording --- .../server-discovery-and-monitoring-logging-and-monitoring.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/server-discovery-and-monitoring/server-discovery-and-monitoring-logging-and-monitoring.rst b/source/server-discovery-and-monitoring/server-discovery-and-monitoring-logging-and-monitoring.rst index f75cd983a3..7f5ef43678 100644 --- a/source/server-discovery-and-monitoring/server-discovery-and-monitoring-logging-and-monitoring.rst +++ b/source/server-discovery-and-monitoring/server-discovery-and-monitoring-logging-and-monitoring.rst @@ -138,7 +138,7 @@ Events that MUST be published (with their conditions) are as follows. * - ``TopologyClosedEvent`` - When a topology is shut down - this MUST be the last SDAM event fired. * - ``ServerHeartbeatStartedEvent`` - - Published when the server monitor sends its ``hello`` or legacy hello call to the server. When the monitor is creating a new connection, this event is published just after the socket is created and just before the ``hello`` or legacy hello. + - Published when the server monitor sends its ``hello`` or legacy hello call to the server. When the monitor is creating a new connection, this event MUST be published just after the socket is created and just before the ``hello`` or legacy hello. * - ``ServerHeartbeatSucceededEvent`` - Published on successful completion of the server monitor's ``hello`` or legacy hello call. * - ``ServerHeartbeatFailedEvent``