From e53ba8efc5fa848671cef9a2d772b19ccdd39955 Mon Sep 17 00:00:00 2001 From: hridyesh bisht <41201308+kakabisht@users.noreply.github.com> Date: Thu, 23 Nov 2023 22:35:57 +0530 Subject: [PATCH] Update pages/docs/concepts/asyncapi-document/add-server.md Co-authored-by: Alejandra Quetzalli --- pages/docs/concepts/asyncapi-document/add-server.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/docs/concepts/asyncapi-document/add-server.md b/pages/docs/concepts/asyncapi-document/add-server.md index 67ab2bde448..fe5594d7bce 100644 --- a/pages/docs/concepts/asyncapi-document/add-server.md +++ b/pages/docs/concepts/asyncapi-document/add-server.md @@ -60,7 +60,7 @@ Servers interact with AsyncAPI apps by following configurations defined in the A Here's an example of a server to publish messages to a channel. 1. The server establishes connections based on the server configurations in the AsyncAPI document. -1. The server uses the publishMessage operation ID to publish messages to the channel. The message payload follows the defined schema in the ChatMessage message component. +1. The server uses the `publishMessage` operation ID to publish messages to the channel. The message payload follows the defined schema in the `ChatMessage` message component. 1. When an app subscribes to the chat.message channel, it receives the published messages. ```yaml