From fae0d7c1f61b3effb806b33dec1d8453030e23c6 Mon Sep 17 00:00:00 2001
From: shainaraskas <58563081+shainaraskas@users.noreply.github.com>
Date: Wed, 5 Mar 2025 11:21:16 -0500
Subject: [PATCH] Update node-settings.md (#123997)

* Update node-settings.md

Port change https://github.com/elastic/elasticsearch/pull/123939 forward to new docs system

* Update docs/reference/elasticsearch/configuration-reference/node-settings.md

(cherry picked from commit a06c8ea5b8d7148467860c0b283e8eda89aa776a)
---
 .../elasticsearch/configuration-reference/node-settings.md      | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/reference/elasticsearch/configuration-reference/node-settings.md b/docs/reference/elasticsearch/configuration-reference/node-settings.md
index 3a9634a37fc6b..47f8fa18ff453 100644
--- a/docs/reference/elasticsearch/configuration-reference/node-settings.md
+++ b/docs/reference/elasticsearch/configuration-reference/node-settings.md
@@ -46,7 +46,7 @@ The following additional roles are available:
 
 * `voting_only`
 
-$$$coordinating-only-node$$$If you leave `node.roles` unset, then the node is considered to be a [coordinating only node](docs-content://deploy-manage/distributed-architecture/clusters-nodes-shards/node-roles.md#coordinating-only-node-role).
+$$$coordinating-only-node$$$If If you set `node.roles` to an empty array (`node.roles: [ ]`), then the node is considered to be a [coordinating only node](docs-content://deploy-manage/distributed-architecture/clusters-nodes-shards/node-roles.md#coordinating-only-node-role).
 
 ::::{important}
 If you set `node.roles`, ensure you specify every node role your cluster needs. Every cluster requires the following node roles: