diff --git a/docs/en/latest/plugins/datadog.md b/docs/en/latest/plugins/datadog.md
index be7661533892..2d5be95b0820 100644
--- a/docs/en/latest/plugins/datadog.md
+++ b/docs/en/latest/plugins/datadog.md
@@ -1,5 +1,11 @@
 ---
 title: datadog
+keywords:
+  - APISIX
+  - API Gateway
+  - Plugin
+  - Datadog
+description: This document contains information about the Apache APISIX datadog Plugin.
 ---
 
 <!--
@@ -23,62 +29,93 @@ title: datadog
 
 ## Description
 
-`datadog` is a monitoring plugin built into Apache APISIX for seamless integration with [Datadog](https://www.datadoghq.com/), one of the most used monitoring and observability platform for cloud applications. If enabled, this plugin supports multiple powerful types of metrics capture for every request and response cycle that essentially reflects the behaviour and health of the system.
+The `datadog` monitoring Plugin is for seamless integration of APISIX with [Datadog](https://www.datadoghq.com/), one of the most used monitoring and observability platform for cloud applications.
 
-This plugin pushes its custom metrics to the DogStatsD server, comes bundled with Datadog agent (to learn more about how to install a datadog agent, please visit [here](https://docs.datadoghq.com/agent/) ), over the UDP protocol. DogStatsD basically is an implementation of StatsD protocol which collects the custom metrics for Apache APISIX agent, aggregates it into a single data point and sends it to the configured Datadog server.
-To learn more about DogStatsD, please visit [DogStatsD](https://docs.datadoghq.com/developers/dogstatsd/?tab=hostagent) documentation.
+When enabled, the Plugin supports multiple metric capture types for request and response cycles.
 
-This plugin provides the ability to push metrics as a batch to the external Datadog agent, reusing the same datagram socket. In case if you did not receive the log data, don't worry give it some time. It will automatically send the logs after the timer function expires in our Batch Processor.
+This Plugin, pushes its custom metrics to the [DogStatsD](https://docs.datadoghq.com/developers/dogstatsd/?tab=hostagent) server over UDP protocol and comes bundled with [Datadog agent](https://docs.datadoghq.com/agent/).
 
-For more info on Batch-Processor in Apache APISIX please refer.
-[Batch-Processor](../batch-processor.md)
+DogStatsD implements the StatsD protocol which collects the custom metrics for the Apache APISIX agent, aggregates them into a single data point, and sends it to the configured Datadog server.
+
+This Plugin provides the ability to push metrics as a batch to the external Datadog agent, reusing the same datagram socket. It might take some time to receive the log data. It will be automatically sent after the timer function in the [batch processor](../batch-processor.md) expires.
 
 ## Attributes
 
-| Name             | Type   | Requirement  | Default      | Valid       | Description                                                                                |
-| -----------      | ------ | -----------  | -------      | -----       | ------------------------------------------------------------                               |
-| prefer_name      | boolean | optional    | true         | true/false  | If set to `false`, would use route/service id instead of name(default) with metric tags.   |
+| Name        | Type    | Required | Default | Valid values | Description                                                                            |
+| ----------- | ------- | -------- | ------- | ------------ | -------------------------------------------------------------------------------------- |
+| prefer_name | boolean | False    | true    | [true,false] | When set to `false`, uses Route/Service ID instead of name (default) with metric tags. |
 
-The plugin supports the use of batch processors to aggregate and process entries(logs/data) in a batch. This avoids frequent data submissions by the plugin, which by default the batch processor submits data every `5` seconds or when the data in the queue reaches `1000`. For information or custom batch processor parameter settings, see [Batch-Processor](../batch-processor.md#configuration) configuration section.
+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.
 
 ## Metadata
 
-| Name        | Type    | Requirement |     Default        | Valid         | Description                                                            |
-| ----------- | ------  | ----------- |      -------       | -----         | ---------------------------------------------------------------------- |
-| host        | string  | optional    |  "127.0.0.1"       |               | The DogStatsD server host address                                      |
-| port        | integer | optional    |    8125            |               | The DogStatsD server host port                                         |
-| namespace   | string  | optional    |    "apisix"        |               | Prefix for all the custom metrics sent by APISIX agent. Useful for finding entities for metric graph. e.g. (apisix.request.counter)                                        |
-| constant_tags | array | optional    | [ "source:apisix" ] |              | Static tags embedded into generated metrics. Useful for grouping metric over certain signals. |
+You can configure the Plugin through the Plugin metadata.
+
+| Name          | Type    | Required | Default             | Description                                                                                                                               |
+| ------------- | ------- | -------- | ------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- |
+| host          | string  | False    | "127.0.0.1"         | DogStatsD server host address.                                                                                                            |
+| port          | integer | False    | 8125                | DogStatsD server host port.                                                                                                               |
+| namespace     | string  | False    | "apisix"            | Prefix for all custom metrics sent by APISIX agent. Useful for finding entities for metrics graph. For example, `apisix.request.counter`. |
+| constant_tags | array   | False    | [ "source:apisix" ] | Static tags to embed into generated metrics. Useful for grouping metrics over certain signals.                                            |
+
+:::tip
+
+See [defining tags](https://docs.datadoghq.com/getting_started/tagging/#defining-tags) to know more about how to effectively use tags.
+
+:::
+
+By default, the Plugin expects the DogStatsD service to be available at `127.0.0.1:8125`. If you want to change this, you can update the Plugin metadata as shown below:
+
+```shell
+curl http://127.0.0.1:9080/apisix/admin/plugin_metadata/datadog -H 'X-API-KEY: edd1c9f034335f136f87ad84b625c8f1' -X PUT -d '
+{
+    "host": "172.168.45.29",
+    "port": 8126,
+    "constant_tags": [
+        "source:apisix",
+        "service:custom"
+    ],
+    "namespace": "apisix"
+}'
+```
+
+To reset to default configuration, make a PUT request with empty body:
 
-To know more about how to effectively write tags, please visit [here](https://docs.datadoghq.com/getting_started/tagging/#defining-tags)
+```shell
+curl http://127.0.0.1:9080/apisix/admin/plugin_metadata/datadog -H 'X-API-KEY: edd1c9f034335f136f87ad84b625c8f1' -X PUT -d '{}'
+```
 
-## Exported Metrics
+## Exported metrics
 
-Apache APISIX agent, for every request response cycle, export the following metrics to DogStatsD server if the datadog plugin is enabled:
+When the `datadog` Plugin is enabled, the APISIX agent exports the following metrics to the DogStatsD server for each request/response cycle:
 
-| Metric Name               | StatsD Type   | Description               |
-| -----------               | -----------   | -------                   |
-| Request Counter           | Counter       | Number of requests received.   |
-| Request Latency           | Histogram     | Time taken to process the request (in milliseconds). |
-| Upstream latency          | Histogram     | Time taken to proxy the request to the upstream server till a response is received (in milliseconds). |
-| APISIX Latency            | Histogram     | Time taken by APISIX agent to process the request (in milliseconds). |
-| Ingress Size              | Timer         | Request body size in bytes. |
-| Egress Size               | Timer         | Response body size in bytes. |
+| Metric name      | StatsD type | Description                                                                                           |
+| ---------------- | ----------- | ----------------------------------------------------------------------------------------------------- |
+| Request Counter  | Counter     | Number of requests received.                                                                          |
+| Request Latency  | Histogram   | Time taken to process the request (in milliseconds).                                                  |
+| Upstream latency | Histogram   | Time taken to proxy the request to the upstream server till a response is received (in milliseconds). |
+| APISIX Latency   | Histogram   | Time taken by APISIX agent to process the request (in milliseconds).                                  |
+| Ingress Size     | Timer       | Request body size in bytes.                                                                           |
+| Egress Size      | Timer       | Response body size in bytes.                                                                          |
 
 The metrics will be sent to the DogStatsD agent with the following tags:
 
-> If there is no suitable value for any particular tag, the tag will simply be omitted.
+- `route_name`: Name specified in the Route schema definition. If not present or if the attribute `prefer_name` is set to false, falls back to the Route ID.
+- `service_name`: If a Route has been created with an abstracted Service, the Service name/ID based on the attribute `prefer_name`.
+- `consumer`: If the Route is linked to a Consumer, the username will be added as a tag.
+- `balancer_ip`: IP address of the Upstream balancer that processed the current request.
+- `response_status`: HTTP response status code.
+- `scheme`: Request scheme such as HTTP, gRPC, and gRPCs.
+
+:::note
 
-- **route_name**: Name specified in the route schema definition. If not present or plugin attribute `prefer_name` is set to `false`, it will fall back to the route id value.
-- **service_name**: If a route has been created with the abstraction of service, the particular service name/id (based on plugin `prefer_name` attribute) will be used.
-- **consumer**: If the route has a linked consumer, the consumer Username will be added as a tag.
-- **balancer_ip**: IP of the Upstream balancer that has processed the current request.
-- **response_status**: HTTP response status code.
-- **scheme**: Scheme that has been used to make the request, such as HTTP, gRPC, gRPCs etc.
+If there are no suitable values for any particular tag, the tag will be omitted.
 
-## How To Enable
+:::
 
-The following is an example on how to enable the datadog plugin for a specific route. We are assuming your datadog agent is already up an running.
+## Enabling the Plugin
+
+Once you have your Datadog agent running, you can enable the Plugin as shown below:
 
 ```shell
 curl http://127.0.0.1:9080/apisix/admin/routes/1 -H 'X-API-KEY: edd1c9f034335f136f87ad84b625c8f1' -X PUT -d '
@@ -96,15 +133,14 @@ curl http://127.0.0.1:9080/apisix/admin/routes/1 -H 'X-API-KEY: edd1c9f034335f13
 }'
 ```
 
-Now any requests to uri `/hello` will generate aforesaid metrics and push it to DogStatsD server of the datadog agent.
+Now, requests to the endpoint `/hello` will generate metrics and push it to the DogStatsD server.
 
 ## Disable Plugin
 
-Remove the corresponding json configuration in the plugin configuration to disable the `datadog`.
-APISIX plugins are hot-reloaded, therefore no need to restart APISIX.
+To disable the `datadog` Plugin, you can delete the corresponding JSON configuration from the Plugin configuration. APISIX will automatically reload and you do not have to restart for this to take effect.
 
 ```shell
-$ curl http://127.0.0.1:9080/apisix/admin/routes/1 -H 'X-API-KEY: edd1c9f034335f136f87ad84b625c8f1' -X PUT -d '
+curl http://127.0.0.1:9080/apisix/admin/routes/1 -H 'X-API-KEY: edd1c9f034335f136f87ad84b625c8f1' -X PUT -d '
 {
     "methods": ["GET"],
     "uri": "/hello",
@@ -117,30 +153,3 @@ $ curl http://127.0.0.1:9080/apisix/admin/routes/1 -H 'X-API-KEY: edd1c9f034335f
     }
 }'
 ```
-
-## Custom Configuration
-
-In the default configuration, the plugin expects the dogstatsd service to be available at `127.0.0.1:8125`. If you wish to update the config, please update the plugin metadata. To know more about the fields of the datadog metadata, see [here](#metadata).
-
-Make a request to _/apisix/admin/plugin_metadata_ endpoint with the updated metadata as following:
-
-```shell
-$ curl http://127.0.0.1:9080/apisix/admin/plugin_metadata/datadog -H 'X-API-KEY: edd1c9f034335f136f87ad84b625c8f1' -X PUT -d '
-{
-    "host": "172.168.45.29",
-    "port": 8126,
-    "constant_tags": [
-        "source:apisix",
-        "service:custom"
-    ],
-    "namespace": "apisix"
-}'
-```
-
-This HTTP PUT request will update the metadata and subsequent metrics will be pushed to the `172.168.45.29:8126` endpoint via UDP StatsD. Everything will be hot-loaded, there is no need to restart Apache APISIX instances.
-
-In case, if you wish to revert the datadog metadata schema to the default values, just make another PUT request to the same endpoint with an empty body. For example:
-
-```shell
-$ curl http://127.0.0.1:9080/apisix/admin/plugin_metadata/datadog -H 'X-API-KEY: edd1c9f034335f136f87ad84b625c8f1' -X PUT -d '{}'
-```
diff --git a/docs/en/latest/plugins/node-status.md b/docs/en/latest/plugins/node-status.md
index b1d06e068bee..ad0c681cc79b 100644
--- a/docs/en/latest/plugins/node-status.md
+++ b/docs/en/latest/plugins/node-status.md
@@ -1,7 +1,12 @@
 ---
 title: node-status
+keywords:
+  - APISIX
+  - API Gateway
+  - Plugin
+  - Node status
+description: This document contains information about the Apache APISIX node-status Plugin.
 ---
-
 <!--
 #
 # Licensed to the Apache Software Foundation (ASF) under one or more
@@ -23,36 +28,36 @@ title: node-status
 
 ## Description
 
-`node-status` is a plugin which we could get request status information through it's API.
+The `node-status` Plugin can be used get the status of requests to APISIX by exposing an API endpoint.
 
 ## Attributes
 
-None
+None.
 
 ## API
 
-This plugin will add `/apisix/status` to get status information.
-You may need to use [public-api](public-api.md) plugin to expose it.
+This Plugin will add the endpoint `/apisix/status` to expose the status of APISIX.
 
-## How To Enable
+You may need to use the [public-api](public-api.md) Plugin to expose the endpoint.
 
-1. Configure `node-status` in the plugin list of the configuration file `conf/config.yaml`,
-then you can add this plugin in any route.
+## Enabling the Plugin
 
-```
-plugins:                          # plugin list
+To configure the `node-status` Plugin, you have to first enable it in your configuration file (`conf/config.yaml`):
+
+```yaml title="conf/config.yaml"
+plugins:
   - example-plugin
   - limit-req
-  - node-status
   - jwt-auth
   - zipkin
+  - node-status
   ......
 ```
 
-2. Setup the route for the status API, which will use the [public-api](public-api.md) plugin.
+You have to the setup the Route for the status API and expose it using the [public-api](public-api.md) Plugin.
 
 ```shell
-$ curl http://127.0.0.1:9080/apisix/admin/routes/ns -H 'X-API-KEY: edd1c9f034335f136f87ad84b625c8f1' -X PUT -d '
+curl http://127.0.0.1:9080/apisix/admin/routes/ns -H 'X-API-KEY: edd1c9f034335f136f87ad84b625c8f1' -X PUT -d '
 {
     "uri": "/apisix/status",
     "plugins": {
@@ -61,12 +66,15 @@ $ curl http://127.0.0.1:9080/apisix/admin/routes/ns -H 'X-API-KEY: edd1c9f034335
 }'
 ```
 
-## Test Plugin
+## Example usage
 
-1. Request with uri `/apisix/status`
+Once you have configured the Plugin, you can make a request to the `apisix/status` endpoint to get the status:
 
-```sh
-$ curl localhost:9080/apisix/status -i
+```shell
+curl localhost:9080/apisix/status -i
+```
+
+```shell
 HTTP/1.1 200 OK
 Date: Tue, 03 Nov 2020 11:12:55 GMT
 Content-Type: text/plain; charset=utf-8
@@ -77,27 +85,26 @@ Server: APISIX web server
 {"status":{"total":"23","waiting":"0","accepted":"22","writing":"1","handled":"22","active":"1","reading":"0"},"id":"6790a064-8f61-44ba-a6d3-5df42f2b1bb3"}
 ```
 
-2. Parameter Description
+The parameters in the response are described below:
 
-| Parameter    | Description                                        |
-| ------------ | -------------------------------------------- |
-| status       | status information                                     |
-| total        | the total number of client requests                               |
-| waiting      | the current number of idle client connections waiting for a request               |
-| accepted     | the total number of accepted client connections                         |
-| writing      | the current number of connections where APISIX is writing the response back to the client               |
-| handled      | the total number of handled connections. Generally, the parameter value is the same as accepted unless some resource limits have been reached          |
-| active       | the current number of active client connections including waiting connections                       |
-| reading      | the current number of connections where APISIX is reading the request header                   |
-| id           | APISIX's uid which is saved in apisix/conf/apisix.uid  |
+| Parameter | Description                                                                                                            |
+|-----------|------------------------------------------------------------------------------------------------------------------------|
+| status    | Status of APISIX.                                                                                                      |
+| total     | Total number of client requests.                                                                                       |
+| waiting   | Number of idle client connections waiting for a request.                                                               |
+| accepted  | Number of accepted client connections.                                                                                 |
+| writing   | Number of connections to which APISIX is writing back a response.                                                      |
+| handled   | Number of handled connections. Generally, this value is the same as `accepted` unless any a resource limit is reached. |
+| active    | Number of active client connections including `waiting` connections.                                                   |
+| reading   | Number of connections where APISIX is reading the request header.                                                      |
+| id        | UID of APISIX instance saved in `apisix/conf/apisix.uid`.                                                              |
 
 ## Disable Plugin
 
-1. You can delete `node-status` in the plugin list of the configuration file `apisix/conf/config.yaml`,
-then you can not add this plugin in any route.
+To remove the Plugin, you can remove it from your configuration file (`conf/config.yaml`):
 
 ```
-plugins:                          # plugin list
+plugins:
   - example-plugin
   - limit-req
   - jwt-auth
@@ -105,12 +112,10 @@ plugins:                          # plugin list
   ......
 ```
 
-2. When you want to disable the `node-status` plugin in the route, it is very simple,
-you can delete the corresponding json configuration in the plugin configuration,
-no need to restart the service, it will take effect immediately.
+To disable the `node-status` Plugin on a Route, you can delete the corresponding JSON configuration from the Plugin configuration. APISIX will automatically reload and you do not have to restart for this to take effect.
 
 ```sh
-$ curl http://127.0.0.1:9080/apisix/admin/routes/1 -H 'X-API-KEY: edd1c9f034335f136f87ad84b625c8f1' -X PUT -i -d '
+curl http://127.0.0.1:9080/apisix/admin/routes/1 -H 'X-API-KEY: edd1c9f034335f136f87ad84b625c8f1' -X PUT -i -d '
 {
     "uri": "/route1",
     "upstream": {
@@ -123,8 +128,8 @@ $ curl http://127.0.0.1:9080/apisix/admin/routes/1 -H 'X-API-KEY: edd1c9f034335f
 }'
 ```
 
-3. You can also remove the route on `/apisix/status`, no one can access the API.
+You can also remove the Route on `/apisix/status`:
 
 ```sh
-$ curl http://127.0.0.1:9080/apisix/admin/routes/ns -H 'X-API-KEY: edd1c9f034335f136f87ad84b625c8f1' -X DELETE
+curl http://127.0.0.1:9080/apisix/admin/routes/ns -H 'X-API-KEY: edd1c9f034335f136f87ad84b625c8f1' -X DELETE
 ```
diff --git a/docs/en/latest/plugins/prometheus.md b/docs/en/latest/plugins/prometheus.md
index 8f30a7195284..0e02aa6bb4b9 100644
--- a/docs/en/latest/plugins/prometheus.md
+++ b/docs/en/latest/plugins/prometheus.md
@@ -1,5 +1,11 @@
 ---
 title: prometheus
+keywords:
+  - APISIX
+  - API Gateway
+  - Plugin
+  - Prometheus
+description: This document contains information about the Apache APISIX prometheus Plugin.
 ---
 
 <!--
@@ -23,22 +29,37 @@ title: prometheus
 
 ## Description
 
-This plugin exposes metrics in Prometheus Exposition format.
+The `prometheus` Plugin exports metrics in [Prometheus exposition format](https://prometheus.io/docs/instrumenting/exposition_formats/#exposition-formats).
 
 ## Attributes
 
-| Name         | Type      | Requirement | Default  | Valid | Description                                                                                |
-| ------------ | --------- | ----------- | -------- | ----- | ------------------------------------------------------------------------------------------ |
-| prefer_name  | boolean   | optional    | false    |       | When set to `true`, would print route/service `name` instead of `id` in Prometheus metric. |
+| Name        | Type    | Required | Default | Description                                                                       |
+| ----------- | ------- | -------- | ------- | --------------------------------------------------------------------------------- |
+| prefer_name | boolean | False    | false   | When set to `true`, prints Route/Service name instead of ID in Prometheus metric. |
 
-## API
+### Specifying `export_uri`
+
+You can change the default export URI by configuring the `export_uri` attribute under `plugin_attr` in your configuration file (`conf/config.yaml`).
 
-This plugin will add `/apisix/prometheus/metrics` to expose the metrics.
+| Name       | Type   | Default                      | Description                           |
+| ---------- | ------ | ---------------------------- | ------------------------------------- |
+| export_uri | string | "/apisix/prometheus/metrics" | URI to export the Prometheus metrics. |
 
-The metrics are exposed via a separate Prometheus server address.
-By default, the address is `127.0.0.1:9091`. You can change it in the `conf/config.yaml`, for example:
+Here is a configuration example:
 
+```yaml title="conf/config.yaml"
+plugin_attr:
+  prometheus:
+    export_uri: /apisix/metrics
 ```
+
+## API
+
+This Plugin will add the API endpoint `/apisix/prometheus/metrics` or your custom export URI for exposing the metrics.
+
+These metrics are exposed by a separate Prometheus server address. By default, the address is `127.0.0.1:9091`. You can change it in your configuration file (`conf/config.yaml`):
+
+```yaml title="conf/config.yaml"
 plugin_attr:
   prometheus:
     export_addr:
@@ -46,24 +67,23 @@ plugin_attr:
       port: 9092
 ```
 
-Assume environment variable `INTRANET_IP` is `172.1.1.1`, now APISIX will export the metrics via `172.1.1.1:9092`.
+Now, if the environment variable `INTRANET_IP` is `172.1.1.1`, APISIX will export the metrics via `172.1.1.1:9092`.
 
-If you still want to expose the metrics via the data plane port (default: 9080), you can configure it like this:
+If you still want to expose the metrics via the data plane port (default: `9080`), you can configure it as shown below:
 
-```
+```yaml title="conf/config.yaml"
 plugin_attr:
   prometheus:
     enable_export_server: false
 ```
 
-And expose it by using [public-api](public-api.md) plugin.
+You can then expose it by using the [public-api](public-api.md) Plugin.
 
-## How to enable it for HTTP
+## Enabling the Plugin
 
-`prometheus` plugin could be enable with empty table.
-Notice, `name` could be duplicated for multiple routes/services, so when set `prefer_name` to `true`, take care of naming format or it could be misleading.
+The `prometheus` Plugin can be enabled with an empty table.
 
-For example:
+The example below shows how you can configure the Plugin on a specific Route:
 
 ```shell
 curl http://127.0.0.1:9080/apisix/admin/routes/1  -H 'X-API-KEY: edd1c9f034335f136f87ad84b625c8f1' -X PUT -d '
@@ -81,7 +101,13 @@ curl http://127.0.0.1:9080/apisix/admin/routes/1  -H 'X-API-KEY: edd1c9f034335f1
 }'
 ```
 
-You can use [APISIX Dashboard](https://github.com/apache/apisix-dashboard) to complete the above operations through the web console.
+:::note
+
+When `prefer_name` is set to `true` make sure to not duplicate names for multiple Routes/Services or it could be misleading.
+
+:::
+
+<!-- You can use [APISIX Dashboard](https://github.com/apache/apisix-dashboard) to complete the above operations through the web console.
 
 First, add a Route:
 
@@ -89,59 +115,38 @@ First, add a Route:
 
 Then add prometheus plugin:
 
-![enable prometheus plugin](../../../assets/images/plugin/prometheus-2.png)
+![enable prometheus plugin](../../../assets/images/plugin/prometheus-2.png) -->
 
-## How to fetch the metric data
+## Fetching metrics
 
-We fetch the metric data from the specified url `/apisix/prometheus/metrics`.
+You can fetch the metrics from the specified export URI (default: `/apisix/prometheus/metrics`):
 
-```
+```shell
 curl -i http://127.0.0.1:9091/apisix/prometheus/metrics
 ```
 
-Puts this URL address into prometheus, and it will automatically fetch
-these metric data.
-
-For example like this:
+You can add this address to Prometheus to fetch the data:
 
 ```yaml
 scrape_configs:
-  - job_name: 'apisix'
+  - job_name: "apisix"
     scrape_interval: 15s # This value will be related to the time range of the rate function in Prometheus QL. The time range in the rate function should be at least twice this value.
-    metrics_path: '/apisix/prometheus/metrics'
+    metrics_path: "/apisix/prometheus/metrics"
     static_configs:
-    - targets: ['127.0.0.1:9091']
+      - targets: ["127.0.0.1:9091"]
 ```
 
-And we can check the status at prometheus console:
+Now, you will be able to check the status in your Prometheus console:
 
 ![checking status on prometheus dashboard](../../../assets/images/plugin/prometheus01.png)
 
 ![prometheus apisix in-depth metric view](../../../assets/images/plugin/prometheus02.png)
 
-## How to specify export uri
-
-We can change the default export uri in the `plugin_attr` section of `conf/config.yaml`.
-
-| Name       | Type   | Default                      | Description                       |
-| ---------- | ------ | ---------------------------- | --------------------------------- |
-| export_uri | string | "/apisix/prometheus/metrics" | uri to get the prometheus metrics |
-
-Here is an example:
+## Using Grafana to graph the metrics
 
-```yaml
-plugin_attr:
-  prometheus:
-    export_uri: /apisix/metrics
-```
+Metrics exported by the `prometheus` Plugin can be graphed in Grafana using a drop in dashboard.
 
-## Grafana dashboard
-
-Metrics exported by the plugin can be graphed in Grafana using a drop in dashboard.
-
-Downloads [Grafana dashboard meta](https://github.com/apache/apisix/blob/master/docs/assets/other/json/apisix-grafana-dashboard.json) and imports it to Grafana。
-
-Or you can goto [Grafana official](https://grafana.com/grafana/dashboards/11719) for `Grafana` meta data.
+To set it up, download [Grafana dashboard meta](https://github.com/apache/apisix/blob/master/docs/assets/other/json/apisix-grafana-dashboard.json) and import it in Grafana. Or, you can go to [Grafana official](https://grafana.com/grafana/dashboards/11719) for Grafana metadata.
 
 ![Grafana chart-1](../../../assets/images/plugin/grafana-1.png)
 
@@ -153,52 +158,57 @@ Or you can goto [Grafana official](https://grafana.com/grafana/dashboards/11719)
 
 ## Available HTTP metrics
 
-* `Status codes`: HTTP status code returned from upstream services. These status code available per service and across all services.
+The following metrics are exported by the `prometheus` Plugin:
 
-    Attributes：
+- Status code: HTTP status code returned from Upstream services. They are available for a single service and across all services.
 
-    | Name         | Description         |
-    | -------------| --------------------|
-    | code         | The HTTP status code returned by the upstream service. |
-    | route        | The `route_id` of the matched route is request. If it does not match, the default value is an empty string. |
-    | matched_uri  | The `uri` of the route matching the request, if it does not match, the default value is an empty string. |
-    | matched_host | The `host` of the route that matches the request. If it does not match, the default value is an empty string. |
-    | service      | The `service_id` of the route matched by the request. When the route lacks service_id, the default is `$host`. |
-    | consumer     | The `consumer_name` of the consumer that matches the request. If it does not match, the default value is an empty string. |
-    | node         | The `ip` of the upstream node. |
+  The available attributes are:
 
-* `Bandwidth`: Total Bandwidth (egress/ingress) flowing through APISIX. The total bandwidth of per service can be counted.
+  | Name         | Description                                                                                                                   |
+  |--------------|-------------------------------------------------------------------------------------------------------------------------------|
+  | code         | HTTP status code returned by the upstream service.                                                                            |
+  | route        | `route_id` of the matched Route with request. Defaults to an empty string if the Routes don't match.                          |
+  | matched_uri  | `uri` of the Route matching the request. Defaults to an empty string if the Routes don't match.                               |
+  | matched_host | `host` of the Route matching the request. Defaults to an empty string if the Routes don't match.                              |
+  | service      | `service_id` of the Route matching the request. If the Route does not have a `service_id` configured, it defaults to `$host`. |
+  | consumer     | `consumer_name` of the Consumer matching the request. Defaults to an empty string if it does not match.                       |
+  | node         | IP address of the Upstream node.                                                                                              |
 
-    Attributes：
+- Bandwidth: Total amount of traffic (ingress and egress) flowing through APISIX. Total bandwidth of a service can also be obtained.
 
-    | Name         | Description |
-    | -------------| ------------- |
-    | type         | The type of bandwidth(egress/ingress). |
-    | route        | The `route_id` of the matched route is request. If it does not match, the default value is an empty string.. |
-    | service      | The `service_id` of the route matched by the request. When the route lacks service_id, the default is `$host`. |
-    | consumer     | The `consumer_name` of the consumer that matches the request. If it does not match, the default value is an empty string. |
-    | node         | The `ip` of the upstream node. |
+  The available attributes are:
 
-* `etcd reachability`: A gauge type with a value of 0 or 1, representing if etcd can be reached by a APISIX or not, where `1` is available, and `0` is unavailable.
-* `Connections`: Various Nginx connection metrics like active, reading, writing, and number of accepted connections.
-* `Batch process entries`: A gauge type, when we use plugins and the plugin used batch process to send data, such as: sys logger, http logger, sls logger, tcp logger, udp logger and zipkin, then the entries which hasn't been sent in batch process will be counted in the metrics.
-* `Latency`: The per service histogram of request time in different dimensions.
+  | Name     | Description                                                                                                                   |
+  |----------|-------------------------------------------------------------------------------------------------------------------------------|
+  | type     | Type of traffic (egress/ingress).                                                                                             |
+  | route    | `route_id` of the matched Route with request. Defaults to an empty string if the Routes don't match.                          |
+  | service  | `service_id` of the Route matching the request. If the Route does not have a `service_id` configured, it defaults to `$host`. |
+  | consumer | `consumer_name` of the Consumer matching the request. Defaults to an empty string if it does not match.                       |
+  | node     | IP address of the Upstream node.                                                                                              |
+
+- etcd reachability: A gauge type representing whether etcd can be reached by APISIX. A value of `1` represents reachable and `0` represents unreachable.
+- Connections: Nginx connection metrics like active, reading, writing, and number of accepted connections.
+- Batch process entries: A gauge type useful when Plugins like [syslog](./syslog.md), [http-logger](./http-logger.md), [tcp-logger](./tcp-logger.md), [udp-logger](./udp-logger.md), and [zipkin](./zipkin.md) use batch process to send data. Entries that hasn't been sent in batch process will be counted in the metrics.
+- Latency: Histogram of the request time per service in different dimensions.
 
-    Attributes：
+  The available attributes are:
 
-    | Name      | Description |
-    | ----------| ------------- |
-    | type      | The value can be `apisix`, `upstream` or `request`, which means http latency caused by apisix, upstream, or their sum. |
-    | service   | The `service_id` of the route matched by the request. When the route lacks service_id, the default is `$host`. |
-    | consumer  | The `consumer_name` of the consumer that matches the request. If it does not match, the default value is an empty string. |
-    | node      | The `ip` of the upstream node. |
+  | Name     | Description                                                                                                                         |
+  |----------|-------------------------------------------------------------------------------------------------------------------------------------|
+  | type     | Value can be one of `apisix`, `upstream`, or `request`. This translates to latency caused by APISIX, Upstream, or both (their sum). |
+  | service  | `service_id` of the Route matching the request. If the Route does not have a `service_id` configured, it defaults to `$host`.       |
+  | consumer | `consumer_name` of the Consumer matching the request. Defaults to an empty string if it does not match.                             |
+  | node     | IP address of the Upstream node.                                                                                                    |
 
-* `Info`: the information of APISIX node.
+- Info: Information about the APISIX node.
 
-Here is the original metric data of APISIX:
+Here are the original metrics from APISIX:
+
+```shell
+curl http://127.0.0.1:9091/apisix/prometheus/metrics
+```
 
 ```shell
-$ curl http://127.0.0.1:9091/apisix/prometheus/metrics
 # HELP apisix_bandwidth Total bandwidth in bytes consumed per service in Apisix
 # TYPE apisix_bandwidth counter
 apisix_bandwidth{type="egress",route="",service="",consumer="",node=""} 8417
@@ -266,8 +276,7 @@ apisix_node_info{hostname="desktop-2022q8f-wsl"} 1
 
 ## Disable Plugin
 
-Remove the corresponding json configuration in the plugin configuration to disable `prometheus`.
-APISIX plugins are hot-reloaded, therefore no need to restart APISIX.
+To disable the `prometheus` Plugin, you can delete the corresponding JSON configuration from the Plugin configuration. APISIX will automatically reload and you do not have to restart for this to take effect.
 
 ```shell
 curl http://127.0.0.1:9080/apisix/admin/routes/1  -H 'X-API-KEY: edd1c9f034335f136f87ad84b625c8f1' -X PUT -d '