Name the safe order of taking shares into use without the retired word

2026-10-08 20:22:05 +02:00
parent bffd0f90d0
commit d05c9d7ca4
2 changed files with 2 additions and 2 deletions
@@ -153,7 +153,7 @@ Rejected:
  source leaves no failed unit.
 - **Not built yet:** a probe in the controller's self-check that counts fstab lines of type `nfs` or
  `cifs` on every node through `mounts_list`, and reports any that are not adopted.
- Until both exist, the modules' own tests and the safe rollout in design 52 are the check.
+- Until both exist, the modules' own tests and taking it into use safely, as design 52 §5 orders it, are the check.

 ## References

@@ -166,7 +166,7 @@ Each says the share, the node and since when: *"The home server's share `library
 from the workstation since 19:21."* An absent occasional source raises nothing; `mounts_list` says
 *"the share `retro-games` is not present since 18:02"*.

-## 5. The safe rollout
+## 5. Taking it into use, safely

 Read-only first, one node first, and every step checked before the next. Each step names how it is
 undone. Every `adopt` is a person's act. Nothing here touches the library's files, owners or modes, or