Skip to content

Agent Mesh

docs: a node trusts the key in a rotation event at once

Tomas Tormo3cf1ac612cbc
diff --git a/site/content/docs/concepts/identity.md b/site/content/docs/concepts/identity.md
index 1b530592..a13fb837 100644
--- a/site/content/docs/concepts/identity.md
+++ b/site/content/docs/concepts/identity.md
@@ -225,9 +225,9 @@ until every credential that key signed has expired. `GET /keys`
returns the current set of keys, signed by each key in the set. Routers and
nodes fetch it at enrollment and then every `--control-plane-sync-interval`,
together with the ban set and the mesh policy. Nodes also pull the revocation
-list and their egress assignments. A rotation event only brings the next pull
-forward. Both
-accept a new set only if one of its signatures verifies under a key they
+list and their egress assignments. A rotation event brings the next pull
+forward. A node also trusts the event's `new_public_key` at once. Routers and
+nodes accept a new set only if one of its signatures verifies under a key they
already trust. The first key comes from enrollment, and each later key is
vouched for by the key it replaces.