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

Jump to bottom

chore(docs): add missing words #8067

Merged
merged 1 commit into from
May 2, 2024
Merged

chore(docs): add missing words #8067

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
6 changes: 3 additions & 3 deletions docs/pages/repo/docs/core-concepts/monorepos/configuring-workspaces.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -151,9 +151,9 @@ but continue to inherit any other tasks defined at the root.

At first glance, Workspace Configurations may sound a lot like the
[`workspace#task` syntax][3] in the root `turbo.json`. The features are
similar, but have one significant difference: when you declare a Workspace-specific
in the root `turbo.json`, it _completely_ overwrites the baseline task
configuration. With a Workspace Configuration, the task configuration is merged
similar, but have one significant difference: when you declare a Workspace-specific
task configuration in the root `turbo.json`, it _completely_ overwrites the baseline
task configuration. With a Workspace Configuration, the task configuration is merged
instead.

Consider the example of the monorepo with multiple Next.js apps and a Sveltekit
Expand Down