diff --git a/docs/changelog/112903.yaml b/docs/changelog/112903.yaml
index f15364336e620..6ac762209b679 100644
--- a/docs/changelog/112903.yaml
+++ b/docs/changelog/112903.yaml
@@ -13,5 +13,5 @@ breaking:
     `single-node`.
   impact: >-
     Remove any value for `discovery.type` from your `elasticsearch.yml`
-    configuration file.
+    configuration file except for `multi-node` and `single-node`.
   notable: false
diff --git a/docs/reference/migration/migrate_9_0.asciidoc b/docs/reference/migration/migrate_9_0.asciidoc
index 38685d9ac1d1f..80469999795af 100644
--- a/docs/reference/migration/migrate_9_0.asciidoc
+++ b/docs/reference/migration/migrate_9_0.asciidoc
@@ -184,7 +184,7 @@ Remove `xpack.searchable.snapshot.allocate_on_rolling_restart` from your setting
 Earlier versions of {es} had a `discovery.type` setting which permitted values that referred to legacy discovery types. From v9.0.0 onwards, the only supported values for this setting are `multi-node` (the default) and `single-node`.
 
 *Impact* +
-Remove any value for `discovery.type` from your `elasticsearch.yml` configuration file.
+Remove any value for `discovery.type` from your `elasticsearch.yml` configuration file except for `multi-node` and `single-node`.
 ====
 
 [discrete]