From f275052b63ce0e7a06433e4b48c49fd1029903f7 Mon Sep 17 00:00:00 2001
From: Josh Cummings <3627351+jzheaux@users.noreply.github.com>
Date: Tue, 18 Feb 2025 14:44:22 -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 fee0911..b763391 100644
--- a/Community-Duty-Tasks.md
+++ b/Community-Duty-Tasks.md
@@ -15,9 +15,9 @@ Otherwise, do the following:
 3. Label the issue with the appropriate `in: xyz` label.
 4. Correct any incorrect labels.
 5. If it's a duplicate, label it as a `status: duplicate` and close the issue with a comment linking to the issue.
-6. If it's a question, label it as `type: stackoverflow`, and close with a comment inviting them to use StackOverflow :star:
+6. If it's a question, label it as `type: stackoverflow`, and close with a comment inviting them to use StackOverflow
 
-:star: - 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 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: