From d0474b6548d1e5bb5fe94e0b050e00b85122b593 Mon Sep 17 00:00:00 2001
From: "mergify[bot]" <37929162+mergify[bot]@users.noreply.github.com>
Date: Wed, 17 Jul 2024 10:27:37 -0700
Subject: [PATCH] Remove cloud shell editor deprecation notification (#5554)
 (#5571)

* remove deprecation notice

* remove deprecation notice

(cherry picked from commit f76b34f4c4b6f81f54aa1af61568233f495a6c14)

Co-authored-by: Uri Weisman <68195305+uri-weisman@users.noreply.github.com>
---
 docs/cloud-native-security/cspm-get-started-gcp.asciidoc | 5 -----
 1 file changed, 5 deletions(-)

diff --git a/docs/cloud-native-security/cspm-get-started-gcp.asciidoc b/docs/cloud-native-security/cspm-get-started-gcp.asciidoc
index 524fc3f54e..e5db04d34f 100644
--- a/docs/cloud-native-security/cspm-get-started-gcp.asciidoc
+++ b/docs/cloud-native-security/cspm-get-started-gcp.asciidoc
@@ -60,11 +60,6 @@ For most users, the simplest option is to use a Google Cloud Shell script to aut
 +
 image::images/cspm-cloudshell-trust.png[The cloud shell confirmation popup]
 +
-NOTE: Google has deprecated its old Cloud Shell editor. If you continue to use it, you may encounter the following message:
-+
-image::images/cspm-cloudshell-old-editor.png[The cloud shell switch editor popup]
-+
-If the message appears, click **X** or **Try the new Editor** and follow the next steps. When you switch to the new editor, your context should remain unchanged.
 . In Google Cloud Shell, execute the command you copied. Once it finishes, return to {kib} and wait for the confirmation of data received from your new integration. Then you can click **View Assets** to see your data.
 
 NOTE: If you encounter any issues running the command, return to {kib} and navigate again to Google Cloud Shell.