Fix broken links

1 files changed, 2 insertions, 2 deletions

diff --git a/PROCESS.md b/PROCESS.md
index 539cc4a243b..43920453722 100644
--- a/PROCESS.md
+++ b/PROCESS.md
@@ -247,12 +247,12 @@ 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),
-   the [subject label](../CONTRIBUTING.md#subject-labels-wiki-container-registry-ldap-api-etc)
+   the [subject label](../CONTRIBUTING.md#subject-labels)
    and any other label that may apply in the specific case
 
 
 1. Add the bug and regression labels
-1. Notify the respective Engineering Manager to evaluate the Severity of the regression and add a [Severity label](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CONTRIBUTING.md#bug-severity-labels-s1-s2-s3-s4). The counterpart Product Manager is included to weigh-in on prioritization as needed to set the [Priority label](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CONTRIBUTING.md#bug-priority-labels-p1-p2-p3-p4).
+1. Notify the respective Engineering Manager to evaluate the Severity of the regression and add a [Severity label](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CONTRIBUTING.md#bug-severity-labels). The counterpart Product Manager is included to weigh-in on prioritization as needed to set the [Priority label](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CONTRIBUTING.md#bug-priority-labels).
 1. If the regression is a ~S1 or ~S2, label the regression with the current milestone as it should be fixed in the current milestone.
   1. If the regression was introduced in an RC of the current release, label with ~Deliverable
   1. If the regression was introduced in the previous release, label with ~"Next Patch Release"