From c948ec09af9ffd0f0af5facfab4a4444df2a24fb Mon Sep 17 00:00:00 2001
From: Robert <17119716+robmonte@users.noreply.github.com>
Date: Wed, 16 Jul 2025 13:20:32 -0500
Subject: [PATCH] Fix gcp auth trust relationship requirements block (#31293)

---
 website/content/docs/auth/gcp.mdx | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/website/content/docs/auth/gcp.mdx b/website/content/docs/auth/gcp.mdx
index 6b4b82c33d..70acc2dfe1 100644
--- a/website/content/docs/auth/gcp.mdx
+++ b/website/content/docs/auth/gcp.mdx
@@ -122,13 +122,13 @@ management tool.
    [federated access token](https://cloud.google.com/docs/authentication/token-types#access).
 
    To configure a trusted relationship between Vault and GCP:
-       - You must configure the [identity token issuer backend](/vault/api-docs/secret/identity/tokens#configure-the-identity-tokens-backend)
-         for Vault.
-       - GCP must have a
-         [workload identity pool and provider](https://cloud.google.com/iam/docs/manage-workload-identity-pools-providers)
-         configured with information about the fully qualified and network-reachable
-         issuer URL for the Vault plugin's
-         [identity token provider](/vault/api-docs/secret/identity/tokens#read-plugin-identity-well-known-configurations).
+   - You must configure the [identity token issuer backend](/vault/api-docs/secret/identity/tokens#configure-the-identity-tokens-backend)
+   for Vault.
+   - GCP must have a
+   [workload identity pool and provider](https://cloud.google.com/iam/docs/manage-workload-identity-pools-providers)
+   configured with information about the fully qualified and network-reachable
+   issuer URL for the Vault plugin's
+   [identity token provider](/vault/api-docs/secret/identity/tokens#read-plugin-identity-well-known-configurations).
 
    Establishing a trusted relationship between Vault and GCP ensures that GCP
    can fetch JWKS