From 5ef0375204650c8dd63729823471b891578cc877 Mon Sep 17 00:00:00 2001
From: Karim Abou Zeid <7303830+kabouzeid@users.noreply.github.com>
Date: Tue, 27 Aug 2024 14:49:59 +0200
Subject: [PATCH] Fix docs for disabling build isolation with `uv sync` (#6674)

Self-explanatory
---
 docs/concepts/projects.md | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/docs/concepts/projects.md b/docs/concepts/projects.md
index e3bc0220b..03e8d00c3 100644
--- a/docs/concepts/projects.md
+++ b/docs/concepts/projects.md
@@ -274,6 +274,9 @@ dependencies = []
 [project.optional-dependencies]
 build = ["setuptools", "cython"]
 compile = ["cchardet"]
+
+[tool.uv]
+no-build-isolation-package = ["cchardet"]
 ```
 
 Given the above, a user would first sync the `build` dependencies:
@@ -304,7 +307,7 @@ $ uv sync --extra build --extra compile
 ```
 
 Some packages, like `cchardet`, only require build dependencies for the _installation_ phase of
-`uv sync`. Others, like `flash-atten`, require their build dependencies to be present even just to
+`uv sync`. Others, like `flash-attn`, require their build dependencies to be present even just to
 resolve the project's lockfile during the _resolution_ phase.
 
 In such cases, the build dependencies must be installed prior to running any `uv lock` or `uv sync`