From 46eb143482ba8df1faece04aaa4d6f04b43a893e Mon Sep 17 00:00:00 2001
From: Tim Condon <0xTim@users.noreply.github.com>
Date: Sun, 1 Dec 2024 14:58:11 +0100
Subject: [PATCH] Apply suggestions from code review

---
 docs/basics/async.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/basics/async.md b/docs/basics/async.md
index 97616478..096e2adc 100644
--- a/docs/basics/async.md
+++ b/docs/basics/async.md
@@ -300,14 +300,14 @@ futureString.whenComplete { result in
 
 ### Get
 
-In case there is no concurrency-based alternative to an API, you can wait for the future's value using `try await future.get()`.
+In case there is no concurrency-based alternative to an API, you can await for the future's value using `try await future.get()`.
 
 ```swift
 /// Assume we get a future string back from some API
 let futureString: EventLoopFuture<String> = ...
 
 /// Wait for the string to be ready
-let string = try await futureString.get()
+let string: String = try await futureString.get()
 print(string) /// String
 ```