diff --git a/akka-docs/src/main/paradox/scala/cluster-sharding.md b/akka-docs/src/main/paradox/scala/cluster-sharding.md
index e36ec5bf67..f0691baa05 100644
--- a/akka-docs/src/main/paradox/scala/cluster-sharding.md
+++ b/akka-docs/src/main/paradox/scala/cluster-sharding.md
@@ -74,7 +74,7 @@ This example illustrates two different ways to define the entity identifier in t
 sent to the entity actor is wrapped in the envelope.
 
 Note how these two messages types are handled in the @scala[`extractEntityId` function] @java[`entityId` and `entityMessage` methods] shown above.
-The message sent to the entity actor is @scala[the second part of the tuple returned by the `extractEntityId`] @[what `entityMessage` returns] and that makes it possible to unwrap envelopes
+The message sent to the entity actor is @scala[the second part of the tuple returned by the `extractEntityId`] @java[what `entityMessage` returns] and that makes it possible to unwrap envelopes
 if needed.
 
 A shard is a group of entities that will be managed together. The grouping is defined by the
@@ -468,4 +468,4 @@ When doing rolling upgrades special care must be taken to not change any of the
  * the role that the shard regions run on
  * the persistence mode
 
- If any one of these needs a change it will require a full cluster restart.
\ No newline at end of file
+ If any one of these needs a change it will require a full cluster restart.