diff --git a/control-plane/connect-sidecar.mdx b/control-plane/connect-sidecar.mdx
index 5764169..8c332bb 100644
--- a/control-plane/connect-sidecar.mdx
+++ b/control-plane/connect-sidecar.mdx
@@ -59,7 +59,7 @@ Four properties fall out of this shape, and they are the reason it looks like th
     hoop start sidecar --config config.yaml --token "<the token you copied>"
     ```
 
-    Listeners still come from the local file. Everything the Control Plane manages — guardrails, masking, analyzer settings — arrives over the ping.
+    The first handshake uploads this whole file. Everything the Control Plane manages — listeners, guardrails, masking, analyzer settings — arrives over the ping.
   </Step>
   <Step title="Confirm what it resolved">
     The admin API reports the merged, live configuration. This is the only place you can see what the Sidecar actually ended up running:
@@ -83,6 +83,7 @@ Four properties fall out of this shape, and they are the reason it looks like th
 | It appears, but runs no managed guardrails | Read `/config` on the admin API. A Sidecar that could not fetch falls back to its local file. |
 | Authentication fails | The token is per-Sidecar. Reusing one across two Sidecars is not a supported shape. |
 | Rules changed centrally but the Sidecar did not | Configuration is picked up on the ping, not pushed. Wait for the next interval or restart the Sidecar. |
+| My listeners never reached the Control Plane | It already had a configuration for this Sidecar, so it kept that one. Edit the listeners there. |
 
 ---