docs: enabling MD045 - images with alternate text (#5280)

Author: bisakhmondal

.markdownlint.yml

@@ -31,5 +31,4 @@ MD034: false
 MD036: false
 MD040: false
 MD041: false
-MD045: false
 MD046: false

docs/en/latest/aws.md

@@ -27,7 +27,7 @@ title: Running APISIX in AWS with AWS CDK
 
 This reference architecture walks you through building **APISIX** as a serverless container API Gateway on top of AWS Fargate with AWS CDK.
 
-![](../../assets/images/aws-fargate-cdk.png)
+![Apache APISIX Serverless Architecture](../../assets/images/aws-fargate-cdk.png)
 
 ## Generate an AWS CDK project with `projen`
 
@@ -208,15 +208,15 @@ Address: 44.226.102.63
 
 Configure the IP addresses returned as your upstream nodes in your **APISIX** dashboard followed by the **Services** and **Routes** configuration. Let's say we have a `/index.php` as the URI for the first route for our first **Service** from the **Upstream** IP addresses.
 
-![](../../assets/images/aws-nlb-ip-addr.png)
-![](../../assets/images/aws-define-service.png)
-![](../../assets/images/aws-define-route.png)
+![upstream with AWS NLB IP addresses](../../assets/images/aws-nlb-ip-addr.png)
+![service with created upstream](../../assets/images/aws-define-service.png)
+![define route with service and uri](../../assets/images/aws-define-route.png)
 
 ## Validation
 
 OK. Let's test the `/index.php` on `{apiSix.ApiSixServiceServiceURL}/index.php`
 
-![](../../assets/images/aws-caddy-php-welcome-page.png)
+![Testing Apache APISIX on AWS Fargate](../../assets/images/aws-caddy-php-welcome-page.png)
 
 Now we have been successfully running **APISIX** in AWS Fargate as serverless container API Gateway service.
 

docs/en/latest/discovery.md

@@ -25,7 +25,7 @@ title: Integration service discovery registry
 
 When system traffic changes, the number of servers of the upstream service also increases or decreases, or the server needs to be replaced due to its hardware failure. If the gateway maintains upstream service information through configuration, the maintenance costs in the microservices architecture pattern are unpredictable. Furthermore, due to the untimely update of these information, will also bring a certain impact for the business, and the impact of human error operation can not be ignored. So it is very necessary for the gateway to automatically get the latest list of service instances through the service registry。As shown in the figure below：
 
-![](../../assets/images/discovery.png)
+![discovery through service registry](../../assets/images/discovery.png)
 
 1. When the service starts, it will report some of its information, such as the service name, IP, port and other information to the registry. The services communicate with the registry using a mechanism such as a heartbeat, and if the registry and the service are unable to communicate for a long time, the instance will be cancel.When the service goes offline, the registry will delete the instance information.
 2. The gateway gets service instance information from the registry in near-real time.

docs/en/latest/discovery/consul_kv.md

@@ -26,7 +26,7 @@ title: consul_kv
 For users who used [nginx-upsync-module](https://github.com/weibocom/nginx-upsync-module) and consul key value for service discovery way, as we Weibo Mobile Team, maybe need it.
 
 Thanks to @fatman-x guy, who developed this module, called `consul_kv`, and its worker process data flow is below:
-![](https://user-images.githubusercontent.com/548385/107141841-6ced3e00-6966-11eb-8aa4-bc790a4ad113.png)
+![consul kv module data flow diagram](https://user-images.githubusercontent.com/548385/107141841-6ced3e00-6966-11eb-8aa4-bc790a4ad113.png)
 
 ## Configuration for discovery client
 

docs/en/latest/plugins/hmac-auth.md

@@ -29,8 +29,10 @@ title: hmac-auth
 - [How To Enable](#how-to-enable)
 - [Test Plugin](#test-plugin)
   - [generate signature:](#generate-signature)
+  - [Request body checking](#request-body-checking)
   - [Use the generated signature to try the request](#use-the-generated-signature-to-try-the-request)
 - [Custom header key](#custom-header-key)
+  - [Enable request body checking](#enable-request-body-checking)
 - [Disable Plugin](#disable-plugin)
 - [Generate Signature Examples](#generate-signature-examples)
 
@@ -76,10 +78,10 @@ curl http://127.0.0.1:9080/apisix/admin/consumers -H 'X-API-KEY: edd1c9f034335f1
 The default `keep_headers` is false and `encode_uri_params` is true.
 
 You can visit the dashboard to complete the above operations through the web interface, first add a consumer:
-![](../../../assets/images/plugin/hmac-auth-1.png)
+![create a consumer](../../../assets/images/plugin/hmac-auth-1.png)
 
 Then add the hmac-auth plugin to the consumer page:
-![](../../../assets/images/plugin/hmac-auth-2.png)
+![enable hmac plugin](../../../assets/images/plugin/hmac-auth-2.png)
 
 2. add a Route or add a Service, and enable the `hmac-auth` plugin
 

docs/en/latest/plugins/jwt-auth.md

@@ -25,8 +25,11 @@ title: jwt-auth
 
 - [**Name**](#name)
 - [**Attributes**](#attributes)
+- [**API**](#api)
 - [**How To Enable**](#how-to-enable)
 - [**Test Plugin**](#test-plugin)
+    - [get the token in `jwt-auth` plugin:](#get-the-token-in-jwt-auth-plugin)
+    - [try request with token](#try-request-with-token)
 - [**Disable Plugin**](#disable-plugin)
 
 ## Name
@@ -111,14 +114,14 @@ You can use [APISIX Dashboard](https://github.com/apache/apisix-dashboard) to co
 
 1. Add a Consumer through the web console:
 
-![](../../../assets/images/plugin/jwt-auth-1.png)
+![create a consumer](../../../assets/images/plugin/jwt-auth-1.png)
 
 then add jwt-auth plugin in the Consumer page:
-![](../../../assets/images/plugin/jwt-auth-2.png)
+![enable jwt plugin](../../../assets/images/plugin/jwt-auth-2.png)
 
 2. Create a Route or Service object and enable the jwt-auth plugin:
 
-![](../../../assets/images/plugin/jwt-auth-3.png)
+![enable jwt from route or service](../../../assets/images/plugin/jwt-auth-3.png)
 
 ## Test Plugin
 

docs/en/latest/plugins/key-auth.md

@@ -69,10 +69,10 @@ curl http://127.0.0.1:9080/apisix/admin/consumers -H 'X-API-KEY: edd1c9f034335f1
 ```
 
 You also can complete the above operation through the web interface, first add a route:
-![](../../../assets/images/plugin/key-auth-1.png)
+![create a consumer](../../../assets/images/plugin/key-auth-1.png)
 
 Then add key-auth plugin:
-![](../../../assets/images/plugin/key-auth-2.png)
+![enable key-auth plugin](../../../assets/images/plugin/key-auth-2.png)
 
 2. creates a route or service object, and enable plugin `key-auth`.
 

docs/en/latest/plugins/limit-conn.md

@@ -78,7 +78,7 @@ curl http://127.0.0.1:9080/apisix/admin/routes/1 -H 'X-API-KEY: edd1c9f034335f13
 ```
 
 You also can complete the above operation through the web interface, first add a route, then add limit-conn plugin:
-![](../../../assets/images/plugin/limit-conn-1.png)
+![enable limit-conn plugin](../../../assets/images/plugin/limit-conn-1.png)
 
 ## Test Plugin
 

docs/en/latest/plugins/prometheus.md

@@ -84,11 +84,11 @@ You can use [APISIX Dashboard](https://github.com/apache/apisix-dashboard) to co
 
 First, add a Route:
 
-![](../../../assets/images/plugin/prometheus-1.png)
+![create a route](../../../assets/images/plugin/prometheus-1.png)
 
 Then add prometheus plugin:
 
-![](../../../assets/images/plugin/prometheus-2.png)
+![enable prometheus plugin](../../../assets/images/plugin/prometheus-2.png)
 
 ## How to fetch the metric data
 
@@ -114,9 +114,9 @@ scrape_configs:
 
 And we can check the status at prometheus console:
 
-![](../../../assets/images/plugin/prometheus01.png)
+![checking status on prometheus dashboard](../../../assets/images/plugin/prometheus01.png)
 
-![](../../../assets/images/plugin/prometheus02.png)
+![prometheus apisix in-depth metric view](../../../assets/images/plugin/prometheus02.png)
 
 ## How to specify export uri
 
@@ -142,13 +142,13 @@ Downloads [Grafana dashboard meta](https://github.com/apache/apisix/blob/master/
 
 Or you can goto [Grafana official](https://grafana.com/grafana/dashboards/11719) for `Grafana` meta data.
 
-![](../../../assets/images/plugin/grafana-1.png)
+![Grafana chart-1](../../../assets/images/plugin/grafana-1.png)
 
-![](../../../assets/images/plugin/grafana-2.png)
+![Grafana chart-2](../../../assets/images/plugin/grafana-2.png)
 
-![](../../../assets/images/plugin/grafana-3.png)
+![Grafana chart-3](../../../assets/images/plugin/grafana-3.png)
 
-![](../../../assets/images/plugin/grafana-4.png)
+![Grafana chart-4](../../../assets/images/plugin/grafana-4.png)
 
 ### Available metrics
 

docs/en/latest/plugins/response-rewrite.md

@@ -131,6 +131,6 @@ The `response-rewrite` plugin has been disabled now. It works for other plugins.
 
 `ngx.exit` will interrupt the execution of the current request and return status code to Nginx.
 
-![](https://cdn.jsdelivr.net/gh/Miss-you/img/picgo/20201113010623.png)
+![ngx.edit tabular overview](https://cdn.jsdelivr.net/gh/Miss-you/img/picgo/20201113010623.png)
 
 However, if you execute `ngx.exit` during the access phase, it only interrupts the request processing phase, and the response phase will still process it, i.e. if you configure the `response-rewrite` plugin, it will force overwriting of your response information (e.g. response status code).