From 34af52b0de455817d9998b402f539e846b1bd750 Mon Sep 17 00:00:00 2001 From: Wes Copeland Date: Wed, 29 Jan 2025 17:17:43 -0500 Subject: [PATCH] Update docs/guidelines/developers/handling-tickets.md --- docs/guidelines/developers/handling-tickets.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/guidelines/developers/handling-tickets.md b/docs/guidelines/developers/handling-tickets.md index ad717699..b727b851 100644 --- a/docs/guidelines/developers/handling-tickets.md +++ b/docs/guidelines/developers/handling-tickets.md @@ -10,7 +10,7 @@ description: Guidelines for managing and resolving achievement tickets, includin ## Handling Own Tickets **After a developer has published achievements, they should be prepared for bug reports.** -A developer's top priority on RetroAchievements is to keep their work bug free by appropriately resolving tickets. Developer shall respond to all tickets as soon as possible. The sooner the response, the better, because the problem is fresh in the player's mind and their knowledge can be used to help resolve the problem. +A developer's top priority on RetroAchievements is to keep their work bug free by appropriately resolving tickets. A developer shall respond to all tickets as soon as possible. The sooner the response, the better, because the problem is fresh in the player's mind and their knowledge can be used to help resolve the problem. ## New Set Claims With Open Tickets?