make the content more precise

Author: guowenatk

platform/configure/config.mdx

@@ -310,23 +310,15 @@ helm upgrade $RELEASE_NAME vcluster-platform \
 ```
 ### Multiple agent replicas deployment
 
-For high availability and scalability, the platform agent can be deployed with multiple replicas. However, certain agent tasks must be executed by only one pod 
+For high availability and scalability, the platform agent can be [deployed with multiple replicas](../configure/high-availability). However, certain agent tasks must be executed by only one pod 
 at a time to prevent duplicate actions, race conditions, or data corruption. Other tasks, such as concurrent background processing, can safely run in parallel 
 across replicas.
 
-#### Leader election
-
-Before scaling the platform agent beyond a single replica, you must enable leader election. This ensures that only one pod performs “singleton” tasks while 
+Thus, by default, the leader election is enabled when [installing vCluster through Helm](../../install/helm) or [using vCluster CLI](../../install/quick-start-guide). 
+This ensures that only one pod performs “singleton” tasks while 
 others act as standby or worker agents. Without leader election, multiple pods may perform the same critical operation, leading to inconsistent or 
 conflicting results.
 
-#### Recommended operational practices
-- Enable leader election prior to scaling the agent above one replica.
-- For sensitive operations (e.g., storage migrations or major version upgrades), temporarily scale the agent to a single replica, complete and validate the operation, then scale back up with leader election enabled.
-
-The agent is deployed and managed as a Helm release when the platform connects to a cluster. Configure replicas and leader election settings through Helm values, 
-not manual scaling, to ensure consistent configuration and reliable leader election.
-
 :::warning Avoid manual scaling of agent replicas
 Do not manually scale Deployment replicas outside of Helm. Doing so can start extra pods without the expected flags or config, resulting in no leader 
 being elected, race conditions, or duplicate execution of singleton activities.