docs: reword the set-key note without passive voice
This commit is contained in:
parent
2370f99229
commit
119e225c17
1 changed files with 2 additions and 2 deletions
|
|
@ -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
|
||||
|
|
|
|||
Loading…
Reference in a new issue