This is an automated email from the ASF dual-hosted git repository.
Yilialinn pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/apisix.git
The following commit(s) were added to refs/heads/master by this push:
new d336d7d008 docs: fix broken anchor links (#14027)
d336d7d008 is described below
commit d336d7d008e2c3d93013c5cfdecf6aa2d873d869
Author: Satvik Mishra <[email protected]>
AuthorDate: Tue Nov 10 11:59:52 2026 +0530
docs: fix broken anchor links (#14027)
---
docs/en/latest/admin-api.md | 6 +++---
docs/en/latest/apisix-variable.md | 2 +-
docs/en/latest/discovery/eureka.md | 2 +-
docs/en/latest/plugins/clickhouse-logger.md | 2 +-
docs/en/latest/plugins/datadog.md | 2 +-
docs/en/latest/plugins/elasticsearch-logger.md | 2 +-
docs/en/latest/plugins/error-log-logger.md | 2 +-
docs/en/latest/plugins/google-cloud-logging.md | 2 +-
docs/en/latest/plugins/http-logger.md | 2 +-
docs/en/latest/plugins/kafka-logger.md | 2 +-
docs/en/latest/plugins/lago.md | 2 +-
docs/en/latest/plugins/loggly.md | 2 +-
docs/en/latest/plugins/loki-logger.md | 2 +-
docs/en/latest/plugins/openid-connect.md | 2 +-
docs/en/latest/plugins/proxy-cache.md | 2 +-
docs/en/latest/plugins/serverless.md | 2 +-
docs/en/latest/plugins/skywalking-logger.md | 2 +-
docs/en/latest/plugins/sls-logger.md | 2 +-
docs/en/latest/plugins/splunk-hec-logging.md | 2 +-
docs/en/latest/plugins/syslog.md | 2 +-
docs/en/latest/plugins/tcp-logger.md | 2 +-
docs/en/latest/plugins/tencent-cloud-cls.md | 2 +-
docs/en/latest/plugins/udp-logger.md | 2 +-
23 files changed, 25 insertions(+), 25 deletions(-)
diff --git a/docs/en/latest/admin-api.md b/docs/en/latest/admin-api.md
index c2fd0d9a6f..39ec14f9ba 100644
--- a/docs/en/latest/admin-api.md
+++ b/docs/en/latest/admin-api.md
@@ -1581,7 +1581,7 @@ Stream Route resource request address:
/apisix/admin/stream_routes/{id}
| protocol.name | False | String | Name of the protocol proxyed by xRPC
framework. | "redis" |
| protocol.conf | False | Configuration | Protocol-specific configuration.
| |
-To learn more about filtering in stream proxies, check
[this](./stream-proxy.md#more-route-match-options) document.
+To learn more about filtering in stream proxies, check
[this](./stream-proxy.md#more-stream-route-filtering-options) document.
## Secret
@@ -1746,7 +1746,7 @@ Currently, the response is returned from etcd.
Proto is used to store protocol buffers so that APISIX can communicate in gRPC.
-See [grpc-transcode plugin](./plugins/grpc-transcode.md#enabling-the-plugin)
doc for more examples.
+See [grpc-transcode plugin](./plugins/grpc-transcode.md#examples) doc for more
examples.
### Proto API
@@ -1766,7 +1766,7 @@ Proto resource request address: /apisix/admin/protos/{id}
| Parameter | Required | Type | Description |
Example |
|-----------|----------|-----------|--------------------------------------|
----------------------------- |
-| content | True | String | Content of `.proto` or `.pb` files |
See [here](./plugins/grpc-transcode.md#enabling-the-plugin) |
+| content | True | String | Content of `.proto` or `.pb` files |
See [here](./plugins/grpc-transcode.md#examples) |
| name | False | Auxiliary | Identifier for the Protobuf definition. |
user-proto |
| desc | False | Auxiliary | Description of usage scenarios. |
protobuf for user service |
| labels | False | Match Rules | Attributes of the Proto specified as
key-value pairs. | {"version":"v2","service":"user","env":"production"} |
diff --git a/docs/en/latest/apisix-variable.md
b/docs/en/latest/apisix-variable.md
index adfb5aabd4..3b9084c57f 100644
--- a/docs/en/latest/apisix-variable.md
+++ b/docs/en/latest/apisix-variable.md
@@ -52,4 +52,4 @@ additional variables.
| rpc_time | xRPC | Time spent at the rpc request level.
| |
| upstream_unresolved_host | core | The upstream host before DNS resolution
(the configured domain or IP of the picked node). | httpbin.org |
-You can also register your own
[variable](./plugin-develop.md#register-custom-variable).
+You can also register your own
[variable](./plugin-develop.md#register-custom-variables).
diff --git a/docs/en/latest/discovery/eureka.md
b/docs/en/latest/discovery/eureka.md
index 3404a93ac8..fcddc71df2 100644
--- a/docs/en/latest/discovery/eureka.md
+++ b/docs/en/latest/discovery/eureka.md
@@ -22,4 +22,4 @@ title: eureka
-->
Apache APISIX supports service discovery via Eureka. For the details, please
start your
-reading from [Supported discovery
registries](../discovery.md#supported-discovery-registries).
+reading from [Supported discovery registries](../discovery.md).
diff --git a/docs/en/latest/plugins/clickhouse-logger.md
b/docs/en/latest/plugins/clickhouse-logger.md
index ef95a7ee40..1d7df6e327 100644
--- a/docs/en/latest/plugins/clickhouse-logger.md
+++ b/docs/en/latest/plugins/clickhouse-logger.md
@@ -65,7 +65,7 @@ NOTE: `encrypt_fields = {"password"}` is also defined in the
schema, which means
NOTE: In addition, you can use Environment Variables or APISIX Secret to store
and reference Plugin attributes. APISIX currently supports storing secrets in
two ways: [Environment Variables and HashiCorp Vault](../terminology/secret.md).
-This Plugin supports using batch processors to aggregate and process entries
(logs/data) in a batch. This avoids the need for frequently submitting the
data. The batch processor submits data every `5` seconds or when the data in
the queue reaches `1000`. See [Batch
Processor](../batch-processor.md#configuration) for more information or setting
your custom configuration.
+This Plugin supports using batch processors to aggregate and process entries
(logs/data) in a batch. This avoids the need for frequently submitting the
data. The batch processor submits data every `5` seconds or when the data in
the queue reaches `1000`. See [Batch
Processor](../batch-processor.md#configurations) for more information or
setting your custom configuration.
## Plugin Metadata
diff --git a/docs/en/latest/plugins/datadog.md
b/docs/en/latest/plugins/datadog.md
index c282c92fff..150a780005 100644
--- a/docs/en/latest/plugins/datadog.md
+++ b/docs/en/latest/plugins/datadog.md
@@ -51,7 +51,7 @@ This Plugin provides the ability to push metrics as a batch
to the external Data
| retry_delay | integer | False | 1 | [0,...] | Time
interval in seconds to retry sending the batch if the previous attempt failed.
|
| max_retry_count | integer | False | 0 | [0,...] | Maximum
number of unsuccessful retries before dropping the metric entries.
|
-This Plugin supports using batch processors to aggregate and process metric
data in a batch. This avoids the need to submit data too frequently. The batch
processor submits data every `5` seconds or when the data in the queue reaches
`1000`. See [Batch Processor](../batch-processor.md#configuration) for more
information or to customize the configuration.
+This Plugin supports using batch processors to aggregate and process metric
data in a batch. This avoids the need to submit data too frequently. The batch
processor submits data every `5` seconds or when the data in the queue reaches
`1000`. See [Batch Processor](../batch-processor.md#configurations) for more
information or to customize the configuration.
## Plugin Metadata
diff --git a/docs/en/latest/plugins/elasticsearch-logger.md
b/docs/en/latest/plugins/elasticsearch-logger.md
index d4ea6c4fb8..b1c92896cd 100644
--- a/docs/en/latest/plugins/elasticsearch-logger.md
+++ b/docs/en/latest/plugins/elasticsearch-logger.md
@@ -59,7 +59,7 @@ The `elasticsearch-logger` Plugin pushes request and response
logs in batches to
NOTE: `encrypt_fields = {"auth.password", "headers"}` is also defined in the
schema, which means that these fields will be stored encrypted in etcd. See
[encrypted storage fields](../plugin-develop.md#encrypted-storage-fields).
-This Plugin supports using batch processors to aggregate and process entries
(logs/data) in a batch. This avoids the need for frequently submitting the
data. The batch processor submits data every `5` seconds or when the data in
the queue reaches `1000`. See [Batch
Processor](../batch-processor.md#configuration) for more information or setting
your custom configuration.
+This Plugin supports using batch processors to aggregate and process entries
(logs/data) in a batch. This avoids the need for frequently submitting the
data. The batch processor submits data every `5` seconds or when the data in
the queue reaches `1000`. See [Batch
Processor](../batch-processor.md#configurations) for more information or
setting your custom configuration.
## Plugin Metadata
diff --git a/docs/en/latest/plugins/error-log-logger.md
b/docs/en/latest/plugins/error-log-logger.md
index bd46666d6d..6e226178ad 100644
--- a/docs/en/latest/plugins/error-log-logger.md
+++ b/docs/en/latest/plugins/error-log-logger.md
@@ -84,7 +84,7 @@ There are no attributes to configure this Plugin on Routes or
Services. All conf
| retry_delay | integer | False | 1
| [0,...]
| Time interval in seconds to retry sending the
batch if the previous attempt failed.
|
| max_retry_count | integer | False | 0
| [0,...]
| Maximum number of unsuccessful retries before
dropping the log entries.
|
-This Plugin supports using batch processors to aggregate and process entries
(logs/data) in a batch. This avoids the need for frequently submitting the
data. The batch processor submits data every `3` seconds or when the data in
the queue reaches `1000`. See [Batch
Processor](../batch-processor.md#configuration) for more information or setting
your custom configuration.
+This Plugin supports using batch processors to aggregate and process entries
(logs/data) in a batch. This avoids the need for frequently submitting the
data. The batch processor submits data every `3` seconds or when the data in
the queue reaches `1000`. See [Batch
Processor](../batch-processor.md#configurations) for more information or
setting your custom configuration.
### Example of default log format
diff --git a/docs/en/latest/plugins/google-cloud-logging.md
b/docs/en/latest/plugins/google-cloud-logging.md
index 0518a853fa..2b07dde90a 100644
--- a/docs/en/latest/plugins/google-cloud-logging.md
+++ b/docs/en/latest/plugins/google-cloud-logging.md
@@ -60,7 +60,7 @@ The `google-cloud-logging` Plugin pushes request and response
logs in batches to
NOTE: `encrypt_fields = {"auth_config.private_key"}` is also defined in the
schema, which means that the field will be stored encrypted in etcd. See
[encrypted storage fields](../plugin-develop.md#encrypted-storage-fields).
-This Plugin supports using batch processors to aggregate and process entries
(logs/data) in a batch. This avoids the need for frequently submitting the
data. The batch processor submits data every `5` seconds or when the data in
the queue reaches `1000`. See [Batch
Processor](../batch-processor.md#configuration) for more information or setting
your custom configuration.
+This Plugin supports using batch processors to aggregate and process entries
(logs/data) in a batch. This avoids the need for frequently submitting the
data. The batch processor submits data every `5` seconds or when the data in
the queue reaches `1000`. See [Batch
Processor](../batch-processor.md#configurations) for more information or
setting your custom configuration.
## Plugin Metadata
diff --git a/docs/en/latest/plugins/http-logger.md
b/docs/en/latest/plugins/http-logger.md
index 4f26a3dcde..23ec615642 100644
--- a/docs/en/latest/plugins/http-logger.md
+++ b/docs/en/latest/plugins/http-logger.md
@@ -55,7 +55,7 @@ The `http-logger` Plugin pushes request and response logs as
JSON objects to HTT
:::note
-This Plugin supports using batch processors to aggregate and process entries
(logs/data) in a batch. This avoids the need for frequently submitting the
data. The batch processor submits data every `5` seconds or when the data in
the queue reaches `1000`. See [Batch
Processor](../batch-processor.md#configuration) for more information or setting
your custom configuration.
+This Plugin supports using batch processors to aggregate and process entries
(logs/data) in a batch. This avoids the need for frequently submitting the
data. The batch processor submits data every `5` seconds or when the data in
the queue reaches `1000`. See [Batch
Processor](../batch-processor.md#configurations) for more information or
setting your custom configuration.
:::
diff --git a/docs/en/latest/plugins/kafka-logger.md
b/docs/en/latest/plugins/kafka-logger.md
index 61081bca67..9548b428af 100644
--- a/docs/en/latest/plugins/kafka-logger.md
+++ b/docs/en/latest/plugins/kafka-logger.md
@@ -74,7 +74,7 @@ It might take some time to receive the log data. It will be
automatically sent a
| meta_refresh_interval | integer | False | 30 |
[1,...] | `refresh_interval`
parameter in [lua-resty-kafka](https://github.com/doujiang24/lua-resty-kafka)
that specifies the interval to auto-refresh the metadata, in seconds.
|
| api_version | integer | False | 1 | [0,
1, 2] | `api_version` parameter in
[lua-resty-kafka](https://github.com/doujiang24/lua-resty-kafka) that specifies
the version of the Kafka Produce API. Set to `2` to make brokers store message
timestamps; otherwise the timestamps are stored as `-1` (shown as `1970-01-01`
in some consumers). Requires Kafka 0.10 or later. |
-This Plugin supports using batch processors to aggregate and process entries
(logs/data) in a batch. This avoids the need for frequently submitting the
data. The batch processor submits data every `5` seconds or when the data in
the queue reaches `1000`. See [Batch
Processor](../batch-processor.md#configuration) for more information or setting
your custom configuration.
+This Plugin supports using batch processors to aggregate and process entries
(logs/data) in a batch. This avoids the need for frequently submitting the
data. The batch processor submits data every `5` seconds or when the data in
the queue reaches `1000`. See [Batch
Processor](../batch-processor.md#configurations) for more information or
setting your custom configuration.
:::info IMPORTANT
diff --git a/docs/en/latest/plugins/lago.md b/docs/en/latest/plugins/lago.md
index dd503ed55c..bc222da62a 100644
--- a/docs/en/latest/plugins/lago.md
+++ b/docs/en/latest/plugins/lago.md
@@ -64,7 +64,7 @@ When enabled, the plugin will collect information from the
request context (e.g.
| keepalive_timeout | integer | False | 60000 | >=1000 | Keepalive
timeout in milliseconds. |
| keepalive_pool | integer | False | 5 | >=1 | Maximum
number of connections in the connection pool. |
-This Plugin supports using batch processors to aggregate and process events in
a batch. This avoids the need for frequently submitting the data. The batch
processor submits data every `5` seconds or when the data in the queue reaches
`1000`. See [Batch Processor](../batch-processor.md#configuration) for more
information or setting your custom configuration.
+This Plugin supports using batch processors to aggregate and process events in
a batch. This avoids the need for frequently submitting the data. The batch
processor submits data every `5` seconds or when the data in the queue reaches
`1000`. See [Batch Processor](../batch-processor.md#configurations) for more
information or setting your custom configuration.
## Plugin Metadata
diff --git a/docs/en/latest/plugins/loggly.md b/docs/en/latest/plugins/loggly.md
index 60e46371e8..344a72c1bc 100644
--- a/docs/en/latest/plugins/loggly.md
+++ b/docs/en/latest/plugins/loggly.md
@@ -52,7 +52,7 @@ When the maximum batch size is exceeded, the data in the
queue is pushed to Logg
| include_resp_body_expr | array | False | | When the
`include_resp_body` attribute is set to `true`, use this to filter based on
[lua-resty-expr](https://github.com/api7/lua-resty-expr). If present, only logs
the response if the expression evaluates to `true`. |
| max_resp_body_bytes | integer | False | 524288 | Response bodies within this
size will be logged, if the size exceeds the configured value it will be
truncated before logging. |
-This Plugin supports using batch processors to aggregate and process entries
(logs/data) in a batch. This avoids the need for frequently submitting the
data. The batch processor submits data every `5` seconds or when the data in
the queue reaches `1000`. See [Batch
Processor](../batch-processor.md#configuration) for more information or setting
your custom configuration.
+This Plugin supports using batch processors to aggregate and process entries
(logs/data) in a batch. This avoids the need for frequently submitting the
data. The batch processor submits data every `5` seconds or when the data in
the queue reaches `1000`. See [Batch
Processor](../batch-processor.md#configurations) for more information or
setting your custom configuration.
To generate a Customer token, go to `<your assigned
subdomain>/loggly.com/tokens` or navigate to Logs > Source setup > Customer
tokens.
diff --git a/docs/en/latest/plugins/loki-logger.md
b/docs/en/latest/plugins/loki-logger.md
index 43e052a1b6..f2d835efe2 100644
--- a/docs/en/latest/plugins/loki-logger.md
+++ b/docs/en/latest/plugins/loki-logger.md
@@ -62,7 +62,7 @@ When enabled, the Plugin will serialize the request context
information to [JSON
| include_resp_body_expr | array[array] | False | | | An array of one or
more conditions in the form of
[lua-resty-expr](https://github.com/api7/lua-resty-expr). Used when the
`include_resp_body` is true. Response body would only be logged when the
expressions configured here evaluate to true. |
| max_resp_body_bytes | integer | False | 524288 | >=1 | Response bodies
within this size will be logged, if the size exceeds the configured value it
will be truncated before logging. |
-This Plugin supports using batch processors to aggregate and process entries
(logs/data) in a batch. This avoids the need for frequently submitting the
data. The batch processor submits data every `5` seconds or when the data in
the queue reaches `1000`. See [Batch
Processor](../batch-processor.md#configuration) for more information or setting
your custom configuration.
+This Plugin supports using batch processors to aggregate and process entries
(logs/data) in a batch. This avoids the need for frequently submitting the
data. The batch processor submits data every `5` seconds or when the data in
the queue reaches `1000`. See [Batch
Processor](../batch-processor.md#configurations) for more information or
setting your custom configuration.
## Plugin Metadata
diff --git a/docs/en/latest/plugins/openid-connect.md
b/docs/en/latest/plugins/openid-connect.md
index f4778bfa53..edf9b877c0 100644
--- a/docs/en/latest/plugins/openid-connect.md
+++ b/docs/en/latest/plugins/openid-connect.md
@@ -535,7 +535,7 @@ It is recommended to set `redirect_uri` to an absolute URL
(scheme and host). Wh
#### 2. Missing Session Secret
-If you deploy APISIX in the [standalone
mode](../deployment-modes.md#standalone-mode), make sure that `session.secret`
is configured.
+If you deploy APISIX in the [standalone
mode](../deployment-modes.md#standalone), make sure that `session.secret` is
configured.
User sessions are stored in browser as cookies and encrypted with session
secret. The secret is automatically generated and saved to etcd if no secret is
configured through the `session.secret` attribute. However, in standalone mode,
etcd is no longer the configuration center. Therefore, you should explicitly
configure `session.secret` for this Plugin in the YAML configuration center
`apisix.yaml`.
diff --git a/docs/en/latest/plugins/proxy-cache.md
b/docs/en/latest/plugins/proxy-cache.md
index 60587d91d4..91be393b15 100644
--- a/docs/en/latest/plugins/proxy-cache.md
+++ b/docs/en/latest/plugins/proxy-cache.md
@@ -112,7 +112,7 @@ On-disk caching strategy offers the advantages of data
persistency when system r
The following example demonstrates how you can use `proxy-cache` Plugin on a
Route to cache data on disk.
-When using the on-disk caching strategy, the cache TTL is determined by value
from the response header `Expires` or `Cache-Control`. If none of these headers
is present or if APISIX returns `502 Bad Gateway` or `504 Gateway Timeout` due
to unavailable Upstreams, the cache TTL defaults to the value configured in the
[configuration files](#static-configuration).
+When using the on-disk caching strategy, the cache TTL is determined by value
from the response header `Expires` or `Cache-Control`. If none of these headers
is present or if APISIX returns `502 Bad Gateway` or `504 Gateway Timeout` due
to unavailable Upstreams, the cache TTL defaults to the value configured in the
[configuration files](#static-configurations).
Create a Route with the `proxy-cache` Plugin to cache data on disk:
diff --git a/docs/en/latest/plugins/serverless.md
b/docs/en/latest/plugins/serverless.md
index 3df036eadb..e8b2aaaa1e 100644
--- a/docs/en/latest/plugins/serverless.md
+++ b/docs/en/latest/plugins/serverless.md
@@ -421,7 +421,7 @@ adc sync -f adc.yaml
</Tabs>
-Next, update the log format for all `syslog` instances with the new variable
by configuring the [Plugin metadata](../terminology/plugin.md#plugin-metadata):
+Next, update the log format for all `syslog` instances with the new variable
by configuring the [Plugin metadata](../terminology/plugin-metadata.md):
<Tabs
groupId="api"
diff --git a/docs/en/latest/plugins/skywalking-logger.md
b/docs/en/latest/plugins/skywalking-logger.md
index f527bdf854..19d099fb67 100644
--- a/docs/en/latest/plugins/skywalking-logger.md
+++ b/docs/en/latest/plugins/skywalking-logger.md
@@ -56,7 +56,7 @@ If there is an existing tracing context, it sets up the
trace-log correlation au
| include_resp_body_expr | array[array] | False | | An array of
one or more conditions in the form of
[lua-resty-expr](https://github.com/api7/lua-resty-expr). Used when the
`include_resp_body` is true. Response body would only be logged when the
expressions configured here evaluate to true. |
| max_resp_body_bytes | integer | False | 524288 | >=1 | Response
bodies within this size will be logged, if the size exceeds the configured
value it will be truncated before logging. |
-This Plugin supports using batch processors to aggregate and process entries
(logs/data) in a batch. This avoids the need for frequently submitting the
data. The batch processor submits data every `5` seconds or when the data in
the queue reaches `1000`. See [Batch
Processor](../batch-processor.md#configuration) for more information or setting
your custom configuration.
+This Plugin supports using batch processors to aggregate and process entries
(logs/data) in a batch. This avoids the need for frequently submitting the
data. The batch processor submits data every `5` seconds or when the data in
the queue reaches `1000`. See [Batch
Processor](../batch-processor.md#configurations) for more information or
setting your custom configuration.
## Metadata
diff --git a/docs/en/latest/plugins/sls-logger.md
b/docs/en/latest/plugins/sls-logger.md
index 1ccfadc157..ccf2ca9fd3 100644
--- a/docs/en/latest/plugins/sls-logger.md
+++ b/docs/en/latest/plugins/sls-logger.md
@@ -57,7 +57,7 @@ It might take some time to receive the log data. It will be
automatically sent a
NOTE: `encrypt_fields = {"access_key_secret"}` is also defined in the schema,
which means that the field will be stored encrypted in etcd. See [encrypted
storage fields](../plugin-develop.md#encrypted-storage-fields).
-This Plugin supports using batch processors to aggregate and process entries
(logs/data) in a batch. This avoids the need for frequently submitting the
data. The batch processor submits data every `5` seconds or when the data in
the queue reaches `1000`. See [Batch
Processor](../batch-processor.md#configuration) for more information or setting
your custom configuration.
+This Plugin supports using batch processors to aggregate and process entries
(logs/data) in a batch. This avoids the need for frequently submitting the
data. The batch processor submits data every `5` seconds or when the data in
the queue reaches `1000`. See [Batch
Processor](../batch-processor.md#configurations) for more information or
setting your custom configuration.
### Example of default log format
diff --git a/docs/en/latest/plugins/splunk-hec-logging.md
b/docs/en/latest/plugins/splunk-hec-logging.md
index df3c5e2c4e..fc738bb728 100644
--- a/docs/en/latest/plugins/splunk-hec-logging.md
+++ b/docs/en/latest/plugins/splunk-hec-logging.md
@@ -56,7 +56,7 @@ The `splunk-hec-logging` Plugin serializes request and
response context informat
| retry_delay | integer | False | 1 | >= 0
| The time interval in seconds to retry sending the batch to the logging
service if the batch was not successfully sent.
|
| max_retry_count | integer | False | 0 | >= 0
| The maximum number of unsuccessful retries allowed before dropping the
log entries.
|
-This Plugin supports using batch processors to aggregate and process entries
(logs/data) in a batch. This avoids the need for frequently submitting the
data. The batch processor submits data every `5` seconds or when the data in
the queue reaches `1000`. See [Batch
Processor](../batch-processor.md#configuration) for more information or setting
your custom configuration.
+This Plugin supports using batch processors to aggregate and process entries
(logs/data) in a batch. This avoids the need for frequently submitting the
data. The batch processor submits data every `5` seconds or when the data in
the queue reaches `1000`. See [Batch
Processor](../batch-processor.md#configurations) for more information or
setting your custom configuration.
## Plugin Metadata
diff --git a/docs/en/latest/plugins/syslog.md b/docs/en/latest/plugins/syslog.md
index b7e76a7030..47d9941d2b 100644
--- a/docs/en/latest/plugins/syslog.md
+++ b/docs/en/latest/plugins/syslog.md
@@ -63,7 +63,7 @@ The `syslog` Plugin pushes request and response logs as JSON
objects to syslog s
:::note
-This Plugin supports using batch processors to aggregate and process entries
(logs/data) in a batch. This avoids the need for frequently submitting the
data. The batch processor submits data every `5` seconds or when the data in
the queue reaches `1000`. See [Batch
Processor](../batch-processor.md#configuration) for more information or setting
your custom configuration.
+This Plugin supports using batch processors to aggregate and process entries
(logs/data) in a batch. This avoids the need for frequently submitting the
data. The batch processor submits data every `5` seconds or when the data in
the queue reaches `1000`. See [Batch
Processor](../batch-processor.md#configurations) for more information or
setting your custom configuration.
:::
diff --git a/docs/en/latest/plugins/tcp-logger.md
b/docs/en/latest/plugins/tcp-logger.md
index cb29b3ac3f..a7696cf4d9 100644
--- a/docs/en/latest/plugins/tcp-logger.md
+++ b/docs/en/latest/plugins/tcp-logger.md
@@ -54,7 +54,7 @@ This plugin also allows to push logs as a batch to your
external TCP server. It
| include_resp_body_expr | array | No | | | Filter
for when the `include_resp_body` attribute is set to `true`. Response body is
only logged when the expression set here evaluates to `true`. See
[lua-resty-expr](https://github.com/api7/lua-resty-expr) for more.
|
| max_resp_body_bytes | integer | False | 524288 | >=1 | Response
bodies within this size will be logged, if the size exceeds the configured
value it will be truncated before logging. |
-This Plugin supports using batch processors to aggregate and process entries
(logs/data) in a batch. This avoids the need for frequently submitting the
data. The batch processor submits data every `5` seconds or when the data in
the queue reaches `1000`. See [Batch
Processor](../batch-processor.md#configuration) for more information or setting
your custom configuration.
+This Plugin supports using batch processors to aggregate and process entries
(logs/data) in a batch. This avoids the need for frequently submitting the
data. The batch processor submits data every `5` seconds or when the data in
the queue reaches `1000`. See [Batch
Processor](../batch-processor.md#configurations) for more information or
setting your custom configuration.
### Example of default log format
diff --git a/docs/en/latest/plugins/tencent-cloud-cls.md
b/docs/en/latest/plugins/tencent-cloud-cls.md
index 6b02a4cf7c..ada24bc5b4 100644
--- a/docs/en/latest/plugins/tencent-cloud-cls.md
+++ b/docs/en/latest/plugins/tencent-cloud-cls.md
@@ -54,7 +54,7 @@ The `tencent-cloud-cls` Plugin uses [TencentCloud
CLS](https://cloud.tencent.com
NOTE: `encrypt_fields = {"secret_key"}` is also defined in the schema, which
means that the field will be stored encrypted in etcd. See [encrypted storage
fields](../plugin-develop.md#encrypted-storage-fields).
-This Plugin supports using batch processors to aggregate and process entries
(logs/data) in a batch. This avoids the need for frequently submitting the
data. The batch processor submits data every `5` seconds or when the data in
the queue reaches `1000`. See [Batch
Processor](../batch-processor.md#configuration) for more information or setting
your custom configuration.
+This Plugin supports using batch processors to aggregate and process entries
(logs/data) in a batch. This avoids the need for frequently submitting the
data. The batch processor submits data every `5` seconds or when the data in
the queue reaches `1000`. See [Batch
Processor](../batch-processor.md#configurations) for more information or
setting your custom configuration.
### Example of default log format
diff --git a/docs/en/latest/plugins/udp-logger.md
b/docs/en/latest/plugins/udp-logger.md
index 02c2b3c37f..db89eedd1f 100644
--- a/docs/en/latest/plugins/udp-logger.md
+++ b/docs/en/latest/plugins/udp-logger.md
@@ -52,7 +52,7 @@ This plugin also allows to push logs as a batch to your
external UDP server. It
| include_resp_body_expr | array | No | | | Filter
for when the `include_resp_body` attribute is set to `true`. Response body is
only logged when the expression set here evaluates to `true`. See
[lua-resty-expr](https://github.com/api7/lua-resty-expr) for more.
|
| max_resp_body_bytes | integer | False | 524288 | >=1 | Response bodies
within this size will be logged, if the size exceeds the configured value it
will be truncated before logging. |
-This Plugin supports using batch processors to aggregate and process entries
(logs/data) in a batch. This avoids the need for frequently submitting the
data. The batch processor submits data every `5` seconds or when the data in
the queue reaches `1000`. See [Batch
Processor](../batch-processor.md#configuration) for more information or setting
your custom configuration.
+This Plugin supports using batch processors to aggregate and process entries
(logs/data) in a batch. This avoids the need for frequently submitting the
data. The batch processor submits data every `5` seconds or when the data in
the queue reaches `1000`. See [Batch
Processor](../batch-processor.md#configurations) for more information or
setting your custom configuration.
### Example of default log format
