From 2dad80a00ce5f339dd39e41a995eda09fe6a3480 Mon Sep 17 00:00:00 2001
From: Dalton McPhaden <44533832+daltonmcphaden@users.noreply.github.com>
Date: Wed, 6 Sep 2023 22:25:59 -0400
Subject: [PATCH] Update 01-server-components.mdx

---
 .../03-rendering/01-server-components.mdx                       | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/02-app/01-building-your-application/03-rendering/01-server-components.mdx b/docs/02-app/01-building-your-application/03-rendering/01-server-components.mdx
index f54290791cdb9..4284a137212e9 100644
--- a/docs/02-app/01-building-your-application/03-rendering/01-server-components.mdx
+++ b/docs/02-app/01-building-your-application/03-rendering/01-server-components.mdx
@@ -29,7 +29,7 @@ There are a couple of benefits to doing the rendering work on the server, includ
 
 ## Using Server Components in Next.js
 
-By default, Next.js uses Server Components. This allows you to automatically implement server rendering with no additional configuration, and you can opt into using Client Components when you needed, see [Client Components](/docs/app/building-your-application/rendering/client-components).
+By default, Next.js uses Server Components. This allows you to automatically implement server rendering with no additional configuration, and you can opt into using Client Components when needed, see [Client Components](/docs/app/building-your-application/rendering/client-components).
 
 ## How are Server Components rendered?