[GitHub] [apisix] tokers commented on a change in pull request #3680: docs: plugin-develop.md add to view all plugin priorities

[GitBox <gi...@apache.org>]

tokers commented on a change in pull request #3680:
URL: https://github.com/apache/apisix/pull/3680#discussion_r584013961



##########
File path: docs/en/latest/plugin-develop.md
##########
@@ -103,7 +103,7 @@ local _M = {
 }
 ```
 
-Note : The priority of the new plugin cannot be the same as the priority of any existing plugin. In addition, plugins with a high priority value will be executed first in a given phase (see the definition of `phase` in [choose-phase-to-run](#choose-phase-to-run)). For example, the priority of example-plugin is 0 and the priority of ip-restriction is 3000. Therefore, the ip-restriction plugin will be executed first, then the example-plugin plugin.
+Note : The priority of the new plugin cannot be the same as the priority of any existing plugin, you can use the `/v1/schema` method of [control API](./control-api.md) to view the priority of all plugins. In addition, plugins with a high priority value will be executed first in a given phase (see the definition of `phase` in [choose-phase-to-run](#choose-phase-to-run)). For example, the priority of example-plugin is 0 and the priority of ip-restriction is 3000. Therefore, the ip-restriction plugin will be executed first, then the example-plugin plugin.

Review comment:
       Some typos.
   
   > The priority of the new plugin cannot be the same as the priority of any existing plugin
   
   Change to "The priority of the new plugin cannot be same to any existing ones".
   
   > plugins with a high priority
   
   Change to "plugins with higher priority".




----------------------------------------------------------------
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.

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