[apisix-website] branch master updated: fix: update xRPC blog incorrect images (#856)

[ju...@apache.org]

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

juzhiyuan pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/apisix-website.git


The following commit(s) were added to refs/heads/master by this push:
     new baae9ff  fix: update xRPC blog incorrect images (#856)
baae9ff is described below

commit baae9ff7b659babd3e43214296a065661ec22409
Author: Sylvia <39...@users.noreply.github.com>
AuthorDate: Tue Jan 25 17:57:26 2022 +0800

    fix: update xRPC blog incorrect images (#856)
---
 website/blog/2022/01/21/apisix-xrpc-details-and-miltilingual.md       | 4 ++--
 .../2022/01/21/apisix-xrpc-details-and-miltilingual.md                | 4 ++--
 2 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/website/blog/2022/01/21/apisix-xrpc-details-and-miltilingual.md b/website/blog/2022/01/21/apisix-xrpc-details-and-miltilingual.md
index 702dcfc..c94c73b 100644
--- a/website/blog/2022/01/21/apisix-xrpc-details-and-miltilingual.md
+++ b/website/blog/2022/01/21/apisix-xrpc-details-and-miltilingual.md
@@ -63,7 +63,7 @@ With the xRPC protocol framework in place, what scenarios can it address? Here a
 
 Of course, there are many similar application scenarios, and we hope that after the release of the feature, you can experience and practice more in the actual application. The process of invoking xPRC is shown in the following diagram.
 
-![Invoke process](https://static.apiseven.com/202108/1642733132478-386c0573-d9df-4c3b-b557-14833fe3fec1.png)
+![Invoke process](https://static.apiseven.com/202108/1643103835579-d215a120-f62e-4ba5-aa14-59ea3d38a429.png)
 
 Once the upstream services are taken over by Apache APISIX, the different upstream application services can be managed in a unified manner. Functions such as logging, monitoring, security, and troubleshooting can all be accomplished through a standardized set of policies.
 
@@ -71,7 +71,7 @@ Once the upstream services are taken over by Apache APISIX, the different upstre
 
 The current design of the Apache APISIX xRPC framework is initially divided into 5 phases.
 
-![5 phases about xRPC](https://static.apiseven.com/202108/1642733218120-933f90a1-49e5-4c3a-b7cc-9670ba4f6911.png)
+![5 phases about xRPC](https://static.apiseven.com/202108/1643103835583-40afb0a0-ec20-40e8-84de-b34afee2724c.png)
 
 - Phase 1: Read Read data and protocol decoding.
 - Phase 2: Access Phase Access phase. Provide plug-in access function, which can realize the demand scenarios of security, flow control and access.
diff --git a/website/i18n/zh/docusaurus-plugin-content-blog/2022/01/21/apisix-xrpc-details-and-miltilingual.md b/website/i18n/zh/docusaurus-plugin-content-blog/2022/01/21/apisix-xrpc-details-and-miltilingual.md
index 9e81a75..0a289e3 100644
--- a/website/i18n/zh/docusaurus-plugin-content-blog/2022/01/21/apisix-xrpc-details-and-miltilingual.md
+++ b/website/i18n/zh/docusaurus-plugin-content-blog/2022/01/21/apisix-xrpc-details-and-miltilingual.md
@@ -63,7 +63,7 @@ xRPC 从字面角度来分析，即 X 为协议资源的抽象代表。而 RPC 
 
 当然，类似的应用场景还很多，也希望在功能发布之后，大家多多在实际的应用过程中去体验和实践。接入 xPRC 后的调用过程如下图所示。
 
-![调用过程](https://static.apiseven.com/202108/1642733132478-386c0573-d9df-4c3b-b557-14833fe3fec1.png)
+![调用过程](https://static.apiseven.com/202108/1643103835579-d215a120-f62e-4ba5-aa14-59ea3d38a429.png)
 
 一旦通过 Apache APISIX 完成了上游服务的接管，就可以把上游不同的应用服务进行统一化管理。类似日志输出、监控、安全还有问题排查等功能，都可以通过一套标准化的策略来完成。
 
@@ -71,7 +71,7 @@ xRPC 从字面角度来分析，即 X 为协议资源的抽象代表。而 RPC 
 
 目前 Apache APISIX xRPC 框架的设计，初步划分为 5 个阶段。
 
-![计划实现阶段图](https://static.apiseven.com/202108/1642733218120-933f90a1-49e5-4c3a-b7cc-9670ba4f6911.png)
+![计划实现阶段图](https://static.apiseven.com/202108/1643103835583-40afb0a0-ec20-40e8-84de-b34afee2724c.png)
 
 - 阶段一：Read 读取数据与协议解码。
 - 阶段二：Access Phase 准入阶段。提供插件接入功能，可实现安全、流控和准入等需求场景。