++++
\ No newline at end of file
diff --git a/docs/en/observability/apm/getting-started-apm/index.asciidoc b/docs/en/observability/apm/getting-started-apm/index.asciidoc
index bf8aebaedb..68e01b8f4d 100644
--- a/docs/en/observability/apm/getting-started-apm/index.asciidoc
+++ b/docs/en/observability/apm/getting-started-apm/index.asciidoc
@@ -16,7 +16,6 @@ There are two options, and the components required are different for each:
* **<>**
* **<>**
-// * **<>**
[float]
[[apm-setup-fleet-managed-apm]]
@@ -27,14 +26,12 @@ In this deployment model, use {agent} to spin up APM Server instances that can b
image::./images/fm-ov.png[APM Server fleet overview]
-// (outputs, stable APIs)
-// not the best option for a simple test setup or if only interested in centrally running APM Server
-
[cols="1,3"]
|===
| *Pros*
-a| Conveniently manage one, some, or many different
+a| * Conveniently manage one, some, or many different
integrations from one central {fleet} UI.
+* Centrally manage multiple APM Servers running on edge machines.
| *Supported outputs*
a| * {es}
@@ -86,7 +83,8 @@ a| YAML
[float]
== Help me decide
-Use the decision tree below to help determine which method of configuring and running the APM Server is best for your use case.
+This decision tree highlights key factors to help you make an informed decision about implementing Elastic APM.
+It provides practical guidance and is not intended to serve as a comprehensive reference of all possible implementations and capabilities.
[subs=attributes+]
include::{observability-docs-root}/docs/en/observability/apm/diagrams/apm-decision-tree.asciidoc[APM Server decision tree]