summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorVictor Wu <victor@gitlab.com>2017-11-06 16:46:50 +0000
committerVictor Wu <victor@gitlab.com>2017-11-06 16:46:50 +0000
commit5bbab0d7cef1c173ac1da914b7d169698038aa61 (patch)
tree47ce43af6cd4aa7cd6f3973762c72851f578fbe9
parent14803eaec5ed5b260cd83c69bad51e376de11879 (diff)
downloadgitlab-ce-sort-order-priority-labels-docs.tar.gz
-rw-r--r--doc/user/project/labels.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/user/project/labels.md b/doc/user/project/labels.md
index b4b543319af..d7eb4bca89c 100644
--- a/doc/user/project/labels.md
+++ b/doc/user/project/labels.md
@@ -97,7 +97,7 @@ The 'Priority' sort order comparison first considers an issue's milestone's due
(if the issue is assigned a milestone and the milestone's due date exists), and then
secondarily considers the label priority comparison above. Sooner due dates results
a higher sort order. If an issue doesn't have a milestone due date, it is equivalent to
-being assigned to a milestone that has a due date in the infinite futue. Given two issues
+being assigned to a milestone that has a due date in the infinite future. Given two issues
are equal according to this two-stage sort comparison, their relative order is equal, and
therefore it's not guaranteed that one will be always above the other.