From 31f533df2735845befedaa7baf71837cb0156d79 Mon Sep 17 00:00:00 2001 From: Noah Talerman <47070608+noahtalerman@users.noreply.github.com> Date: Wed, 12 Nov 2025 17:39:42 -0500 Subject: [PATCH] Fix spelling error in communications.md (#35630) --- handbook/company/communications.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/handbook/company/communications.md b/handbook/company/communications.md index eec766f052..f9b5e89a38 100644 --- a/handbook/company/communications.md +++ b/handbook/company/communications.md @@ -452,7 +452,7 @@ All issues are treated as standard priority by default. Some issues are assigned - Urgent: `P2` - Examples: A supported workflow is not functioning as intended, a newly drafted feature has an associated urgent Fleet need. - - Response: Issue is prioritized at the top of the next sprint. If opporunity cost of waiting for the next sprint is too high, it may be considered for current sprint. + - Response: Issue is prioritized at the top of the next sprint. If opportunity cost of waiting for the next sprint is too high, it may be considered for current sprint. - Impact: Low to medium impact. If prioritized into current sprint, may reduce overall velocity and require deprioritizing other work. Any fleetie can follow the process below to add a priority label to an issue.