chore(docs): add missing words (vercel#8067)

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