From 9290c62dcd485b2fcbdf20412468c9f513b003c8 Mon Sep 17 00:00:00 2001
From: Paul Schisa <75806143+pschisa@users.noreply.github.com>
Date: Fri, 16 Jun 2023 10:58:51 -0400
Subject: [PATCH] Update ssh-approval-slack.mdx

remove messaging indicating approvals happen directly in slack as that was removed for security concerns
---
 .../access-request-plugins/ssh-approval-slack.mdx           | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/pages/access-controls/access-request-plugins/ssh-approval-slack.mdx b/docs/pages/access-controls/access-request-plugins/ssh-approval-slack.mdx
index 51127183ff57d..f3552feb21feb 100644
--- a/docs/pages/access-controls/access-request-plugins/ssh-approval-slack.mdx
+++ b/docs/pages/access-controls/access-request-plugins/ssh-approval-slack.mdx
@@ -5,9 +5,9 @@ description: How to set up Teleport's Slack plugin for privilege elevation appro
 
 This guide will explain how to set up Slack to receive Access Request messages
 from Teleport. Teleport's Slack integration notifies individuals and channels of
-Access Requests. Users can then approve and deny Access Requests from within
-Slack, making it easier to implement security best practices without
-compromising productivity.
+Access Requests. Users are then directed to log in to the Teleport cluster where
+they can approve and deny Access Requests, making it easier to implement security 
+best practices without compromising productivity.
 
 (!docs/pages/includes/plugins/diagram.mdx api="Slack" action="Listen for Access Requests" messages="Slack messages" !)