Add latest changes from gitlab-org/gitlab@13-1-stable-ee

1 files changed, 2 insertions, 2 deletions

diff --git a/doc/user/project/merge_requests/browser_performance_testing.md b/doc/user/project/merge_requests/browser_performance_testing.md
index 0fa3d7be265..390d480724d 100644
--- a/doc/user/project/merge_requests/browser_performance_testing.md
+++ b/doc/user/project/merge_requests/browser_performance_testing.md
@@ -60,7 +60,7 @@ on your code by using GitLab CI/CD and [sitespeed.io](https://www.sitespeed.io)
 using Docker-in-Docker.
 
 1. First, set up GitLab Runner with a
-   [docker-in-docker build](../../../ci/docker/using_docker_build.md#use-docker-in-docker-workflow-with-docker-executor).
+   [Docker-in-Docker build](../../../ci/docker/using_docker_build.md#use-docker-in-docker-workflow-with-docker-executor).
 1. After configuring the Runner, add a new job to `.gitlab-ci.yml` that generates
    the expected report.
 1. Define the `performance` job according to your version of GitLab:
@@ -125,7 +125,7 @@ Key metrics are automatically extracted and shown in the merge request widget.
 
 ### Configuring degradation threshold
 
-> [Introduced](https://gitlab.com/gitlab-org/gitlab/issues/27599) in GitLab 13.0.
+> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/27599) in GitLab 13.0.
 
 You can configure the sensitivity of degradation alerts to avoid getting alerts for minor drops in metrics.
 This is done by setting the `DEGRADATION_THRESHOLD` variable. In the example below, the alert will only show up