From 4b77a8516a83dd3580cdfd8e19154be0b5c98e99 Mon Sep 17 00:00:00 2001 From: Barry Grenon Date: Fri, 13 Dec 2024 17:07:35 -0400 Subject: [PATCH] Update content/docs/manage/api-keys.md Co-authored-by: Daniel <10074684+danieltprice@users.noreply.github.com> --- content/docs/manage/api-keys.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/docs/manage/api-keys.md b/content/docs/manage/api-keys.md index 644fbd201e..e717ab11eb 100644 --- a/content/docs/manage/api-keys.md +++ b/content/docs/manage/api-keys.md @@ -24,7 +24,7 @@ While there is no strict limit on the number of API keys you can create, we reco You'll need to create your first API key from the Neon Console, where you are already authenticated. You can then use that key to generate new keys from the API. -When creating API keys from the Neon Console, the secret token will be displayed only once. Copy it immediately and store it securely in a credential manager (like AWS Key Management Service or Azure Key Vault) - you won't be able to retrieve it later. If you lose an API key, you'll need to revoke it and create a new one. +When creating API keys from the Neon Console, the secret token will be displayed only once. Copy it immediately and store it securely in a credential manager (like AWS Key Management Service or Azure Key Vault) — you won't be able to retrieve it later. If you lose an API key, you'll need to revoke it and create a new one. ### Create a personal API key