diff --git a/deploy/display-kiosk.md b/deploy/display-kiosk.md
index eb21adb..1ecd422 100644
--- a/deploy/display-kiosk.md
+++ b/deploy/display-kiosk.md
@@ -97,9 +97,10 @@ is always safer for a browser profile.
 3. Within a few seconds the screen collects its credential and starts showing content.
 4. In Signage → **Displays**, name the display and choose its group and audience.
 
-A paired screen stays paired across browser restarts and reboots. The credential lasts **180 days**
-from pairing and is not renewed automatically (ADR 0036); after that the screen returns to its pairing
-code and is paired again the same way. Note the pairing date of each screen.
+A paired screen stays paired across browser restarts and reboots, and for as long as it is in use:
+its credential is renewed each time it checks in, and only expires after **180 days without being
+used** (ADR 0056). A screen that is switched off and stored for longer than that, or that is revoked,
+returns to its pairing code and is paired again the same way.
 
 ## What happens when things go wrong
 
@@ -124,6 +125,6 @@ reachable — nobody needs to touch it.
 - [ ] One systemd unit, no desktop autostart entry, no second launcher.
 - [ ] `--user-data-dir` on persistent storage, not shared, not cleared on exit.
 - [ ] Automatic login of the kiosk user, and screen blanking/power saving disabled.
-- [ ] Paired and named; assigned in Signage; pairing date recorded.
+- [ ] Paired and named; assigned in Signage.
 - [ ] Unplug the network for a minute: content keeps playing, then the note clears on reconnect.
 - [ ] Reboot: the screen comes back paired without anyone touching it.