diff --git a/sql-plan-management.md b/sql-plan-management.md
index 7b8dafbcc7f8b..b3d76f876c09f 100644
--- a/sql-plan-management.md
+++ b/sql-plan-management.md
@@ -258,7 +258,7 @@ The default value of `tidb_evolve_plan_baselines` is `off`.
 
 > **Warning:**
 >
-> + Baseline evolution is an experimental feature. Unknown risks exist. It is **NOT** recommended that you use it in the production environment.
+> + Baseline evolution is an experimental feature. Unknown risks might exist. It is **NOT** recommended that you use it in the production environment.
 > This variable is forcibly set to `off` until the baseline evolution feature becomes generally available (GA). If you try to enable this feature, an error is returned. If you have already used this feature in a production environment, disable it as soon as possible. If you find that the binding status is not as expected, contact PingCAP's technical support for help.
 
 After the automatic binding evolution feature is enabled, if the optimal execution plan selected by the optimizer is not among the binding execution plans, the optimizer marks the plan as an execution plan that waits for verification. At every `bind-info-lease` (the default value is `3s`) interval, an execution plan to be verified is selected and compared with the binding execution plan that has the least cost in terms of the actual execution time. If the plan to be verified has shorter execution time (the current criterion for the comparison is that the execution time of the plan to be verified is no longer than 2/3 that of the binding execution plan), this plan is marked as a usable binding. The following example describes the process above.