summaryrefslogtreecommitdiff
path: root/doc/user/project/integrations/slack_slash_commands.md
diff options
context:
space:
mode:
Diffstat (limited to 'doc/user/project/integrations/slack_slash_commands.md')
-rw-r--r--doc/user/project/integrations/slack_slash_commands.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/user/project/integrations/slack_slash_commands.md b/doc/user/project/integrations/slack_slash_commands.md
index 7c2413fce81..1e4577fb88e 100644
--- a/doc/user/project/integrations/slack_slash_commands.md
+++ b/doc/user/project/integrations/slack_slash_commands.md
@@ -1,7 +1,7 @@
---
stage: Create
group: Ecosystem
-info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#designated-technical-writers
+info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments
---
# Slack slash commands **(CORE ONLY)**
@@ -14,7 +14,7 @@ Slack, without having to leave it. This requires configurations in both Slack an
GitLab can also send events (e.g., `issue created`) to Slack as notifications.
This is the separately configured [Slack Notifications Service](slack.md).
-NOTE: **Note:**
+NOTE:
For GitLab.com, use the [Slack app](gitlab_slack_application.md) instead.
## Configuration