(apisix-website) 01/01: fix(docs/blog): inline image width syntax

[yilialin]

This is an automated email from the ASF dual-hosted git repository.

yilialin pushed a commit to branch fix-inline-image-width-syntax
in repository https://gitbox.apache.org/repos/asf/apisix-website.git

commit 41d6d10750b740b5b9b24d6cab5d7e5a5e42a092
Author: Yilia Lin <114121331+yilial...@users.noreply.github.com>
AuthorDate: Mon Dec 22 15:01:00 2025 +0800

    fix(docs/blog): inline image width syntax
---
 .../blog/2025/12/19/apisix-ingress-controller-2-0-release.md | 12 ++++++++----
 1 file changed, 8 insertions(+), 4 deletions(-)

diff --git a/blog/en/blog/2025/12/19/apisix-ingress-controller-2-0-release.md 
b/blog/en/blog/2025/12/19/apisix-ingress-controller-2-0-release.md
index b5fb8f1ec3e..f79841c32f9 100644
--- a/blog/en/blog/2025/12/19/apisix-ingress-controller-2-0-release.md
+++ b/blog/en/blog/2025/12/19/apisix-ingress-controller-2-0-release.md
@@ -13,7 +13,7 @@ keywords:
   - Apache APISIX
 description: Apache APISIX Ingress Controller 2.0 delivers comprehensive 
Gateway API support, flexible multi-data-plane deployment, and etcd-free 
operation for robust, scalable Kubernetes traffic management.
 tags: [Community]
-image: https://static.apiseven.com/2022/10/19/634f6677742a1.png
+image: 
https://static.api7.ai/uploads/2025/12/22/q17SNFmp_apisix-ingress-controller-cover.webp
 ---
 
 > Apache APISIX Ingress Controller 2.0 is officially released. It delivers 
 > comprehensive Gateway API support, flexible multi-data-plane deployment, and 
 > etcd-free operation for robust, scalable Kubernetes traffic management.
@@ -60,9 +60,9 @@ This release introduces flexible deployment options 
supporting multiple data pla
 
 In the traditional deployment approach, APISIX uses etcd as its configuration 
center, allowing administrators to dynamically manage routes, upstreams, and 
other resources through RESTful APIs. It supports distributed cluster 
deployments with real-time configuration synchronization.
 
-<div align="center">
-<img alt="APISIX Ingress Controller Admin API Mode" style="width: 60%" 
src="https://static.api7.ai/uploads/2025/12/19/lX98Vcaj_apisix-ingress-controller-2-admin-api-mode.webp";></img>
-</div>
+<p align="center">
+  <img width="550" alt="APISIX Ingress Controller Admin API Mode" 
src="[https://static.api7.ai/uploads/2025/05/13/Pk221A8e_2-honor-plugins-2.webp](https://static.api7.ai/uploads/2025/12/19/lX98Vcaj_apisix-ingress-controller-2-admin-api-mode.webp)"
 />
+</p>
 
 #### Standalone Mode
 
@@ -74,6 +74,10 @@ This mode is particularly suitable for Kubernetes 
environments and single-node d
 <img alt="APISIX Ingress Controller Standalone Mode" style="width: 60%" 
src="https://static.api7.ai/uploads/2025/12/19/8IxjQgCP_apisix-ingress-controller-2-standalone-mode.webp";></img>
 </div>
 
+<p align="center">
+  <img width="550" alt="APISIX Ingress Controller Standalone Mode" 
src="[[https://static.api7.ai/uploads/2025/05/13/Pk221A8e_2-honor-plugins-2.webp](https://static.api7.ai/uploads/2025/12/19/lX98Vcaj_apisix-ingress-controller-2-admin-api-mode.webp](https://static.api7.ai/uploads/2025/12/19/8IxjQgCP_apisix-ingress-controller-2-standalone-mode.webp))"
 />
+</p>
+
 This multi-mode strategy empowers organizations to tailor their ingress 
architecture to diverse requirements without sacrificing manageability or 
control.
 
 ## Conclusion