=doc fix typo in sharding docs

This commit is contained in:
hepin 2015-09-29 10:21:59 +08:00
parent f0edeeeadf
commit c0bba54d6b
2 changed files with 2 additions and 2 deletions

View file

@ -36,7 +36,7 @@ The above actor uses event sourcing and the support provided in ``UntypedPersist
It does not have to be a persistent actor, but in case of failure or migration of entities between nodes it must be able to recover It does not have to be a persistent actor, but in case of failure or migration of entities between nodes it must be able to recover
its state if it is valuable. its state if it is valuable.
Note how the ``persistenceId`` is defined. The name of the actor is the entity entity identifier (utf-8 URL-encoded). Note how the ``persistenceId`` is defined. The name of the actor is the entity identifier (utf-8 URL-encoded).
You may define it another way, but it must be unique. You may define it another way, but it must be unique.
When using the sharding extension you are first, typically at system startup on each node When using the sharding extension you are first, typically at system startup on each node

View file

@ -36,7 +36,7 @@ The above actor uses event sourcing and the support provided in ``PersistentActo
It does not have to be a persistent actor, but in case of failure or migration of entities between nodes it must be able to recover It does not have to be a persistent actor, but in case of failure or migration of entities between nodes it must be able to recover
its state if it is valuable. its state if it is valuable.
Note how the ``persistenceId`` is defined. The name of the actor is the entity entity identifier (utf-8 URL-encoded). Note how the ``persistenceId`` is defined. The name of the actor is the entity identifier (utf-8 URL-encoded).
You may define it another way, but it must be unique. You may define it another way, but it must be unique.
When using the sharding extension you are first, typically at system startup on each node When using the sharding extension you are first, typically at system startup on each node