diff --git a/README.md b/README.md
index 060f12d..4f6b0e5 100644
--- a/README.md
+++ b/README.md
@@ -369,7 +369,10 @@ line again resets the task to plain `Vista.exe`: point it back at the script aft
 ## ProPresenter guard (every location with ProPresenter on the Companion Mac)
 
 `prop_guard.py` (LaunchAgent `org.waterschurch.prop-guard`, log `~/Library/Logs/prop-guard.log`) is started by
-`install.sh` on any Mac with `/Applications/ProPresenter*.app`: today SC and WS, and AB with its next package. When a
+`install.sh` on any Mac with `/Applications/ProPresenter*.app`: today SC and WS, and AB with its next package. NA's
+ProPresenter is not on the Companion Mac: its guard was copied by hand (na-propresenter-mac, cfg
+`{"stage_screen": "Stage Screen", "api": "http://127.0.0.1:1025"}`; to update it, copy `prop_guard.py` there and
+`launchctl kickstart -k gui/$(id -u)/org.waterschurch.prop-guard`). When a
 song (a presentation with a timeline) comes up and its first slide's macro left the **Stage Display** screen (else the
 first stage screen) on a layout without "Worship" in its name, it is set to **Worship** within 12 s; later picks are left
 alone, and so is a song that was already up when the guard started. ProPresenter's network port differs per Mac