docs: update config-file behavior after 3.4.0.0.

docs/en/14-reference/01-components/01-taosd.md

@@ -32,7 +32,7 @@ Additional Notes:
 
 1. Method to modify global configuration parameters via SQL: `alter all dnodes 'parameter_name' 'parameter_value';`, Whether the modifications take effect immediately, please refer to the "Dynamic Modification" description for each parameter.
 2. Method to modify local configuration parameters via SQL: `alter dnode <dnode_id> 'parameter_name' 'parameter_value';`, Whether the modifications take effect immediately, please refer to the "Dynamic Modification" description for each parameter.
-3. From 3.4.0.0, to prevent configuration file tampering, the `forceReadConfig` parameter has been removed. Except for the first startup, configuration will not be loaded from the configuration file.
+3. From 3.4.0.0, to prevent configuration file tampering, the `forceReadConfig` parameter has been removed. Except for the first startup, configuration items will not be loaded from the configuration file. If you need to modify configuration parameters, use the `ALTER` command and modify them via SQL.
 4. For dynamic modification methods of configuration parameters, please refer to [Node Management](../../sql-manual/manage-nodes/).
 5. Some parameters exist in both the client (taosc) and server (taosd), with different scopes and meanings in different contexts. For details, please refer to [TDengine Configuration Parameter Scope Comparison](../../components/configuration-scope/).
 
@@ -362,7 +362,7 @@ The effective value of charset is UTF-8.
 | -------------------- | ----------------- | -------------------------------- | ------------------------------------------------------------ |
 | enableCoreFile       |                   | Supported, effective immediately | Whether to generate a core file when crashing, 0: do not generate, 1: generate; default value is 1 |
 | configDir            |                   | Not supported                    | Directory where the configuration files are located          |
-| forceReadConfig        | After 3.3.5.0, Before 3.4.0.0      | Not supported                                                | Force read configuration file; default value false |
+| forceReadConfig        | After 3.3.5.0, Before 3.4.0.0      | Not supported                                                | Whether to use persisted local configuration parameters: modifying configuration parameters via the configuration file has been deprecated since v3.4.0.0. For v3.4.0.0 and later, please modify configuration parameters via SQL. |
 | scriptDir            |                   | Not supported                    | Directory for internal test tool scripts                     |
 | assert               |                   | Not supported                    | Assertion control switch, default value is 0                 |
 | randErrorChance      |                   | Supported, effective immediately | Internal parameter, used for random failure testing          |

docs/en/27-train-faq/index.md

