From 65ed5ec206a95e26d6f36dd5685f3f6ac8f7f11e Mon Sep 17 00:00:00 2001 From: ssd04 Date: Mon, 22 Apr 2024 10:46:48 +0300 Subject: [PATCH] fixes after review --- docs/sdk-and-tools/notifier.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/sdk-and-tools/notifier.md b/docs/sdk-and-tools/notifier.md index c050b3090..d8e45e688 100644 --- a/docs/sdk-and-tools/notifier.md +++ b/docs/sdk-and-tools/notifier.md @@ -8,7 +8,7 @@ title: Events notifier ## Overview A MultiversX observer node can push block events to a notifier service, which will process -and forward the events to subscribers (via RabbitMQ, WebSocket Client). This way, one can subscribe to a RabbitMQ +and forward the events to subscribers (via RabbitMQ or WebSocket Client). This way, one can subscribe to a RabbitMQ queue (or WebSocket connection) and receive block events, whenever a block is committed to the chain, instead of polling an API frequently. @@ -252,7 +252,7 @@ There is a separate config section `WebSocketConnector` that has to be aligned w [comment]: # (mx-context-auto) -### HTTP Integration +### HTTP Integration {#websocket-http-integration} The supported config variables are: - `Host`: the address and/or port on which the http server listens on. Should be the same