From 5e902ca255b434207b7ed7d1cc9022052efd94c4 Mon Sep 17 00:00:00 2001
From: Dmitry Ng <19asdek91@gmail.com>
Date: Fri, 24 Apr 2026 03:00:48 +0300
Subject: [PATCH] docs: update API tokens section to reflect new naming
 convention in settings

---
 README.md              | 2 +-
 backend/docs/config.md | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index 54bf1cb3..5714d768 100644
--- a/README.md
+++ b/README.md
@@ -639,7 +639,7 @@ The PentAGI web console already manages several settings areas after the server
 
 - **Settings -> Providers**: Create, edit, delete, and test user-defined provider profiles for supported provider types. These profiles control per-agent model selection, runtime parameters, reasoning options, and pricing metadata.
 - **Settings -> Prompts**: Manage system, human, and tool prompt templates.
-- **Settings -> API Tokens**: Create and manage PentAGI Bearer tokens for REST and GraphQL access.
+- **Settings -> PentAGI API**: Create and manage PentAGI Bearer tokens for REST and GraphQL access.
 - **Other UI-managed preferences**: Favorite flows are stored as user preferences, and theme selection is handled from the main sidebar/profile controls rather than the Settings pages.
 
 ### Still Server-Managed
diff --git a/backend/docs/config.md b/backend/docs/config.md
index 7d1ac8fe..378f635d 100644
--- a/backend/docs/config.md
+++ b/backend/docs/config.md
@@ -109,7 +109,7 @@ The running PentAGI instance already exposes several settings areas in the web U
 
 - **Settings -> Providers**: Manage user-defined provider profiles, per-agent model and runtime options, and provider test actions for provider types supported by the running server.
 - **Settings -> Prompts**: Manage system, human, and tool prompt templates.
-- **Settings -> API Tokens**: Create, revoke, and delete PentAGI API tokens.
+- **Settings -> PentAGI API**: Create, revoke, and delete PentAGI API tokens.
 - **Other UI-managed preferences**: Favorite flows are stored as user preferences, and theme selection is handled client-side from the main sidebar/profile controls.
 
 These web-console features do not replace the environment variables in this guide for provider credentials, endpoints, or external integrations.