From c7e4cb7a175db693115cf18eb5d941974468499b Mon Sep 17 00:00:00 2001 From: Yuan Tang Date: Fri, 11 Jul 2025 11:19:59 -0400 Subject: [PATCH] docs: change "Open AI" to "OpenAI" in upstream-auth.mdx Signed-off-by: Yuan Tang --- site/docs/capabilities/security/upstream-auth.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/site/docs/capabilities/security/upstream-auth.mdx b/site/docs/capabilities/security/upstream-auth.mdx index d82ee6978f..5cf113aee6 100644 --- a/site/docs/capabilities/security/upstream-auth.mdx +++ b/site/docs/capabilities/security/upstream-auth.mdx @@ -64,7 +64,7 @@ Learn more about connecting to [AWS Bedrock](/docs/getting-started/connect-provi For providers that support long lived access credentials, the Envoy AI Gateway control plane supports a manual credential management process. In these cases the credentials, like API keys, are stored in Kubernetes secrets and managed by the AI Gateway administrator. Envoy AI Gateway will use the credentials from the secret to authenticate with the upstream service, attaching them to each request by securely retrieving them from the secret and attaching them to the request. :::info -Learn more about connecting to [Open AI](/docs/getting-started/connect-providers/openai) and adding your API key to the secret. You can use the same approach for other providers that support long lived credentials. +Learn more about connecting to [OpenAI](/docs/getting-started/connect-providers/openai) and adding your API key to the secret. You can use the same approach for other providers that support long lived credentials. ::: ## Conclusion