From 015f3c5ba28f687cdfdcf78bef534ea8fcdd72cc Mon Sep 17 00:00:00 2001
From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com>
Date: Mon, 17 Nov 2025 08:44:54 +0000
Subject: [PATCH] Fix documentation discrepancy about UI behavior

- Corrected override behavior description in optional-config.md
- Web UI displays database values with warning indicators, not overridden values
- Clarified that overrides take precedence at runtime, not in the UI display

Co-authored-by: kaaax0815 <32197462+kaaax0815@users.noreply.github.com>
---
 docs/content/advanced/config/optional-config.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/content/advanced/config/optional-config.md b/docs/content/advanced/config/optional-config.md
index 436703e1..0bba7b3e 100644
--- a/docs/content/advanced/config/optional-config.md
+++ b/docs/content/advanced/config/optional-config.md
@@ -70,8 +70,8 @@ When these override environment variables are set:
 
 - The specified values will be used at runtime instead of database settings
 - You can still update these fields through the Web UI and they will be saved to the database
-- However, the overridden values from environment variables will always take precedence
-- The Web UI will display the overridden (effective) values
+- However, the overridden values from environment variables will always take precedence at runtime
+- The Web UI will display the database values with warning indicators showing which fields are overridden
 
 These overrides are useful for containerized environments where configuration should be controlled externally.