From 4e66cfda9044567db97e4874169d9709adf4e9d6 Mon Sep 17 00:00:00 2001 From: Travis Leeden Date: Wed, 18 Dec 2024 11:02:52 +1000 Subject: [PATCH] slight wording change --- .../docs/infrastructure/deployment-targets/machine-policies.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/pages/docs/infrastructure/deployment-targets/machine-policies.mdx b/src/pages/docs/infrastructure/deployment-targets/machine-policies.mdx index 65ef18ec4..1e2b4c1ce 100644 --- a/src/pages/docs/infrastructure/deployment-targets/machine-policies.mdx +++ b/src/pages/docs/infrastructure/deployment-targets/machine-policies.mdx @@ -238,7 +238,7 @@ For example you have the following configuration: In this scenario only a maximum of 2 retries could be attempted before reaching the time limit. ### Polling request queue timeout -This setting controls how long Octopus Deploy will wait before cancelling a task in a polling Tentacle's queue. For more details on what the Polling Tentacle queue is see the doc on [Tentacle communication modes](/docs/infrastructure/deployment-targets/tentacle/tentacle-communication#polling-tentacles) +This setting controls how long Octopus Deploy will wait before cancelling a task in a polling Tentacle's queue. For more details on what the Polling Tentacle queue is see the documentation on [Tentacle communication modes](/docs/infrastructure/deployment-targets/tentacle/tentacle-communication#polling-tentacles) :::figure ![](/docs/infrastructure/deployment-targets/machine-policies/machine-policies-connectivity-polling-queue.png) :::