From a475e5a9fbf7867394320700de93ba5e0716671b Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=F0=9D=95=AF=F0=9D=96=8A=F0=9D=96=92=F0=9D=96=94?=
 =?UTF-8?q?=F0=9D=96=93?= <78769380+codegod100@users.noreply.github.com>
Date: Sun, 22 Sep 2024 02:43:24 -0700
Subject: [PATCH] Update 01_chapter.md

---
 src/04_pinning/01_chapter.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/04_pinning/01_chapter.md b/src/04_pinning/01_chapter.md
index b169f993..defcb4ea 100644
--- a/src/04_pinning/01_chapter.md
+++ b/src/04_pinning/01_chapter.md
@@ -323,7 +323,7 @@ out of `Pin`. For example, `u8` is `Unpin`, so `Pin<&mut u8>` behaves just like
 a normal `&mut u8`.
 
 However, types that can't be moved after they're pinned have a marker called
-`!Unpin`. Futures created by async/await is an example of this.
+`!Unpin`. Futures created by async/await are an example of this.
 
 ### Pinning to the Stack