Polish "Add support for Hazelcast YAML configuration"

Closes gh-16632

spring-boot-project/spring-boot-docs/src/main/asciidoc/spring-boot-features.adoc

@@ -6539,8 +6539,8 @@ If you define a `com.hazelcast.config.Config` bean, Spring Boot uses that. If yo
 configuration defines an instance name, Spring Boot tries to locate an existing instance
 rather than creating a new one.
 
-You could also specify the `hazelcast.xml` configuration file to use through
-configuration, as shown in the following example:
+You could also specify the Hazelcast configuration file to use through configuration, as
+shown in the following example:
 
 [source,properties,indent=0]
 ----
@@ -6548,8 +6548,9 @@ configuration, as shown in the following example:
 ----
 
 Otherwise, Spring Boot tries to find the Hazelcast configuration from the default
-locations: `hazelcast.xml` in the working directory or at the root of the classpath. We
-also check if the `hazelcast.config` system property is set. See the
+locations: `hazelcast.xml` in the working directory or at the root of the classpath, or
+a `.yaml` counterpart in the same locations. We also check if the `hazelcast.config`
+system property is set. See the
 https://docs.hazelcast.org/docs/latest/manual/html-single/[Hazelcast documentation] for
 more details.
 
@@ -6560,6 +6561,7 @@ client by checking the following configuration options:
 * A configuration file defined by the `spring.hazelcast.config` property.
 * The presence of the `hazelcast.client.config` system property.
 * A `hazelcast-client.xml` in the working directory or at the root of the classpath.
+* A `hazelcast-client.yaml` in the working directory or at the root of the classpath.
 
 NOTE: Spring Boot also has
 <<boot-features-caching-provider-hazelcast,explicit caching support for Hazelcast>>. If