update site doc to link consumer plugin section in consumer.md (#722)

Co-authored-by: shimeng <[email protected]>

site/content/en/docs/concept/consumer.md

@@ -82,7 +82,7 @@ spec:
 
 Without the Consumer layer of abstraction, each route would have to be configured with `key: Leo`. Imagine one day, for example, `Leo` is just a temporary user and we need to revoke their permissions. With the Consumer, we would only need to delete the consumer `Leo`, without any need to alter the route configurations.
 
-[Consumer plugins](../developer-guide/plugin_development.md) can be configured within the `auth` field of a Consumer. There are two types of configurations for each Consumer plugin: one is set on the Route, which specifies the source of authentication parameters, such as the `keys` in the previously mentioned FilterPolicy. The second type is configured on the Consumer, which determines the matching authentication parameters for that specific Consumer, as exemplified by the `key` in the above Consumer.
+[Consumer plugins](../developer-guide/plugin_development.md#consumer-plugins) can be configured within the `auth` field of a Consumer. There are two types of configurations for each Consumer plugin: one is set on the Route, which specifies the source of authentication parameters, such as the `keys` in the previously mentioned FilterPolicy. The second type is configured on the Consumer, which determines the matching authentication parameters for that specific Consumer, as exemplified by the `key` in the above Consumer.
 
 Each Consumer plugin configured on the Route will proceed through the following steps:
 

site/content/zh-hans/docs/concept/consumer.md

@@ -82,7 +82,7 @@ spec:
 
 如果没有消费者这一层抽象，那么每个路由都需要配置 `key: Leo`。假设有一天，比如说 `Leo` 只是个临时用户，我们需要回收权限。在有消费者的情况下，我们只需删除消费者 `Leo`，无需改动任何路由配置。
 
-我们可以在消费者的 `auth` 字段下配置[消费者插件](../developer-guide/plugin_development.md)。每种消费者插件都会有两种配置：一种配置在路由上，负责指定认证参数的来源，比如上面的 FilterPolicy 的 `keys`。另一种配置在消费者上，负责指定怎样的认证参数匹配到所在的消费者，比如上面的 Consumer 的 `key`。
+我们可以在消费者的 `auth` 字段下配置[消费者插件](../developer-guide/plugin_development.md#消费者插件)。每种消费者插件都会有两种配置：一种配置在路由上，负责指定认证参数的来源，比如上面的 FilterPolicy 的 `keys`。另一种配置在消费者上，负责指定怎样的认证参数匹配到所在的消费者，比如上面的 Consumer 的 `key`。
 
 路由上配置的每个消费者插件，都会执行下面的步骤：