From 08f52760ae2128d33db1fa9c4d971c9eeaebc530 Mon Sep 17 00:00:00 2001
From: Herbert Reiter <46045854+damoasda@users.noreply.github.com>
Date: Sat, 29 Mar 2025 12:27:59 +0100
Subject: [PATCH] Add missing bracket

---
 src/ch17-05-traits-for-async.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/ch17-05-traits-for-async.md b/src/ch17-05-traits-for-async.md
index d4447a34b5..42abb2e0de 100644
--- a/src/ch17-05-traits-for-async.md
+++ b/src/ch17-05-traits-for-async.md
@@ -286,7 +286,7 @@ the `Box` pointer. Figure 17-6 illustrates this process.
 In fact, the `Box` pointer can still move around freely. Remember: we care about
 making sure the data ultimately being referenced stays in place. If a pointer
 moves around, _but the data it points to is in the same place_, as in Figure
-17-7, there’s no potential problem. As an independent exercise, look at the docs
+17-7, there’s no potential problem. (As an independent exercise, look at the docs
 for the types as well as the `std::pin` module and try to work out how you’d do
 this with a `Pin` wrapping a `Box`.) The key is that the self-referential type
 itself cannot move, because it is still pinned.