backport of commit 493a6a1 (#36145)

Co-authored-by: Mark Lewis <lewis@hashicorp.com>

Author: github-actions[bot]

website/docs/language/stacks/reference/tfdeploy.mdx

@@ -163,7 +163,7 @@ The object in the `context.plan.deployment` field includes the following fields.
 
 The `identity_token` block defines a JSON Web Token (JWT) that Terraform generates for a given deployment if that `deployment` block references an `identity_token` in its `inputs`. 
 
-You can directly pass the token generated by the `identity_token` block to a provider's configuration for OIDC authentication. For more information on authenticating a Stack using OIDC, refer to [Authenticate a Stack](/terraform/language/stacks/authenticate).
+You can directly pass the token generated by the `identity_token` block to a provider's configuration for OIDC authentication. For more information on authenticating a Stack using OIDC, refer to [Authenticate a Stack](/terraform/language/stacks/deploy/authenticate).
 
 ### Complete configuration
 
@@ -311,4 +311,4 @@ You can access specific environment variables by key from the `store.varset.avai
 
 ## `locals` block configuration
 
-A local value assigns a name to an expression, so you can use the name multiple times within your Stack configuration instead of repeating the expression. The `locals` block works exactly as it does in traditional Terraform configurations. Learn more about [the `locals` block](/terraform/language/values/locals).
+A local value assigns a name to an expression, so you can use the name multiple times within your Stack configuration instead of repeating the expression. The `locals` block works exactly as it does in traditional Terraform configurations. Learn more about [the `locals` block](/terraform/language/values/locals).