Update docs/reference/announcements.md

Co-authored-by: Cole Isaac <[email protected]> Signed-off-by: Ahmed AbouZaid <[email protected]>
camunda · Sep 5, 2024 · 96fa0e5 · 96fa0e5
1 parent 740b437
commit 96fa0e5
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/docs/reference/announcements.md b/docs/reference/announcements.md
@@ -123,7 +123,7 @@ The separated Ingress Helm configuration for Camunda 8 Self-Managed has been dep
 
 #### Helm chart - Elasticsearch nodes number
 
-The default value of Elasticsearch deployment pods has changed from 2 to 3 with an affinity setting. This avoids scheduling Elasticsearch pods on the same Kubernetes worker.
+The default value of Elasticsearch deployment pods has changed from 2 to 3, and an affinity setting has been added to avoid scheduling Elasticsearch pods on the same Kubernetes worker.
 
 ## Camunda 8.5
 

diff --git a/docs/self-managed/operational-guides/update-guide/850-to-860.md b/docs/self-managed/operational-guides/update-guide/850-to-860.md
@@ -14,4 +14,4 @@ The separated Ingress Helm configuration for Camunda 8 Self-Managed has been dep
 
 ### Elasticsearch nodes number
 
-The default value of Elasticsearch deployment pods has changed from 2 to 3 with an affinity setting. This avoids scheduling Elasticsearch pods on the same Kubernetes worker.
+The default value of Elasticsearch deployment pods has changed from 2 to 3, and an affinity setting has been added to avoid scheduling Elasticsearch pods on the same Kubernetes worker.
Original file line number	Diff line number	Diff line change
Expand Up		@@ -14,4 +14,4 @@ The separated Ingress Helm configuration for Camunda 8 Self-Managed has been dep

		### Elasticsearch nodes number

		The default value of Elasticsearch deployment pods has changed from 2 to 3 with an affinity setting. This avoids scheduling Elasticsearch pods on the same Kubernetes worker.
		The default value of Elasticsearch deployment pods has changed from 2 to 3, and an affinity setting has been added to avoid scheduling Elasticsearch pods on the same Kubernetes worker.