From e2b5e70597a8f8b3a314590817cbffee8eef5af4 Mon Sep 17 00:00:00 2001 From: Alden Torres Date: Tue, 12 Nov 2024 15:20:16 -0500 Subject: [PATCH] minor documentation fix (#1558) --- .../main/paradox/typed/handling-actor-responses-with-scala3.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/src/main/paradox/typed/handling-actor-responses-with-scala3.md b/docs/src/main/paradox/typed/handling-actor-responses-with-scala3.md index 5f5cee90927..1fe9534aebf 100644 --- a/docs/src/main/paradox/typed/handling-actor-responses-with-scala3.md +++ b/docs/src/main/paradox/typed/handling-actor-responses-with-scala3.md @@ -5,7 +5,7 @@ Scala 2, it doesn't require the utilisation of message adapters and response wra A distinction exists between an actor's public protocol (`Command `) and its internal protocol (`CommandAndResponse`). The latter is the union of the public protocol and all -the responses the actor should understand. This is union is implemented with Scala 3's +the responses the actor should understand. This union is implemented with Scala 3's Union types. **Example:**