Corrected several misspellings of the word "losing".

This commit is contained in:
Brendan McAdams 2016-01-15 20:20:15 -08:00
parent ecc916abfd
commit 269a3b3647
6 changed files with 8 additions and 8 deletions

View file

@ -214,7 +214,7 @@ If the state of the entities are persistent you may stop entities that are not u
reduce memory consumption. This is done by the application specific implementation of
the entity actors for example by defining receive timeout (``context.setReceiveTimeout``).
If a message is already enqueued to the entity when it stops itself the enqueued message
in the mailbox will be dropped. To support graceful passivation without loosing such
in the mailbox will be dropped. To support graceful passivation without losing such
messages the entity actor can send ``ShardRegion.Passivate`` to its parent ``Shard``.
The specified wrapped message in ``Passivate`` will be sent back to the entity, which is
then supposed to stop itself. Incoming messages will be buffered by the ``Shard``
@ -357,4 +357,4 @@ a ``ClusterShard.ClusterShardingStats`` containing the identifiers of the shards
of entities that are alive in each shard.
The purpose of these messages is testing and monitoring, they are not provided to give access to
directly sending messages to the individual entities.
directly sending messages to the individual entities.