From 9fc5a06906c4dfc0dcf8da83cef815e12e0405c3 Mon Sep 17 00:00:00 2001
From: christinaausley <84338309+christinaausley@users.noreply.github.com>
Date: Mon, 1 Apr 2024 11:23:19 -0400
Subject: [PATCH] backport 3546 (#3553)

---
 .../best-practices/development/routing-events-to-processes.md   | 2 +-
 .../best-practices/development/routing-events-to-processes.md   | 2 +-
 .../best-practices/development/routing-events-to-processes.md   | 2 +-
 .../best-practices/development/routing-events-to-processes.md   | 2 +-
 4 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/docs/components/best-practices/development/routing-events-to-processes.md b/docs/components/best-practices/development/routing-events-to-processes.md
index b4cf9d5825b..62734af8fa5 100644
--- a/docs/components/best-practices/development/routing-events-to-processes.md
+++ b/docs/components/best-practices/development/routing-events-to-processes.md
@@ -151,7 +151,7 @@ You can also use [`CreateProcessInstanceWithResult`](/apis-tools/zeebe-api/gatew
 As soon as you have multiple possible starting points, you have to use named messages to start process instances. The API method is [`PublishMessage`](/apis-tools/zeebe-api/gateway-service.md#publishmessage-rpc):
 
 ```java
-client.newPublishMessageComment()
+client.newPublishMessageCommand()
   .messageName("message_invoiceReceived") // <1>
   .corrlationKey(invoiceId) // <2>
   .variables( // <3>
diff --git a/versioned_docs/version-8.1/components/best-practices/development/routing-events-to-processes.md b/versioned_docs/version-8.1/components/best-practices/development/routing-events-to-processes.md
index c1660506995..510a8b2b671 100644
--- a/versioned_docs/version-8.1/components/best-practices/development/routing-events-to-processes.md
+++ b/versioned_docs/version-8.1/components/best-practices/development/routing-events-to-processes.md
@@ -155,7 +155,7 @@ You can also use [`CreateProcessInstanceWithResult`](/apis-tools/grpc.md/#create
 As soon as you have multiple possible starting points, you have to use named messages to start process instances. The API method is [`PublishMessage`](/apis-tools/grpc.md/#publishmessage-rpc):
 
 ```java
-client.newPublishMessageComment()
+client.newPublishMessageCommand()
   .messageName("message_invoiceReceived") // <1>
   .corrlationKey(invoiceId) // <2>
   .variables( // <3>
diff --git a/versioned_docs/version-8.2/components/best-practices/development/routing-events-to-processes.md b/versioned_docs/version-8.2/components/best-practices/development/routing-events-to-processes.md
index 51f14b6b160..7b088cf86c8 100644
--- a/versioned_docs/version-8.2/components/best-practices/development/routing-events-to-processes.md
+++ b/versioned_docs/version-8.2/components/best-practices/development/routing-events-to-processes.md
@@ -155,7 +155,7 @@ You can also use [`CreateProcessInstanceWithResult`](../../../apis-tools/grpc.md
 As soon as you have multiple possible starting points, you have to use named messages to start process instances. The API method is [`PublishMessage`](../../../apis-tools/grpc.md#publishmessage-rpc):
 
 ```java
-client.newPublishMessageComment()
+client.newPublishMessageCommand()
   .messageName("message_invoiceReceived") // <1>
   .corrlationKey(invoiceId) // <2>
   .variables( // <3>
diff --git a/versioned_docs/version-8.3/components/best-practices/development/routing-events-to-processes.md b/versioned_docs/version-8.3/components/best-practices/development/routing-events-to-processes.md
index d3f9d14023f..8c99f704e41 100644
--- a/versioned_docs/version-8.3/components/best-practices/development/routing-events-to-processes.md
+++ b/versioned_docs/version-8.3/components/best-practices/development/routing-events-to-processes.md
@@ -155,7 +155,7 @@ You can also use [`CreateProcessInstanceWithResult`](../../../apis-tools/grpc.md
 As soon as you have multiple possible starting points, you have to use named messages to start process instances. The API method is [`PublishMessage`](../../../apis-tools/grpc.md#publishmessage-rpc):
 
 ```java
-client.newPublishMessageComment()
+client.newPublishMessageCommand()
   .messageName("message_invoiceReceived") // <1>
   .corrlationKey(invoiceId) // <2>
   .variables( // <3>