diff --git a/docs/site/content/docs/crafting-your-repository/configuring-tasks.mdx b/docs/site/content/docs/crafting-your-repository/configuring-tasks.mdx
index 12245522208b7..47bee307fa0d1 100644
--- a/docs/site/content/docs/crafting-your-repository/configuring-tasks.mdx
+++ b/docs/site/content/docs/crafting-your-repository/configuring-tasks.mdx
@@ -9,7 +9,9 @@ import { Tabs, Tab } from '#components/tabs';
 import { Files, File, Folder } from '#components/files';
 import { ThemeAwareImage } from '#components/theme-aware-image';
 
-Turborepo will always run tasks in the order described in your [`turbo.json` configuration](/docs/reference/configuration) and [Package Graph](/docs/core-concepts/package-and-task-graph#package-graph), parallelizing work whenever possible to ensure everything runs as fast as possible. This is faster than running tasks one at a time, and it's a part of what makes Turborepo so fast.
+A task is a script that Turborepo runs. You can express relationships between tasks in your [`turbo.json` configuration](/docs/reference/configuration) and [Package Graph](/docs/core-concepts/package-and-task-graph#package-graph).
+
+Turborepo will always parallelize any work that it can to ensure everything runs as fast as possible. This is faster than running tasks one at a time, and it's a part of what makes Turborepo so fast.
 
 For example, <code style={{textWrap: "wrap"}}>yarn workspaces run lint && yarn workspaces run test && yarn workspaces run build</code> would look like this: