Skip to content

Agent Mesh

docs: a bootstrap token is not single-use

Tomas Tormo0d303c989227
diff --git a/README.md b/README.md
index 8fb604fa..d367c95a 100644
--- a/README.md
+++ b/README.md
@@ -19,7 +19,7 @@ Two properties hold everywhere:
configuration says so, and no node may call a service the mesh policy has
not granted. Grants are evaluated on service names, never on addresses.
- **Identity comes from your identity provider.** A node enrolls with an
- OpenID Connect token or a one-time bootstrap token, and the control plane
+ OpenID Connect token or a bootstrap token, and the control plane
turns that into a short-lived, offline-verifiable credential bound to the
node's own key.
diff --git a/site/content/docs/_index.md b/site/content/docs/_index.md
index 1a65b167..3937dc4d 100644
--- a/site/content/docs/_index.md
+++ b/site/content/docs/_index.md
@@ -27,7 +27,7 @@ Two rules apply to every mesh:
configure one, and a node cannot call a service unless the mesh policy
grants it. Policy is written in terms of service names, not IP addresses.
- **Identity comes from your identity provider.** A node enrolls with an
- OpenID Connect token or with a one-time bootstrap token. The control plane
+ OpenID Connect token or with a bootstrap token. The control plane
turns that into a short-lived credential
([Biscuit](https://www.biscuitsec.org/)) that is bound to the node's own
key and that any node can verify offline.