From c71b40d05fd374ad57757d013d4c4e374ea67657 Mon Sep 17 00:00:00 2001 From: "Jabir S. Minjibir" Date: Sun, 18 Oct 2020 12:04:19 +0100 Subject: [PATCH] Update cluster.md Fixed a simple typo (cherry picked from commit d357edccd1b2f0ecdb2445396da9a571fe883a50) --- akka-docs/src/main/paradox/typed/cluster.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/akka-docs/src/main/paradox/typed/cluster.md b/akka-docs/src/main/paradox/typed/cluster.md index f1251ccd9d..2680ddec52 100644 --- a/akka-docs/src/main/paradox/typed/cluster.md +++ b/akka-docs/src/main/paradox/typed/cluster.md @@ -270,7 +270,7 @@ be necessary to set the node’s status to `Down` in order to complete the remov In many cases a member can gracefully exit from the cluster, as described in @ref:[Leaving](#leaving), but there are scenarios when an explicit downing decision is needed before it can be removed. For example in case of abrupt termination of the the JVM process, system overload that doesn't recover, or network partitions -that don't heal. I such cases the node(s) will be detected as unreachable by other nodes, but they must also +that don't heal. In such cases, the node(s) will be detected as unreachable by other nodes, but they must also be marked as `Down` before they are removed. When a member is considered by the failure detector to be `unreachable` the