vercel · jaredpalmer · Dec 14, 2021 · Dec 14, 2021 · Dec 14, 2021
@@ -14,7 +14,7 @@ By default, [`turbo run`](../reference/command-line-reference#turbo-run-task1-ta
 
 Using [`pipeline`](../reference/configuration#pipeline), you can configure cache conventions across your Turborepo.
 
-To override the default cache folder behavior, pass an array of globs to a [`pipeline.<task>.outputs`](../reference/configuration#outputs) array. Any file that satifies the glob patterns for a task will be treated as artifact.
+To override the default cache folder behavior, pass an array of globs to a [`pipeline.<task>.outputs`](../reference/configuration#outputs) array. Any file that satisfies the glob patterns for a task will be treated as artifact.
 
 ```json
 {

@@ -56,7 +56,7 @@ The `turbo` package is a little shell that will install the proper `@turborepo/*
 
 ### Add `turbo` to `package.json`
 
-In your root `package.json`, add a key `turbo`. If your git repo's base branch is NOT `origin/master` then you need to specify a `baseBranch` too (for example, our's is set to `origin/main`).
+In your root `package.json`, add a key `turbo`. If your git repo's base branch is NOT `origin/master` then you need to specify a `baseBranch` too (for example, ours is set to `origin/main`).
 
 ```json
 {

@@ -17,7 +17,7 @@ However, unlike Turborepo, Lerna has no ability to [cache prior work](../feature
 
 ### Task Scheduling
 
-Turborepos's task scheduler is more powerful than Lerna's (which can only schedule one task at a time) thanks to [Turborepo pipelines](../features/pipelines). Turborepo reduces idle CPUs, saves compute resource, and collapse waterfalls—which ultimately results in faster overall builds.
+Turborepo's task scheduler is more powerful than Lerna's (which can only schedule one task at a time) thanks to [Turborepo pipelines](../features/pipelines). Turborepo reduces idle CPUs, saves compute resource, and collapse waterfalls—which ultimately results in faster overall builds.
 
 Let's look at an example. Imagine you have two packages A and B each with 3 tasks `build`, `test`, and `bundle`, where A depends on B being built....
 

@@ -38,7 +38,7 @@ yarn add turbo -W --dev
 
 ## 3. Setup Remote Caching
 
-As mentioned, Turborepo now provides zero-config Remote Caching through [Vercel](https://vercel.com?utm_source=turborepo.org&utm_medium=referral&utm_campaign=docs-link). Remote Caching is free for all Vercel plans during this transition period. Each Vercel account has a shared Remote Cache. This cache is shared across all enviroments (Development, Preview, and Production).
+As mentioned, Turborepo now provides zero-config Remote Caching through [Vercel](https://vercel.com?utm_source=turborepo.org&utm_medium=referral&utm_campaign=docs-link). Remote Caching is free for all Vercel plans during this transition period. Each Vercel account has a shared Remote Cache. This cache is shared across all environments (Development, Preview, and Production).
 
 **Important**: turborepo.com allowed multiple caches (i.e. projects) per team (denoted through `--project` flag). With v1.x caching on Vercel, each Vercel account (user or team) has a single shared Remote Cache. If you were actively using multiple turborepo.com projects for your team, please let us know in [Discord](https://turborepo.org/discord).
-Original file line number
+Diff line change
@@ Expand Up @@
     Using [`pipeline`](../reference/configuration#pipeline), you can configure cache conventions across your Turborepo.
-    To override the default cache folder behavior, pass an array of globs to a [`pipeline.<task>.outputs`](../reference/configuration#outputs) array. Any file that satifies the glob patterns for a task will be treated as artifact.
+    To override the default cache folder behavior, pass an array of globs to a [`pipeline.<task>.outputs`](../reference/configuration#outputs) array. Any file that satisfies the glob patterns for a task will be treated as artifact.
     ```json
     {
@@ Expand Down @@