about summary refs log tree commit diff
path: root/.github/ISSUE_TEMPLATE
diff options
context:
space:
mode:
authordylni <46035563+dylni@users.noreply.github.com>2020-09-05 20:12:26 -0400
committerdylni <46035563+dylni@users.noreply.github.com>2020-09-05 20:12:26 -0400
commitb92b0d6ee6ef1aaca1d7b7777eaa431fd29920a3 (patch)
tree397f3f9bba99895f19d364b45fe3146ed3791c3e /.github/ISSUE_TEMPLATE
parentcdc8f0606d0f3c4f3866643382c8a5776d1bdaed (diff)
downloadrust-b92b0d6ee6ef1aaca1d7b7777eaa431fd29920a3.tar.gz
rust-b92b0d6ee6ef1aaca1d7b7777eaa431fd29920a3.zip
Fix typo in tracking issue template
Diffstat (limited to '.github/ISSUE_TEMPLATE')
-rw-r--r--.github/ISSUE_TEMPLATE/tracking_issue.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/.github/ISSUE_TEMPLATE/tracking_issue.md b/.github/ISSUE_TEMPLATE/tracking_issue.md
index 51bf0c3ee67..24f43213897 100644
--- a/.github/ISSUE_TEMPLATE/tracking_issue.md
+++ b/.github/ISSUE_TEMPLATE/tracking_issue.md
@@ -23,7 +23,7 @@ The feature gate for the issue is `#![feature(FFF)]`.
 ### About tracking issues
 
 Tracking issues are used to record the overall progress of implementation.
-They are also uses as hubs connecting to other relevant issues, e.g., bugs or open design questions.
+They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions.
 A tracking issue is however *not* meant for large scale discussion, questions, or bug reports about a feature.
 Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.