diff --git a/explore-analyze/query-filter/languages/esql-cross-clusters.md b/explore-analyze/query-filter/languages/esql-cross-clusters.md
index 1dc6f83304..88c6e5e379 100644
--- a/explore-analyze/query-filter/languages/esql-cross-clusters.md
+++ b/explore-analyze/query-filter/languages/esql-cross-clusters.md
@@ -169,7 +169,7 @@ PUT _cluster/settings
 }
 ```
 
-1. Since `skip_unavailable` was not set on `cluster_three`, it uses the default of `false`. See the [Optional remote clusters](#ccq-skip-unavailable-clusters) section for details.
+1. Since `skip_unavailable` was not set on `cluster_three`, it uses the default of `true`. See the [Optional remote clusters](#ccq-skip-unavailable-clusters) section for details.
 
 
 
@@ -284,7 +284,7 @@ Which returns:
 ```
 
 1. How long the entire search (across all clusters) took, in milliseconds.
-2. This section of counters shows all possible cluster search states and how many cluster searches are currently in that state. The clusters can have one of the following statuses: **running**, **successful** (searches on all shards were successful), **skipped** (the search failed on a cluster marked with `skip_unavailable`=`true`), **failed** (the search failed on a cluster marked with `skip_unavailable`=`false`) or **partial** (the search was [interrupted](https://www.elastic.co/guide/en/elasticsearch/reference/current/esql-async-query-stop-api.html) before finishing).
+2. This section of counters shows all possible cluster search states and how many cluster searches are currently in that state. The clusters can have one of the following statuses: **running**, **successful** (searches on all shards were successful), **skipped** (the search failed on a cluster marked with `skip_unavailable`=`true`), **failed** (the search failed on a cluster marked with `skip_unavailable`=`false`) or **partial** (the search was [interrupted](https://www.elastic.co/guide/en/elasticsearch/reference/current/esql-async-query-stop-api.html) before finishing or has partially failed).
 3. The `_clusters/details` section shows metadata about the search on each cluster.
 4. If you included indices from the local cluster you sent the request to in your {{ccs}}, it is identified as "(local)".
 5. How long (in milliseconds) the search took on each cluster. This can be useful to determine which clusters have slower response times than others.
@@ -469,10 +469,9 @@ FROM my-index-000001,cluster*:my-index-*,cluster_three:-my-index-000001
 
 ## Optional remote clusters [ccq-skip-unavailable-clusters]
 
-{{ccs-cap}} for {{esql}} currently does not respect the `skip_unavailable` setting. As a result, if a remote cluster specified in the request is unavailable or failed, {{ccs}} for {{esql}} queries will fail regardless of the setting.
-
-We are actively working to align the behavior of {{ccs}} for {{esql}} with other {{ccs}} APIs.
-
+If a remote cluster disconnects from the querying cluster, {ccs-cap} for {esql} will set it to `skipped`
+and continue the query with other clusters, unless the remote cluster's `skip_unavailable` setting is set to `false`,
+in which case the query will fail.
 
 ## Query across clusters during an upgrade [ccq-during-upgrade]