Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update 01-server-components.mdx #55085

Merged
merged 2 commits into from
Sep 7, 2023
Merged

Update 01-server-components.mdx #55085

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
2dad80a
Update 01-server-components.mdx
daltonmcphaden Sep 7, 2023
d3e8d99
Merge branch 'canary' into patch-2
manovotny Sep 7, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/02-app/01-building-your-application/03-rendering/01-server-components.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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?

Expand Down