diff --git a/docs/pages/docs/features/caching.mdx b/docs/pages/docs/features/caching.mdx
index 71c64fb9135e3..0233e826d970e 100644
--- a/docs/pages/docs/features/caching.mdx
+++ b/docs/pages/docs/features/caching.mdx
@@ -95,7 +95,7 @@ By now, you're probably wondering how `turbo` decides what constitutes a cache h
First `turbo` constructs a hash of the current global state of the monorepo:
-- The contents of any file that satifies the the glob patterns in [`globalDependencies`](../reference/configuration#globalDependencies-1)
+- The contents of any file that satisfies the glob patterns in [`globalDependencies`](../reference/configuration#globalDependencies-1)
Then it adds on more factors relative to a given package's task:
diff --git a/docs/pages/docs/features/pipelines.mdx b/docs/pages/docs/features/pipelines.mdx
index 74ee4f8991a89..ef35301b805d1 100644
--- a/docs/pages/docs/features/pipelines.mdx
+++ b/docs/pages/docs/features/pipelines.mdx
@@ -144,7 +144,7 @@ Sometimes tasks declared in the `pipeline` are not present in all packages' `pac
### Implicit Dependencies and Specific Package Tasks
-Sometimes you need to manually place a package-task dependency on another package-task. This can occur especially in repos that are just coming off of a `lerna` or `rush` repository where the tasks are traditionally run in separate phases. Sometimes assumptions are made for those repositories that are not expressable in the simple task `pipeline` configuration, as seen above.
+Sometimes you need to manually place a package-task dependency on another package-task. This can occur especially in repos that are just coming off of a `lerna` or `rush` repository where the tasks are traditionally run in separate phases. Sometimes assumptions are made for those repositories that are not expressible in the simple task `pipeline` configuration, as seen above.
Additionally, you may need to express implicit dependencies or sequences between applications or microservices when using `turbo` in CI/CD.
For these cases, you can express these relationships in your `pipeline` configuration like this:
diff --git a/docs/pages/docs/features/scopes.mdx b/docs/pages/docs/features/scopes.mdx
index 79c1854fad0bc..a646e52d57db4 100644
--- a/docs/pages/docs/features/scopes.mdx
+++ b/docs/pages/docs/features/scopes.mdx
@@ -9,7 +9,7 @@ import Callout from "../../../components/callout";
Scoping task execution can speed up the process especially if there are distinct clusters of packages that are not related to each other within your repository. Turborepo has a `scope` option that allows the task running to proceed up to the packages found that matches the `scope` argument. It's useful to think of `scope` as an "entry point" into your monorepo's package/task graph. This is a string matcher based on the name of the packages (not the package path).
- It is important to note that depedendents and dependencies refer to the
+ It is important to note that dependents and dependencies refer to the
package and task.
diff --git a/docs/pages/docs/getting-started.mdx b/docs/pages/docs/getting-started.mdx
index 21eae85ee54aa..99ceb413b4188 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 `dependencies` and `devDependencies` being built first, this is denoted with the `^` prefix.
+In the above example, the `build` and `test` tasks are dependent 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-