From c8662fc5bfa6d9481f2522409c53d8e542c51110 Mon Sep 17 00:00:00 2001 From: Jorge Date: Thu, 9 Dec 2021 11:58:22 -0300 Subject: [PATCH] Fix typo in getting started section. --- docs/pages/docs/getting-started.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/pages/docs/getting-started.mdx b/docs/pages/docs/getting-started.mdx index 56615a99094cf..21eae85ee54aa 100644 --- a/docs/pages/docs/getting-started.mdx +++ b/docs/pages/docs/getting-started.mdx @@ -96,7 +96,7 @@ Your pipeline both defines the way in which your NPM `package.json` scripts rela } ``` -In the above example, the `build` and `test` tasks are dependant on their packages `dependancies` and `devDependancies` being built first, this is denoted with the `^` prefix. +In the above example, the `build` and `test` tasks are dependant on their packages `dependencies` and `devDependencies` being built first, this is denoted with the `^` prefix. For each script in each workspace's `package.json`, Turborepo will cache files outputted to `dist/**` and `build/**` folders by default if an override isn't added. Using the [`outputs`](./features/caching#configuring-cache-outputs-1) array allows you to override the default cache folders, like in the example above, where the `.next/**` folder is selected to be the default cache folder for the `build` task. Turborepo will automatically record and cache logs to `.turbo/turbo-