From 119e225c17cbdb6d3fcd4dae83e76a40d27de0eb Mon Sep 17 00:00:00 2001 From: iris Date: Wed, 11 Nov 2026 18:34:40 +0100 Subject: [PATCH] docs: reword the set-key note without passive voice --- docs/2-handbook/swarm/services.md | 2 +- docs/4-implementation/swarm/review-classifier.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/2-handbook/swarm/services.md b/docs/2-handbook/swarm/services.md index 347f64087..e67789a66 100644 --- a/docs/2-handbook/swarm/services.md +++ b/docs/2-handbook/swarm/services.md @@ -353,7 +353,7 @@ below). Set `deploy.review-classifier.enable` directly to override either way. The operator sets the key of the runtime the swarm settings choose in the swarm UI: the **classifier settings** card on `/jobs` takes a key for the chosen runtime and shows whether one exists and when it changed, never the -key. "Set" means a key was written, not that it works: a run with a bad key +key. "Set" means a key exists, not that it works: a run with a bad key still fails. You can also write the same two keys in the secret store's UI under the OIDC login, field `api_key`: diff --git a/docs/4-implementation/swarm/review-classifier.md b/docs/4-implementation/swarm/review-classifier.md index 305c3b56f..8a73b4b89 100644 --- a/docs/4-implementation/swarm/review-classifier.md +++ b/docs/4-implementation/swarm/review-classifier.md @@ -310,7 +310,7 @@ a runtime that isn't one of the two or a refused key, **401** for no `Remote-User`, **503** when the store is unreachable or refuses. `set` means the leaf's metadata exists. It doesn't mean the key works: a leaf -written by hand under another field name, or one whose latest version was +written by hand under another field name, or one with its latest version deleted, still shows as set, because the controller can't read a value to check. The classifier reads the leaf on every run, so a new key applies from the next