From 569ff0495ae2db9238618879a2565d565aadfd51 Mon Sep 17 00:00:00 2001 From: Robert Stoll Date: Thu, 12 Dec 2019 06:41:26 +0100 Subject: [PATCH] [doc] adjust link text to next section and add the missing `the` --- akka-docs/src/main/paradox/typed/persistence-style.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/akka-docs/src/main/paradox/typed/persistence-style.md b/akka-docs/src/main/paradox/typed/persistence-style.md index ebc9998a76..df4deabd41 100644 --- a/akka-docs/src/main/paradox/typed/persistence-style.md +++ b/akka-docs/src/main/paradox/typed/persistence-style.md @@ -4,11 +4,11 @@ The section about @ref:[Changing Behavior](persistence.md#changing-behavior) described how commands and events can be handled differently depending on the state. One can take that one step further and define the event -handler inside the state classes. @scala[In @ref:[next section the command handlers](#command-handlers-in-the-state) are -also defined in the state.] +handler inside the state classes. @scala[In @ref:[the next section](#command-handlers-in-the-state) +the command handlers are also defined in the state.] The state can be seen as your domain object and it should contain the core business logic. Then it's a matter -of taste if event handlers and command handlers should be defined in the state or be kept outside it. +of taste if event handlers and command handlers should be defined in the state or be kept outside of it. Here we are using a bank account as the example domain. It has 3 state classes that are representing the lifecycle of the account; `EmptyAccount`, `OpenedAccount`, and `ClosedAccount`.