Skip to content

Worktrunk is a CLI for Git worktree management, designed for parallel AI agent workflows

docs: improve grammar and clarity in why-worktrunk documentation

Maximilian Rooscdccfd71c5f0
diff --git a/README.md b/README.md
index 65311c945..e546644f1 100644
--- a/README.md
+++ b/README.md
@@ -25,11 +25,11 @@ Here's a quick demo:
## Context: git worktrees
-AI agents like Claude and Codex can increasingly handle longer tasks without supervision, and it's very practical to run several in parallel. But on a single file tree they step on each other's uncommitted changes.
+AI agents like Claude and Codex can increasingly handle longer tasks without supervision, and it's very practical to run several in parallel. On a single file tree, they step on each other's uncommitted changes.
Git worktrees are a great primitive for this: multiple working directories sharing one `.git`.
-But git worktrees' UX is clunky: `git worktree add -b feature ../repo.feature`, then `cd ../repo.feature`, then `git worktree remove ../repo.feature`.
+But the UX is clunky: `git worktree add -b feature ../repo.feature`, then `cd ../repo.feature`, then `git worktree remove ../repo.feature`.
## What Worktrunk adds
diff --git a/docs/content/why-worktrunk.md b/docs/content/why-worktrunk.md
index dfe229fa2..19c62e5e2 100644
--- a/docs/content/why-worktrunk.md
+++ b/docs/content/why-worktrunk.md
@@ -14,11 +14,11 @@ Here's a quick demo:
## Context: git worktrees
-AI agents like Claude and Codex can increasingly handle longer tasks without supervision, and it's very practical to run several in parallel. But on a single file tree they step on each other's uncommitted changes.
+AI agents like Claude and Codex can increasingly handle longer tasks without supervision, and it's very practical to run several in parallel. On a single file tree, they step on each other's uncommitted changes.
Git worktrees are a great primitive for this: multiple working directories sharing one `.git`.
-But git worktrees' UX is clunky: `git worktree add -b feature ../repo.feature`, then `cd ../repo.feature`, then `git worktree remove ../repo.feature`.
+But the UX is clunky: `git worktree add -b feature ../repo.feature`, then `cd ../repo.feature`, then `git worktree remove ../repo.feature`.
## What Worktrunk adds