From 607f66daeecc3304323225bf996186a4bc0fd5ba Mon Sep 17 00:00:00 2001
From: cinderflash <154299375+cinderflash@users.noreply.github.com>
Date: Thu, 21 Dec 2023 17:17:46 -0700
Subject: [PATCH] Remove extraneous word

---
 introduction/issue-tracking.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/introduction/issue-tracking.md b/introduction/issue-tracking.md
index 64db9112..f711dd9d 100644
--- a/introduction/issue-tracking.md
+++ b/introduction/issue-tracking.md
@@ -188,7 +188,7 @@ We close issues at step 3. Then, as updates are released, the issue automaticall
 
 Therefore, if you see that an issue is closed, but the fix is not yet available to you, be aware that it may be at an intermediate stage of this process between issue closure and the update being available in whichever repos you have enabled in whichever version of Qubes you're using.
 
-In order to assist with this, we have a label called [backport pending](https://github.com/QubesOS/qubes-issues/labels/backport%20pending), which means, "The fix has been released for the testing release but is pending backport to the stable release." Our infrastructure will attempt to apply this label automatically, when appropriate, but it is not perfect, and the developers may be need to adjust it manually.
+In order to assist with this, we have a label called [backport pending](https://github.com/QubesOS/qubes-issues/labels/backport%20pending), which means, "The fix has been released for the testing release but is pending backport to the stable release." Our infrastructure will attempt to apply this label automatically, when appropriate, but it is not perfect, and the developers may need to adjust it manually.
 
 ### Understanding open and closed issues