From 00fbaa0e64125bf3944a8a0da87f236b7a55f86e Mon Sep 17 00:00:00 2001
From: Josh Cummings <3627351+jzheaux@users.noreply.github.com>
Date: Tue, 18 Feb 2025 14:44:55 -0700
Subject: [PATCH] Updated Community Duty Tasks (markdown)

---
 Community-Duty-Tasks.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/Community-Duty-Tasks.md b/Community-Duty-Tasks.md
index b763391..b7e39fe 100644
--- a/Community-Duty-Tasks.md
+++ b/Community-Duty-Tasks.md
@@ -19,7 +19,7 @@ Otherwise, do the following:
 
 (If a feature is brand new, still consider answering the question. The reason for this is that the likelihood that it is a bug or a much-needed feature is higher and so it is worth it to allow those questions as an exception to the rule.)
 
-If it's a bug, also do the following:
+If it's a `type: bug`, also do the following:
 
 1. Consider the urgency of the issue. Does it affect many users? :arrow_up: Has it been around for a long time and we are just hearing about it now? :arrow_down: Is it part of a new feature? :arrow_up: Is there an easy workaround? :arrow_down:
 2. Reproduce it. If you don't have enough information, ask and label with `status: waiting-for-feedback`.
@@ -31,7 +31,7 @@ If it's a bug, also do the following:
 8. Add any additional needed explanation in a comment.
 9. If at this point the bug is addressed, close it.
 
-If it's a feature, do the following:
+If it's a `type: enhancement`, do the following:
 
 1. Evaluate it. If you don't have enough information, ask and label with `status: waiting-for-feedback`.
 2. If you disagree, mark the ticket as `status: declined`.