From 33b4dcb7743a1fe83566b39991f754412da930f2 Mon Sep 17 00:00:00 2001
From: Jeremiah K <17190268+jeremiah-k@users.noreply.github.com>
Date: Wed, 4 Dec 2024 16:59:07 -0600
Subject: [PATCH] Fix typo in merge-queue readme.md (#380)

---
 merge-queue/readme.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/merge-queue/readme.md b/merge-queue/readme.md
index c5195694..10fc1301 100644
--- a/merge-queue/readme.md
+++ b/merge-queue/readme.md
@@ -16,7 +16,7 @@ Merge queues automate PR merges into your repo's `main` branch, ensuring incompa
 
 ### **Why do teams adopt a merge queue?**
 
-As the number of concurrent, changes to a repository grows, the likelihood that your pull request has stale/invalid test results increases. The only way to guarantee that your `main` branch doesn not become "broken" is to make sure that all code changes are tested against the head of `main`.
+As the number of concurrent, changes to a repository grows, the likelihood that your pull request has stale/invalid test results increases. The only way to guarantee that your `main` branch does not become "broken" is to make sure that all code changes are tested against the head of `main`.
 
 As an example: