Merge pull request #192 from KarelVerschraegen/fix-setup-set-up-typo

Use the verb set up instead of the noun setup
vercel · Dec 11, 2021 · ddd35b7 · ddd35b7 · vercel · Dec 11, 2021
2 parents d13e57e + a80891a
commit ddd35b7
Show file tree

Hide file tree

Showing 3 changed files with 3 additions and 3 deletions.
diff --git a/docs/pages/docs/faq.mdx b/docs/pages/docs/faq.mdx
@@ -12,7 +12,7 @@ No. [Remote Caching](./features/remote-caching) is optional. However, you'll fin
 
 No. Turborepo does not store source code. Without Remote Caching, no code ever leaves your machine—it will only cache artifacts to local disk.
 
-With Turborepo's Remote Caching, you are responsible for configuring cache behavior and should only setup Turborepo to cache compiled artifacts. Please be aware that Turborepo treats all logs as artifacts and so these _will_ be stored along with other cache artifacts. There is also a retention period of 14 days. In the future, this retention period will be configurable on a per-task basis.
+With Turborepo's Remote Caching, you are responsible for configuring cache behavior and should only set up Turborepo to cache compiled artifacts. Please be aware that Turborepo treats all logs as artifacts and so these _will_ be stored along with other cache artifacts. There is also a retention period of 14 days. In the future, this retention period will be configurable on a per-task basis.
 
 ## Is Turborepo's Remote Caching secure?
 

diff --git a/docs/pages/docs/features/remote-caching.mdx b/docs/pages/docs/features/remote-caching.mdx
@@ -49,7 +49,7 @@ Then run the same build again. If things are working properly, `turbo` should no
 
 ### Remote Caching on Vercel Builds
 
-If you are building and hosting your apps on Vercel, then Remote Caching will be automatically setup for you on your behalf once you use `turbo`. You just need to update your build settings to build with `turbo`.
+If you are building and hosting your apps on Vercel, then Remote Caching will be automatically set up for you on your behalf once you use `turbo`. You just need to update your build settings to build with `turbo`.
 
 Please refer to the [Vercel documentation](https://vercel.com/docs/concepts/git/monorepos#turborepo?utm_source=turborepo.org&utm_medium=referral&utm_campaign=docs-link) for instructions.
 

diff --git a/docs/pages/docs/upgrading-to-v1.mdx b/docs/pages/docs/upgrading-to-v1.mdx
@@ -52,7 +52,7 @@ If you were using Remote Caching for local development, upgrading will take a mi
 npx vercel login
 ```
 
-Now we can setup Remote Caching through Vercel by running:
+Now we can set up Remote Caching through Vercel by running:
 
 ```sh
 npx turbo link