From a0cae5b4b2735f3dab0c4a7f3ca0c63c174d0027 Mon Sep 17 00:00:00 2001
From: kruskall <99559985+kruskall@users.noreply.github.com>
Date: Mon, 15 Apr 2024 18:27:22 +0200
Subject: [PATCH] docs: remove false deprecation note for standalone apm-server
 (#3752)

(cherry picked from commit 38f04c90afb0f794a0b3a54b54b6a3b33e0642ff)
---
 docs/en/apm-server/upgrading-to-8.x.asciidoc | 1 -
 1 file changed, 1 deletion(-)

diff --git a/docs/en/apm-server/upgrading-to-8.x.asciidoc b/docs/en/apm-server/upgrading-to-8.x.asciidoc
index bde78f8d96..d923d8003b 100644
--- a/docs/en/apm-server/upgrading-to-8.x.asciidoc
+++ b/docs/en/apm-server/upgrading-to-8.x.asciidoc
@@ -30,7 +30,6 @@ Starting in version 7.14, there are two ways to run Elastic APM.
 Determine which method you're using, then use the links below to find the correct upgrading guide.
 
 * **Standalone**: Users in this mode run and configure the APM Server binary.
-This mode has been deprecated and will be removed in a future release.
 * **{fleet} and the APM integration**: Users in this mode run and configure {fleet} and the Elastic APM integration.
 
 **Self-installation (non-{ecloud} users) upgrade guides**