AlinsRan commented on code in PR #12214:
URL: https://github.com/apache/apisix/pull/12214#discussion_r2096667082


##########
docs/en/latest/deployment-modes.md:
##########
@@ -115,73 +115,162 @@ This method is more suitable for two types of users:
 
 Now, we have two standalone running modes, file-driven and API-driven.
 
-1. The file-driven mode is the kind APISIX has always supported.
+#### File-driven
 
-    The routing rules in the `conf/apisix.yaml` file are loaded into memory 
immediately after the APISIX node service starts. At each interval (default: 1 
second), APISIX checks for updates to the file. If changes are detected, it 
reloads the rules.
+The file-driven mode is the kind APISIX has always supported.
 
-    *Note*: Reloading and updating routing rules are all hot memory updates. 
There is no replacement of working processes, since it's a hot update.
+The routing rules in the `conf/apisix.yaml` file are loaded into memory 
immediately after the APISIX node service starts. At each interval (default: 1 
second), APISIX checks for updates to the file. If changes are detected, it 
reloads the rules.
 
-    This requires us to set the APISIX role to data plane. That is, set 
`deployment.role` to `data_plane` and 
`deployment.role_data_plane.config_provider` to `yaml`.
+*Note*: Reloading and updating routing rules are all hot memory updates. There 
is no replacement of working processes, since it's a hot update.
 
-    Refer to the example below:
+This requires us to set the APISIX role to data plane. That is, set 
`deployment.role` to `data_plane` and 
`deployment.role_data_plane.config_provider` to `yaml`.
 
-    ```yaml
-    deployment:
-      role: data_plane
-      role_data_plane:
-        config_provider: yaml
-    #END
-    ```
+Refer to the example below:
 
-    This makes it possible to disable the Admin API and discover configuration 
changes and reloads based on the local file system.
+```yaml
+deployment:
+  role: data_plane
+  role_data_plane:
+    config_provider: yaml
+```
 
-2. The API-driven is an emerging paradigm for standalone.
+This makes it possible to disable the Admin API and discover configuration 
changes and reloads based on the local file system.
 
-    The routing rules will be entirely in memory and not in a file, and it 
will need to be updated using the dedicated Standalone Admin API.
+#### API-driven (Experimental)

Review Comment:
   done.



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@apisix.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to