summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMarcia Ramos <marcia@gitlab.com>2019-02-06 11:38:18 +0000
committerMarcia Ramos <marcia@gitlab.com>2019-02-06 11:38:18 +0000
commit4e24db32cd6269d22ee1df8a3d57c47ff25ac864 (patch)
tree346ee60926d42c6afebfd7896e0bf2c506db5a54
parent561ce0c09516cf62125a0832ff3656a1ed93470f (diff)
parent9937b07bf3a1091f74bd75ba30df5e95ce18f3b9 (diff)
downloadgitlab-ce-4e24db32cd6269d22ee1df8a3d57c47ff25ac864.tar.gz
Merge branch 'vzagorodny-fix-typo-feat-proposal-comment' into 'master'
Fix comment typo in feature proposal issue template See merge request gitlab-org/gitlab-ce!24927
-rw-r--r--.gitlab/issue_templates/Feature proposal.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/.gitlab/issue_templates/Feature proposal.md b/.gitlab/issue_templates/Feature proposal.md
index 0b22c7bc26b..1bb8d33ff63 100644
--- a/.gitlab/issue_templates/Feature proposal.md
+++ b/.gitlab/issue_templates/Feature proposal.md
@@ -39,7 +39,7 @@ Existing personas are: (copy relevant personas out of this comment, and delete a
### What does success look like, and how can we measure that?
-<!--- Define both the success metrics and acceptance criteria. Note thet success metrics indicate the desired business outcomes, while acceptance criteria indicate when the solution is working correctly. If there is no way to measure success, link to an issue that will implement a way to measure this -->
+<!--- Define both the success metrics and acceptance criteria. Note that success metrics indicate the desired business outcomes, while acceptance criteria indicate when the solution is working correctly. If there is no way to measure success, link to an issue that will implement a way to measure this -->
### Links / references