From d4ed47f3091c48f708bfc4a4327c4933e4390e2b Mon Sep 17 00:00:00 2001 From: Luke Eller Date: Tue, 12 Nov 2019 18:38:05 +1100 Subject: [PATCH] Fix fire and forget wording (#28160) --- akka-docs/src/main/paradox/typed/interaction-patterns.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/akka-docs/src/main/paradox/typed/interaction-patterns.md b/akka-docs/src/main/paradox/typed/interaction-patterns.md index 866aab22cd..9f6b9d5c05 100644 --- a/akka-docs/src/main/paradox/typed/interaction-patterns.md +++ b/akka-docs/src/main/paradox/typed/interaction-patterns.md @@ -22,7 +22,7 @@ Message exchange with Actors follow a few common patterns, let's go through each The fundamental way to interact with an actor is through @scala["tell", which is so common that it has a special symbolic method name: `actorRef ! message`]@java[`actorRef.tell(message)`]. Sending a message with tell can safely be done from any thread. -Tell is asynchronous which means that the method returns right away, when the statement after it is executed there is no guarantee that the message has been processed by the recipient yet. It also means there is no way to know if the message was received, the processing succeeded or failed. +Tell is asynchronous which means that the method returns right away. After the statement is executed there is no guarantee that the message has been processed by the recipient yet. It also means there is no way to know if the message was received, the processing succeeded or failed. **Example:**