From bfa866772a41c046e73818ed164b190c64ec0bd2 Mon Sep 17 00:00:00 2001
From: Stompy <45337015+airamare01@users.noreply.github.com>
Date: Mon, 20 Nov 2023 17:19:00 +0300
Subject: [PATCH] Minor team update to slack channel (#8235)

This minor edit changes the team slack channel to reflect what we have
currently.
---
 .../departments/engineering/teams/source/support_rotation.md    | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/departments/engineering/teams/source/support_rotation.md b/content/departments/engineering/teams/source/support_rotation.md
index adafc8f44117..21f609deb64a 100644
--- a/content/departments/engineering/teams/source/support_rotation.md
+++ b/content/departments/engineering/teams/source/support_rotation.md
@@ -11,7 +11,7 @@ It does _not_ mean that you are alone and should fix every issue completely and
 Here are the expectations when you are on support rotation:
 
 1. Triaging and resolving support requests is your #1 priority for the week. You can plan to do other work, but if a support request comes in or needs work, then that's the #1 priority.
-1. Monitor #discuss-source and #ask-engineering for Source-related questions and bug reports.
+1. Monitor #discuss-source and #discuss-engineering for Source-related questions and bug reports.
 1. Acknowledge bug reports and questions. Even a simple "I'm on it, taking a look" in the Slack thread is good, since it lets others on the team know that you are working on it.
 1. Provide the next engineering on support with the status of all in-flight issues before their rotation begins: prepare to report status of support in sprint planning.
 1. Ask for help when you are stuck! Don't spend too much time trying to troubleshoot an issue alone and you get stuck, especially if it's high priority. Do your best, ask the team, and resolve the issue.