Skip to content

fix: improve wording partial reference section #12916

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

Merged
ArmandPhilippot merged 3 commits into from
Dec 16, 2025
Merged

fix: improve wording partial reference section #12916

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
d3134a1
fix: improve wording partial reference section
trueberryless Dec 15, 2025
38f5fa0
Apply Sarah's suggestion
ArmandPhilippot Dec 16, 2025
91e339a
Merge branch 'main' into fix/partial-typo
ArmandPhilippot Dec 16, 2025
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 src/content/docs/en/reference/container-reference.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -430,7 +430,7 @@ const json = await response.json();
<Since v="4.16.6" />
</p>

Whether or not the Container API renders components as if they were [page partials](/en/basics/astro-pages/#page-partials). This is usually the behavior you want when rendering `components.boolean` so you can render components without a full page shell.
Whether or not the Container API renders components as if they were [page partials](/en/basics/astro-pages/#page-partials). The default `true` setting renders the component in isolation without a full page shell.

To render a component as a full Astro page, including `<!DOCTYPE html>`, you can opt-out of this behavior by setting `partial` to `false`:

Expand Down