diff --git a/docs/02-app/01-building-your-application/02-data-fetching/02-patterns.mdx b/docs/02-app/01-building-your-application/02-data-fetching/02-patterns.mdx
index 878b63e3de90f..a2b71d5884b24 100644
--- a/docs/02-app/01-building-your-application/02-data-fetching/02-patterns.mdx
+++ b/docs/02-app/01-building-your-application/02-data-fetching/02-patterns.mdx
@@ -137,7 +137,7 @@ This will prevent the whole route from being blocked by data fetching, and the u
 >
 > An alternative approach to prevent waterfalls is to fetch data globally, at the root of your application, but this will block rendering for all route segments beneath it until the data has finished loading. This can be described as "all or nothing" data fetching. Either you have the entire data for your page or application, or none.
 >
-> Any fetch requests with `await` will block rendering and data fetching for the entire tree beneath it, unless they are wrapped in a `<Suspense>` boundary or `loading.js` is used. Another alternative is use [parallel data fetching](#parallel-data-fetching) or the [preload pattern](#preloading-data).
+> Any fetch requests with `await` will block rendering and data fetching for the entire tree beneath it, unless they are wrapped in a `<Suspense>` boundary or `loading.js` is used. Another alternative is to use [parallel data fetching](#parallel-data-fetching) or the [preload pattern](#preloading-data).
 
 #### Parallel Data Fetching