From 91082ff17d0892e40294e52fe9678e4d23e107f1 Mon Sep 17 00:00:00 2001 From: sal rashid Date: Wed, 4 Mar 2026 16:20:19 -0500 Subject: [PATCH] fix typo from pr416 Signed-off-by: sal rashid --- content/en/cosign/signing/overview.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/content/en/cosign/signing/overview.md b/content/en/cosign/signing/overview.md index 503a1d7b..7258e9af 100644 --- a/content/en/cosign/signing/overview.md +++ b/content/en/cosign/signing/overview.md @@ -74,7 +74,8 @@ $ cosign sign --identity-token=$( gcr.io/user-vmtest2/demo ``` -On Google Cloud Build, the standard identity tokens endpoint is also available thorugh its metadata server as described [here](https://docs.cloud.google.com/build/docs/securing-builds/authorize-service-to-service-access). +On Google Cloud Build, the standard identity tokens endpoint is also available through its metadata server as described [here](https://docs.cloud.google.com/build/docs/securing-builds/authorize-service-to-service-access). + ## Custom infrastructure If you're running your own Sigstore services flags are available to set your own endpoint's, e.g