From d91c4c58a158d79ef65bc14fe20c060f5f3ef9c7 Mon Sep 17 00:00:00 2001 From: Cole Isaac <82131455+conceptualshark@users.noreply.github.com> Date: Wed, 5 Mar 2025 15:29:51 -0500 Subject: [PATCH] update usage of guess to determine (#5162) --- docs/self-managed/operate-deployment/importer-and-archiver.md | 2 +- docs/self-managed/tasklist-deployment/importer-and-archiver.md | 2 +- .../self-managed/operate-deployment/importer-and-archiver.md | 2 +- .../self-managed/tasklist-deployment/importer-and-archiver.md | 2 +- .../self-managed/operate-deployment/importer-and-archiver.md | 2 +- .../self-managed/tasklist-deployment/importer-and-archiver.md | 2 +- .../self-managed/operate-deployment/importer-and-archiver.md | 2 +- .../self-managed/tasklist-deployment/importer-and-archiver.md | 2 +- .../self-managed/operate-deployment/importer-and-archiver.md | 2 +- .../self-managed/tasklist-deployment/importer-and-archiver.md | 2 +- .../self-managed/operate-deployment/importer-and-archiver.md | 2 +- .../self-managed/tasklist-deployment/importer-and-archiver.md | 2 +- 12 files changed, 12 insertions(+), 12 deletions(-) diff --git a/docs/self-managed/operate-deployment/importer-and-archiver.md b/docs/self-managed/operate-deployment/importer-and-archiver.md index 17a48be690f..0ccd95c9e10 100644 --- 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 index 3950abebce1..f474df13514 100644 --- 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/versioned_docs/version-8.3/self-managed/operate-deployment/importer-and-archiver.md b/versioned_docs/version-8.3/self-managed/operate-deployment/importer-and-archiver.md index be8ac0605ff..b1679ec32db 100644 --- a/versioned_docs/version-8.3/self-managed/operate-deployment/importer-and-archiver.md +++ b/versioned_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/versioned_docs/version-8.3/self-managed/tasklist-deployment/importer-and-archiver.md b/versioned_docs/version-8.3/self-managed/tasklist-deployment/importer-and-archiver.md index f591e120cf2..f22a9a02341 100644 --- a/versioned_docs/version-8.3/self-managed/tasklist-deployment/importer-and-archiver.md +++ b/versioned_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/versioned_docs/version-8.4/self-managed/operate-deployment/importer-and-archiver.md b/versioned_docs/version-8.4/self-managed/operate-deployment/importer-and-archiver.md index be8ac0605ff..b1679ec32db 100644 --- a/versioned_docs/version-8.4/self-managed/operate-deployment/importer-and-archiver.md +++ b/versioned_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/versioned_docs/version-8.4/self-managed/tasklist-deployment/importer-and-archiver.md b/versioned_docs/version-8.4/self-managed/tasklist-deployment/importer-and-archiver.md index f591e120cf2..f22a9a02341 100644 --- a/versioned_docs/version-8.4/self-managed/tasklist-deployment/importer-and-archiver.md +++ b/versioned_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/versioned_docs/version-8.5/self-managed/operate-deployment/importer-and-archiver.md b/versioned_docs/version-8.5/self-managed/operate-deployment/importer-and-archiver.md index be8ac0605ff..b1679ec32db 100644 --- a/versioned_docs/version-8.5/self-managed/operate-deployment/importer-and-archiver.md +++ b/versioned_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/versioned_docs/version-8.5/self-managed/tasklist-deployment/importer-and-archiver.md b/versioned_docs/version-8.5/self-managed/tasklist-deployment/importer-and-archiver.md index f591e120cf2..f22a9a02341 100644 --- a/versioned_docs/version-8.5/self-managed/tasklist-deployment/importer-and-archiver.md +++ b/versioned_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/versioned_docs/version-8.6/self-managed/operate-deployment/importer-and-archiver.md b/versioned_docs/version-8.6/self-managed/operate-deployment/importer-and-archiver.md index a2108724138..b18833f1942 100644 --- a/versioned_docs/version-8.6/self-managed/operate-deployment/importer-and-archiver.md +++ b/versioned_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/versioned_docs/version-8.6/self-managed/tasklist-deployment/importer-and-archiver.md b/versioned_docs/version-8.6/self-managed/tasklist-deployment/importer-and-archiver.md index 28dd56feb5c..bd4023756aa 100644 --- a/versioned_docs/version-8.6/self-managed/tasklist-deployment/importer-and-archiver.md +++ b/versioned_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/versioned_docs/version-8.7/self-managed/operate-deployment/importer-and-archiver.md b/versioned_docs/version-8.7/self-managed/operate-deployment/importer-and-archiver.md index a2108724138..b18833f1942 100644 --- a/versioned_docs/version-8.7/self-managed/operate-deployment/importer-and-archiver.md +++ b/versioned_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/versioned_docs/version-8.7/self-managed/tasklist-deployment/importer-and-archiver.md b/versioned_docs/version-8.7/self-managed/tasklist-deployment/importer-and-archiver.md index 28dd56feb5c..bd4023756aa 100644 --- a/versioned_docs/version-8.7/self-managed/tasklist-deployment/importer-and-archiver.md +++ b/versioned_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.