aboutsummaryrefslogtreecommitdiff
path: root/doc/zmq.md
diff options
context:
space:
mode:
Diffstat (limited to 'doc/zmq.md')
-rw-r--r--doc/zmq.md9
1 files changed, 4 insertions, 5 deletions
diff --git a/doc/zmq.md b/doc/zmq.md
index 07c340fb99..0a74d6eef9 100644
--- a/doc/zmq.md
+++ b/doc/zmq.md
@@ -46,11 +46,10 @@ operation.
## Enabling
-By default, the ZeroMQ feature is automatically compiled in if the
-necessary prerequisites are found. To disable, use --disable-zmq
-during the *configure* step of building bitcoind:
+By default, the ZeroMQ feature is not automatically compiled.
+To enable, use `-DWITH_ZMQ=ON` when configuring the build system:
- $ ./configure --disable-zmq (other options)
+ $ cmake -B build -DWITH_ZMQ=ON
To actually enable operation, one must set the appropriate options on
the command line or in the configuration file.
@@ -163,7 +162,7 @@ Note that for `*block` topics, when the block chain tip changes,
a reorganisation may occur and just the tip will be notified.
It is up to the subscriber to retrieve the chain from the last known
block to the new tip. Also note that no notification will occur if the tip
-was in the active chain--as would be the case after calling invalidateblock RPC.
+was in the active chain, as would be the case after calling the `invalidateblock` RPC.
In contrast, the `sequence` topic publishes all block connections and
disconnections.