update usage of guess to determine (#5162)

camunda · Mar 5, 2025 · d91c4c5 · d91c4c5
1 parent 26fbcf7
commit d91c4c5
Show file tree

Hide file tree

Showing 12 changed files with 12 additions and 12 deletions.
diff --git a/docs/self-managed/operate-deployment/importer-and-archiver.md b/docs/self-managed/operate-deployment/importer-and-archiver.md
@@ -34,7 +34,7 @@ Each single importer/archiver node must be configured using the following config
 | camunda.operate.clusterNode.nodeCount     | Total amount of Importer (or Archiver) nodes in the cluster.                           | 1                                                   |
 | camunda.operate.clusterNode.currentNodeId | ID of current Importer (or Archiver) node, starting from 0.                            | 0                                                   |
 
-It's enough to configure either `partitionIds` or a pair of `nodeCount` and `currentNodeId`. If you provide `nodeCount` and `currentNodeId`, each node will automatically guess the Zeebe partitions they're responsible for.
+It's enough to configure either `partitionIds` or a pair of `nodeCount` and `currentNodeId`. If you provide `nodeCount` and `currentNodeId`, each node will automatically determine the Zeebe partitions they're responsible for.
 
 :::note
 `nodeCount` always represents the number of nodes of one specific type.

diff --git a/docs/self-managed/tasklist-deployment/importer-and-archiver.md b/docs/self-managed/tasklist-deployment/importer-and-archiver.md
@@ -34,7 +34,7 @@ Each single importer/archiver node must be configured using the following config
 | camunda.tasklist.clusterNode.nodeCount     | Total amount of Importer (or archiver) nodes in the cluster.                           | 1                                                   |
 | camunda.tasklist.clusterNode.currentNodeId | ID of current Importer (or archiver) node, starting from 0.                            | 0                                                   |
 
-It's enough to configure either `partitionIds` or a pair of `nodeCount` and `currentNodeId`. If you provide `nodeCount` and `currentNodeId`, each node will automatically guess the Zeebe partitions they're responsible for.
+It's enough to configure either `partitionIds` or a pair of `nodeCount` and `currentNodeId`. If you provide `nodeCount` and `currentNodeId`, each node will automatically determine the Zeebe partitions they're responsible for.
 
 :::note
 `nodeCount` always represents the number of nodes of one specific type.

diff --git a/...ioned_docs/version-8.3/self-managed/operate-deployment/importer-and-archiver.md b/...ioned_docs/version-8.3/self-managed/operate-deployment/importer-and-archiver.md
@@ -38,7 +38,7 @@ Each single importer/archiver node must be configured using the following config
 | camunda.operate.clusterNode.nodeCount     | Total amount of Importer (or Archiver) nodes in the cluster.                           | 1                                                   |
 | camunda.operate.clusterNode.currentNodeId | Id of current Importer (or Archiver) node, starting from 0.                            | 0                                                   |
 
-It's enough to configure either `partitionIds` or a pair of `nodeCount` and `currentNodeId`. If you provide `nodeCount` and `currentNodeId`, each node will automatically guess the Zeebe partitions they're responsible for.
+It's enough to configure either `partitionIds` or a pair of `nodeCount` and `currentNodeId`. If you provide `nodeCount` and `currentNodeId`, each node will automatically determine the Zeebe partitions they're responsible for.
 
 :::note
 `nodeCount` always represents the number of nodes of one specific type.

diff --git a/...oned_docs/version-8.3/self-managed/tasklist-deployment/importer-and-archiver.md b/...oned_docs/version-8.3/self-managed/tasklist-deployment/importer-and-archiver.md
@@ -38,7 +38,7 @@ Each single importer/archiver node must be configured using the following config
 | camunda.tasklist.clusterNode.nodeCount     | Total amount of Importer (or archiver) nodes in the cluster.                           | 1                                                   |
 | camunda.tasklist.clusterNode.currentNodeId | Id of current Importer (or archiver) node, starting from 0.                            | 0                                                   |
 
-It's enough to configure either `partitionIds` or a pair of `nodeCount` and `currentNodeId`. If you provide `nodeCount` and `currentNodeId`, each node will automatically guess the Zeebe partitions they're responsible for.
+It's enough to configure either `partitionIds` or a pair of `nodeCount` and `currentNodeId`. If you provide `nodeCount` and `currentNodeId`, each node will automatically determine the Zeebe partitions they're responsible for.
 
 :::note
 `nodeCount` always represents the number of nodes of one specific type.

diff --git a/...ioned_docs/version-8.4/self-managed/operate-deployment/importer-and-archiver.md b/...ioned_docs/version-8.4/self-managed/operate-deployment/importer-and-archiver.md
@@ -38,7 +38,7 @@ Each single importer/archiver node must be configured using the following config
 | camunda.operate.clusterNode.nodeCount     | Total amount of Importer (or Archiver) nodes in the cluster.                           | 1                                                   |
 | camunda.operate.clusterNode.currentNodeId | Id of current Importer (or Archiver) node, starting from 0.                            | 0                                                   |
 
-It's enough to configure either `partitionIds` or a pair of `nodeCount` and `currentNodeId`. If you provide `nodeCount` and `currentNodeId`, each node will automatically guess the Zeebe partitions they're responsible for.
+It's enough to configure either `partitionIds` or a pair of `nodeCount` and `currentNodeId`. If you provide `nodeCount` and `currentNodeId`, each node will automatically determine the Zeebe partitions they're responsible for.
 
 :::note
 `nodeCount` always represents the number of nodes of one specific type.

diff --git a/...oned_docs/version-8.4/self-managed/tasklist-deployment/importer-and-archiver.md b/...oned_docs/version-8.4/self-managed/tasklist-deployment/importer-and-archiver.md
@@ -38,7 +38,7 @@ Each single importer/archiver node must be configured using the following config
 | camunda.tasklist.clusterNode.nodeCount     | Total amount of Importer (or archiver) nodes in the cluster.                           | 1                                                   |
 | camunda.tasklist.clusterNode.currentNodeId | Id of current Importer (or archiver) node, starting from 0.                            | 0                                                   |
 
-It's enough to configure either `partitionIds` or a pair of `nodeCount` and `currentNodeId`. If you provide `nodeCount` and `currentNodeId`, each node will automatically guess the Zeebe partitions they're responsible for.
+It's enough to configure either `partitionIds` or a pair of `nodeCount` and `currentNodeId`. If you provide `nodeCount` and `currentNodeId`, each node will automatically determine the Zeebe partitions they're responsible for.
 
 :::note
 `nodeCount` always represents the number of nodes of one specific type.

diff --git a/...ioned_docs/version-8.5/self-managed/operate-deployment/importer-and-archiver.md b/...ioned_docs/version-8.5/self-managed/operate-deployment/importer-and-archiver.md
@@ -38,7 +38,7 @@ Each single importer/archiver node must be configured using the following config
 | camunda.operate.clusterNode.nodeCount     | Total amount of Importer (or Archiver) nodes in the cluster.                           | 1                                                   |
 | camunda.operate.clusterNode.currentNodeId | Id of current Importer (or Archiver) node, starting from 0.                            | 0                                                   |
 
-It's enough to configure either `partitionIds` or a pair of `nodeCount` and `currentNodeId`. If you provide `nodeCount` and `currentNodeId`, each node will automatically guess the Zeebe partitions they're responsible for.
+It's enough to configure either `partitionIds` or a pair of `nodeCount` and `currentNodeId`. If you provide `nodeCount` and `currentNodeId`, each node will automatically determine the Zeebe partitions they're responsible for.
 
 :::note
 `nodeCount` always represents the number of nodes of one specific type.

diff --git a/...oned_docs/version-8.5/self-managed/tasklist-deployment/importer-and-archiver.md b/...oned_docs/version-8.5/self-managed/tasklist-deployment/importer-and-archiver.md
@@ -38,7 +38,7 @@ Each single importer/archiver node must be configured using the following config
 | camunda.tasklist.clusterNode.nodeCount     | Total amount of Importer (or archiver) nodes in the cluster.                           | 1                                                   |
 | camunda.tasklist.clusterNode.currentNodeId | Id of current Importer (or archiver) node, starting from 0.                            | 0                                                   |
 
-It's enough to configure either `partitionIds` or a pair of `nodeCount` and `currentNodeId`. If you provide `nodeCount` and `currentNodeId`, each node will automatically guess the Zeebe partitions they're responsible for.
+It's enough to configure either `partitionIds` or a pair of `nodeCount` and `currentNodeId`. If you provide `nodeCount` and `currentNodeId`, each node will automatically determine the Zeebe partitions they're responsible for.
 
 :::note
 `nodeCount` always represents the number of nodes of one specific type.

diff --git a/...ioned_docs/version-8.6/self-managed/operate-deployment/importer-and-archiver.md b/...ioned_docs/version-8.6/self-managed/operate-deployment/importer-and-archiver.md
@@ -38,7 +38,7 @@ Each single importer/archiver node must be configured using the following config
 | camunda.operate.clusterNode.nodeCount     | Total amount of Importer (or Archiver) nodes in the cluster.                           | 1                                                   |
 | camunda.operate.clusterNode.currentNodeId | ID of current Importer (or Archiver) node, starting from 0.                            | 0                                                   |
 
-It's enough to configure either `partitionIds` or a pair of `nodeCount` and `currentNodeId`. If you provide `nodeCount` and `currentNodeId`, each node will automatically guess the Zeebe partitions they're responsible for.
+It's enough to configure either `partitionIds` or a pair of `nodeCount` and `currentNodeId`. If you provide `nodeCount` and `currentNodeId`, each node will automatically determine the Zeebe partitions they're responsible for.
 
 :::note
 `nodeCount` always represents the number of nodes of one specific type.

diff --git a/...oned_docs/version-8.6/self-managed/tasklist-deployment/importer-and-archiver.md b/...oned_docs/version-8.6/self-managed/tasklist-deployment/importer-and-archiver.md
@@ -38,7 +38,7 @@ Each single importer/archiver node must be configured using the following config
 | camunda.tasklist.clusterNode.nodeCount     | Total amount of Importer (or archiver) nodes in the cluster.                           | 1                                                   |
 | camunda.tasklist.clusterNode.currentNodeId | ID of current Importer (or archiver) node, starting from 0.                            | 0                                                   |
 
-It's enough to configure either `partitionIds` or a pair of `nodeCount` and `currentNodeId`. If you provide `nodeCount` and `currentNodeId`, each node will automatically guess the Zeebe partitions they're responsible for.
+It's enough to configure either `partitionIds` or a pair of `nodeCount` and `currentNodeId`. If you provide `nodeCount` and `currentNodeId`, each node will automatically determine the Zeebe partitions they're responsible for.
 
 :::note
 `nodeCount` always represents the number of nodes of one specific type.

diff --git a/...ioned_docs/version-8.7/self-managed/operate-deployment/importer-and-archiver.md b/...ioned_docs/version-8.7/self-managed/operate-deployment/importer-and-archiver.md
@@ -38,7 +38,7 @@ Each single importer/archiver node must be configured using the following config
 | camunda.operate.clusterNode.nodeCount     | Total amount of Importer (or Archiver) nodes in the cluster.                           | 1                                                   |
 | camunda.operate.clusterNode.currentNodeId | ID of current Importer (or Archiver) node, starting from 0.                            | 0                                                   |
 
-It's enough to configure either `partitionIds` or a pair of `nodeCount` and `currentNodeId`. If you provide `nodeCount` and `currentNodeId`, each node will automatically guess the Zeebe partitions they're responsible for.
+It's enough to configure either `partitionIds` or a pair of `nodeCount` and `currentNodeId`. If you provide `nodeCount` and `currentNodeId`, each node will automatically determine the Zeebe partitions they're responsible for.
 
 :::note
 `nodeCount` always represents the number of nodes of one specific type.

diff --git a/...oned_docs/version-8.7/self-managed/tasklist-deployment/importer-and-archiver.md b/...oned_docs/version-8.7/self-managed/tasklist-deployment/importer-and-archiver.md
@@ -38,7 +38,7 @@ Each single importer/archiver node must be configured using the following config
 | camunda.tasklist.clusterNode.nodeCount     | Total amount of Importer (or archiver) nodes in the cluster.                           | 1                                                   |
 | camunda.tasklist.clusterNode.currentNodeId | ID of current Importer (or archiver) node, starting from 0.                            | 0                                                   |
 
-It's enough to configure either `partitionIds` or a pair of `nodeCount` and `currentNodeId`. If you provide `nodeCount` and `currentNodeId`, each node will automatically guess the Zeebe partitions they're responsible for.
+It's enough to configure either `partitionIds` or a pair of `nodeCount` and `currentNodeId`. If you provide `nodeCount` and `currentNodeId`, each node will automatically determine the Zeebe partitions they're responsible for.
 
 :::note
 `nodeCount` always represents the number of nodes of one specific type.