From 2e8c5792185c6eee86b0d5fc7a18dd22f485d17e Mon Sep 17 00:00:00 2001
From: Rajas Paranjpe <52586855+ChocolateLoverRaj@users.noreply.github.com>
Date: Sat, 25 Nov 2023 19:55:26 -0800
Subject: [PATCH] Fix typo: at a time instead of at time

---
 docs/src/tutorial/receiving_messages.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/src/tutorial/receiving_messages.md b/docs/src/tutorial/receiving_messages.md
index f62b65d9c..036bc4597 100644
--- a/docs/src/tutorial/receiving_messages.md
+++ b/docs/src/tutorial/receiving_messages.md
@@ -118,7 +118,7 @@ handle.await?
 The `.await` waits until the client finishes, and `?` propagates the result.
 
 There are two problems with this solution however!
-*First*, because we immediately await the client, we can only handle one client at time, and that completely defeats the purpose of async!
+*First*, because we immediately await the client, we can only handle one client at a time, and that completely defeats the purpose of async!
 *Second*, if a client encounters an IO error, the whole server immediately exits.
 That is, a flaky internet connection of one peer brings down the whole chat room!