diff --git a/go/api/commands.go b/go/api/commands.go
index 63a825e7bc..f48239c524 100644
--- a/go/api/commands.go
+++ b/go/api/commands.go
@@ -132,13 +132,7 @@ type StringCommands interface {
 	// Sets multiple keys to multiple values in a single operation.
 	//
 	// Note:
-	//   In cluster mode, if keys in `keyValueMap` map to different hash slots,
-	//   the command will be split across these slots and executed separately for each.
-	//   This means the command is atomic only at the slot level. If one or more slot-specific
-	//   requests fail, the entire call will return the first encountered error, even
-	//   though some requests may have succeeded while others did not.
-	//   If this behavior impacts your application logic, consider splitting the
-	//   request into sub-requests per slot to ensure atomicity.
+	//  When in cluster mode, the command may route to multiple nodes when keys in keyValueMap map to different hash slots.
 	//
 	// See [valkey.io] for details.
 	//
@@ -159,13 +153,7 @@ type StringCommands interface {
 	// Retrieves the values of multiple keys.
 	//
 	// Note:
-	//   In cluster mode, if keys in `keys` map to different hash slots,
-	//   the command will be split across these slots and executed separately for each.
-	//   This means the command is atomic only at the slot level. If one or more slot-specific
-	//   requests fail, the entire call will return the first encountered error, even
-	//   though some requests may have succeeded while others did not.
-	//   If this behavior impacts your application logic, consider splitting the
-	//   request into sub-requests per slot to ensure atomicity.
+	//  When in cluster mode, the command may route to multiple nodes when keys map to different hash slots.
 	//
 	// See [valkey.io] for details.
 	//
diff --git a/java/client/src/main/java/glide/api/commands/GenericBaseCommands.java b/java/client/src/main/java/glide/api/commands/GenericBaseCommands.java
index 6fa8806c05..6234672899 100644
--- a/java/client/src/main/java/glide/api/commands/GenericBaseCommands.java
+++ b/java/client/src/main/java/glide/api/commands/GenericBaseCommands.java
@@ -23,14 +23,12 @@ public interface GenericBaseCommands {
      * Removes the specified <code>keys</code> from the database. A key is ignored if it does not
      * exist.
      *
-     * @apiNote In cluster mode, if keys in <code>keys</code> map to different hash slots,
-     * the command will be split across these slots and executed separately for each.
-     * This means the command is atomic only at the slot level. If one or more slot-specific
-     * requests fail, the entire call will return the first encountered error, even
-     * though some requests may have succeeded while others did not.
-     * If this behavior impacts your application logic, consider splitting the
-     * request into sub-requests per slot to ensure atomicity.
-     * 
+     * @apiNote In cluster mode, if keys in <code>keys</code> map to different hash slots, the command
+     *     will be split across these slots and executed separately for each. This means the command
+     *     is atomic only at the slot level. If one or more slot-specific requests fail, the entire
+     *     call will return the first encountered error, even though some requests may have succeeded
+     *     while others did not. If this behavior impacts your application logic, consider splitting
+     *     the request into sub-requests per slot to ensure atomicity.
      * @see <a href="https://valkey.io/commands/del/">valkey.io</a> for details.
      * @param keys The keys we wanted to remove.
      * @return The number of keys that were removed.
@@ -46,14 +44,12 @@ public interface GenericBaseCommands {
      * Removes the specified <code>keys</code> from the database. A key is ignored if it does not
      * exist.
      *
-     * @apiNote In cluster mode, if keys in <code>keys</code> map to different hash slots,
-     * the command will be split across these slots and executed separately for each.
-     * This means the command is atomic only at the slot level. If one or more slot-specific
-     * requests fail, the entire call will return the first encountered error, even
-     * though some requests may have succeeded while others did not.
-     * If this behavior impacts your application logic, consider splitting the
-     * request into sub-requests per slot to ensure atomicity.
-     * 
+     * @apiNote In cluster mode, if keys in <code>keys</code> map to different hash slots, the command
+     *     will be split across these slots and executed separately for each. This means the command
+     *     is atomic only at the slot level. If one or more slot-specific requests fail, the entire
+     *     call will return the first encountered error, even though some requests may have succeeded
+     *     while others did not. If this behavior impacts your application logic, consider splitting
+     *     the request into sub-requests per slot to ensure atomicity.
      * @see <a href="https://valkey.io/commands/del/">valkey.io</a> for details.
      * @param keys The keys we wanted to remove.
      * @return The number of keys that were removed.
@@ -68,14 +64,12 @@ public interface GenericBaseCommands {
     /**
      * Returns the number of keys in <code>keys</code> that exist in the database.
      *
-     * @apiNote In cluster mode, if keys in <code>keys</code> map to different hash slots,
-     * the command will be split across these slots and executed separately for each.
-     * This means the command is atomic only at the slot level. If one or more slot-specific
-     * requests fail, the entire call will return the first encountered error, even
-     * though some requests may have succeeded while others did not.
-     * If this behavior impacts your application logic, consider splitting the
-     * request into sub-requests per slot to ensure atomicity.
-     * 
+     * @apiNote In cluster mode, if keys in <code>keys</code> map to different hash slots, the command
+     *     will be split across these slots and executed separately for each. This means the command
+     *     is atomic only at the slot level. If one or more slot-specific requests fail, the entire
+     *     call will return the first encountered error, even though some requests may have succeeded
+     *     while others did not. If this behavior impacts your application logic, consider splitting
+     *     the request into sub-requests per slot to ensure atomicity.
      * @see <a href="https://valkey.io/commands/exists/">valkey.io</a> for details.
      * @param keys The keys list to check.
      * @return The number of keys that exist. If the same existing key is mentioned in <code>keys
@@ -91,14 +85,12 @@ public interface GenericBaseCommands {
     /**
      * Returns the number of keys in <code>keys</code> that exist in the database.
      *
-     * @apiNote In cluster mode, if keys in <code>keys</code> map to different hash slots,
-     * the command will be split across these slots and executed separately for each.
-     * This means the command is atomic only at the slot level. If one or more slot-specific
-     * requests fail, the entire call will return the first encountered error, even
-     * though some requests may have succeeded while others did not.
-     * If this behavior impacts your application logic, consider splitting the
-     * request into sub-requests per slot to ensure atomicity.
-     * 
+     * @apiNote In cluster mode, if keys in <code>keys</code> map to different hash slots, the command
+     *     will be split across these slots and executed separately for each. This means the command
+     *     is atomic only at the slot level. If one or more slot-specific requests fail, the entire
+     *     call will return the first encountered error, even though some requests may have succeeded
+     *     while others did not. If this behavior impacts your application logic, consider splitting
+     *     the request into sub-requests per slot to ensure atomicity.
      * @see <a href="https://valkey.io/commands/exists/">valkey.io</a> for details.
      * @param keys The keys list to check.
      * @return The number of keys that exist. If the same existing key is mentioned in <code>keys
@@ -117,14 +109,12 @@ public interface GenericBaseCommands {
      * specified keys and ignores non-existent ones. However, this command does not block the server,
      * while <a href="https://valkey.io/commands/del/">DEL</a> does.
      *
-     * @apiNote In cluster mode, if keys in <code>keys</code> map to different hash slots,
-     * the command will be split across these slots and executed separately for each.
-     * This means the command is atomic only at the slot level. If one or more slot-specific
-     * requests fail, the entire call will return the first encountered error, even
-     * though some requests may have succeeded while others did not.
-     * If this behavior impacts your application logic, consider splitting the
-     * request into sub-requests per slot to ensure atomicity.
-     * 
+     * @apiNote In cluster mode, if keys in <code>keys</code> map to different hash slots, the command
+     *     will be split across these slots and executed separately for each. This means the command
+     *     is atomic only at the slot level. If one or more slot-specific requests fail, the entire
+     *     call will return the first encountered error, even though some requests may have succeeded
+     *     while others did not. If this behavior impacts your application logic, consider splitting
+     *     the request into sub-requests per slot to ensure atomicity.
      * @see <a href="https://valkey.io/commands/unlink/">valkey.io</a> for details.
      * @param keys The list of keys to unlink.
      * @return The number of <code>keys</code> that were unlinked.
@@ -142,14 +132,12 @@ public interface GenericBaseCommands {
      * specified keys and ignores non-existent ones. However, this command does not block the server,
      * while <a href="https://valkey.io/commands/del/">DEL</a> does.
      *
-     * @apiNote In cluster mode, if keys in <code>keys</code> map to different hash slots,
-     * the command will be split across these slots and executed separately for each.
-     * This means the command is atomic only at the slot level. If one or more slot-specific
-     * requests fail, the entire call will return the first encountered error, even
-     * though some requests may have succeeded while others did not.
-     * If this behavior impacts your application logic, consider splitting the
-     * request into sub-requests per slot to ensure atomicity.
-     * 
+     * @apiNote In cluster mode, if keys in <code>keys</code> map to different hash slots, the command
+     *     will be split across these slots and executed separately for each. This means the command
+     *     is atomic only at the slot level. If one or more slot-specific requests fail, the entire
+     *     call will return the first encountered error, even though some requests may have succeeded
+     *     while others did not. If this behavior impacts your application logic, consider splitting
+     *     the request into sub-requests per slot to ensure atomicity.
      * @see <a href="https://valkey.io/commands/unlink/">valkey.io</a> for details.
      * @param keys The list of keys to unlink.
      * @return The number of <code>keys</code> that were unlinked.
@@ -988,14 +976,12 @@ CompletableFuture<Boolean> pexpireAt(
     /**
      * Updates the last access time of specified <code>keys</code>.
      *
-     * @apiNote In cluster mode, if keys in <code>keys</code> map to different hash slots,
-     * the command will be split across these slots and executed separately for each.
-     * This means the command is atomic only at the slot level. If one or more slot-specific
-     * requests fail, the entire call will return the first encountered error, even
-     * though some requests may have succeeded while others did not.
-     * If this behavior impacts your application logic, consider splitting the
-     * request into sub-requests per slot to ensure atomicity.
-     * 
+     * @apiNote In cluster mode, if keys in <code>keys</code> map to different hash slots, the command
+     *     will be split across these slots and executed separately for each. This means the command
+     *     is atomic only at the slot level. If one or more slot-specific requests fail, the entire
+     *     call will return the first encountered error, even though some requests may have succeeded
+     *     while others did not. If this behavior impacts your application logic, consider splitting
+     *     the request into sub-requests per slot to ensure atomicity.
      * @see <a href="https://valkey.io/commands/touch/">valkey.io</a> for details.
      * @param keys The keys to update last access time.
      * @return The number of keys that were updated.
@@ -1010,14 +996,12 @@ CompletableFuture<Boolean> pexpireAt(
     /**
      * Updates the last access time of specified <code>keys</code>.
      *
-     * @apiNote In cluster mode, if keys in <code>keys</code> map to different hash slots,
-     * the command will be split across these slots and executed separately for each.
-     * This means the command is atomic only at the slot level. If one or more slot-specific
-     * requests fail, the entire call will return the first encountered error, even
-     * though some requests may have succeeded while others did not.
-     * If this behavior impacts your application logic, consider splitting the
-     * request into sub-requests per slot to ensure atomicity.
-     * 
+     * @apiNote In cluster mode, if keys in <code>keys</code> map to different hash slots, the command
+     *     will be split across these slots and executed separately for each. This means the command
+     *     is atomic only at the slot level. If one or more slot-specific requests fail, the entire
+     *     call will return the first encountered error, even though some requests may have succeeded
+     *     while others did not. If this behavior impacts your application logic, consider splitting
+     *     the request into sub-requests per slot to ensure atomicity.
      * @see <a href="https://valkey.io/commands/touch/">valkey.io</a> for details.
      * @param keys The keys to update last access time.
      * @return The number of keys that were updated.
diff --git a/java/client/src/main/java/glide/api/commands/StringBaseCommands.java b/java/client/src/main/java/glide/api/commands/StringBaseCommands.java
index 736c4d4eb3..20f13c30f2 100644
--- a/java/client/src/main/java/glide/api/commands/StringBaseCommands.java
+++ b/java/client/src/main/java/glide/api/commands/StringBaseCommands.java
@@ -249,14 +249,12 @@ public interface StringBaseCommands {
     /**
      * Retrieves the values of multiple <code>keys</code>.
      *
-     * @apiNote In cluster mode, if keys in <code>keys</code> map to different hash slots,
-     * the command will be split across these slots and executed separately for each.
-     * This means the command is atomic only at the slot level. If one or more slot-specific
-     * requests fail, the entire call will return the first encountered error, even
-     * though some requests may have succeeded while others did not.
-     * If this behavior impacts your application logic, consider splitting the
-     * request into sub-requests per slot to ensure atomicity.
-     * 
+     * @apiNote In cluster mode, if keys in <code>keys</code> map to different hash slots, the command
+     *     will be split across these slots and executed separately for each. This means the command
+     *     is atomic only at the slot level. If one or more slot-specific requests fail, the entire
+     *     call will return the first encountered error, even though some requests may have succeeded
+     *     while others did not. If this behavior impacts your application logic, consider splitting
+     *     the request into sub-requests per slot to ensure atomicity.
      * @see <a href="https://valkey.io/commands/mget/">valkey.io</a> for details.
      * @param keys A list of keys to retrieve values for.
      * @return An array of values corresponding to the provided <code>keys</code>.<br>
@@ -273,14 +271,12 @@ public interface StringBaseCommands {
     /**
      * Retrieves the values of multiple <code>keys</code>.
      *
-     * @apiNote In cluster mode, if keys in <code>keys</code> map to different hash slots,
-     * the command will be split across these slots and executed separately for each.
-     * This means the command is atomic only at the slot level. If one or more slot-specific
-     * requests fail, the entire call will return the first encountered error, even
-     * though some requests may have succeeded while others did not.
-     * If this behavior impacts your application logic, consider splitting the
-     * request into sub-requests per slot to ensure atomicity.
-     * 
+     * @apiNote In cluster mode, if keys in <code>keys</code> map to different hash slots, the command
+     *     will be split across these slots and executed separately for each. This means the command
+     *     is atomic only at the slot level. If one or more slot-specific requests fail, the entire
+     *     call will return the first encountered error, even though some requests may have succeeded
+     *     while others did not. If this behavior impacts your application logic, consider splitting
+     *     the request into sub-requests per slot to ensure atomicity.
      * @see <a href="https://valkey.io/commands/mget/">valkey.io</a> for details.
      * @param keys A list of keys to retrieve values for.
      * @return An array of values corresponding to the provided <code>keys</code>.<br>
@@ -297,14 +293,12 @@ public interface StringBaseCommands {
     /**
      * Sets multiple keys to multiple values in a single operation.
      *
-     * @apiNote In cluster mode, if keys in <code>keyValueMap</code> map to different hash slots,
-     * the command will be split across these slots and executed separately for each.
-     * This means the command is atomic only at the slot level. If one or more slot-specific
-     * requests fail, the entire call will return the first encountered error, even
-     * though some requests may have succeeded while others did not.
-     * If this behavior impacts your application logic, consider splitting the
-     * request into sub-requests per slot to ensure atomicity.
-     * 
+     * @apiNote In cluster mode, if keys in <code>keyValueMap</code> map to different hash slots, the
+     *     command will be split across these slots and executed separately for each. This means the
+     *     command is atomic only at the slot level. If one or more slot-specific requests fail, the
+     *     entire call will return the first encountered error, even though some requests may have
+     *     succeeded while others did not. If this behavior impacts your application logic, consider
+     *     splitting the request into sub-requests per slot to ensure atomicity.
      * @see <a href="https://valkey.io/commands/mset/">valkey.io</a> for details.
      * @param keyValueMap A key-value map consisting of keys and their respective values to set.
      * @return A simple <code>OK</code> response.
@@ -319,14 +313,12 @@ public interface StringBaseCommands {
     /**
      * Sets multiple keys to multiple values in a single operation.
      *
-     * @apiNote In cluster mode, if keys in <code>keyValueMap</code> map to different hash slots,
-     * the command will be split across these slots and executed separately for each.
-     * This means the command is atomic only at the slot level. If one or more slot-specific
-     * requests fail, the entire call will return the first encountered error, even
-     * though some requests may have succeeded while others did not.
-     * If this behavior impacts your application logic, consider splitting the
-     * request into sub-requests per slot to ensure atomicity.
-     * 
+     * @apiNote In cluster mode, if keys in <code>keyValueMap</code> map to different hash slots, the
+     *     command will be split across these slots and executed separately for each. This means the
+     *     command is atomic only at the slot level. If one or more slot-specific requests fail, the
+     *     entire call will return the first encountered error, even though some requests may have
+     *     succeeded while others did not. If this behavior impacts your application logic, consider
+     *     splitting the request into sub-requests per slot to ensure atomicity.
      * @see <a href="https://valkey.io/commands/mset/">valkey.io</a> for details.
      * @param keyValueMap A key-value map consisting of keys and their respective values to set.
      * @return A simple <code>OK</code> response.
diff --git a/java/client/src/main/java/glide/api/commands/TransactionsBaseCommands.java b/java/client/src/main/java/glide/api/commands/TransactionsBaseCommands.java
index a519e38891..d4db27785e 100644
--- a/java/client/src/main/java/glide/api/commands/TransactionsBaseCommands.java
+++ b/java/client/src/main/java/glide/api/commands/TransactionsBaseCommands.java
@@ -15,14 +15,12 @@ public interface TransactionsBaseCommands {
      * will only execute commands if the watched keys are not modified before execution of the
      * transaction.
      *
-     * @apiNote In cluster mode, if keys in <code>keys</code> map to different hash slots,
-     * the command will be split across these slots and executed separately for each.
-     * This means the command is atomic only at the slot level. If one or more slot-specific
-     * requests fail, the entire call will return the first encountered error, even
-     * though some requests may have succeeded while others did not.
-     * If this behavior impacts your application logic, consider splitting the
-     * request into sub-requests per slot to ensure atomicity.
-     * 
+     * @apiNote In cluster mode, if keys in <code>keys</code> map to different hash slots, the command
+     *     will be split across these slots and executed separately for each. This means the command
+     *     is atomic only at the slot level. If one or more slot-specific requests fail, the entire
+     *     call will return the first encountered error, even though some requests may have succeeded
+     *     while others did not. If this behavior impacts your application logic, consider splitting
+     *     the request into sub-requests per slot to ensure atomicity.
      * @see <a href="https://valkey.io/commands/watch/">valkey.io</a> for details.
      * @param keys The keys to watch.
      * @return <code>OK</code>.
@@ -47,14 +45,12 @@ public interface TransactionsBaseCommands {
      * will only execute commands if the watched keys are not modified before execution of the
      * transaction.
      *
-     * @apiNote In cluster mode, if keys in <code>keys</code> map to different hash slots,
-     * the command will be split across these slots and executed separately for each.
-     * This means the command is atomic only at the slot level. If one or more slot-specific
-     * requests fail, the entire call will return the first encountered error, even
-     * though some requests may have succeeded while others did not.
-     * If this behavior impacts your application logic, consider splitting the
-     * request into sub-requests per slot to ensure atomicity.
-     * 
+     * @apiNote In cluster mode, if keys in <code>keys</code> map to different hash slots, the command
+     *     will be split across these slots and executed separately for each. This means the command
+     *     is atomic only at the slot level. If one or more slot-specific requests fail, the entire
+     *     call will return the first encountered error, even though some requests may have succeeded
+     *     while others did not. If this behavior impacts your application logic, consider splitting
+     *     the request into sub-requests per slot to ensure atomicity.
      * @see <a href="https://valkey.io/commands/watch/">valkey.io</a> for details.
      * @param keys The keys to watch.
      * @return <code>OK</code>.