From 08074807cc39240d8e08980a25e0a8dd12de1505 Mon Sep 17 00:00:00 2001 From: iris Date: Wed, 9 Sep 2026 15:55:40 +0200 Subject: [PATCH] docs: fix a Contractions + Passive regression in setup.md cc8fb0ee44191621bd09fcc2b6b5eddcc07bc4b3 (swarm-bao controller-write-credentials work) added a fresh 'did not' warning callout in the bao-provision section, right after #4129 zeroed out the genuine error-level Microsoft.Contractions backlog, and its passive 'has been exercised' phrasing put getting-started/ back above its documented Passive-pass accepted-residual baseline (10) too. Contracted the 'did not' and reworded the passive opener to an active one ('This has only run once...') in the same sentence, since both hits were on the same line. --- docs/getting-started/setup.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/getting-started/setup.md b/docs/getting-started/setup.md index a81b4d07..4bcf9446 100644 --- a/docs/getting-started/setup.md +++ b/docs/getting-started/setup.md @@ -94,7 +94,7 @@ Put the token's value at `services.hyperhive.deploy.bao.bootstrapTokenFile` store's container reads it, writes the `swarm-controller` policy, enables the cert auth method, and creates the `swarm-controller` role that attaches the two. -⚠️ **This has been exercised once, and it did not go all the way through.** The +⚠️ **This has only run once, and it didn't go all the way through.** The first real provision against a live store returned 403 (hyperhive#4124), so treat the block above as derived-then-partly-tested rather than proven: the grants still come from `-output-policy`, not from a swarm that came up on them.