diff --git a/docs/02-app/01-building-your-application/02-data-fetching/01-fetching-caching-and-revalidating.mdx b/docs/02-app/01-building-your-application/02-data-fetching/01-fetching-caching-and-revalidating.mdx
index 4cf2baa00841f..2b3f8d1f0f61e 100644
--- a/docs/02-app/01-building-your-application/02-data-fetching/01-fetching-caching-and-revalidating.mdx
+++ b/docs/02-app/01-building-your-application/02-data-fetching/01-fetching-caching-and-revalidating.mdx
@@ -247,7 +247,7 @@ If an error is thrown while attempting to revalidate data, the last successfully
 - The `fetchCache` route segment option is configured to skip cache by default.
 - The `fetch` request uses `Authorization` or `Cookie` headers and there's an uncached request above it in the component tree.
 
-#### Individiual `fetch` Requests
+#### Individual `fetch` Requests
 
 To opt out of caching for individual `fetch` requests, you can set the `cache` option in `fetch` to `'no-store'`. This will fetch data dynamically, on every request.