From 839fd45468f5780f2fead04c36c64c48fc24f016 Mon Sep 17 00:00:00 2001 From: Jeremy Davis Date: Tue, 30 Apr 2024 21:34:12 -0400 Subject: [PATCH] Update configuring-workspaces.mdx Added missing words --- .../docs/core-concepts/monorepos/configuring-workspaces.mdx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/pages/repo/docs/core-concepts/monorepos/configuring-workspaces.mdx b/docs/pages/repo/docs/core-concepts/monorepos/configuring-workspaces.mdx index b82333f573b30..79ca2eb6e1339 100644 --- a/docs/pages/repo/docs/core-concepts/monorepos/configuring-workspaces.mdx +++ b/docs/pages/repo/docs/core-concepts/monorepos/configuring-workspaces.mdx @@ -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