From 24d1f5439c63aa8b503ff8668ac565f698f8892c Mon Sep 17 00:00:00 2001
From: omahs <73983677+omahs@users.noreply.github.com>
Date: Mon, 6 Jan 2025 17:19:44 +0100
Subject: [PATCH] fix typo

---
 lectures/Asynchrony/ReadMe.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/lectures/Asynchrony/ReadMe.md b/lectures/Asynchrony/ReadMe.md
index fdc640be..f6dce59b 100644
--- a/lectures/Asynchrony/ReadMe.md
+++ b/lectures/Asynchrony/ReadMe.md
@@ -303,7 +303,7 @@ We provide a [solution example](exercises/solutions/lecture/src/main/java/Basics
 ### Sync over async
 
 Doing the exercise above, you've noticed `App.java` uses `join()` to block until a future finishes and either return the result or throw the error represented by the future.
-There are other such "sync over async" operations, such as `isDone()` and `isCompletedExceptionallly()` to check a future's status.
+There are other such "sync over async" operations, such as `isDone()` and `isCompletedExceptionally()` to check a future's status.
 
 "Sync over async" operations are useful specifically to use asynchronous operations in a context that must be synchronous,
 typically because you are working with a framework that expects a synchronous operation.