ovsdb-server.7: Mention update3 as replies to monitor_cond_change.

Monitor_cond_change might trigger updates to be sent to clients as results
to condition changes. These updates can be either update2 (for monitor_cond
monitors) or update3 (for monitor_cond_since monitors). The documentation
used to mention only update2.

Signed-off-by: Dumitru Ceara <dceara@redhat.com>
Acked-by: Han Zhou <hzhou@ovn.org>
Signed-off-by: Ilya Maximets <i.maximets@ovn.org>

diff --git a/Documentation/ref/ovsdb-server.7.rst b/Documentation/ref/ovsdb-server.7.rst
index 967761bdfb8451ca672adcd7c1dd47b9d7f0990a..04414350a7755d58907a0fa81373b09728cb0157 100644 (file)
--- a/Documentation/ref/ovsdb-server.7.rst
+++ b/Documentation/ref/ovsdb-server.7.rst
@@ -316,9 +316,9 @@ monitor request, <table-updates2> will contain any matched rows by old
 condition and not matched by the new condition.
 
 Changes according to the new conditions are automatically sent to the client
-using the ``update2`` monitor notification.  An update, if any, as a result of
-a condition change, will be sent to the client before the reply to the
-``monitor_cond_change`` request.
+using the ``update2`` or ``update3`` monitor notification depending on the
+monitor method.  An update, if any, as a result of a condition change, will
+be sent to the client before the reply to the ``monitor_cond_change`` request.
 
 4.1.14 Update2 notification
 ---------------------------