diff --git a/docs/kb/semgrep-ci/mr-comments-through-gitlab-runner.md b/docs/kb/semgrep-ci/mr-comments-through-gitlab-runner.md
index 22c93a187..aca4fb2c3 100644
--- a/docs/kb/semgrep-ci/mr-comments-through-gitlab-runner.md
+++ b/docs/kb/semgrep-ci/mr-comments-through-gitlab-runner.md
@@ -2,16 +2,16 @@
 append_help_link: true
 title: Receive Semgrep MR comments through a GitLab runner
 hide_title: true
-description: Set additional environment variables to receive Semgrep MR comments through a GitLab runner.
+description: Set additional environment variables to receive Semgrep MR comments with other pipeline events.
 tags:
   - Semgrep in CI
 ---
 
-# Receive Semgrep MR comments through a GitLab runner
+# Receive Semgrep MR comments with other pipeline events
 
 Generally, Semgrep recommends using the [<i class="fas fa-external-link fa-xs"></i> GitLab merge request pipeline](https://docs.gitlab.com/ee/ci/pipelines/merge_request_pipelines.html) to receive MR comments. This method is used in the default [Semgrep GitLab config file](/semgrep-ci/sample-ci-configs/#sample-github-actions-configuration-file).
 
-However, you can also receive comments through your own [<i class="fas fa-external-link fa-xs"></i> GitLab runner](https://docs.gitlab.com/runner/) by setting the following variables in your CI job:
+However, if you run pipelines on [other events](https://docs.gitlab.com/ee/user/project/integrations/webhook_events.html), and want those pipelines to run [diff-aware scans](https://semgrep.dev/docs/semgrep-code/glossary#diff-aware-scan), you can configure them to do so and thereby receive comments by setting the following variables in your CI job:
 
 <pre class="language-bash"><code>
  export GITLAB_CI='true'