diff --git a/akka-docs/src/main/paradox/typed/cluster-sharding.md b/akka-docs/src/main/paradox/typed/cluster-sharding.md
index 5a94ec7408..1cf6671945 100644
--- a/akka-docs/src/main/paradox/typed/cluster-sharding.md
+++ b/akka-docs/src/main/paradox/typed/cluster-sharding.md
@@ -337,7 +337,7 @@ When `rememberEntities` is enabled, whenever a `Shard` is rebalanced onto anothe
 node or recovers after a crash, it will recreate all the entities which were previously
 running in that `Shard`. 
 
-To permanently stop entities sent a `ClusterSharding.Passivate` to the
+To permanently stop entities send a `ClusterSharding.Passivate` to the
 @scala[`ActorRef[ShardCommand]`]@java[`ActorRef<ShardCommand>`] that was passed in to
 the factory method when creating the entity.
 Otherwise, the entity will be automatically restarted after the entity restart backoff specified in the configuration.
@@ -397,10 +397,10 @@ If using remembered entities there are two migration options:
    reads the data written by the old `persistence` mode. Your remembered entities will be remembered after a full cluster restart. 
 
 For migrating existing remembered entities an event adapter needs to be configured in the config for the journal you use in your `application.conf`.
-In this example `leveldb` is the used journal:
+In this example `cassandra` is the used journal:
 
 ```
-akka.persistence.journal.leveldb {
+akka.persistence.cassandra.journal {
   event-adapters {
     coordinator-migration = "akka.cluster.sharding.OldCoordinatorStateMigrationEventAdapter"
   }