summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorbikebilly <fabio@gitlab.com>2018-06-20 23:16:46 -0400
committerbikebilly <fabio@gitlab.com>2018-06-20 23:16:46 -0400
commitc5073e67f4d0d777b3015ad1f6bde6d69815df6b (patch)
treec0e8e89c446051f7a0b9c37f89cf5d78f1d2a80b
parent3739c1b9d4aa878b5766b8e196a5952160340972 (diff)
downloadgitlab-ce-c5073e67f4d0d777b3015ad1f6bde6d69815df6b.tar.gz
Copyedits
-rw-r--r--PROCESS.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/PROCESS.md b/PROCESS.md
index d09f6a41899..965a3b62873 100644
--- a/PROCESS.md
+++ b/PROCESS.md
@@ -246,7 +246,7 @@ will be scheduled.
When a regression is found:
1. Create an issue describing the problem in the most detailed way possible
1. If possible, provide links to real examples and how to reproduce the problem
-1. Label the issue properly, using the [team label](../CONTRIBUTING.md#team-labels-ci-discussion-edge-platform-etc),
+1. Label the issue properly, using the [team label](../CONTRIBUTING.md#team-labels),
the [subject label](../CONTRIBUTING.md#subject-labels-wiki-container-registry-ldap-api-etc)
and any other label that may apply in the specific case
1. Add the ~bug and ~regression labels