From f57bed868738b5c3615d137948427ccb46646b97 Mon Sep 17 00:00:00 2001 From: Sebastian Harko Date: Tue, 18 Jul 2017 00:08:34 -0700 Subject: [PATCH] fix small issue (#23363) --- akka-docs/src/main/paradox/scala/persistence.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/akka-docs/src/main/paradox/scala/persistence.md b/akka-docs/src/main/paradox/scala/persistence.md index 6701e2bd87..b993f76c7d 100644 --- a/akka-docs/src/main/paradox/scala/persistence.md +++ b/akka-docs/src/main/paradox/scala/persistence.md @@ -187,7 +187,7 @@ akka.persistence.max-concurrent-recoveries = 50 @@@ note -Accessing the @scala[`sender()`]@java[sender with `getSender()] for replayed messages will always result in a `deadLetters` reference, +Accessing the @scala[`sender()`]@java[sender with `getSender()`] for replayed messages will always result in a `deadLetters` reference, as the original sender is presumed to be long gone. If you indeed have to notify an actor during recovery in the future, store its `ActorPath` explicitly in your persisted events. @@ -338,7 +338,7 @@ Java @@@ note -In order to implement the pattern known as "*command sourcing*" simply call @scala[persistAsync(cmd)(...)`]@java[`persistAsync`] right away on all incoming +In order to implement the pattern known as "*command sourcing*" simply call @scala[`persistAsync(cmd)(...)`]@java[`persistAsync`] right away on all incoming messages and handle them in the callback. @@@