更新标题

docs/en_US/guide/agent.md

@@ -2,6 +2,8 @@
 outline: deep
 ---
 
+# Install Agent
+
 **This document will introduce how to install the Agent on the monitored server and connect it to the Dashboard.**  
 ::: tip  
 The repository for Agent binaries can be found at: <https://github.com/nezhahq/agent/releases>

docs/en_US/guide/agentq.md

@@ -2,6 +2,8 @@
 outline: deep
 ---
 
+# Frequently Asked Questions about the Agent
+
 ## The IP Displayed in the Admin Panel is Different from the Actual Agent IP?
 
 Please refer to [Dashboard Related - Why is the IP Displayed in the Admin Panel Different from the Actual Agent IP?](/en_US/guide/dashboardq.html#why-is-the-ip-displayed-in-the-admin-panel-different-from-the-actual-agent-ip). This will not be repeated here.

docs/en_US/guide/api.md

@@ -2,6 +2,8 @@
 outline: deep
 ---
 
+# API Interface
+
 **Nezha Monitoring supports querying the status information of Agents using the API interface**
 
 ## Creating a Token

docs/en_US/guide/dashboard.md

@@ -2,6 +2,8 @@
 outline: deep
 ---
 
+# Install Dashboard
+
 ## Preparation
 
 To set up Nezha Monitoring, you need:

docs/en_US/guide/dashboardq.md

@@ -2,6 +2,8 @@
 outline: deep
 ---
 
+# Frequently Asked Questions about the Dashboard
+
 ## Why is the IP Displayed in the Admin Panel Different from the Actual Agent IP?
 
 First, let's explain how the IP displayed in the Admin panel is obtained: The Agent periodically requests IP-API to get IP information and reports it to the Dashboard. The currently used IP-API can be viewed here: [myip.go](https://github.com/nezhahq/agent/blob/main/pkg/monitor/myip.go).  

docs/en_US/guide/loginq.md

@@ -2,6 +2,8 @@
 outline: deep
 ---
 
+# Frequently Asked Questions about logging into the Dashboard
+
 ## Stuck Page/Connection Refused/Long Response Time After Login Callback
 
 These issues can manifest in various ways, but ultimately the browser cannot display correctly after login.

docs/en_US/guide/notifications.md

@@ -2,6 +2,8 @@
 outline: deep
 ---
 
+# Notification Configuration
+
 Nezha Monitoring supports monitoring server load, CPU, memory, disk, traffic, monthly traffic, process count, and connection count, and sending notifications when user-defined thresholds are reached.
 
 ## Flexible Notification Methods

docs/en_US/guide/q8.md

@@ -1,3 +1,4 @@
+# Cloudflare Access OAuth2 Configuration
 If you encounter issues logging in as an administrator using Github, Gitlab, or Gitee, you may consider switching to Cloudflare Access as the OAuth2 provider.
 
 ## Example Configuration:

docs/en_US/guide/servers.md

@@ -2,7 +2,7 @@
 outline: deep
 ---
 
-# Server
+# Server Management
 
 ## Introduction
 

docs/en_US/guide/services.md

@@ -2,6 +2,8 @@
 outline: deep
 ---
 
+# Service Monitoring
+
 **The Services section is where you set up monitoring for external websites or servers using Agents.**  
 **Configured service monitors can be viewed on the "Services" page of the homepage, displaying the availability monitoring results for the past 30 days.**
 

docs/en_US/guide/settings.md

@@ -2,6 +2,8 @@
 outline: deep
 ---
 
+# Settings
+
 ## Site Title
 
 You can customize the site title in this section.

docs/en_US/guide/tasks.md

@@ -2,6 +2,8 @@
 outline: deep
 ---
 
+# Task Management
+
 **In the Tasks section, you can set up scheduled tasks, trigger tasks, and batch execute tasks on multiple servers.**
 
 Nezha Monitoring supports pushing commands to Agents for execution. This feature is highly flexible and can be used for regular backups using tools like restic or rclone, periodically restarting a service to reset network connections, or executing a task when an notification is triggered, such as running a script when CPU usage is high for an extended period.