diff --git a/akka-docs/src/main/paradox/typed/routers.md b/akka-docs/src/main/paradox/typed/routers.md
index 4aea1048e6..690bf2c2bb 100644
--- a/akka-docs/src/main/paradox/typed/routers.md
+++ b/akka-docs/src/main/paradox/typed/routers.md
@@ -124,7 +124,7 @@ gives good insight into how consistent hashing is implemented.
 Currently you have to define hashMapping of the router to map incoming messages to their consistent
 hash key. This makes the decision transparent for the sender.
 
-Consistent hashing makes messages with the same hash routee to the same routee as long as the set of routees stays the same.
+Consistent hashing delivers messages with the same hash to the same routee as long as the set of routees stays the same.
 When the set of routees changes, consistent hashing tries to make sure, but does not guarantee, that messages with the same hash are routed to the same routee.
 
 See also @ref[Akka Cluster Sharding](cluster-sharding.md) which provides stable routing and rebalancing of the routee actors.