@@ -356,35 +356,17 @@ Directly querying from child table is fast. The query from super table with TAG
 
 Currently, TDengine only provides compression ratios based on tables, not databases or the entire system. To view the compression ratios, execute the `SHOW TABLE DISTRIBUTED table_name;` command in the client TDengine CLI. The table_name can be a super table, regular table, or subtable. For details, see [SHOW TABLE DISTRIBUTED](https://docs.tdengine.com/tdengine-reference/sql-manual/show-commands/#show-table-distributed).
 
-### 37. Why didn't my configuration parameter take effect even though I modified the configuration file?
+### 37. I modified the configuration file, but the parameters didn't take effect. Why?
 
 #### Problem Description
 
-In TDengine versions 3.3.5.0 and above, some users might encounter an issue: they modify a configuration parameter in `taos.cfg`, but after restarting, the parameter doesn't seem to take effect, and no errors are found in the logs.
+In TDengine TSDB 3.4.0.0 and later, some users may encounter this: they change a parameter in `taos.cfg`, but after restarting, the change does not take effect, and no errors appear in the logs.
 
 #### Problem Reason
 
-This is because TDengine versions 3.3.5.0 and above support persisting dynamically modified configuration parameters. This means that parameters you change dynamically using the `ALTER` command will remain effective even after a restart. Therefore, when restarting, TDengine versions 3.3.5.0 and above will, by default, load configuration parameters (except for `dataDir` itself) from the `dataDir`, rather than using the parameters configured in `taos.cfg`.
+In TDengine TSDB 3.4.0.0 and later, to improve security and prevent configuration file tampering, configuration can no longer be changed by editing the configuration file. Use the `ALTER` command and change parameter values via SQL instead.
 
-#### Problem Solution
-
-If you understand the feature of persistent configuration parameters but still wish to load configuration parameters from the configuration file upon restart, you can add `forceReadConfig 1` to the configuration file. This will force TDengine to read configuration parameters from the file.
-
-### 38. I have clearly modified the configuration file, but the configuration parameters haven't taken effect
-
-#### Problem description
-
-In TDengine versions 3.3.5.0 and above, some users may encounter an issue: they have clearly modified a certain configuration parameter in the taos.cfg file, but after restarting, they find that the modification has not taken effect, and no error reports can be found when checking the logs.
-
-#### Cause of the problem
-
-This is because TDengine versions 3.3.5.0 and above support the persistence of dynamically modified configuration parameters. That is, the parameters dynamically modified through ALTER will still be effective after a restart. Therefore, in TDengine versions 3.3.5.0 and above, when restarting, it will by default load the configuration parameters (except for dataDir) from dataDir, and will not use the configuration parameters in the taos.cfg file.
-
-#### Solution to the problem
-
-If you understand the function of configuration parameter persistence but still want to load the configuration parameters from the configuration file after a restart, you can add forceReadConfig 1 to the configuration file. This will make TDengine forcefully read the configuration parameters from the configuration file.
-
-### 39. Database upgrade from version 2.6 to 3.3, When data migration is carried out and data is being written in the business at the same time, will there be serious out-of-order issues?
+### 38. Database upgrade from version 2.6 to 3.3, When data migration is carried out and data is being written in the business at the same time, will there be serious out-of-order issues?
 
 In this situation, out-of-order issues generally won't occur. First, let's explain what out-of-order means in TDengine. In TDengine, out-of-order refers to the situation where, starting from a timestamp of 0, time windows are cut according to the Duration parameter set in the database (the default is 10 days). The out-of-order phenomenon occurs when the data written in each time window is not written in chronological order. As long as the data written in the same window is in order, even if the writing between windows is not sequential, there will be no out-of-order situation.
 

docs/zh/14-reference/01-components/01-taosd.md

@@ -34,7 +34,7 @@ taosd 命令行参数如下：
 
 1. 通过 SQL 修改全局配置参数命令：`alter all dnodes ‘参数名’ ‘参数值’;`，修改后是否立即生效请参考各参数**动态修改**说明。
 2. 通过 SQL 修改局部配置参数命令，`alter dnode <dnode_id> ‘参数名’ ‘参数值’;`，修改后是否立即生效请参考各参数**动态修改**说明。
-3. 自 3.4.0.0 起，为防止配置文件被篡改，我们取消了 `forceReadConfig` 参数；除首次启动外，不再从配置文件中加载配置项。
+3. 自 3.4.0.0 起，为防止配置文件被篡改，我们取消了 `forceReadConfig` 参数；除首次启动外，不再从配置文件中加载配置项，如果需要修改配置参数，请您使用 ALTER 命令，通过 SQL 的方式修改配置参数的值。。
 4. 配置参数动态修改方法更多请您参考 [节点管理](../../taos-sql/node/)。
 5. 有些参数在客户端 (taosc) 和服务器端 (taosd) 中都有，在不同地方其作用范围和意义有所不同，详细请参考 [TDengine 配置参数作用范围对比](../../components/config-scope)。
 
@@ -2197,7 +2197,7 @@ charset 的有效值是 UTF-8。
 
 #### forceReadConfig
 
-- 说明：是否使用持久化的局部配置参数
+- 说明：是否使用持久化的局部配置参数，改配置参数从 v3.4.0.0 废弃，v3.4.0.0 之后请通过 SQL 修改配置参数。
 - 类型：整数；0：使用持久化的局部配置参数，1：使用配置文件中的局部配置参数。
 - 默认值：0
 - 最小值：0