From 0bebcd77d27087db716ecb711cad23d154d808c2 Mon Sep 17 00:00:00 2001
From: Rowan Walsh <1158758+rowan-walsh@users.noreply.github.com>
Date: Tue, 23 Apr 2024 18:20:41 -0700
Subject: [PATCH] Fixes grammar issues in docs

---
 docs/contributing.md | 2 +-
 docs/design/run.md   | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/contributing.md b/docs/contributing.md
index 881185385a..a65fe0783e 100644
--- a/docs/contributing.md
+++ b/docs/contributing.md
@@ -35,7 +35,7 @@ function in order to add a new feature cleanly, put the refactoring in one
 commit and the new feature in a different commit. If the refactoring itself
 consists of many parts, try to separate out those into separate commits. You can
 use `jj split` to do it if you didn't realize ahead of time how it should be
-split up. Include tests and documentation in the same commit as the code the
+split up. Include tests and documentation in the same commit as the code they
 test and document. The commit message should describe the changes in the commit;
 the PR description can even be empty, but feel free to include a personal
 message.
diff --git a/docs/design/run.md b/docs/design/run.md
index 56b664e8d4..3c7883e089 100644
--- a/docs/design/run.md
+++ b/docs/design/run.md
@@ -194,7 +194,7 @@ running processes. Notify the user that we failed to apply the command to the
 specific revision. 
 
 We will leave any affected commit in its current state, if any subprocess fails.
-This allows us provide a better user experience, as leaving revisions in an 
+This allows us to provide a better user experience, as leaving revisions in an 
 undesirable state, e.g partially formatted, may confuse users.
 
 ## Resource constraints