diff --git a/docs/en/observability/slo-create.asciidoc b/docs/en/observability/slo-create.asciidoc
index 911ba63cbb..00052f5ba3 100644
--- a/docs/en/observability/slo-create.asciidoc
+++ b/docs/en/observability/slo-create.asciidoc
@@ -139,7 +139,7 @@ When defining a histogram metric SLI, set the following fields:
 [[apm-latency-sli]]
 === APM latency
 
-Create an indicator based on the APM data that you received from your instrumented services and a latency threshold.
+Create an indicator based on latency data received from your instrumented services and a latency threshold.
 
 *Example:* You can define an indicator on an APM service named `banking-service` for the `production` environment, and the transaction name `POST /deposit` with a latency threshold value of 300ms.
 
@@ -147,7 +147,8 @@ Create an indicator based on the APM data that you received from your instrument
 [[apm-availability-sli]]
 === APM availability
 
-Create an indicator based on the APM data received from your instrumented services.
+Create an indicator based on the availability of your instrumented services.
+Availability is determined by calculating the percentage of successful transactions (`event.outcome : "success"`) out of the total number of successful and failed transactions—unknown outcomes are excluded.
 
 *Example:* You can define an indicator on an APM service named `search-service` for the `production` environment, and the transaction name `POST /search`.
 
diff --git a/docs/en/serverless/slos/create-an-slo.mdx b/docs/en/serverless/slos/create-an-slo.mdx
index d9cab62932..94f299aadc 100644
--- a/docs/en/serverless/slos/create-an-slo.mdx
+++ b/docs/en/serverless/slos/create-an-slo.mdx
@@ -143,11 +143,12 @@ When defining a histogram metric SLI, set the following fields:
 
 There are two types of SLI you can create based on services using application performance monitoring (APM): APM latency and APM availability.
 
-Use **APM latency** to create an indicator based on the APM data that you received from your instrumented services and a latency threshold.
+Use **APM latency** to create an indicator based on latency data received from your instrumented services and a latency threshold.
 
 **Example:** You can define an indicator on an APM service named `banking-service` for the `production` environment, and the transaction name `POST /deposit` with a latency threshold value of 300ms.
 
-Use **APM availability** to create an indicator based on the APM data received from your instrumented services.
+Use **APM availability** to create an indicator based on the availability of your instrumented services.
+Availability is determined by calculating the percentage of successful transactions (`event.outcome : "success"`) out of the total number of successful and failed transactions—unknown outcomes are excluded.
 
 **Example:** You can define an indicator on an APM service named `search-service` for the `production` environment, and the transaction name `POST /search`.