You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@apisix.apache.org by GitBox <gi...@apache.org> on 2021/11/01 09:38:52 UTC

[GitHub] [apisix-website] yzeng25 commented on a change in pull request #680: docs: translate blogs on 08/2021

yzeng25 commented on a change in pull request #680:
URL: https://github.com/apache/apisix-website/pull/680#discussion_r740051050



##########
File path: website/blog/2021/08/10/apisix-nginx.md
##########
@@ -164,13 +164,13 @@ local function init(env)
     local conf_render = template.compile(ngx_tpl)
     local ngxconf = conf_render(sys_conf)
 
-    local ok, err = util.write_file(env.apisix_home .. "/conf/nginx.conf",
+    local ok, err = util.write_file(env.apisix_home . "/conf/nginx.conf",
                                     ngxconf)

Review comment:
       is it a repeated line here? please delete if it is

##########
File path: website/blog/2021/08/11/interview-TuZhengsong.md
##########
@@ -1,145 +1,145 @@
 ---
-title: "从新手村出来,我在 Apache APISIX 社区发出了第一个 PR"
-author: "Apache APISIX 社区"
+title: I issued my first PR in the Apache APISIX community
+author: Apache APISIX
 authorURL: "https://github.com/Yangxiamao"
 authorImageURL: "https://avatars.githubusercontent.com/u/47442074?v=4"
 keywords:
-- API 网关
+- API Gateway
 - APISIX
 - Apache APISIX
-- 开源社区
-- 开源项目
-description: 这篇采访稿讲述了屠正松从开源社区小白成长为 Apache 顶级开源项目 APISIX committer 的历程。屠正松(GitHub ID:tzssangglass)因深度参与 Apache APISIX 的开发,在社区中贡献很多,2021 年 7 月 22 日被推选为 Apache APISIX committer。
+- Community
+- Open Source
+description: "This interview is about Zhengsong Tu's journey from an open source community nerd to an APISIX committer for Apache's top open source project. Zhengsong Tu (GitHub ID: tzssangglass) was elected as an Apache APISIX committer on July 22, 2021 for his deep involvement in Apache APISIX development and his many contributions to the community."
 tags: [Interview]
 ---
 
-> 这篇采访稿讲述了屠正松从开源社区小白成长为 Apache 顶级开源项目 APISIX committer 的历程。屠正松(GitHub ID:tzssangglass)因深度参与 Apache APISIX 的开发,在社区中贡献很多,2021 年 7 月 22 日被推选为 Apache APISIX committer。
+> This interview is about Zhengsong Tu's journey from an open source community nerd to an APISIX committer for Apache's top open source project. Zhengsong Tu (GitHub ID: tzssangglass) was elected as an Apache APISIX committer on July 22, 2021 for his deep involvement in Apache APISIX development and his many contributions to the community.
 
 <!--truncate-->
 
-> 当我看到那个 issue 后,就有种强烈的想要参与到社区的冲动。看了社区的新手指南后,我像从新手村出来的勇者,准备打怪。
+> When I saw that issue, I had a strong urge to get involved in the community. After reading the community's newbie guide, I was like a brave man coming out of the newbie village, ready to fight.
 >
-> —— Apache APISIX committer 屠正松
+> -- Zhengsong Tu, Apache APISIX committer
 
-历时 282 天,屠正松(GitHub ID:tzssangglass)从开源社区的小白成长为了 Apache APISIX 的 committer。
+In 282 days, Zhengsong Tu (GitHub ID: tzssangglass) has grown from an open source community nerd to an Apache APISIX committer.
 
 ![Apache APISIX committer tzssangglass github](/img/blog_img/2021-08-11-1.webp)
 
-屠正松因深度参与 Apache APISIX 的开发,在社区中贡献很多,2021 年 7 月 22 日被推选为 Apache APISIX committer。
+Zhengsong Tu was elected as Apache APISIX committer on July 22, 2021 for his deep involvement in Apache APISIX development and many contributions in the community.
 
-在一个平淡的下午,我们和正松连线聊了聊。因为疫情关系,居住在南京的他已经多日未外出。在没有和他聊天之前,我没有想到,胡子拉碴的他,竟然走过了这么曲折的路。
+On an uneventful afternoon, we chatted with Zhengsong by phone. Because of the epidemic, he has not been out for many days in Nanjing. Before I talked to him, I didn't expect that the bearded man had traveled such a winding road.
 
-## 大学,我的大学
+## University, my university
 
-> 我大学的时候学的是通信工程,每天最开心的事就是踢球。现在有时候会想,如果能带着现在的记忆回到大学时光就好了。
+> When I was in college, I studied communication engineering, and the happiest thing I did every day was to play soccer. Now sometimes I think that it would be nice to go back to my college days with the memories I have now.
 
-正松在大学期间里面其实没怎么接触过编程,他当年其实有 C 语言的编程课,但是因为忙着踢球,挂科了。可是,他挂科之后的补考也没过,导致重修。最尴尬的是,他重修也没过,后来怎么办呢?毕业之前还有毕业清考。这可不能再挂了,于是正松就去图书馆去借了一本 C 语言的书来看。
+Zhengsong actually didn't have much contact with programming during his college years, he actually had a C programming class, but he failed it because he was too busy playing soccer. However, he failed a make-up exam after failing the class, resulting in a retake. The most embarrassing thing is that he failed the retake as well, so what did he do afterwards? There was a graduation clearing exam before graduation. This can not be failed again, so Zhengsong went to the library to borrow a C language book to read.
 
-“我当时心想,C 语言真的这么难吗?”正松说。
+"I was thinking, "Is C really that hard?" Zhengsong said.
 
-然后他就一直看一直看,看着看着就突然发现编程好像有那么点意思,他看懂了!最后他在毕业前顺利通过了考试。在毕业之后,找到了一份做程序员的工作。
+Then he kept reading and reading and reading, and suddenly he realized that programming seemed to have some meaning, and he understood it! He finally passed the exam before graduating. After graduation, he found a job as a programmer.
 
-“我本来都准备毕业回家找个厂上班了。”,他半开玩笑地说。
+"I was ready to graduate and go home and find a factory to work." , he said half-jokingly.
 
-彼时,他可能不会想到如今的他会成为数个知名开源项目的 developer,参与一些支撑着千万级并发流量的基础设施的开发。
+At that time, he probably wouldn't have thought that today he would be the developer of several well-known open source projects, and involved in the development of some infrastructure that supports millions of concurrent traffic.
 
-## 出象牙塔记
+## Out of the Ivory Tower
 
-> 在工业界,真实的业务场景和学校里学的很不一样的
+> In industry, the real business scenario is very different from what you learn in school.
 
-正松的第一份工作就职于一家做穿戴设备的创业公司,从事智能手环的研发工作。正松和他的前同事们需要通过处理从智能手环上的获取的各种传感器数据,来完成对用户的心率、运动量、血压等的监测。
+Zhengsong's first job was at a wearable device startup, working on the development of smart bracelets. Zhengsong and his former colleagues had to process various sensor data from the smart bracelet to monitor the user's heart rate, exercise, blood pressure and so on.
 
-“工作蛮好玩的,因为在工业界,真实的业务场景和学校里学的很不一样的,很多东西都得从头开始学”,正松说。
+"It was fun because in industry, the real business scenario is very different from what you learn in school, and a lot of things have to be learned from scratch," Masatsu said.

Review comment:
       ```suggestion
   "It was fun because in industry, the real business scenario is very different from what you learn in school, and a lot of things have to be learned from scratch," Zhengsong said.
   ```

##########
File path: website/blog/2021/08/06/using-apache-apisix-to-improve-the-observability-of-nginx.md
##########
@@ -1,213 +1,213 @@
 ---
-title: "如何利用 Apache APISX 提升 Nginx 的可观测性"
-author: "金卫"
+title: How to Improve the Observability of Nginx with Apache APISX
+author: Wei Jin
 authorURL: "https://github.com/gxthrj"
 authorImageURL: "https://avatars.githubusercontent.com/u/4413028?v=4"
 keywords:
-- API 网关
+- API Gateway
 - APISIX
 - Apache APISIX
 - Nginx
-- 可观测性
-description: 最佳实践:本文将从 Nginx 可观测性、Apache APISIX 与 Nginx 的关系、Apache APISIX 可观测性,以及结合 Apache SkyWalking 进一步提升可观测性这些方面分享关于可观测性的方案与实践。
+- observability
+description: "Best Practices: This article shares solutions and practices for observability in the context of Nginx observability, the relationship between Apache APISIX and Nginx, Apache APISIX observability, and further enhancing observability with Apache SkyWalking."
 tags: [Practical Case]
 ---
 
-> 本文将从 Nginx 可观测性、Apache APISIX 与 Nginx 的关系、Apache APISIX 可观测性,以及结合 Apache SkyWalking 进一步提升可观测性这些方面分享关于可观测性的方案与实践。
+> This article shares solutions and practices for observability in the context of Nginx observability, the relationship between Apache APISIX and Nginx, Apache APISIX observability, and further enhancing observability in conjunction with Apache SkyWalking.
 
 <!--truncate-->
 
-## 概述
+## Overview
 
-“可观测性“是一种度量手段,方便掌握基础设施、系统平台或者应用程序的运行状况。常见的手段是收集 metrics、logging 和 tracing 及 events 数据,可以帮助开发人员和运维人员检测、调查、预警和纠正系统问题。
+"Observability" is a metric that allows you to keep track of how your infrastructure, system platform, or application is performing. Commonly, metrics, logging, and tracing and events data are collected to help developers and operations staff detect, investigate, alert, and correct system problems.
 
-本文将从 Nginx 可观测性、Apache APISIX 与 Nginx 的关系、Apache APISIX 可观测性,以及结合 Apache SkyWalking 进一步提升可观测性这些方面分享关于可观测性的方案与实践。
+In this article, we will share solutions and practices for observability in the context of Nginx observability, the relationship between Apache APISIX and Nginx, Apache APISIX observability, and further observability improvements in conjunction with Apache SkyWalking.
 
-## Nginx 的可观测性
+## Nginx Observability
 
-### Nginx 常见监控方式
+### Common monitoring methods for Nginx
 
-Nginx 在一定程度上能够做到可观测,以下罗列出 Nginx 的常见监控方式:
+Nginx is observable to some extent, and the following is a list of common monitoring methods for Nginx.
 
 1. ngx_http_stub_status_module
-2. VTS module + exporter + prometheus + grafana(如果 Nginx 版本比较低,需要引入 exporter )
+2. VTS module + exporter + prometheus + grafana (if you have a low version of Nginx, you need to introduce exporter)
 3. Nginx Amplify SaaS
 
 #### ngx_http_stub_status_module
 
-ngx_http_stub_status_module 主要收集实例级别的统计信息。
+The ngx_http_stub_status_module mainly collects instance-level statistics.
 
 #### VTS module
 
-VTS module 有 3 个比较明显的缺点:
+The VTS module has 3 obvious drawbacks.
 
-1. **安装复杂**:虽然 VTS module 能够采集指标,采集的指标类型也比较多,但是它的安装比较复杂。如果想要采用 VTS module,需要重新编译 Nginx,在编译 Nginx 之前加入 VTS moudle,完成编译后重新安装 Nginx 才可以正常使用 VTS。
+1. **Complex installation**: Although VTS module is able to collect metrics and collect more types of metrics, it is more complex to install. If you want to use the VTS module, you need to recompile Nginx, add the VTS moudle before compiling Nginx, and reinstall Nginx after completing the compilation before you can use VTS properly. 2.
 
-2. **扩展能力弱**:VTS 扩展能力分为两部分,一是在编译之前给 VTS 增加扩展;二是在编译之后增加扩展 —— 修改 nginx.conf 配置文件。通过修改 nginx.conf 文件来增加扩展会使 Nginx reload,生产环境直接 reload 或多或少会对业务产生一些影响。
+2. **Weak extensibility**: VTS extensibility is divided into two parts: one is to add extensions to VTS before compilation; the other is to add extensions after compilation -- modifying the nginx.conf configuration file. Adding extensions by modifying the nginx.conf file will cause Nginx to reload, and a direct reload of the production environment may have some impact on the business.
 
-3. **社区更新缓慢**:VTS module 最新的一次更新是在 2018 年,已经停摆 3 年了。
+3. **Slow community updates**: The last update to the VTS module was in 2018, and it has been down for 3 years.
 
 #### Nginx Amplify SaaS
 
-Nginx Amplify 是一个 SaaS 服务,Nginx Amplify 在远端提供服务,在 Nginx 服务之外安装 Agent。
-在 Nginx 之外安装采集模块,那么在采集指标上就会有限制,只能拿到 Nginx 暴露出来的信息,没有暴露的内部信息是拿不到的。
+Nginx Amplify is a SaaS service where Nginx Amplify provides services on the remote end and installs agents outside of the Nginx service.
+If you install the collection module outside of Nginx, you are limited in the metrics you can collect, and you can only get the information exposed by Nginx, not the internal information that is not exposed.
 
-另外,由于 Nginx Amplify SaaS 是一个 SaaS 服务,需要通过公网将采集到的数据传到服务端,这会带来一些安全隐患,同时把一些企业用户阻挡在外面。或许 Nginx Amplify 的目标群体是 Nginx plus 这样的企业用户,不是开源用户。
+In addition, because Nginx Amplify SaaS is a SaaS service, you need to transfer the collected data to the server through the public network, which can pose some security risks and keep some enterprise users out. Perhaps Nginx Amplify is targeted at enterprise users like Nginx plus, not open source users.
 
-另外,Nginx Amplify SaaS 社区也不活跃,已经停摆 2 年。
+Also, the Nginx Amplify SaaS community is not active and has been down for 2 years.
 
-### Nginx 的缺陷
+### Nginx's pitfalls
 
-Nginx 在 Events 收集上自身有缺陷,这里列举出两个问题:
+Nginx has its own flaws in Events collection, two of which are listed here.
 
-1. Nginx 基于 nginx.conf 进行配置,修改后通过 reload nginx.conf 文件使配置生效。除 reload 事件外,没有其他 Events 可用,我们无法得知每次修改文件的变化,如:起初只配置 1 个路由,修改文件增加 10 个路由,只有 reload 事件无法得知增加的到低是哪 10 个路由。
+Nginx is configured based on nginx.conf, which is reloaded after changes are made to the nginx.conf file. There are no Events available other than reload events, so we can't know what has changed each time we modify the file, e.g., if we start with one route and modify the file to add 10 routes, we won't know which 10 routes have been added with only reload events.
 
-2. Nginx 开源产品缺少主动健康检查。Nginx 是一个反向代理,真正的后端服务可能会出现重启、升级或者异常的情况,如果没有主动的健康检查,依靠被动检查,只能在流量出现异常的时候,才知道服务出了问题,这会丢掉很多 Events,导致上游 Events 事件信息不完整。
+Nginx is a reverse proxy, and the real backend service may be restarted, upgraded, or abnormal, so without active health checks and relying on passive checks, we will only know that something is wrong with the service when the traffic is abnormal, which will throw away many Events and result in incomplete information about upstream Events. .
 
-### Nginx 可观测性总结
+### Nginx Observability Summary
 
-Nginx 的开源版本没有提供非常好用的监控。虽然 Nginx 提供了一些监控工具,但这些工具的安装和配置非常复杂,几乎没有扩展性。可能这些工具的设计并不是为了可观测性,只是为了能看到指标或统计数据,方便定位问题。现在有各种可观测性设置类的产品,但是很难集成到 Nginx 上。
+The open source version of Nginx does not provide very good monitoring. Although Nginx provides some monitoring tools, they are very complex to install and configure and have little scalability. It is possible that these tools are not designed for observability, but simply to be able to see metrics or statistics to easily pinpoint problems. There are various observability setup products available, but they are difficult to integrate into Nginx.
 
-另外,Nginx 社区停滞不前,导致 Nginx 迭代速度慢。
+In addition, the Nginx community is stagnant, resulting in slow iterations of Nginx.
 
-## Apache APISIX 概述
+## Apache APISIX Overview
 
-### Apache APISIX 与 Nginx 的关系
+### Apache APISIX in relation to Nginx
 
-![Apache APISIX 与 Nginx 的关系](https://static.apiseven.com/202108/1630651158638-aba4e627-d2d6-4bf5-b431-61eb3913a296.png)
+! Relationship between [Apache APISIX and Nginx](https://static.apiseven.com/202108/1630651158638-aba4e627-d2d6-4bf5-b431-61eb3913a296.png)

Review comment:
       ```suggestion
   ![Relationship between Apache APISIX and Nginx](https://static.apiseven.com/202108/1630651158638-aba4e627-d2d6-4bf5-b431-61eb3913a296.png)
   ```

##########
File path: website/blog/2021/08/11/interview-TuZhengsong.md
##########
@@ -1,145 +1,145 @@
 ---
-title: "从新手村出来,我在 Apache APISIX 社区发出了第一个 PR"
-author: "Apache APISIX 社区"
+title: I issued my first PR in the Apache APISIX community
+author: Apache APISIX
 authorURL: "https://github.com/Yangxiamao"
 authorImageURL: "https://avatars.githubusercontent.com/u/47442074?v=4"
 keywords:
-- API 网关
+- API Gateway
 - APISIX
 - Apache APISIX
-- 开源社区
-- 开源项目
-description: 这篇采访稿讲述了屠正松从开源社区小白成长为 Apache 顶级开源项目 APISIX committer 的历程。屠正松(GitHub ID:tzssangglass)因深度参与 Apache APISIX 的开发,在社区中贡献很多,2021 年 7 月 22 日被推选为 Apache APISIX committer。
+- Community
+- Open Source
+description: "This interview is about Zhengsong Tu's journey from an open source community nerd to an APISIX committer for Apache's top open source project. Zhengsong Tu (GitHub ID: tzssangglass) was elected as an Apache APISIX committer on July 22, 2021 for his deep involvement in Apache APISIX development and his many contributions to the community."
 tags: [Interview]
 ---
 
-> 这篇采访稿讲述了屠正松从开源社区小白成长为 Apache 顶级开源项目 APISIX committer 的历程。屠正松(GitHub ID:tzssangglass)因深度参与 Apache APISIX 的开发,在社区中贡献很多,2021 年 7 月 22 日被推选为 Apache APISIX committer。
+> This interview is about Zhengsong Tu's journey from an open source community nerd to an APISIX committer for Apache's top open source project. Zhengsong Tu (GitHub ID: tzssangglass) was elected as an Apache APISIX committer on July 22, 2021 for his deep involvement in Apache APISIX development and his many contributions to the community.
 
 <!--truncate-->
 
-> 当我看到那个 issue 后,就有种强烈的想要参与到社区的冲动。看了社区的新手指南后,我像从新手村出来的勇者,准备打怪。
+> When I saw that issue, I had a strong urge to get involved in the community. After reading the community's newbie guide, I was like a brave man coming out of the newbie village, ready to fight.
 >
-> —— Apache APISIX committer 屠正松
+> -- Zhengsong Tu, Apache APISIX committer
 
-历时 282 天,屠正松(GitHub ID:tzssangglass)从开源社区的小白成长为了 Apache APISIX 的 committer。
+In 282 days, Zhengsong Tu (GitHub ID: tzssangglass) has grown from an open source community nerd to an Apache APISIX committer.
 
 ![Apache APISIX committer tzssangglass github](/img/blog_img/2021-08-11-1.webp)
 
-屠正松因深度参与 Apache APISIX 的开发,在社区中贡献很多,2021 年 7 月 22 日被推选为 Apache APISIX committer。
+Zhengsong Tu was elected as Apache APISIX committer on July 22, 2021 for his deep involvement in Apache APISIX development and many contributions in the community.
 
-在一个平淡的下午,我们和正松连线聊了聊。因为疫情关系,居住在南京的他已经多日未外出。在没有和他聊天之前,我没有想到,胡子拉碴的他,竟然走过了这么曲折的路。
+On an uneventful afternoon, we chatted with Zhengsong by phone. Because of the epidemic, he has not been out for many days in Nanjing. Before I talked to him, I didn't expect that the bearded man had traveled such a winding road.
 
-## 大学,我的大学
+## University, my university
 
-> 我大学的时候学的是通信工程,每天最开心的事就是踢球。现在有时候会想,如果能带着现在的记忆回到大学时光就好了。
+> When I was in college, I studied communication engineering, and the happiest thing I did every day was to play soccer. Now sometimes I think that it would be nice to go back to my college days with the memories I have now.
 
-正松在大学期间里面其实没怎么接触过编程,他当年其实有 C 语言的编程课,但是因为忙着踢球,挂科了。可是,他挂科之后的补考也没过,导致重修。最尴尬的是,他重修也没过,后来怎么办呢?毕业之前还有毕业清考。这可不能再挂了,于是正松就去图书馆去借了一本 C 语言的书来看。
+Zhengsong actually didn't have much contact with programming during his college years, he actually had a C programming class, but he failed it because he was too busy playing soccer. However, he failed a make-up exam after failing the class, resulting in a retake. The most embarrassing thing is that he failed the retake as well, so what did he do afterwards? There was a graduation clearing exam before graduation. This can not be failed again, so Zhengsong went to the library to borrow a C language book to read.
 
-“我当时心想,C 语言真的这么难吗?”正松说。
+"I was thinking, "Is C really that hard?" Zhengsong said.
 
-然后他就一直看一直看,看着看着就突然发现编程好像有那么点意思,他看懂了!最后他在毕业前顺利通过了考试。在毕业之后,找到了一份做程序员的工作。
+Then he kept reading and reading and reading, and suddenly he realized that programming seemed to have some meaning, and he understood it! He finally passed the exam before graduating. After graduation, he found a job as a programmer.
 
-“我本来都准备毕业回家找个厂上班了。”,他半开玩笑地说。
+"I was ready to graduate and go home and find a factory to work." , he said half-jokingly.
 
-彼时,他可能不会想到如今的他会成为数个知名开源项目的 developer,参与一些支撑着千万级并发流量的基础设施的开发。
+At that time, he probably wouldn't have thought that today he would be the developer of several well-known open source projects, and involved in the development of some infrastructure that supports millions of concurrent traffic.
 
-## 出象牙塔记
+## Out of the Ivory Tower
 
-> 在工业界,真实的业务场景和学校里学的很不一样的
+> In industry, the real business scenario is very different from what you learn in school.
 
-正松的第一份工作就职于一家做穿戴设备的创业公司,从事智能手环的研发工作。正松和他的前同事们需要通过处理从智能手环上的获取的各种传感器数据,来完成对用户的心率、运动量、血压等的监测。
+Zhengsong's first job was at a wearable device startup, working on the development of smart bracelets. Zhengsong and his former colleagues had to process various sensor data from the smart bracelet to monitor the user's heart rate, exercise, blood pressure and so on.
 
-“工作蛮好玩的,因为在工业界,真实的业务场景和学校里学的很不一样的,很多东西都得从头开始学”,正松说。
+"It was fun because in industry, the real business scenario is very different from what you learn in school, and a lot of things have to be learned from scratch," Masatsu said.
 
-有一天下班之后,这家公司的老板娘突然发了一条信息,说公司的员工暂时休假,什么时候上班等通知。
+One day after work, the owner of this company suddenly sent a message saying that the company's employees were on temporary leave and that they would wait to be notified when to work.
 
-正松当时就觉得不对劲,怎么好好的上着班,突然就休假了?然后他立马打开招聘软件,开始找新的工作。后来才知道,公司的老板跟供应商有合同纠纷,公司短暂停摆了。
+Masatsu felt something was wrong at that time, how to work well, suddenly on vacation? Then he immediately opened the recruitment software and started looking for a new job. Later, he found out that the owner of the company had a contract dispute with the supplier, and the company was briefly shut down.
 
-然后,正松便到另外一家公司从事后端业务开发的工作,学习业界规范、进一步增进技术。过了快一年,因为正松比较喜欢 Nginx、OpenResty、Netty 这类简洁和高性能的技术,他进入一家大公司的开发团队,从事中间件相关开发工作。
+Then, Masatsu went to another company to engage in back-end business development work, to learn the industry norms and further improve technology. After almost a year, he joined the development team of a large company to work on middleware-related development because he liked the simplicity and high performance of technologies like Nginx, OpenResty, and Netty.
 
-“在这家大公司,我做的离业务稍微远那么一点点,更偏向技术一些。“正松说。
+"In this big company, I did a little bit far from the business, more technically oriented. "Masatsu said.
 
-正松接触 Apache APISIX 的时间是 2020 年 9 月份,那时候,他所在的团队使用的是 Kong,但是当时 Kong 无法完全满足他们的需求,于是他们便重新做网关的技术选型,试图寻找更好的方案。正松担任本次技术选型的负责人,于是他关注到了 Apache 基金会的顶级项目 Apache APISIX,进而接触了 Apache APISIX 的社区。
+Zhengsong's contact with Apache APISIX was in September 2020, when his team was using Kong, but Kong was not fully meeting their needs, so they redid the technical selection of the gateway to try to find a better solution. Masatsu was in charge of this technical selection, so he came across the Apache Foundation's top project, Apache APISIX, and was introduced to the Apache APISIX community.
 
-彼时的他,已经毕业三年多了。
+At that time, he had already graduated more than three years ago.
 
-## 出新手村
+## Out of the newbie village
 
-> 我可以给 Apache 基金会的顶级项目提交代码了!作为一个技术工作者,这是一种技术上的自信。
+> I can submit code to the Apache Foundation's top projects! As a technical worker, that's a lot of technical confidence.
 
-正松在开源社区的第一个 PR 是一个 enhancement(功能增强)类型的 PR,这个 PR 让 Apache APISIX 支持了多端口监听。
+Zhengsong's first PR in the open source community was an enhancement type PR, which enabled Apache APISIX to support multi-port listening.
 
-- issue:https://github.com/apache/apisix/issues/1195
-- PR:https://github.com/apache/apisix/pull/2409
+- issue: https://github.com/apache/apisix/issues/1195
+- PR: https://github.com/apache/apisix/pull/2409
 
-这个功能是正松公司需要的,在 issue 区也早有人提到,但是不知为何一直无人认领。之前,正松正好对这方面的知识有所了解,于是他想:”我可以给 Apache APISIX 提个 PR 来 fix 这个问题。“所以他在 issue 里主动要求把这个问题指派给他。
+This feature is needed by Masatsu and has been mentioned in the issue area for a long time, but for some reason it has been unclaimed. Before that, Zhengsong happened to know something about this, so he thought, "I can propose a PR to Apache APISIX to fix this problem. "So he volunteered to have the issue assigned to him in the issue.
 
-他说:“当时我有一种强烈的参与社区的冲动,然后我看了一下 Apache APISIX 社区的新手指南,然后就像拿着武器从新手村出来一样,兴致冲冲的准备参与。”
+He says, "I had a strong urge to get involved in the community, and then I looked at the Apache APISIX community's Beginner's Guide and was as excited to get involved as if I were coming out of the Beginner's Village with a weapon."
 
-选择了这个 issue 之后,正松开始在 GitHub 上面开始跟社区的伙伴讨论细节上的问题,像是配置端口的 style、实现的思路等。在讨论完之后,他开始动手实现。每天晚上下班之后去翻看 Apache APISIX 的代码,测试相关用例。在经历了三四个晚上的奋斗后,测试第一次跑通了!
+After choosing this issue, Masatsu started discussing details with his community partners on GitHub, such as the style of the configuration port, the idea of the implementation, and so on. After the discussion, he started to implement it. Every night after work, he went through the Apache APISIX code and tested the use cases. After three or four nights of struggling, the test ran for the first time!
 
-当时正松内心非常的兴奋,马上按照那个新手指南的引导把 PR 提上去了。然后接受 Code Review 的意见,进一步修改代码。终于,在 10 月 18 号,PR 顺利地 merge 进了仓库。
+Masatsu was very excited and immediately followed the guide to bring up the PR. Then he accepted the comments from Code Review and further modified the code. Finally, on October 18, the PR was successfully merged into the repository.
 
 ![Apache APISIX committer tzssangglass pr](/img/blog_img/2021-08-11-2.webp)
 
-“当时我非常的激动,感觉自己终于实质性地参与到开源社区里面去了。我可以给 Apache 基金会的顶级项目提交代码了!作为一个技术工作者,这是一种技术上的自信。”
+"I was very excited and felt like I was finally substantially involved in the open source community. I could submit code to the Apache Foundation's top projects! As a technical worker, it was a technical confidence."
 
-**这是正松在开源世界的第一个 PR。**
+**This is Zhengsong's first PR in the open source world.**
 
-## 在社区印象深刻的事
+## Things that impressed me in the community
 
-> 因为 etcd 有 MaxCallRecvMsgSize 的限制,就从 etcd 的源头去解决,这是最优雅,也是最适合的。
+> Because etcd has a MaxCallRecvMsgSize limit, it was most elegant and appropriate to go to the source of etcd.
 
-当我们问到,正松在社区印象最深刻的事情是什么的时候,正松想了想说,可能是一个和 bug 有关的问题:etcd 的 MaxCallRecvMsgSize 限制。
+When we asked what was the thing that impressed Masatsu most in the community, Masatsu thought about it and said it was probably a bug-related issue: etcd's MaxCallRecvMsgSize limitation.
 
-正松曾经被 etcd 限制返回体大小的问题折磨过,社区内也多次反映、讨论过这个问题,但在 Apache APISIX 上无论怎么处理都不是很优雅。
+Masatsu had been tormented by etcd's return size limitation problem, and the community had reflected and discussed this problem many times, but it was not very elegant on Apache APISIX no matter how it was handled.
 
-直到今年 4 月份,支流科技的一位小伙伴给 etcd 提交了 PR,最终解决了这个问题。正松听说这个消息时,感到非常的震撼,当时他没有想过这个事情会以这样的方式去解决。但是现在来看的话,这个方法确实是最适合的。
+In April this year, one of our partners submitted a PR to etcd, which finally solved the problem. When Masatsu heard about this, he was very shocked, he didn't think it would be solved in such a way. But in hindsight, this was the way to go.

Review comment:
       ```suggestion
   In April this year, one of our partners submitted a PR to etcd, which finally solved the problem. When Zhengsong heard about this, he was very shocked, he didn't think it would be solved in such a way. But in hindsight, this was the way to go.
   ```

##########
File path: website/blog/2021/08/19/go-makes-Apache-APISIX-better.md
##########
@@ -97,19 +97,19 @@ func (p *Say) ParseConf(in []byte) (interface{}, error) {
 }
 ```
 
-该插件的上下文是这样的:
+The context of the plugin looks like this.
 
 ```go
 type SayConf struct {
-  Body string `json:"body"`
+  Body string `json: "body"`

Review comment:
       ```suggestion
     Body string `json:"body"`
   ```

##########
File path: website/blog/2021/08/23/ApacheCon-Asia-2021.md
##########
@@ -1,121 +1,120 @@
 ---
-title: "ApacheCon Asia 2021"
+title: ApacheCon Asia 2021
 keywords:
 - APISIX
 - ApacheCon
 - Apache Way
-- 孵化
-- 商业化
-description: ApacheCon 是 Apache 软件基金会的官方全球系列会议。自 1998 年以来,ApacheCon 一直吸引着各个层次的参与者,在 350 多个 Apache 项目及其不同的社区中探索 “明日的技术”。ApacheCon Asia 是 ApacheCon 组委会针对亚太地区举办的 ApacheCon 在线会议,主要目标在于更好地服务亚太地区快速增长的 Apache 用户和贡献者。ApacheCon Asia 2021 于 2021 年 8 月 6-8 日在线举办。Apache APISIX 社区积极参与本次年度开源盛会,共提报了 8 个 API/微服务技术相关的议题,内容丰富。
+- Commercial
+description: ApacheCon is the official global conference series of the Apache Software Foundation. Since 1998, ApacheCon has been attracting participants at all levels to explore the "technologies of tomorrow" across more than 350 Apache projects and their diverse communities. ApacheCon Asia 2021 was held online from August 6-8, 2021. The Apache APISIX community actively participated in this annual open source event, presenting a total of eight API/microservices technology-related topics. The content was rich.
 tags: [Events]
 ---
 
-> ApacheCon 是 Apache 软件基金会的官方全球系列会议。自 1998 年以来,ApacheCon 一直吸引着各个层次的参与者,在 350 多个 Apache 项目及其不同的社区中探索 “明日的技术”。ApacheCon Asia 是 ApacheCon 组委会针对亚太地区举办的 ApacheCon 在线会议,主要目标在于更好地服务亚太地区快速增长的 Apache 用户和贡献者。ApacheCon Asia 2021 于 2021 年 8 月 6-8 日在线举办。
+> ApacheCon is the official global conference series of the Apache Software Foundation. Since 1998, ApacheCon has been attracting participants at all levels to explore the "technologies of tomorrow" in more than 350 Apache projects and their diverse communities. ApacheCon Asia is an online ApacheCon conference with the primary goal of better serving the rapidly growing number of Apache users and contributors in the Asia-Pacific region. ApacheCon Asia 2021 takes place online August 6-8, 2021.
 
-<!--truncate-->
+<! --truncate-->

Review comment:
       ```suggestion
   <!--truncate-->
   ```

##########
File path: website/blog/2021/08/10/apisix-nginx.md
##########
@@ -164,13 +164,13 @@ local function init(env)
     local conf_render = template.compile(ngx_tpl)
     local ngxconf = conf_render(sys_conf)
 
-    local ok, err = util.write_file(env.apisix_home .. "/conf/nginx.conf",
+    local ok, err = util.write_file(env.apisix_home . "/conf/nginx.conf",

Review comment:
       ```suggestion
       local ok, err = util.write_file(env.apisix_home .. "/conf/nginx.conf",
   ```

##########
File path: website/blog/2021/08/10/apisix-nginx.md
##########
@@ -433,51 +433,51 @@ local resources = {
 }
 ```
 
-因此,上面的 curl 请求将被 /apisix/admin/upstreams.lua 文件的 `put` 函数处理,看下 `put` 函数的实现:
+Therefore, the above curl request will be processed by the ``put`` function in the /apisix/admin/upstreams.lua file, see the implementation of the ``put`` function as follows:

Review comment:
       ```suggestion
   Therefore, the above curl request will be processed by the `put` function in the /apisix/admin/upstreams.lua file, see the implementation of the `put` function as follows:
   ```

##########
File path: website/blog/2021/08/10/apisix-nginx.md
##########
@@ -377,26 +377,26 @@ local uri_route = {
 }
 ```
 
-比如,当通过 /apisix/admin/upstreams/1 和 PUT 方法创建 1 个 Upstream 上游时:
+For example, when creating 1 Upstream via /apisix/admin/upstreams/1 and the PUT method.
 
 ```shell
 curl "http://127.0.0.1:9080/apisix/admin/upstreams/1" -H "X-API-KEY: edd1c9f034335f136f87ad84b625c8f1" -X PUT -d '
 > {
->   "type": "roundrobin",
->   "nodes": {
->     "httpbin.org:80": 1
->   }
-> }'
-{"action":"set","node":{"key":"\/apisix\/upstreams\/1","value":{"hash_on":"vars","nodes":{"httpbin.org:80":1},"create_time":1627982128,"update_time":1627982128,"scheme":"http","type":"roundrobin","pass_host":"pass","id":"1"}}}
+> "type": "roundrobin",
+> "nodes": {
+> "httpbin.org:80": 1
+> }
+> }
+{"action":"set","node":{"key":"\/apisix\/upstreams\/1","value":{"hash_on":"vars","nodes":{"httpbin.org:80":1},"create_time":1627982128,"update_time":1627982128,"scheme":"http","type":"roundrobin","pass_host":"pass","id":"1"}}}'

Review comment:
       ```suggestion
   >   "type": "roundrobin",
   >   "nodes": {
   >     "httpbin.org:80": 1
   >   }
   > }'
   {"action":"set","node":{"key":"\/apisix\/upstreams\/1","value":{"hash_on":"vars","nodes":{"httpbin.org:80":1},"create_time":1627982128,"update_time":1627982128,"scheme":"http","type":"roundrobin","pass_host":"pass","id":"1"}}}
   ```

##########
File path: website/blog/2021/08/11/interview-TuZhengsong.md
##########
@@ -1,145 +1,145 @@
 ---
-title: "从新手村出来,我在 Apache APISIX 社区发出了第一个 PR"
-author: "Apache APISIX 社区"
+title: I issued my first PR in the Apache APISIX community
+author: Apache APISIX
 authorURL: "https://github.com/Yangxiamao"
 authorImageURL: "https://avatars.githubusercontent.com/u/47442074?v=4"
 keywords:
-- API 网关
+- API Gateway
 - APISIX
 - Apache APISIX
-- 开源社区
-- 开源项目
-description: 这篇采访稿讲述了屠正松从开源社区小白成长为 Apache 顶级开源项目 APISIX committer 的历程。屠正松(GitHub ID:tzssangglass)因深度参与 Apache APISIX 的开发,在社区中贡献很多,2021 年 7 月 22 日被推选为 Apache APISIX committer。
+- Community
+- Open Source
+description: "This interview is about Zhengsong Tu's journey from an open source community nerd to an APISIX committer for Apache's top open source project. Zhengsong Tu (GitHub ID: tzssangglass) was elected as an Apache APISIX committer on July 22, 2021 for his deep involvement in Apache APISIX development and his many contributions to the community."
 tags: [Interview]
 ---
 
-> 这篇采访稿讲述了屠正松从开源社区小白成长为 Apache 顶级开源项目 APISIX committer 的历程。屠正松(GitHub ID:tzssangglass)因深度参与 Apache APISIX 的开发,在社区中贡献很多,2021 年 7 月 22 日被推选为 Apache APISIX committer。
+> This interview is about Zhengsong Tu's journey from an open source community nerd to an APISIX committer for Apache's top open source project. Zhengsong Tu (GitHub ID: tzssangglass) was elected as an Apache APISIX committer on July 22, 2021 for his deep involvement in Apache APISIX development and his many contributions to the community.
 
 <!--truncate-->
 
-> 当我看到那个 issue 后,就有种强烈的想要参与到社区的冲动。看了社区的新手指南后,我像从新手村出来的勇者,准备打怪。
+> When I saw that issue, I had a strong urge to get involved in the community. After reading the community's newbie guide, I was like a brave man coming out of the newbie village, ready to fight.
 >
-> —— Apache APISIX committer 屠正松
+> -- Zhengsong Tu, Apache APISIX committer
 
-历时 282 天,屠正松(GitHub ID:tzssangglass)从开源社区的小白成长为了 Apache APISIX 的 committer。
+In 282 days, Zhengsong Tu (GitHub ID: tzssangglass) has grown from an open source community nerd to an Apache APISIX committer.
 
 ![Apache APISIX committer tzssangglass github](/img/blog_img/2021-08-11-1.webp)
 
-屠正松因深度参与 Apache APISIX 的开发,在社区中贡献很多,2021 年 7 月 22 日被推选为 Apache APISIX committer。
+Zhengsong Tu was elected as Apache APISIX committer on July 22, 2021 for his deep involvement in Apache APISIX development and many contributions in the community.
 
-在一个平淡的下午,我们和正松连线聊了聊。因为疫情关系,居住在南京的他已经多日未外出。在没有和他聊天之前,我没有想到,胡子拉碴的他,竟然走过了这么曲折的路。
+On an uneventful afternoon, we chatted with Zhengsong by phone. Because of the epidemic, he has not been out for many days in Nanjing. Before I talked to him, I didn't expect that the bearded man had traveled such a winding road.
 
-## 大学,我的大学
+## University, my university
 
-> 我大学的时候学的是通信工程,每天最开心的事就是踢球。现在有时候会想,如果能带着现在的记忆回到大学时光就好了。
+> When I was in college, I studied communication engineering, and the happiest thing I did every day was to play soccer. Now sometimes I think that it would be nice to go back to my college days with the memories I have now.
 
-正松在大学期间里面其实没怎么接触过编程,他当年其实有 C 语言的编程课,但是因为忙着踢球,挂科了。可是,他挂科之后的补考也没过,导致重修。最尴尬的是,他重修也没过,后来怎么办呢?毕业之前还有毕业清考。这可不能再挂了,于是正松就去图书馆去借了一本 C 语言的书来看。
+Zhengsong actually didn't have much contact with programming during his college years, he actually had a C programming class, but he failed it because he was too busy playing soccer. However, he failed a make-up exam after failing the class, resulting in a retake. The most embarrassing thing is that he failed the retake as well, so what did he do afterwards? There was a graduation clearing exam before graduation. This can not be failed again, so Zhengsong went to the library to borrow a C language book to read.
 
-“我当时心想,C 语言真的这么难吗?”正松说。
+"I was thinking, "Is C really that hard?" Zhengsong said.
 
-然后他就一直看一直看,看着看着就突然发现编程好像有那么点意思,他看懂了!最后他在毕业前顺利通过了考试。在毕业之后,找到了一份做程序员的工作。
+Then he kept reading and reading and reading, and suddenly he realized that programming seemed to have some meaning, and he understood it! He finally passed the exam before graduating. After graduation, he found a job as a programmer.
 
-“我本来都准备毕业回家找个厂上班了。”,他半开玩笑地说。
+"I was ready to graduate and go home and find a factory to work." , he said half-jokingly.
 
-彼时,他可能不会想到如今的他会成为数个知名开源项目的 developer,参与一些支撑着千万级并发流量的基础设施的开发。
+At that time, he probably wouldn't have thought that today he would be the developer of several well-known open source projects, and involved in the development of some infrastructure that supports millions of concurrent traffic.
 
-## 出象牙塔记
+## Out of the Ivory Tower
 
-> 在工业界,真实的业务场景和学校里学的很不一样的
+> In industry, the real business scenario is very different from what you learn in school.
 
-正松的第一份工作就职于一家做穿戴设备的创业公司,从事智能手环的研发工作。正松和他的前同事们需要通过处理从智能手环上的获取的各种传感器数据,来完成对用户的心率、运动量、血压等的监测。
+Zhengsong's first job was at a wearable device startup, working on the development of smart bracelets. Zhengsong and his former colleagues had to process various sensor data from the smart bracelet to monitor the user's heart rate, exercise, blood pressure and so on.
 
-“工作蛮好玩的,因为在工业界,真实的业务场景和学校里学的很不一样的,很多东西都得从头开始学”,正松说。
+"It was fun because in industry, the real business scenario is very different from what you learn in school, and a lot of things have to be learned from scratch," Masatsu said.
 
-有一天下班之后,这家公司的老板娘突然发了一条信息,说公司的员工暂时休假,什么时候上班等通知。
+One day after work, the owner of this company suddenly sent a message saying that the company's employees were on temporary leave and that they would wait to be notified when to work.
 
-正松当时就觉得不对劲,怎么好好的上着班,突然就休假了?然后他立马打开招聘软件,开始找新的工作。后来才知道,公司的老板跟供应商有合同纠纷,公司短暂停摆了。
+Masatsu felt something was wrong at that time, how to work well, suddenly on vacation? Then he immediately opened the recruitment software and started looking for a new job. Later, he found out that the owner of the company had a contract dispute with the supplier, and the company was briefly shut down.
 
-然后,正松便到另外一家公司从事后端业务开发的工作,学习业界规范、进一步增进技术。过了快一年,因为正松比较喜欢 Nginx、OpenResty、Netty 这类简洁和高性能的技术,他进入一家大公司的开发团队,从事中间件相关开发工作。
+Then, Masatsu went to another company to engage in back-end business development work, to learn the industry norms and further improve technology. After almost a year, he joined the development team of a large company to work on middleware-related development because he liked the simplicity and high performance of technologies like Nginx, OpenResty, and Netty.

Review comment:
       ```suggestion
   Then, Zhengsong went to another company to engage in back-end business development work, to learn the industry norms and further improve technology. After almost a year, he joined the development team of a large company to work on middleware-related development because he liked the simplicity and high performance of technologies like Nginx, OpenResty, and Netty.
   ```

##########
File path: website/blog/2021/08/10/apisix-nginx.md
##########
@@ -433,51 +433,51 @@ local resources = {
 }
 ```
 
-因此,上面的 curl 请求将被 /apisix/admin/upstreams.lua 文件的 `put` 函数处理,看下 `put` 函数的实现:
+Therefore, the above curl request will be processed by the ``put`` function in the /apisix/admin/upstreams.lua file, see the implementation of the ``put`` function as follows:
 
 ```lua
--- /apisix/admin/upstreams.lua文件
+-- /apisix/admin/upstreams.lua file
 function _M.put(id, conf)
-    -- 校验请求数据的合法性
+    -- check the legitimacy of the requested data
     local id, err = check_conf(id, conf, true)
     local key = "/upstreams/" .. id
     core.log.info("key: ", key)
-    -- 生成etcd中的配置数据
+    -- Generate configuration data in etcd
     local ok, err = utils.inject_conf_with_prev_conf("upstream", key, conf)
-    -- 写入etcd
+    -- write to etcd
     local res, err = core.etcd.set(key, conf)
 end
 
 -- /apisix/core/etcd.lua
 local function set(key, value, ttl)
-    local res, err = etcd_cli:set(prefix .. key, value, {prev_kv = true, lease = data.body.ID})
+    local res, err = etcd_cli:set(prefix ... key, value, {prev_kv = true, lease = data.body.ID})
 end
 ```
 
-最终新配置被写入 etcd 中。可见,Nginx 会校验数据再写入 etcd,这样其他 Worker 进程、Nginx 节点都将通过 watch 机制接收到正确的配置。上述流程你可以通过 error.log 中的日志验证:
+The new configuration is eventually written to etcd. As you can see, Nginx verifies the data before writing it to etcd, so that other worker processes and Nginx nodes will receive the correct configuration through the watch mechanism. You can verify this process with the logs in error.log.
 
 ```yaml
-2021/08/03 17:15:28 [info] 16437#16437: *23572 [lua] upstreams.lua:72: key: /upstreams/1, client: 127.0.0.1, server: _, request: "PUT /apisix/admin/upstreams/1 HTTP/1.1", host: "127.0.0.1:9080"
+2021/08/03 17:15:28 [info] 16437#16437: *23572 [lua] upstreams.lua:72: key: /upstreams/1, client: 127.0.0.1, server: _, request: "PUT /apisix/ admin/upstreams/1 HTTP/1.1", host: "127.0.0.1:9080"

Review comment:
       ```suggestion
   2021/08/03 17:15:28 [info] 16437#16437: *23572 [lua] upstreams.lua:72: key: /upstreams/1, client: 127.0.0.1, server: _, request: "PUT /apisix/admin/upstreams/1 HTTP/1.1", host: "127.0.0.1:9080"
   ```

##########
File path: website/blog/2021/08/10/apisix-nginx.md
##########
@@ -377,26 +377,26 @@ local uri_route = {
 }
 ```
 
-比如,当通过 /apisix/admin/upstreams/1 和 PUT 方法创建 1 个 Upstream 上游时:
+For example, when creating 1 Upstream via /apisix/admin/upstreams/1 and the PUT method.
 
 ```shell
 curl "http://127.0.0.1:9080/apisix/admin/upstreams/1" -H "X-API-KEY: edd1c9f034335f136f87ad84b625c8f1" -X PUT -d '
 > {
->   "type": "roundrobin",
->   "nodes": {
->     "httpbin.org:80": 1
->   }
-> }'
-{"action":"set","node":{"key":"\/apisix\/upstreams\/1","value":{"hash_on":"vars","nodes":{"httpbin.org:80":1},"create_time":1627982128,"update_time":1627982128,"scheme":"http","type":"roundrobin","pass_host":"pass","id":"1"}}}
+> "type": "roundrobin",
+> "nodes": {
+> "httpbin.org:80": 1
+> }
+> }
+{"action":"set","node":{"key":"\/apisix\/upstreams\/1","value":{"hash_on":"vars","nodes":{"httpbin.org:80":1},"create_time":1627982128,"update_time":1627982128,"scheme":"http","type":"roundrobin","pass_host":"pass","id":"1"}}}'
 ```
 
-你会在 error.log 中会看到如下日志(想看到这行日志,必须将 config.yaml 中的 nginx_config.error_log_level 设为 INFO):
+You will see the following log in error.log (to see this line, you must set the nginx_config.error_log_level in config.yaml to INFO)
 
 ```yaml
-2021/08/03 17:15:28 [info] 16437#16437: *23572 [lua] init.lua:130: handler(): uri: ["","apisix","admin","upstreams","1"], client: 127.0.0.1, server: _, request: "PUT /apisix/admin/upstreams/1 HTTP/1.1", host: "127.0.0.1:9080"
+2021/08/03 17:15:28 [info] 16437#16437: *23572 [lua] init.lua:130: handler(): uri: ["", "apisix", "admin", "upstreams", "1"], client: 127.0.0.1, server: _, request: "PUT /apisix/admin/upstreams/1 HTTP/1.1", host: "127.0.0.1:9080"

Review comment:
       ```suggestion
   2021/08/03 17:15:28 [info] 16437#16437: *23572 [lua] init.lua:130: handler(): uri: ["","apisix","admin","upstreams","1"], client: 127.0.0.1, server: _, request: "PUT /apisix/admin/upstreams/1 HTTP/1.1", host: "127.0.0.1:9080"
   ```

##########
File path: website/blog/2021/08/11/interview-TuZhengsong.md
##########
@@ -1,145 +1,145 @@
 ---
-title: "从新手村出来,我在 Apache APISIX 社区发出了第一个 PR"
-author: "Apache APISIX 社区"
+title: I issued my first PR in the Apache APISIX community
+author: Apache APISIX
 authorURL: "https://github.com/Yangxiamao"
 authorImageURL: "https://avatars.githubusercontent.com/u/47442074?v=4"
 keywords:
-- API 网关
+- API Gateway
 - APISIX
 - Apache APISIX
-- 开源社区
-- 开源项目
-description: 这篇采访稿讲述了屠正松从开源社区小白成长为 Apache 顶级开源项目 APISIX committer 的历程。屠正松(GitHub ID:tzssangglass)因深度参与 Apache APISIX 的开发,在社区中贡献很多,2021 年 7 月 22 日被推选为 Apache APISIX committer。
+- Community
+- Open Source
+description: "This interview is about Zhengsong Tu's journey from an open source community nerd to an APISIX committer for Apache's top open source project. Zhengsong Tu (GitHub ID: tzssangglass) was elected as an Apache APISIX committer on July 22, 2021 for his deep involvement in Apache APISIX development and his many contributions to the community."
 tags: [Interview]
 ---
 
-> 这篇采访稿讲述了屠正松从开源社区小白成长为 Apache 顶级开源项目 APISIX committer 的历程。屠正松(GitHub ID:tzssangglass)因深度参与 Apache APISIX 的开发,在社区中贡献很多,2021 年 7 月 22 日被推选为 Apache APISIX committer。
+> This interview is about Zhengsong Tu's journey from an open source community nerd to an APISIX committer for Apache's top open source project. Zhengsong Tu (GitHub ID: tzssangglass) was elected as an Apache APISIX committer on July 22, 2021 for his deep involvement in Apache APISIX development and his many contributions to the community.
 
 <!--truncate-->
 
-> 当我看到那个 issue 后,就有种强烈的想要参与到社区的冲动。看了社区的新手指南后,我像从新手村出来的勇者,准备打怪。
+> When I saw that issue, I had a strong urge to get involved in the community. After reading the community's newbie guide, I was like a brave man coming out of the newbie village, ready to fight.
 >
-> —— Apache APISIX committer 屠正松
+> -- Zhengsong Tu, Apache APISIX committer
 
-历时 282 天,屠正松(GitHub ID:tzssangglass)从开源社区的小白成长为了 Apache APISIX 的 committer。
+In 282 days, Zhengsong Tu (GitHub ID: tzssangglass) has grown from an open source community nerd to an Apache APISIX committer.
 
 ![Apache APISIX committer tzssangglass github](/img/blog_img/2021-08-11-1.webp)
 
-屠正松因深度参与 Apache APISIX 的开发,在社区中贡献很多,2021 年 7 月 22 日被推选为 Apache APISIX committer。
+Zhengsong Tu was elected as Apache APISIX committer on July 22, 2021 for his deep involvement in Apache APISIX development and many contributions in the community.
 
-在一个平淡的下午,我们和正松连线聊了聊。因为疫情关系,居住在南京的他已经多日未外出。在没有和他聊天之前,我没有想到,胡子拉碴的他,竟然走过了这么曲折的路。
+On an uneventful afternoon, we chatted with Zhengsong by phone. Because of the epidemic, he has not been out for many days in Nanjing. Before I talked to him, I didn't expect that the bearded man had traveled such a winding road.
 
-## 大学,我的大学
+## University, my university
 
-> 我大学的时候学的是通信工程,每天最开心的事就是踢球。现在有时候会想,如果能带着现在的记忆回到大学时光就好了。
+> When I was in college, I studied communication engineering, and the happiest thing I did every day was to play soccer. Now sometimes I think that it would be nice to go back to my college days with the memories I have now.
 
-正松在大学期间里面其实没怎么接触过编程,他当年其实有 C 语言的编程课,但是因为忙着踢球,挂科了。可是,他挂科之后的补考也没过,导致重修。最尴尬的是,他重修也没过,后来怎么办呢?毕业之前还有毕业清考。这可不能再挂了,于是正松就去图书馆去借了一本 C 语言的书来看。
+Zhengsong actually didn't have much contact with programming during his college years, he actually had a C programming class, but he failed it because he was too busy playing soccer. However, he failed a make-up exam after failing the class, resulting in a retake. The most embarrassing thing is that he failed the retake as well, so what did he do afterwards? There was a graduation clearing exam before graduation. This can not be failed again, so Zhengsong went to the library to borrow a C language book to read.
 
-“我当时心想,C 语言真的这么难吗?”正松说。
+"I was thinking, "Is C really that hard?" Zhengsong said.
 
-然后他就一直看一直看,看着看着就突然发现编程好像有那么点意思,他看懂了!最后他在毕业前顺利通过了考试。在毕业之后,找到了一份做程序员的工作。
+Then he kept reading and reading and reading, and suddenly he realized that programming seemed to have some meaning, and he understood it! He finally passed the exam before graduating. After graduation, he found a job as a programmer.
 
-“我本来都准备毕业回家找个厂上班了。”,他半开玩笑地说。
+"I was ready to graduate and go home and find a factory to work." , he said half-jokingly.
 
-彼时,他可能不会想到如今的他会成为数个知名开源项目的 developer,参与一些支撑着千万级并发流量的基础设施的开发。
+At that time, he probably wouldn't have thought that today he would be the developer of several well-known open source projects, and involved in the development of some infrastructure that supports millions of concurrent traffic.
 
-## 出象牙塔记
+## Out of the Ivory Tower
 
-> 在工业界,真实的业务场景和学校里学的很不一样的
+> In industry, the real business scenario is very different from what you learn in school.
 
-正松的第一份工作就职于一家做穿戴设备的创业公司,从事智能手环的研发工作。正松和他的前同事们需要通过处理从智能手环上的获取的各种传感器数据,来完成对用户的心率、运动量、血压等的监测。
+Zhengsong's first job was at a wearable device startup, working on the development of smart bracelets. Zhengsong and his former colleagues had to process various sensor data from the smart bracelet to monitor the user's heart rate, exercise, blood pressure and so on.
 
-“工作蛮好玩的,因为在工业界,真实的业务场景和学校里学的很不一样的,很多东西都得从头开始学”,正松说。
+"It was fun because in industry, the real business scenario is very different from what you learn in school, and a lot of things have to be learned from scratch," Masatsu said.
 
-有一天下班之后,这家公司的老板娘突然发了一条信息,说公司的员工暂时休假,什么时候上班等通知。
+One day after work, the owner of this company suddenly sent a message saying that the company's employees were on temporary leave and that they would wait to be notified when to work.
 
-正松当时就觉得不对劲,怎么好好的上着班,突然就休假了?然后他立马打开招聘软件,开始找新的工作。后来才知道,公司的老板跟供应商有合同纠纷,公司短暂停摆了。
+Masatsu felt something was wrong at that time, how to work well, suddenly on vacation? Then he immediately opened the recruitment software and started looking for a new job. Later, he found out that the owner of the company had a contract dispute with the supplier, and the company was briefly shut down.
 
-然后,正松便到另外一家公司从事后端业务开发的工作,学习业界规范、进一步增进技术。过了快一年,因为正松比较喜欢 Nginx、OpenResty、Netty 这类简洁和高性能的技术,他进入一家大公司的开发团队,从事中间件相关开发工作。
+Then, Masatsu went to another company to engage in back-end business development work, to learn the industry norms and further improve technology. After almost a year, he joined the development team of a large company to work on middleware-related development because he liked the simplicity and high performance of technologies like Nginx, OpenResty, and Netty.
 
-“在这家大公司,我做的离业务稍微远那么一点点,更偏向技术一些。“正松说。
+"In this big company, I did a little bit far from the business, more technically oriented. "Masatsu said.
 
-正松接触 Apache APISIX 的时间是 2020 年 9 月份,那时候,他所在的团队使用的是 Kong,但是当时 Kong 无法完全满足他们的需求,于是他们便重新做网关的技术选型,试图寻找更好的方案。正松担任本次技术选型的负责人,于是他关注到了 Apache 基金会的顶级项目 Apache APISIX,进而接触了 Apache APISIX 的社区。
+Zhengsong's contact with Apache APISIX was in September 2020, when his team was using Kong, but Kong was not fully meeting their needs, so they redid the technical selection of the gateway to try to find a better solution. Masatsu was in charge of this technical selection, so he came across the Apache Foundation's top project, Apache APISIX, and was introduced to the Apache APISIX community.

Review comment:
       ```suggestion
   Zhengsong's contact with Apache APISIX was in September 2020, when his team was using Kong, but Kong was not fully meeting their needs, so they redid the technical selection of the gateway to try to find a better solution. Zhengsong was in charge of this technical selection, so he came across the Apache Foundation's top project, Apache APISIX, and was introduced to the Apache APISIX community.
   ```

##########
File path: website/blog/2021/08/11/interview-TuZhengsong.md
##########
@@ -1,145 +1,145 @@
 ---
-title: "从新手村出来,我在 Apache APISIX 社区发出了第一个 PR"
-author: "Apache APISIX 社区"
+title: I issued my first PR in the Apache APISIX community
+author: Apache APISIX
 authorURL: "https://github.com/Yangxiamao"
 authorImageURL: "https://avatars.githubusercontent.com/u/47442074?v=4"
 keywords:
-- API 网关
+- API Gateway
 - APISIX
 - Apache APISIX
-- 开源社区
-- 开源项目
-description: 这篇采访稿讲述了屠正松从开源社区小白成长为 Apache 顶级开源项目 APISIX committer 的历程。屠正松(GitHub ID:tzssangglass)因深度参与 Apache APISIX 的开发,在社区中贡献很多,2021 年 7 月 22 日被推选为 Apache APISIX committer。
+- Community
+- Open Source
+description: "This interview is about Zhengsong Tu's journey from an open source community nerd to an APISIX committer for Apache's top open source project. Zhengsong Tu (GitHub ID: tzssangglass) was elected as an Apache APISIX committer on July 22, 2021 for his deep involvement in Apache APISIX development and his many contributions to the community."
 tags: [Interview]
 ---
 
-> 这篇采访稿讲述了屠正松从开源社区小白成长为 Apache 顶级开源项目 APISIX committer 的历程。屠正松(GitHub ID:tzssangglass)因深度参与 Apache APISIX 的开发,在社区中贡献很多,2021 年 7 月 22 日被推选为 Apache APISIX committer。
+> This interview is about Zhengsong Tu's journey from an open source community nerd to an APISIX committer for Apache's top open source project. Zhengsong Tu (GitHub ID: tzssangglass) was elected as an Apache APISIX committer on July 22, 2021 for his deep involvement in Apache APISIX development and his many contributions to the community.
 
 <!--truncate-->
 
-> 当我看到那个 issue 后,就有种强烈的想要参与到社区的冲动。看了社区的新手指南后,我像从新手村出来的勇者,准备打怪。
+> When I saw that issue, I had a strong urge to get involved in the community. After reading the community's newbie guide, I was like a brave man coming out of the newbie village, ready to fight.
 >
-> —— Apache APISIX committer 屠正松
+> -- Zhengsong Tu, Apache APISIX committer
 
-历时 282 天,屠正松(GitHub ID:tzssangglass)从开源社区的小白成长为了 Apache APISIX 的 committer。
+In 282 days, Zhengsong Tu (GitHub ID: tzssangglass) has grown from an open source community nerd to an Apache APISIX committer.
 
 ![Apache APISIX committer tzssangglass github](/img/blog_img/2021-08-11-1.webp)
 
-屠正松因深度参与 Apache APISIX 的开发,在社区中贡献很多,2021 年 7 月 22 日被推选为 Apache APISIX committer。
+Zhengsong Tu was elected as Apache APISIX committer on July 22, 2021 for his deep involvement in Apache APISIX development and many contributions in the community.
 
-在一个平淡的下午,我们和正松连线聊了聊。因为疫情关系,居住在南京的他已经多日未外出。在没有和他聊天之前,我没有想到,胡子拉碴的他,竟然走过了这么曲折的路。
+On an uneventful afternoon, we chatted with Zhengsong by phone. Because of the epidemic, he has not been out for many days in Nanjing. Before I talked to him, I didn't expect that the bearded man had traveled such a winding road.
 
-## 大学,我的大学
+## University, my university
 
-> 我大学的时候学的是通信工程,每天最开心的事就是踢球。现在有时候会想,如果能带着现在的记忆回到大学时光就好了。
+> When I was in college, I studied communication engineering, and the happiest thing I did every day was to play soccer. Now sometimes I think that it would be nice to go back to my college days with the memories I have now.
 
-正松在大学期间里面其实没怎么接触过编程,他当年其实有 C 语言的编程课,但是因为忙着踢球,挂科了。可是,他挂科之后的补考也没过,导致重修。最尴尬的是,他重修也没过,后来怎么办呢?毕业之前还有毕业清考。这可不能再挂了,于是正松就去图书馆去借了一本 C 语言的书来看。
+Zhengsong actually didn't have much contact with programming during his college years, he actually had a C programming class, but he failed it because he was too busy playing soccer. However, he failed a make-up exam after failing the class, resulting in a retake. The most embarrassing thing is that he failed the retake as well, so what did he do afterwards? There was a graduation clearing exam before graduation. This can not be failed again, so Zhengsong went to the library to borrow a C language book to read.
 
-“我当时心想,C 语言真的这么难吗?”正松说。
+"I was thinking, "Is C really that hard?" Zhengsong said.
 
-然后他就一直看一直看,看着看着就突然发现编程好像有那么点意思,他看懂了!最后他在毕业前顺利通过了考试。在毕业之后,找到了一份做程序员的工作。
+Then he kept reading and reading and reading, and suddenly he realized that programming seemed to have some meaning, and he understood it! He finally passed the exam before graduating. After graduation, he found a job as a programmer.
 
-“我本来都准备毕业回家找个厂上班了。”,他半开玩笑地说。
+"I was ready to graduate and go home and find a factory to work." , he said half-jokingly.
 
-彼时,他可能不会想到如今的他会成为数个知名开源项目的 developer,参与一些支撑着千万级并发流量的基础设施的开发。
+At that time, he probably wouldn't have thought that today he would be the developer of several well-known open source projects, and involved in the development of some infrastructure that supports millions of concurrent traffic.
 
-## 出象牙塔记
+## Out of the Ivory Tower
 
-> 在工业界,真实的业务场景和学校里学的很不一样的
+> In industry, the real business scenario is very different from what you learn in school.
 
-正松的第一份工作就职于一家做穿戴设备的创业公司,从事智能手环的研发工作。正松和他的前同事们需要通过处理从智能手环上的获取的各种传感器数据,来完成对用户的心率、运动量、血压等的监测。
+Zhengsong's first job was at a wearable device startup, working on the development of smart bracelets. Zhengsong and his former colleagues had to process various sensor data from the smart bracelet to monitor the user's heart rate, exercise, blood pressure and so on.
 
-“工作蛮好玩的,因为在工业界,真实的业务场景和学校里学的很不一样的,很多东西都得从头开始学”,正松说。
+"It was fun because in industry, the real business scenario is very different from what you learn in school, and a lot of things have to be learned from scratch," Masatsu said.
 
-有一天下班之后,这家公司的老板娘突然发了一条信息,说公司的员工暂时休假,什么时候上班等通知。
+One day after work, the owner of this company suddenly sent a message saying that the company's employees were on temporary leave and that they would wait to be notified when to work.
 
-正松当时就觉得不对劲,怎么好好的上着班,突然就休假了?然后他立马打开招聘软件,开始找新的工作。后来才知道,公司的老板跟供应商有合同纠纷,公司短暂停摆了。
+Masatsu felt something was wrong at that time, how to work well, suddenly on vacation? Then he immediately opened the recruitment software and started looking for a new job. Later, he found out that the owner of the company had a contract dispute with the supplier, and the company was briefly shut down.
 
-然后,正松便到另外一家公司从事后端业务开发的工作,学习业界规范、进一步增进技术。过了快一年,因为正松比较喜欢 Nginx、OpenResty、Netty 这类简洁和高性能的技术,他进入一家大公司的开发团队,从事中间件相关开发工作。
+Then, Masatsu went to another company to engage in back-end business development work, to learn the industry norms and further improve technology. After almost a year, he joined the development team of a large company to work on middleware-related development because he liked the simplicity and high performance of technologies like Nginx, OpenResty, and Netty.
 
-“在这家大公司,我做的离业务稍微远那么一点点,更偏向技术一些。“正松说。
+"In this big company, I did a little bit far from the business, more technically oriented. "Masatsu said.

Review comment:
       ```suggestion
   "In this big company, I did a little bit far from the business, more technically oriented. "Zhengsong said.
   ```

##########
File path: website/blog/2021/08/11/interview-TuZhengsong.md
##########
@@ -1,145 +1,145 @@
 ---
-title: "从新手村出来,我在 Apache APISIX 社区发出了第一个 PR"
-author: "Apache APISIX 社区"
+title: I issued my first PR in the Apache APISIX community
+author: Apache APISIX
 authorURL: "https://github.com/Yangxiamao"
 authorImageURL: "https://avatars.githubusercontent.com/u/47442074?v=4"
 keywords:
-- API 网关
+- API Gateway
 - APISIX
 - Apache APISIX
-- 开源社区
-- 开源项目
-description: 这篇采访稿讲述了屠正松从开源社区小白成长为 Apache 顶级开源项目 APISIX committer 的历程。屠正松(GitHub ID:tzssangglass)因深度参与 Apache APISIX 的开发,在社区中贡献很多,2021 年 7 月 22 日被推选为 Apache APISIX committer。
+- Community
+- Open Source
+description: "This interview is about Zhengsong Tu's journey from an open source community nerd to an APISIX committer for Apache's top open source project. Zhengsong Tu (GitHub ID: tzssangglass) was elected as an Apache APISIX committer on July 22, 2021 for his deep involvement in Apache APISIX development and his many contributions to the community."
 tags: [Interview]
 ---
 
-> 这篇采访稿讲述了屠正松从开源社区小白成长为 Apache 顶级开源项目 APISIX committer 的历程。屠正松(GitHub ID:tzssangglass)因深度参与 Apache APISIX 的开发,在社区中贡献很多,2021 年 7 月 22 日被推选为 Apache APISIX committer。
+> This interview is about Zhengsong Tu's journey from an open source community nerd to an APISIX committer for Apache's top open source project. Zhengsong Tu (GitHub ID: tzssangglass) was elected as an Apache APISIX committer on July 22, 2021 for his deep involvement in Apache APISIX development and his many contributions to the community.
 
 <!--truncate-->
 
-> 当我看到那个 issue 后,就有种强烈的想要参与到社区的冲动。看了社区的新手指南后,我像从新手村出来的勇者,准备打怪。
+> When I saw that issue, I had a strong urge to get involved in the community. After reading the community's newbie guide, I was like a brave man coming out of the newbie village, ready to fight.
 >
-> —— Apache APISIX committer 屠正松
+> -- Zhengsong Tu, Apache APISIX committer
 
-历时 282 天,屠正松(GitHub ID:tzssangglass)从开源社区的小白成长为了 Apache APISIX 的 committer。
+In 282 days, Zhengsong Tu (GitHub ID: tzssangglass) has grown from an open source community nerd to an Apache APISIX committer.
 
 ![Apache APISIX committer tzssangglass github](/img/blog_img/2021-08-11-1.webp)
 
-屠正松因深度参与 Apache APISIX 的开发,在社区中贡献很多,2021 年 7 月 22 日被推选为 Apache APISIX committer。
+Zhengsong Tu was elected as Apache APISIX committer on July 22, 2021 for his deep involvement in Apache APISIX development and many contributions in the community.
 
-在一个平淡的下午,我们和正松连线聊了聊。因为疫情关系,居住在南京的他已经多日未外出。在没有和他聊天之前,我没有想到,胡子拉碴的他,竟然走过了这么曲折的路。
+On an uneventful afternoon, we chatted with Zhengsong by phone. Because of the epidemic, he has not been out for many days in Nanjing. Before I talked to him, I didn't expect that the bearded man had traveled such a winding road.
 
-## 大学,我的大学
+## University, my university
 
-> 我大学的时候学的是通信工程,每天最开心的事就是踢球。现在有时候会想,如果能带着现在的记忆回到大学时光就好了。
+> When I was in college, I studied communication engineering, and the happiest thing I did every day was to play soccer. Now sometimes I think that it would be nice to go back to my college days with the memories I have now.
 
-正松在大学期间里面其实没怎么接触过编程,他当年其实有 C 语言的编程课,但是因为忙着踢球,挂科了。可是,他挂科之后的补考也没过,导致重修。最尴尬的是,他重修也没过,后来怎么办呢?毕业之前还有毕业清考。这可不能再挂了,于是正松就去图书馆去借了一本 C 语言的书来看。
+Zhengsong actually didn't have much contact with programming during his college years, he actually had a C programming class, but he failed it because he was too busy playing soccer. However, he failed a make-up exam after failing the class, resulting in a retake. The most embarrassing thing is that he failed the retake as well, so what did he do afterwards? There was a graduation clearing exam before graduation. This can not be failed again, so Zhengsong went to the library to borrow a C language book to read.
 
-“我当时心想,C 语言真的这么难吗?”正松说。
+"I was thinking, "Is C really that hard?" Zhengsong said.
 
-然后他就一直看一直看,看着看着就突然发现编程好像有那么点意思,他看懂了!最后他在毕业前顺利通过了考试。在毕业之后,找到了一份做程序员的工作。
+Then he kept reading and reading and reading, and suddenly he realized that programming seemed to have some meaning, and he understood it! He finally passed the exam before graduating. After graduation, he found a job as a programmer.
 
-“我本来都准备毕业回家找个厂上班了。”,他半开玩笑地说。
+"I was ready to graduate and go home and find a factory to work." , he said half-jokingly.
 
-彼时,他可能不会想到如今的他会成为数个知名开源项目的 developer,参与一些支撑着千万级并发流量的基础设施的开发。
+At that time, he probably wouldn't have thought that today he would be the developer of several well-known open source projects, and involved in the development of some infrastructure that supports millions of concurrent traffic.
 
-## 出象牙塔记
+## Out of the Ivory Tower
 
-> 在工业界,真实的业务场景和学校里学的很不一样的
+> In industry, the real business scenario is very different from what you learn in school.
 
-正松的第一份工作就职于一家做穿戴设备的创业公司,从事智能手环的研发工作。正松和他的前同事们需要通过处理从智能手环上的获取的各种传感器数据,来完成对用户的心率、运动量、血压等的监测。
+Zhengsong's first job was at a wearable device startup, working on the development of smart bracelets. Zhengsong and his former colleagues had to process various sensor data from the smart bracelet to monitor the user's heart rate, exercise, blood pressure and so on.
 
-“工作蛮好玩的,因为在工业界,真实的业务场景和学校里学的很不一样的,很多东西都得从头开始学”,正松说。
+"It was fun because in industry, the real business scenario is very different from what you learn in school, and a lot of things have to be learned from scratch," Masatsu said.
 
-有一天下班之后,这家公司的老板娘突然发了一条信息,说公司的员工暂时休假,什么时候上班等通知。
+One day after work, the owner of this company suddenly sent a message saying that the company's employees were on temporary leave and that they would wait to be notified when to work.
 
-正松当时就觉得不对劲,怎么好好的上着班,突然就休假了?然后他立马打开招聘软件,开始找新的工作。后来才知道,公司的老板跟供应商有合同纠纷,公司短暂停摆了。
+Masatsu felt something was wrong at that time, how to work well, suddenly on vacation? Then he immediately opened the recruitment software and started looking for a new job. Later, he found out that the owner of the company had a contract dispute with the supplier, and the company was briefly shut down.
 
-然后,正松便到另外一家公司从事后端业务开发的工作,学习业界规范、进一步增进技术。过了快一年,因为正松比较喜欢 Nginx、OpenResty、Netty 这类简洁和高性能的技术,他进入一家大公司的开发团队,从事中间件相关开发工作。
+Then, Masatsu went to another company to engage in back-end business development work, to learn the industry norms and further improve technology. After almost a year, he joined the development team of a large company to work on middleware-related development because he liked the simplicity and high performance of technologies like Nginx, OpenResty, and Netty.
 
-“在这家大公司,我做的离业务稍微远那么一点点,更偏向技术一些。“正松说。
+"In this big company, I did a little bit far from the business, more technically oriented. "Masatsu said.
 
-正松接触 Apache APISIX 的时间是 2020 年 9 月份,那时候,他所在的团队使用的是 Kong,但是当时 Kong 无法完全满足他们的需求,于是他们便重新做网关的技术选型,试图寻找更好的方案。正松担任本次技术选型的负责人,于是他关注到了 Apache 基金会的顶级项目 Apache APISIX,进而接触了 Apache APISIX 的社区。
+Zhengsong's contact with Apache APISIX was in September 2020, when his team was using Kong, but Kong was not fully meeting their needs, so they redid the technical selection of the gateway to try to find a better solution. Masatsu was in charge of this technical selection, so he came across the Apache Foundation's top project, Apache APISIX, and was introduced to the Apache APISIX community.
 
-彼时的他,已经毕业三年多了。
+At that time, he had already graduated more than three years ago.
 
-## 出新手村
+## Out of the newbie village
 
-> 我可以给 Apache 基金会的顶级项目提交代码了!作为一个技术工作者,这是一种技术上的自信。
+> I can submit code to the Apache Foundation's top projects! As a technical worker, that's a lot of technical confidence.
 
-正松在开源社区的第一个 PR 是一个 enhancement(功能增强)类型的 PR,这个 PR 让 Apache APISIX 支持了多端口监听。
+Zhengsong's first PR in the open source community was an enhancement type PR, which enabled Apache APISIX to support multi-port listening.
 
-- issue:https://github.com/apache/apisix/issues/1195
-- PR:https://github.com/apache/apisix/pull/2409
+- issue: https://github.com/apache/apisix/issues/1195
+- PR: https://github.com/apache/apisix/pull/2409
 
-这个功能是正松公司需要的,在 issue 区也早有人提到,但是不知为何一直无人认领。之前,正松正好对这方面的知识有所了解,于是他想:”我可以给 Apache APISIX 提个 PR 来 fix 这个问题。“所以他在 issue 里主动要求把这个问题指派给他。
+This feature is needed by Masatsu and has been mentioned in the issue area for a long time, but for some reason it has been unclaimed. Before that, Zhengsong happened to know something about this, so he thought, "I can propose a PR to Apache APISIX to fix this problem. "So he volunteered to have the issue assigned to him in the issue.

Review comment:
       ```suggestion
   This feature is needed by Zhengsong and has been mentioned in the issue area for a long time, but for some reason it has been unclaimed. Before that, Zhengsong happened to know something about this, so he thought, "I can propose a PR to Apache APISIX to fix this problem. "So he volunteered to have the issue assigned to him in the issue.
   ```

##########
File path: website/blog/2021/08/11/interview-TuZhengsong.md
##########
@@ -1,145 +1,145 @@
 ---
-title: "从新手村出来,我在 Apache APISIX 社区发出了第一个 PR"
-author: "Apache APISIX 社区"
+title: I issued my first PR in the Apache APISIX community
+author: Apache APISIX
 authorURL: "https://github.com/Yangxiamao"
 authorImageURL: "https://avatars.githubusercontent.com/u/47442074?v=4"
 keywords:
-- API 网关
+- API Gateway
 - APISIX
 - Apache APISIX
-- 开源社区
-- 开源项目
-description: 这篇采访稿讲述了屠正松从开源社区小白成长为 Apache 顶级开源项目 APISIX committer 的历程。屠正松(GitHub ID:tzssangglass)因深度参与 Apache APISIX 的开发,在社区中贡献很多,2021 年 7 月 22 日被推选为 Apache APISIX committer。
+- Community
+- Open Source
+description: "This interview is about Zhengsong Tu's journey from an open source community nerd to an APISIX committer for Apache's top open source project. Zhengsong Tu (GitHub ID: tzssangglass) was elected as an Apache APISIX committer on July 22, 2021 for his deep involvement in Apache APISIX development and his many contributions to the community."
 tags: [Interview]
 ---
 
-> 这篇采访稿讲述了屠正松从开源社区小白成长为 Apache 顶级开源项目 APISIX committer 的历程。屠正松(GitHub ID:tzssangglass)因深度参与 Apache APISIX 的开发,在社区中贡献很多,2021 年 7 月 22 日被推选为 Apache APISIX committer。
+> This interview is about Zhengsong Tu's journey from an open source community nerd to an APISIX committer for Apache's top open source project. Zhengsong Tu (GitHub ID: tzssangglass) was elected as an Apache APISIX committer on July 22, 2021 for his deep involvement in Apache APISIX development and his many contributions to the community.
 
 <!--truncate-->
 
-> 当我看到那个 issue 后,就有种强烈的想要参与到社区的冲动。看了社区的新手指南后,我像从新手村出来的勇者,准备打怪。
+> When I saw that issue, I had a strong urge to get involved in the community. After reading the community's newbie guide, I was like a brave man coming out of the newbie village, ready to fight.
 >
-> —— Apache APISIX committer 屠正松
+> -- Zhengsong Tu, Apache APISIX committer
 
-历时 282 天,屠正松(GitHub ID:tzssangglass)从开源社区的小白成长为了 Apache APISIX 的 committer。
+In 282 days, Zhengsong Tu (GitHub ID: tzssangglass) has grown from an open source community nerd to an Apache APISIX committer.
 
 ![Apache APISIX committer tzssangglass github](/img/blog_img/2021-08-11-1.webp)
 
-屠正松因深度参与 Apache APISIX 的开发,在社区中贡献很多,2021 年 7 月 22 日被推选为 Apache APISIX committer。
+Zhengsong Tu was elected as Apache APISIX committer on July 22, 2021 for his deep involvement in Apache APISIX development and many contributions in the community.
 
-在一个平淡的下午,我们和正松连线聊了聊。因为疫情关系,居住在南京的他已经多日未外出。在没有和他聊天之前,我没有想到,胡子拉碴的他,竟然走过了这么曲折的路。
+On an uneventful afternoon, we chatted with Zhengsong by phone. Because of the epidemic, he has not been out for many days in Nanjing. Before I talked to him, I didn't expect that the bearded man had traveled such a winding road.
 
-## 大学,我的大学
+## University, my university
 
-> 我大学的时候学的是通信工程,每天最开心的事就是踢球。现在有时候会想,如果能带着现在的记忆回到大学时光就好了。
+> When I was in college, I studied communication engineering, and the happiest thing I did every day was to play soccer. Now sometimes I think that it would be nice to go back to my college days with the memories I have now.
 
-正松在大学期间里面其实没怎么接触过编程,他当年其实有 C 语言的编程课,但是因为忙着踢球,挂科了。可是,他挂科之后的补考也没过,导致重修。最尴尬的是,他重修也没过,后来怎么办呢?毕业之前还有毕业清考。这可不能再挂了,于是正松就去图书馆去借了一本 C 语言的书来看。
+Zhengsong actually didn't have much contact with programming during his college years, he actually had a C programming class, but he failed it because he was too busy playing soccer. However, he failed a make-up exam after failing the class, resulting in a retake. The most embarrassing thing is that he failed the retake as well, so what did he do afterwards? There was a graduation clearing exam before graduation. This can not be failed again, so Zhengsong went to the library to borrow a C language book to read.
 
-“我当时心想,C 语言真的这么难吗?”正松说。
+"I was thinking, "Is C really that hard?" Zhengsong said.
 
-然后他就一直看一直看,看着看着就突然发现编程好像有那么点意思,他看懂了!最后他在毕业前顺利通过了考试。在毕业之后,找到了一份做程序员的工作。
+Then he kept reading and reading and reading, and suddenly he realized that programming seemed to have some meaning, and he understood it! He finally passed the exam before graduating. After graduation, he found a job as a programmer.
 
-“我本来都准备毕业回家找个厂上班了。”,他半开玩笑地说。
+"I was ready to graduate and go home and find a factory to work." , he said half-jokingly.
 
-彼时,他可能不会想到如今的他会成为数个知名开源项目的 developer,参与一些支撑着千万级并发流量的基础设施的开发。
+At that time, he probably wouldn't have thought that today he would be the developer of several well-known open source projects, and involved in the development of some infrastructure that supports millions of concurrent traffic.
 
-## 出象牙塔记
+## Out of the Ivory Tower
 
-> 在工业界,真实的业务场景和学校里学的很不一样的
+> In industry, the real business scenario is very different from what you learn in school.
 
-正松的第一份工作就职于一家做穿戴设备的创业公司,从事智能手环的研发工作。正松和他的前同事们需要通过处理从智能手环上的获取的各种传感器数据,来完成对用户的心率、运动量、血压等的监测。
+Zhengsong's first job was at a wearable device startup, working on the development of smart bracelets. Zhengsong and his former colleagues had to process various sensor data from the smart bracelet to monitor the user's heart rate, exercise, blood pressure and so on.
 
-“工作蛮好玩的,因为在工业界,真实的业务场景和学校里学的很不一样的,很多东西都得从头开始学”,正松说。
+"It was fun because in industry, the real business scenario is very different from what you learn in school, and a lot of things have to be learned from scratch," Masatsu said.
 
-有一天下班之后,这家公司的老板娘突然发了一条信息,说公司的员工暂时休假,什么时候上班等通知。
+One day after work, the owner of this company suddenly sent a message saying that the company's employees were on temporary leave and that they would wait to be notified when to work.
 
-正松当时就觉得不对劲,怎么好好的上着班,突然就休假了?然后他立马打开招聘软件,开始找新的工作。后来才知道,公司的老板跟供应商有合同纠纷,公司短暂停摆了。
+Masatsu felt something was wrong at that time, how to work well, suddenly on vacation? Then he immediately opened the recruitment software and started looking for a new job. Later, he found out that the owner of the company had a contract dispute with the supplier, and the company was briefly shut down.
 
-然后,正松便到另外一家公司从事后端业务开发的工作,学习业界规范、进一步增进技术。过了快一年,因为正松比较喜欢 Nginx、OpenResty、Netty 这类简洁和高性能的技术,他进入一家大公司的开发团队,从事中间件相关开发工作。
+Then, Masatsu went to another company to engage in back-end business development work, to learn the industry norms and further improve technology. After almost a year, he joined the development team of a large company to work on middleware-related development because he liked the simplicity and high performance of technologies like Nginx, OpenResty, and Netty.
 
-“在这家大公司,我做的离业务稍微远那么一点点,更偏向技术一些。“正松说。
+"In this big company, I did a little bit far from the business, more technically oriented. "Masatsu said.
 
-正松接触 Apache APISIX 的时间是 2020 年 9 月份,那时候,他所在的团队使用的是 Kong,但是当时 Kong 无法完全满足他们的需求,于是他们便重新做网关的技术选型,试图寻找更好的方案。正松担任本次技术选型的负责人,于是他关注到了 Apache 基金会的顶级项目 Apache APISIX,进而接触了 Apache APISIX 的社区。
+Zhengsong's contact with Apache APISIX was in September 2020, when his team was using Kong, but Kong was not fully meeting their needs, so they redid the technical selection of the gateway to try to find a better solution. Masatsu was in charge of this technical selection, so he came across the Apache Foundation's top project, Apache APISIX, and was introduced to the Apache APISIX community.
 
-彼时的他,已经毕业三年多了。
+At that time, he had already graduated more than three years ago.
 
-## 出新手村
+## Out of the newbie village
 
-> 我可以给 Apache 基金会的顶级项目提交代码了!作为一个技术工作者,这是一种技术上的自信。
+> I can submit code to the Apache Foundation's top projects! As a technical worker, that's a lot of technical confidence.
 
-正松在开源社区的第一个 PR 是一个 enhancement(功能增强)类型的 PR,这个 PR 让 Apache APISIX 支持了多端口监听。
+Zhengsong's first PR in the open source community was an enhancement type PR, which enabled Apache APISIX to support multi-port listening.
 
-- issue:https://github.com/apache/apisix/issues/1195
-- PR:https://github.com/apache/apisix/pull/2409
+- issue: https://github.com/apache/apisix/issues/1195
+- PR: https://github.com/apache/apisix/pull/2409
 
-这个功能是正松公司需要的,在 issue 区也早有人提到,但是不知为何一直无人认领。之前,正松正好对这方面的知识有所了解,于是他想:”我可以给 Apache APISIX 提个 PR 来 fix 这个问题。“所以他在 issue 里主动要求把这个问题指派给他。
+This feature is needed by Masatsu and has been mentioned in the issue area for a long time, but for some reason it has been unclaimed. Before that, Zhengsong happened to know something about this, so he thought, "I can propose a PR to Apache APISIX to fix this problem. "So he volunteered to have the issue assigned to him in the issue.
 
-他说:“当时我有一种强烈的参与社区的冲动,然后我看了一下 Apache APISIX 社区的新手指南,然后就像拿着武器从新手村出来一样,兴致冲冲的准备参与。”
+He says, "I had a strong urge to get involved in the community, and then I looked at the Apache APISIX community's Beginner's Guide and was as excited to get involved as if I were coming out of the Beginner's Village with a weapon."
 
-选择了这个 issue 之后,正松开始在 GitHub 上面开始跟社区的伙伴讨论细节上的问题,像是配置端口的 style、实现的思路等。在讨论完之后,他开始动手实现。每天晚上下班之后去翻看 Apache APISIX 的代码,测试相关用例。在经历了三四个晚上的奋斗后,测试第一次跑通了!
+After choosing this issue, Masatsu started discussing details with his community partners on GitHub, such as the style of the configuration port, the idea of the implementation, and so on. After the discussion, he started to implement it. Every night after work, he went through the Apache APISIX code and tested the use cases. After three or four nights of struggling, the test ran for the first time!
 
-当时正松内心非常的兴奋,马上按照那个新手指南的引导把 PR 提上去了。然后接受 Code Review 的意见,进一步修改代码。终于,在 10 月 18 号,PR 顺利地 merge 进了仓库。
+Masatsu was very excited and immediately followed the guide to bring up the PR. Then he accepted the comments from Code Review and further modified the code. Finally, on October 18, the PR was successfully merged into the repository.

Review comment:
       ```suggestion
   Zhengsong was very excited and immediately followed the guide to bring up the PR. Then he accepted the comments from Code Review and further modified the code. Finally, on October 18, the PR was successfully merged into the repository.
   ```

##########
File path: website/blog/2021/08/11/interview-TuZhengsong.md
##########
@@ -1,145 +1,145 @@
 ---
-title: "从新手村出来,我在 Apache APISIX 社区发出了第一个 PR"
-author: "Apache APISIX 社区"
+title: I issued my first PR in the Apache APISIX community
+author: Apache APISIX
 authorURL: "https://github.com/Yangxiamao"
 authorImageURL: "https://avatars.githubusercontent.com/u/47442074?v=4"
 keywords:
-- API 网关
+- API Gateway
 - APISIX
 - Apache APISIX
-- 开源社区
-- 开源项目
-description: 这篇采访稿讲述了屠正松从开源社区小白成长为 Apache 顶级开源项目 APISIX committer 的历程。屠正松(GitHub ID:tzssangglass)因深度参与 Apache APISIX 的开发,在社区中贡献很多,2021 年 7 月 22 日被推选为 Apache APISIX committer。
+- Community
+- Open Source
+description: "This interview is about Zhengsong Tu's journey from an open source community nerd to an APISIX committer for Apache's top open source project. Zhengsong Tu (GitHub ID: tzssangglass) was elected as an Apache APISIX committer on July 22, 2021 for his deep involvement in Apache APISIX development and his many contributions to the community."
 tags: [Interview]
 ---
 
-> 这篇采访稿讲述了屠正松从开源社区小白成长为 Apache 顶级开源项目 APISIX committer 的历程。屠正松(GitHub ID:tzssangglass)因深度参与 Apache APISIX 的开发,在社区中贡献很多,2021 年 7 月 22 日被推选为 Apache APISIX committer。
+> This interview is about Zhengsong Tu's journey from an open source community nerd to an APISIX committer for Apache's top open source project. Zhengsong Tu (GitHub ID: tzssangglass) was elected as an Apache APISIX committer on July 22, 2021 for his deep involvement in Apache APISIX development and his many contributions to the community.
 
 <!--truncate-->
 
-> 当我看到那个 issue 后,就有种强烈的想要参与到社区的冲动。看了社区的新手指南后,我像从新手村出来的勇者,准备打怪。
+> When I saw that issue, I had a strong urge to get involved in the community. After reading the community's newbie guide, I was like a brave man coming out of the newbie village, ready to fight.
 >
-> —— Apache APISIX committer 屠正松
+> -- Zhengsong Tu, Apache APISIX committer
 
-历时 282 天,屠正松(GitHub ID:tzssangglass)从开源社区的小白成长为了 Apache APISIX 的 committer。
+In 282 days, Zhengsong Tu (GitHub ID: tzssangglass) has grown from an open source community nerd to an Apache APISIX committer.
 
 ![Apache APISIX committer tzssangglass github](/img/blog_img/2021-08-11-1.webp)
 
-屠正松因深度参与 Apache APISIX 的开发,在社区中贡献很多,2021 年 7 月 22 日被推选为 Apache APISIX committer。
+Zhengsong Tu was elected as Apache APISIX committer on July 22, 2021 for his deep involvement in Apache APISIX development and many contributions in the community.
 
-在一个平淡的下午,我们和正松连线聊了聊。因为疫情关系,居住在南京的他已经多日未外出。在没有和他聊天之前,我没有想到,胡子拉碴的他,竟然走过了这么曲折的路。
+On an uneventful afternoon, we chatted with Zhengsong by phone. Because of the epidemic, he has not been out for many days in Nanjing. Before I talked to him, I didn't expect that the bearded man had traveled such a winding road.
 
-## 大学,我的大学
+## University, my university
 
-> 我大学的时候学的是通信工程,每天最开心的事就是踢球。现在有时候会想,如果能带着现在的记忆回到大学时光就好了。
+> When I was in college, I studied communication engineering, and the happiest thing I did every day was to play soccer. Now sometimes I think that it would be nice to go back to my college days with the memories I have now.
 
-正松在大学期间里面其实没怎么接触过编程,他当年其实有 C 语言的编程课,但是因为忙着踢球,挂科了。可是,他挂科之后的补考也没过,导致重修。最尴尬的是,他重修也没过,后来怎么办呢?毕业之前还有毕业清考。这可不能再挂了,于是正松就去图书馆去借了一本 C 语言的书来看。
+Zhengsong actually didn't have much contact with programming during his college years, he actually had a C programming class, but he failed it because he was too busy playing soccer. However, he failed a make-up exam after failing the class, resulting in a retake. The most embarrassing thing is that he failed the retake as well, so what did he do afterwards? There was a graduation clearing exam before graduation. This can not be failed again, so Zhengsong went to the library to borrow a C language book to read.
 
-“我当时心想,C 语言真的这么难吗?”正松说。
+"I was thinking, "Is C really that hard?" Zhengsong said.
 
-然后他就一直看一直看,看着看着就突然发现编程好像有那么点意思,他看懂了!最后他在毕业前顺利通过了考试。在毕业之后,找到了一份做程序员的工作。
+Then he kept reading and reading and reading, and suddenly he realized that programming seemed to have some meaning, and he understood it! He finally passed the exam before graduating. After graduation, he found a job as a programmer.
 
-“我本来都准备毕业回家找个厂上班了。”,他半开玩笑地说。
+"I was ready to graduate and go home and find a factory to work." , he said half-jokingly.
 
-彼时,他可能不会想到如今的他会成为数个知名开源项目的 developer,参与一些支撑着千万级并发流量的基础设施的开发。
+At that time, he probably wouldn't have thought that today he would be the developer of several well-known open source projects, and involved in the development of some infrastructure that supports millions of concurrent traffic.
 
-## 出象牙塔记
+## Out of the Ivory Tower
 
-> 在工业界,真实的业务场景和学校里学的很不一样的
+> In industry, the real business scenario is very different from what you learn in school.
 
-正松的第一份工作就职于一家做穿戴设备的创业公司,从事智能手环的研发工作。正松和他的前同事们需要通过处理从智能手环上的获取的各种传感器数据,来完成对用户的心率、运动量、血压等的监测。
+Zhengsong's first job was at a wearable device startup, working on the development of smart bracelets. Zhengsong and his former colleagues had to process various sensor data from the smart bracelet to monitor the user's heart rate, exercise, blood pressure and so on.
 
-“工作蛮好玩的,因为在工业界,真实的业务场景和学校里学的很不一样的,很多东西都得从头开始学”,正松说。
+"It was fun because in industry, the real business scenario is very different from what you learn in school, and a lot of things have to be learned from scratch," Masatsu said.
 
-有一天下班之后,这家公司的老板娘突然发了一条信息,说公司的员工暂时休假,什么时候上班等通知。
+One day after work, the owner of this company suddenly sent a message saying that the company's employees were on temporary leave and that they would wait to be notified when to work.
 
-正松当时就觉得不对劲,怎么好好的上着班,突然就休假了?然后他立马打开招聘软件,开始找新的工作。后来才知道,公司的老板跟供应商有合同纠纷,公司短暂停摆了。
+Masatsu felt something was wrong at that time, how to work well, suddenly on vacation? Then he immediately opened the recruitment software and started looking for a new job. Later, he found out that the owner of the company had a contract dispute with the supplier, and the company was briefly shut down.
 
-然后,正松便到另外一家公司从事后端业务开发的工作,学习业界规范、进一步增进技术。过了快一年,因为正松比较喜欢 Nginx、OpenResty、Netty 这类简洁和高性能的技术,他进入一家大公司的开发团队,从事中间件相关开发工作。
+Then, Masatsu went to another company to engage in back-end business development work, to learn the industry norms and further improve technology. After almost a year, he joined the development team of a large company to work on middleware-related development because he liked the simplicity and high performance of technologies like Nginx, OpenResty, and Netty.
 
-“在这家大公司,我做的离业务稍微远那么一点点,更偏向技术一些。“正松说。
+"In this big company, I did a little bit far from the business, more technically oriented. "Masatsu said.
 
-正松接触 Apache APISIX 的时间是 2020 年 9 月份,那时候,他所在的团队使用的是 Kong,但是当时 Kong 无法完全满足他们的需求,于是他们便重新做网关的技术选型,试图寻找更好的方案。正松担任本次技术选型的负责人,于是他关注到了 Apache 基金会的顶级项目 Apache APISIX,进而接触了 Apache APISIX 的社区。
+Zhengsong's contact with Apache APISIX was in September 2020, when his team was using Kong, but Kong was not fully meeting their needs, so they redid the technical selection of the gateway to try to find a better solution. Masatsu was in charge of this technical selection, so he came across the Apache Foundation's top project, Apache APISIX, and was introduced to the Apache APISIX community.
 
-彼时的他,已经毕业三年多了。
+At that time, he had already graduated more than three years ago.
 
-## 出新手村
+## Out of the newbie village
 
-> 我可以给 Apache 基金会的顶级项目提交代码了!作为一个技术工作者,这是一种技术上的自信。
+> I can submit code to the Apache Foundation's top projects! As a technical worker, that's a lot of technical confidence.
 
-正松在开源社区的第一个 PR 是一个 enhancement(功能增强)类型的 PR,这个 PR 让 Apache APISIX 支持了多端口监听。
+Zhengsong's first PR in the open source community was an enhancement type PR, which enabled Apache APISIX to support multi-port listening.
 
-- issue:https://github.com/apache/apisix/issues/1195
-- PR:https://github.com/apache/apisix/pull/2409
+- issue: https://github.com/apache/apisix/issues/1195
+- PR: https://github.com/apache/apisix/pull/2409
 
-这个功能是正松公司需要的,在 issue 区也早有人提到,但是不知为何一直无人认领。之前,正松正好对这方面的知识有所了解,于是他想:”我可以给 Apache APISIX 提个 PR 来 fix 这个问题。“所以他在 issue 里主动要求把这个问题指派给他。
+This feature is needed by Masatsu and has been mentioned in the issue area for a long time, but for some reason it has been unclaimed. Before that, Zhengsong happened to know something about this, so he thought, "I can propose a PR to Apache APISIX to fix this problem. "So he volunteered to have the issue assigned to him in the issue.
 
-他说:“当时我有一种强烈的参与社区的冲动,然后我看了一下 Apache APISIX 社区的新手指南,然后就像拿着武器从新手村出来一样,兴致冲冲的准备参与。”
+He says, "I had a strong urge to get involved in the community, and then I looked at the Apache APISIX community's Beginner's Guide and was as excited to get involved as if I were coming out of the Beginner's Village with a weapon."
 
-选择了这个 issue 之后,正松开始在 GitHub 上面开始跟社区的伙伴讨论细节上的问题,像是配置端口的 style、实现的思路等。在讨论完之后,他开始动手实现。每天晚上下班之后去翻看 Apache APISIX 的代码,测试相关用例。在经历了三四个晚上的奋斗后,测试第一次跑通了!
+After choosing this issue, Masatsu started discussing details with his community partners on GitHub, such as the style of the configuration port, the idea of the implementation, and so on. After the discussion, he started to implement it. Every night after work, he went through the Apache APISIX code and tested the use cases. After three or four nights of struggling, the test ran for the first time!
 
-当时正松内心非常的兴奋,马上按照那个新手指南的引导把 PR 提上去了。然后接受 Code Review 的意见,进一步修改代码。终于,在 10 月 18 号,PR 顺利地 merge 进了仓库。
+Masatsu was very excited and immediately followed the guide to bring up the PR. Then he accepted the comments from Code Review and further modified the code. Finally, on October 18, the PR was successfully merged into the repository.
 
 ![Apache APISIX committer tzssangglass pr](/img/blog_img/2021-08-11-2.webp)
 
-“当时我非常的激动,感觉自己终于实质性地参与到开源社区里面去了。我可以给 Apache 基金会的顶级项目提交代码了!作为一个技术工作者,这是一种技术上的自信。”
+"I was very excited and felt like I was finally substantially involved in the open source community. I could submit code to the Apache Foundation's top projects! As a technical worker, it was a technical confidence."
 
-**这是正松在开源世界的第一个 PR。**
+**This is Zhengsong's first PR in the open source world.**
 
-## 在社区印象深刻的事
+## Things that impressed me in the community
 
-> 因为 etcd 有 MaxCallRecvMsgSize 的限制,就从 etcd 的源头去解决,这是最优雅,也是最适合的。
+> Because etcd has a MaxCallRecvMsgSize limit, it was most elegant and appropriate to go to the source of etcd.
 
-当我们问到,正松在社区印象最深刻的事情是什么的时候,正松想了想说,可能是一个和 bug 有关的问题:etcd 的 MaxCallRecvMsgSize 限制。
+When we asked what was the thing that impressed Masatsu most in the community, Masatsu thought about it and said it was probably a bug-related issue: etcd's MaxCallRecvMsgSize limitation.

Review comment:
       ```suggestion
   When we asked what was the thing that impressed Zhengsong most in the community, Zhengsong thought about it and said it was probably a bug-related issue: etcd's MaxCallRecvMsgSize limitation.
   ```

##########
File path: website/blog/2021/08/11/interview-TuZhengsong.md
##########
@@ -1,145 +1,145 @@
 ---
-title: "从新手村出来,我在 Apache APISIX 社区发出了第一个 PR"
-author: "Apache APISIX 社区"
+title: I issued my first PR in the Apache APISIX community
+author: Apache APISIX
 authorURL: "https://github.com/Yangxiamao"
 authorImageURL: "https://avatars.githubusercontent.com/u/47442074?v=4"
 keywords:
-- API 网关
+- API Gateway
 - APISIX
 - Apache APISIX
-- 开源社区
-- 开源项目
-description: 这篇采访稿讲述了屠正松从开源社区小白成长为 Apache 顶级开源项目 APISIX committer 的历程。屠正松(GitHub ID:tzssangglass)因深度参与 Apache APISIX 的开发,在社区中贡献很多,2021 年 7 月 22 日被推选为 Apache APISIX committer。
+- Community
+- Open Source
+description: "This interview is about Zhengsong Tu's journey from an open source community nerd to an APISIX committer for Apache's top open source project. Zhengsong Tu (GitHub ID: tzssangglass) was elected as an Apache APISIX committer on July 22, 2021 for his deep involvement in Apache APISIX development and his many contributions to the community."
 tags: [Interview]
 ---
 
-> 这篇采访稿讲述了屠正松从开源社区小白成长为 Apache 顶级开源项目 APISIX committer 的历程。屠正松(GitHub ID:tzssangglass)因深度参与 Apache APISIX 的开发,在社区中贡献很多,2021 年 7 月 22 日被推选为 Apache APISIX committer。
+> This interview is about Zhengsong Tu's journey from an open source community nerd to an APISIX committer for Apache's top open source project. Zhengsong Tu (GitHub ID: tzssangglass) was elected as an Apache APISIX committer on July 22, 2021 for his deep involvement in Apache APISIX development and his many contributions to the community.
 
 <!--truncate-->
 
-> 当我看到那个 issue 后,就有种强烈的想要参与到社区的冲动。看了社区的新手指南后,我像从新手村出来的勇者,准备打怪。
+> When I saw that issue, I had a strong urge to get involved in the community. After reading the community's newbie guide, I was like a brave man coming out of the newbie village, ready to fight.
 >
-> —— Apache APISIX committer 屠正松
+> -- Zhengsong Tu, Apache APISIX committer
 
-历时 282 天,屠正松(GitHub ID:tzssangglass)从开源社区的小白成长为了 Apache APISIX 的 committer。
+In 282 days, Zhengsong Tu (GitHub ID: tzssangglass) has grown from an open source community nerd to an Apache APISIX committer.
 
 ![Apache APISIX committer tzssangglass github](/img/blog_img/2021-08-11-1.webp)
 
-屠正松因深度参与 Apache APISIX 的开发,在社区中贡献很多,2021 年 7 月 22 日被推选为 Apache APISIX committer。
+Zhengsong Tu was elected as Apache APISIX committer on July 22, 2021 for his deep involvement in Apache APISIX development and many contributions in the community.
 
-在一个平淡的下午,我们和正松连线聊了聊。因为疫情关系,居住在南京的他已经多日未外出。在没有和他聊天之前,我没有想到,胡子拉碴的他,竟然走过了这么曲折的路。
+On an uneventful afternoon, we chatted with Zhengsong by phone. Because of the epidemic, he has not been out for many days in Nanjing. Before I talked to him, I didn't expect that the bearded man had traveled such a winding road.
 
-## 大学,我的大学
+## University, my university
 
-> 我大学的时候学的是通信工程,每天最开心的事就是踢球。现在有时候会想,如果能带着现在的记忆回到大学时光就好了。
+> When I was in college, I studied communication engineering, and the happiest thing I did every day was to play soccer. Now sometimes I think that it would be nice to go back to my college days with the memories I have now.
 
-正松在大学期间里面其实没怎么接触过编程,他当年其实有 C 语言的编程课,但是因为忙着踢球,挂科了。可是,他挂科之后的补考也没过,导致重修。最尴尬的是,他重修也没过,后来怎么办呢?毕业之前还有毕业清考。这可不能再挂了,于是正松就去图书馆去借了一本 C 语言的书来看。
+Zhengsong actually didn't have much contact with programming during his college years, he actually had a C programming class, but he failed it because he was too busy playing soccer. However, he failed a make-up exam after failing the class, resulting in a retake. The most embarrassing thing is that he failed the retake as well, so what did he do afterwards? There was a graduation clearing exam before graduation. This can not be failed again, so Zhengsong went to the library to borrow a C language book to read.
 
-“我当时心想,C 语言真的这么难吗?”正松说。
+"I was thinking, "Is C really that hard?" Zhengsong said.
 
-然后他就一直看一直看,看着看着就突然发现编程好像有那么点意思,他看懂了!最后他在毕业前顺利通过了考试。在毕业之后,找到了一份做程序员的工作。
+Then he kept reading and reading and reading, and suddenly he realized that programming seemed to have some meaning, and he understood it! He finally passed the exam before graduating. After graduation, he found a job as a programmer.
 
-“我本来都准备毕业回家找个厂上班了。”,他半开玩笑地说。
+"I was ready to graduate and go home and find a factory to work." , he said half-jokingly.
 
-彼时,他可能不会想到如今的他会成为数个知名开源项目的 developer,参与一些支撑着千万级并发流量的基础设施的开发。
+At that time, he probably wouldn't have thought that today he would be the developer of several well-known open source projects, and involved in the development of some infrastructure that supports millions of concurrent traffic.
 
-## 出象牙塔记
+## Out of the Ivory Tower
 
-> 在工业界,真实的业务场景和学校里学的很不一样的
+> In industry, the real business scenario is very different from what you learn in school.
 
-正松的第一份工作就职于一家做穿戴设备的创业公司,从事智能手环的研发工作。正松和他的前同事们需要通过处理从智能手环上的获取的各种传感器数据,来完成对用户的心率、运动量、血压等的监测。
+Zhengsong's first job was at a wearable device startup, working on the development of smart bracelets. Zhengsong and his former colleagues had to process various sensor data from the smart bracelet to monitor the user's heart rate, exercise, blood pressure and so on.
 
-“工作蛮好玩的,因为在工业界,真实的业务场景和学校里学的很不一样的,很多东西都得从头开始学”,正松说。
+"It was fun because in industry, the real business scenario is very different from what you learn in school, and a lot of things have to be learned from scratch," Masatsu said.
 
-有一天下班之后,这家公司的老板娘突然发了一条信息,说公司的员工暂时休假,什么时候上班等通知。
+One day after work, the owner of this company suddenly sent a message saying that the company's employees were on temporary leave and that they would wait to be notified when to work.
 
-正松当时就觉得不对劲,怎么好好的上着班,突然就休假了?然后他立马打开招聘软件,开始找新的工作。后来才知道,公司的老板跟供应商有合同纠纷,公司短暂停摆了。
+Masatsu felt something was wrong at that time, how to work well, suddenly on vacation? Then he immediately opened the recruitment software and started looking for a new job. Later, he found out that the owner of the company had a contract dispute with the supplier, and the company was briefly shut down.
 
-然后,正松便到另外一家公司从事后端业务开发的工作,学习业界规范、进一步增进技术。过了快一年,因为正松比较喜欢 Nginx、OpenResty、Netty 这类简洁和高性能的技术,他进入一家大公司的开发团队,从事中间件相关开发工作。
+Then, Masatsu went to another company to engage in back-end business development work, to learn the industry norms and further improve technology. After almost a year, he joined the development team of a large company to work on middleware-related development because he liked the simplicity and high performance of technologies like Nginx, OpenResty, and Netty.
 
-“在这家大公司,我做的离业务稍微远那么一点点,更偏向技术一些。“正松说。
+"In this big company, I did a little bit far from the business, more technically oriented. "Masatsu said.
 
-正松接触 Apache APISIX 的时间是 2020 年 9 月份,那时候,他所在的团队使用的是 Kong,但是当时 Kong 无法完全满足他们的需求,于是他们便重新做网关的技术选型,试图寻找更好的方案。正松担任本次技术选型的负责人,于是他关注到了 Apache 基金会的顶级项目 Apache APISIX,进而接触了 Apache APISIX 的社区。
+Zhengsong's contact with Apache APISIX was in September 2020, when his team was using Kong, but Kong was not fully meeting their needs, so they redid the technical selection of the gateway to try to find a better solution. Masatsu was in charge of this technical selection, so he came across the Apache Foundation's top project, Apache APISIX, and was introduced to the Apache APISIX community.
 
-彼时的他,已经毕业三年多了。
+At that time, he had already graduated more than three years ago.
 
-## 出新手村
+## Out of the newbie village
 
-> 我可以给 Apache 基金会的顶级项目提交代码了!作为一个技术工作者,这是一种技术上的自信。
+> I can submit code to the Apache Foundation's top projects! As a technical worker, that's a lot of technical confidence.
 
-正松在开源社区的第一个 PR 是一个 enhancement(功能增强)类型的 PR,这个 PR 让 Apache APISIX 支持了多端口监听。
+Zhengsong's first PR in the open source community was an enhancement type PR, which enabled Apache APISIX to support multi-port listening.
 
-- issue:https://github.com/apache/apisix/issues/1195
-- PR:https://github.com/apache/apisix/pull/2409
+- issue: https://github.com/apache/apisix/issues/1195
+- PR: https://github.com/apache/apisix/pull/2409
 
-这个功能是正松公司需要的,在 issue 区也早有人提到,但是不知为何一直无人认领。之前,正松正好对这方面的知识有所了解,于是他想:”我可以给 Apache APISIX 提个 PR 来 fix 这个问题。“所以他在 issue 里主动要求把这个问题指派给他。
+This feature is needed by Masatsu and has been mentioned in the issue area for a long time, but for some reason it has been unclaimed. Before that, Zhengsong happened to know something about this, so he thought, "I can propose a PR to Apache APISIX to fix this problem. "So he volunteered to have the issue assigned to him in the issue.
 
-他说:“当时我有一种强烈的参与社区的冲动,然后我看了一下 Apache APISIX 社区的新手指南,然后就像拿着武器从新手村出来一样,兴致冲冲的准备参与。”
+He says, "I had a strong urge to get involved in the community, and then I looked at the Apache APISIX community's Beginner's Guide and was as excited to get involved as if I were coming out of the Beginner's Village with a weapon."
 
-选择了这个 issue 之后,正松开始在 GitHub 上面开始跟社区的伙伴讨论细节上的问题,像是配置端口的 style、实现的思路等。在讨论完之后,他开始动手实现。每天晚上下班之后去翻看 Apache APISIX 的代码,测试相关用例。在经历了三四个晚上的奋斗后,测试第一次跑通了!
+After choosing this issue, Masatsu started discussing details with his community partners on GitHub, such as the style of the configuration port, the idea of the implementation, and so on. After the discussion, he started to implement it. Every night after work, he went through the Apache APISIX code and tested the use cases. After three or four nights of struggling, the test ran for the first time!
 
-当时正松内心非常的兴奋,马上按照那个新手指南的引导把 PR 提上去了。然后接受 Code Review 的意见,进一步修改代码。终于,在 10 月 18 号,PR 顺利地 merge 进了仓库。
+Masatsu was very excited and immediately followed the guide to bring up the PR. Then he accepted the comments from Code Review and further modified the code. Finally, on October 18, the PR was successfully merged into the repository.
 
 ![Apache APISIX committer tzssangglass pr](/img/blog_img/2021-08-11-2.webp)
 
-“当时我非常的激动,感觉自己终于实质性地参与到开源社区里面去了。我可以给 Apache 基金会的顶级项目提交代码了!作为一个技术工作者,这是一种技术上的自信。”
+"I was very excited and felt like I was finally substantially involved in the open source community. I could submit code to the Apache Foundation's top projects! As a technical worker, it was a technical confidence."
 
-**这是正松在开源世界的第一个 PR。**
+**This is Zhengsong's first PR in the open source world.**
 
-## 在社区印象深刻的事
+## Things that impressed me in the community
 
-> 因为 etcd 有 MaxCallRecvMsgSize 的限制,就从 etcd 的源头去解决,这是最优雅,也是最适合的。
+> Because etcd has a MaxCallRecvMsgSize limit, it was most elegant and appropriate to go to the source of etcd.
 
-当我们问到,正松在社区印象最深刻的事情是什么的时候,正松想了想说,可能是一个和 bug 有关的问题:etcd 的 MaxCallRecvMsgSize 限制。
+When we asked what was the thing that impressed Masatsu most in the community, Masatsu thought about it and said it was probably a bug-related issue: etcd's MaxCallRecvMsgSize limitation.
 
-正松曾经被 etcd 限制返回体大小的问题折磨过,社区内也多次反映、讨论过这个问题,但在 Apache APISIX 上无论怎么处理都不是很优雅。
+Masatsu had been tormented by etcd's return size limitation problem, and the community had reflected and discussed this problem many times, but it was not very elegant on Apache APISIX no matter how it was handled.

Review comment:
       ```suggestion
   Zhengsong had been tormented by etcd's return size limitation problem, and the community had reflected and discussed this problem many times, but it was not very elegant on Apache APISIX no matter how it was handled.
   ```

##########
File path: website/blog/2021/08/24/shanghai-meetup-recap.md
##########
@@ -1,62 +1,60 @@
 ---
-title: "Apache APISIX Meetup 上海站全程回顾"
-author: "Apache APISIX 社区"
+title: Apache APISIX Meetup in Shanghai
+author: Apache APISIX
 keywords:
-- API 网关
+- API Gateway
 - APISIX
 - Meetup
-- 上海站
-- 回顾
-description: 活动回顾:Apache APISIX Meetup 上海站议题分享及视频回顾。
+description: "Event Review: Apache APISIX Meetup Shanghai Topic Sharing and Video Review."
 tags: [Events]
 ---
 
-> 活动回顾:Apache APISIX Meetup 上海站议题分享及视频回顾。
+> Event review: Apache APISIX Meetup Shanghai topic sharing and video review.
 
-<!--truncate-->
+<! --truncate-->

Review comment:
       ```suggestion
   <!--truncate-->
   ```

##########
File path: website/blog/2021/08/11/interview-TuZhengsong.md
##########
@@ -1,145 +1,145 @@
 ---
-title: "从新手村出来,我在 Apache APISIX 社区发出了第一个 PR"
-author: "Apache APISIX 社区"
+title: I issued my first PR in the Apache APISIX community
+author: Apache APISIX
 authorURL: "https://github.com/Yangxiamao"
 authorImageURL: "https://avatars.githubusercontent.com/u/47442074?v=4"
 keywords:
-- API 网关
+- API Gateway
 - APISIX
 - Apache APISIX
-- 开源社区
-- 开源项目
-description: 这篇采访稿讲述了屠正松从开源社区小白成长为 Apache 顶级开源项目 APISIX committer 的历程。屠正松(GitHub ID:tzssangglass)因深度参与 Apache APISIX 的开发,在社区中贡献很多,2021 年 7 月 22 日被推选为 Apache APISIX committer。
+- Community
+- Open Source
+description: "This interview is about Zhengsong Tu's journey from an open source community nerd to an APISIX committer for Apache's top open source project. Zhengsong Tu (GitHub ID: tzssangglass) was elected as an Apache APISIX committer on July 22, 2021 for his deep involvement in Apache APISIX development and his many contributions to the community."
 tags: [Interview]
 ---
 
-> 这篇采访稿讲述了屠正松从开源社区小白成长为 Apache 顶级开源项目 APISIX committer 的历程。屠正松(GitHub ID:tzssangglass)因深度参与 Apache APISIX 的开发,在社区中贡献很多,2021 年 7 月 22 日被推选为 Apache APISIX committer。
+> This interview is about Zhengsong Tu's journey from an open source community nerd to an APISIX committer for Apache's top open source project. Zhengsong Tu (GitHub ID: tzssangglass) was elected as an Apache APISIX committer on July 22, 2021 for his deep involvement in Apache APISIX development and his many contributions to the community.
 
 <!--truncate-->
 
-> 当我看到那个 issue 后,就有种强烈的想要参与到社区的冲动。看了社区的新手指南后,我像从新手村出来的勇者,准备打怪。
+> When I saw that issue, I had a strong urge to get involved in the community. After reading the community's newbie guide, I was like a brave man coming out of the newbie village, ready to fight.
 >
-> —— Apache APISIX committer 屠正松
+> -- Zhengsong Tu, Apache APISIX committer
 
-历时 282 天,屠正松(GitHub ID:tzssangglass)从开源社区的小白成长为了 Apache APISIX 的 committer。
+In 282 days, Zhengsong Tu (GitHub ID: tzssangglass) has grown from an open source community nerd to an Apache APISIX committer.
 
 ![Apache APISIX committer tzssangglass github](/img/blog_img/2021-08-11-1.webp)
 
-屠正松因深度参与 Apache APISIX 的开发,在社区中贡献很多,2021 年 7 月 22 日被推选为 Apache APISIX committer。
+Zhengsong Tu was elected as Apache APISIX committer on July 22, 2021 for his deep involvement in Apache APISIX development and many contributions in the community.
 
-在一个平淡的下午,我们和正松连线聊了聊。因为疫情关系,居住在南京的他已经多日未外出。在没有和他聊天之前,我没有想到,胡子拉碴的他,竟然走过了这么曲折的路。
+On an uneventful afternoon, we chatted with Zhengsong by phone. Because of the epidemic, he has not been out for many days in Nanjing. Before I talked to him, I didn't expect that the bearded man had traveled such a winding road.
 
-## 大学,我的大学
+## University, my university
 
-> 我大学的时候学的是通信工程,每天最开心的事就是踢球。现在有时候会想,如果能带着现在的记忆回到大学时光就好了。
+> When I was in college, I studied communication engineering, and the happiest thing I did every day was to play soccer. Now sometimes I think that it would be nice to go back to my college days with the memories I have now.
 
-正松在大学期间里面其实没怎么接触过编程,他当年其实有 C 语言的编程课,但是因为忙着踢球,挂科了。可是,他挂科之后的补考也没过,导致重修。最尴尬的是,他重修也没过,后来怎么办呢?毕业之前还有毕业清考。这可不能再挂了,于是正松就去图书馆去借了一本 C 语言的书来看。
+Zhengsong actually didn't have much contact with programming during his college years, he actually had a C programming class, but he failed it because he was too busy playing soccer. However, he failed a make-up exam after failing the class, resulting in a retake. The most embarrassing thing is that he failed the retake as well, so what did he do afterwards? There was a graduation clearing exam before graduation. This can not be failed again, so Zhengsong went to the library to borrow a C language book to read.
 
-“我当时心想,C 语言真的这么难吗?”正松说。
+"I was thinking, "Is C really that hard?" Zhengsong said.
 
-然后他就一直看一直看,看着看着就突然发现编程好像有那么点意思,他看懂了!最后他在毕业前顺利通过了考试。在毕业之后,找到了一份做程序员的工作。
+Then he kept reading and reading and reading, and suddenly he realized that programming seemed to have some meaning, and he understood it! He finally passed the exam before graduating. After graduation, he found a job as a programmer.
 
-“我本来都准备毕业回家找个厂上班了。”,他半开玩笑地说。
+"I was ready to graduate and go home and find a factory to work." , he said half-jokingly.
 
-彼时,他可能不会想到如今的他会成为数个知名开源项目的 developer,参与一些支撑着千万级并发流量的基础设施的开发。
+At that time, he probably wouldn't have thought that today he would be the developer of several well-known open source projects, and involved in the development of some infrastructure that supports millions of concurrent traffic.
 
-## 出象牙塔记
+## Out of the Ivory Tower
 
-> 在工业界,真实的业务场景和学校里学的很不一样的
+> In industry, the real business scenario is very different from what you learn in school.
 
-正松的第一份工作就职于一家做穿戴设备的创业公司,从事智能手环的研发工作。正松和他的前同事们需要通过处理从智能手环上的获取的各种传感器数据,来完成对用户的心率、运动量、血压等的监测。
+Zhengsong's first job was at a wearable device startup, working on the development of smart bracelets. Zhengsong and his former colleagues had to process various sensor data from the smart bracelet to monitor the user's heart rate, exercise, blood pressure and so on.
 
-“工作蛮好玩的,因为在工业界,真实的业务场景和学校里学的很不一样的,很多东西都得从头开始学”,正松说。
+"It was fun because in industry, the real business scenario is very different from what you learn in school, and a lot of things have to be learned from scratch," Masatsu said.
 
-有一天下班之后,这家公司的老板娘突然发了一条信息,说公司的员工暂时休假,什么时候上班等通知。
+One day after work, the owner of this company suddenly sent a message saying that the company's employees were on temporary leave and that they would wait to be notified when to work.
 
-正松当时就觉得不对劲,怎么好好的上着班,突然就休假了?然后他立马打开招聘软件,开始找新的工作。后来才知道,公司的老板跟供应商有合同纠纷,公司短暂停摆了。
+Masatsu felt something was wrong at that time, how to work well, suddenly on vacation? Then he immediately opened the recruitment software and started looking for a new job. Later, he found out that the owner of the company had a contract dispute with the supplier, and the company was briefly shut down.
 
-然后,正松便到另外一家公司从事后端业务开发的工作,学习业界规范、进一步增进技术。过了快一年,因为正松比较喜欢 Nginx、OpenResty、Netty 这类简洁和高性能的技术,他进入一家大公司的开发团队,从事中间件相关开发工作。
+Then, Masatsu went to another company to engage in back-end business development work, to learn the industry norms and further improve technology. After almost a year, he joined the development team of a large company to work on middleware-related development because he liked the simplicity and high performance of technologies like Nginx, OpenResty, and Netty.
 
-“在这家大公司,我做的离业务稍微远那么一点点,更偏向技术一些。“正松说。
+"In this big company, I did a little bit far from the business, more technically oriented. "Masatsu said.
 
-正松接触 Apache APISIX 的时间是 2020 年 9 月份,那时候,他所在的团队使用的是 Kong,但是当时 Kong 无法完全满足他们的需求,于是他们便重新做网关的技术选型,试图寻找更好的方案。正松担任本次技术选型的负责人,于是他关注到了 Apache 基金会的顶级项目 Apache APISIX,进而接触了 Apache APISIX 的社区。
+Zhengsong's contact with Apache APISIX was in September 2020, when his team was using Kong, but Kong was not fully meeting their needs, so they redid the technical selection of the gateway to try to find a better solution. Masatsu was in charge of this technical selection, so he came across the Apache Foundation's top project, Apache APISIX, and was introduced to the Apache APISIX community.
 
-彼时的他,已经毕业三年多了。
+At that time, he had already graduated more than three years ago.
 
-## 出新手村
+## Out of the newbie village
 
-> 我可以给 Apache 基金会的顶级项目提交代码了!作为一个技术工作者,这是一种技术上的自信。
+> I can submit code to the Apache Foundation's top projects! As a technical worker, that's a lot of technical confidence.
 
-正松在开源社区的第一个 PR 是一个 enhancement(功能增强)类型的 PR,这个 PR 让 Apache APISIX 支持了多端口监听。
+Zhengsong's first PR in the open source community was an enhancement type PR, which enabled Apache APISIX to support multi-port listening.
 
-- issue:https://github.com/apache/apisix/issues/1195
-- PR:https://github.com/apache/apisix/pull/2409
+- issue: https://github.com/apache/apisix/issues/1195
+- PR: https://github.com/apache/apisix/pull/2409
 
-这个功能是正松公司需要的,在 issue 区也早有人提到,但是不知为何一直无人认领。之前,正松正好对这方面的知识有所了解,于是他想:”我可以给 Apache APISIX 提个 PR 来 fix 这个问题。“所以他在 issue 里主动要求把这个问题指派给他。
+This feature is needed by Masatsu and has been mentioned in the issue area for a long time, but for some reason it has been unclaimed. Before that, Zhengsong happened to know something about this, so he thought, "I can propose a PR to Apache APISIX to fix this problem. "So he volunteered to have the issue assigned to him in the issue.
 
-他说:“当时我有一种强烈的参与社区的冲动,然后我看了一下 Apache APISIX 社区的新手指南,然后就像拿着武器从新手村出来一样,兴致冲冲的准备参与。”
+He says, "I had a strong urge to get involved in the community, and then I looked at the Apache APISIX community's Beginner's Guide and was as excited to get involved as if I were coming out of the Beginner's Village with a weapon."
 
-选择了这个 issue 之后,正松开始在 GitHub 上面开始跟社区的伙伴讨论细节上的问题,像是配置端口的 style、实现的思路等。在讨论完之后,他开始动手实现。每天晚上下班之后去翻看 Apache APISIX 的代码,测试相关用例。在经历了三四个晚上的奋斗后,测试第一次跑通了!
+After choosing this issue, Masatsu started discussing details with his community partners on GitHub, such as the style of the configuration port, the idea of the implementation, and so on. After the discussion, he started to implement it. Every night after work, he went through the Apache APISIX code and tested the use cases. After three or four nights of struggling, the test ran for the first time!
 
-当时正松内心非常的兴奋,马上按照那个新手指南的引导把 PR 提上去了。然后接受 Code Review 的意见,进一步修改代码。终于,在 10 月 18 号,PR 顺利地 merge 进了仓库。
+Masatsu was very excited and immediately followed the guide to bring up the PR. Then he accepted the comments from Code Review and further modified the code. Finally, on October 18, the PR was successfully merged into the repository.
 
 ![Apache APISIX committer tzssangglass pr](/img/blog_img/2021-08-11-2.webp)
 
-“当时我非常的激动,感觉自己终于实质性地参与到开源社区里面去了。我可以给 Apache 基金会的顶级项目提交代码了!作为一个技术工作者,这是一种技术上的自信。”
+"I was very excited and felt like I was finally substantially involved in the open source community. I could submit code to the Apache Foundation's top projects! As a technical worker, it was a technical confidence."
 
-**这是正松在开源世界的第一个 PR。**
+**This is Zhengsong's first PR in the open source world.**
 
-## 在社区印象深刻的事
+## Things that impressed me in the community
 
-> 因为 etcd 有 MaxCallRecvMsgSize 的限制,就从 etcd 的源头去解决,这是最优雅,也是最适合的。
+> Because etcd has a MaxCallRecvMsgSize limit, it was most elegant and appropriate to go to the source of etcd.
 
-当我们问到,正松在社区印象最深刻的事情是什么的时候,正松想了想说,可能是一个和 bug 有关的问题:etcd 的 MaxCallRecvMsgSize 限制。
+When we asked what was the thing that impressed Masatsu most in the community, Masatsu thought about it and said it was probably a bug-related issue: etcd's MaxCallRecvMsgSize limitation.
 
-正松曾经被 etcd 限制返回体大小的问题折磨过,社区内也多次反映、讨论过这个问题,但在 Apache APISIX 上无论怎么处理都不是很优雅。
+Masatsu had been tormented by etcd's return size limitation problem, and the community had reflected and discussed this problem many times, but it was not very elegant on Apache APISIX no matter how it was handled.
 
-直到今年 4 月份,支流科技的一位小伙伴给 etcd 提交了 PR,最终解决了这个问题。正松听说这个消息时,感到非常的震撼,当时他没有想过这个事情会以这样的方式去解决。但是现在来看的话,这个方法确实是最适合的。
+In April this year, one of our partners submitted a PR to etcd, which finally solved the problem. When Masatsu heard about this, he was very shocked, he didn't think it would be solved in such a way. But in hindsight, this was the way to go.
 
-“因为 etcd 有 MaxCallRecvMsgSize 的限制,就从 etcd 的源头去解决,这是最优雅,也是最适合的。这是很棒的跨社区合作的示例”,正松说。
+"Because etcd has a MaxCallRecvMsgSize limit, it's most elegant and appropriate to go to the source of etcd. This is great example of cross-community collaboration," says Masatsu.
 
 ## Sir, this way
 
-> 大家分工合作不同,但是都是在为开源做贡献。
+> We're all working together differently, but we're all contributing to open source.
 
-正松说,他刚开始参与社区的时候,把当时能看到的 APISIX 文档大部分都过了一遍。所以当时在所在公司工作的时候,同事问他问题,他虽然并不是很清楚,但是他清楚项目的文档分布情况,直接把文档找出来看一下,就大概知道是什么问题了。他认为看文档是熟悉项目的一个合适的方式。
+Zhengsong says that when he first started participating in the community, he went through most of the APISIX documentation he could see at the time. So when he was working in his company, his colleagues asked him questions, and although he was not very clear, he knew the distribution of the project's documentation, so he could look it up directly and know roughly what the problem was. He believes that reading the documentation is an appropriate way to get familiar with the project.
 
-Apache APISIX 的项目官网上,有完善的包括如何提 PR 的新手指南。如果想参与社区的话,可以先把官网和 Github 上的主要的文档都看一下,对项目有基本的了解,也清楚项目的文档分布情况,后面再按需索引文档。
+The Apache APISIX project website has a good guide for newcomers, including how to raise PR. If you want to participate in the community, you can first read the main documentation on the website and Github to get a basic understanding of the project and the distribution of the project's documentation, and then index the documentation as needed.
 
-如果想在代码方面做贡献,或者参与设计的话,一些 Ngnix 或者 OpenResty 方面的知识的储备是必要的。包括看他们官方的文档及和代码,学习他们对于相关 feature 的实现等。
+If you want to contribute to the code, or participate in the design, some knowledge of Ngnix or OpenResty is necessary. This includes looking at their official documentation and code, and learning about their implementation of relevant features.
 
-正松说:“我觉得这一步是无法跳过的。”
+Zhengsong said, "I think this step is impossible to skip."
 
-当然,你可以以使用者的身份,去参与到社区里。比如说你觉得文档有问题,或者说你按照文档去实践的时候,发现并不是那样,你也可以去提一些 issue 指出这些问题。
+Of course, you can get involved in the community as a user. For example, if you think there is something wrong with the documentation, or if you follow the documentation and find that it is not the case, you can also raise some issues to point out these problems.
 
-大家分工合作不同,但是都是在为开源做贡献。
+We are all working together, but we are all contributing to open source.
 
-## 社区欢迎所有人
+## Everyone is welcome in the community
 
-> 但这样做更好
+> But it's better this way
 
-正松说,大家都在开源社区,首先要注意的就是要遵守社区的一些规矩,和社区的小伙伴平等交流。
+Masatsu said, we are all in the open source community, the first thing to pay attention to is to comply with some of the community rules, and the community of partners to communicate on an equal footing.
 
-交流时要注意的点可以分成两种。
+The points to note when communicating can be divided into two kinds.
 
-第一种是,假如你遇到了一些问题,那你应该尽量准确地描述问题,提供可复现的用例。这个其实是最受欢迎的,或者说最能提高沟通效率的一个方式。如果你能把一个问题描述的很清晰,那大家回答问题的效率自然会非常高。
+The first is that if you encounter some problems, then you should try to accurately describe the problem and provide reproducible use cases. This is actually the most popular, or one of the most effective ways to improve communication. If you can describe a problem very clearly, then people will naturally answer the question very high efficiency.
 
-第二种是,如果是提出想法,解决问题等,在动手做之前,对于有歧义的点,需要在公开的场合,比如 issue ,邮件列表等上面讨论,在社区内达成一致,取得共识之后,再开始做。
+The second is that if you are proposing ideas, solving problems, etc., before you do it, for points of ambiguity, you need to discuss them in a public forum, such as issue, mailing lists, etc., to reach agreement in the community, and then start doing it after you have achieved consensus.
 
-## 关于 Apache Way
+## About Apache Way
 
-> 共识也会更新,它是社区推动项目前进的一种力量。
+> Consensus will also be updated, and it is a force for the community to move the project forward.
 
-正松理解的 Apache Way,是社区大于代码。
+The Apache Way, as Masatsu understands it, is about community over code.

Review comment:
       ```suggestion
   The Apache Way, as Zhengsong understands it, is about community over code.
   ```

##########
File path: website/blog/2021/08/19/go-makes-Apache-APISIX-better.md
##########
@@ -1,60 +1,60 @@
 ---
-title: "Go 让 Apache APISIX 如虎添翼"
-author: "罗泽轩"
+title: Go gives Apache APISIX a run for its money
+author: Zexuan Luo
 authorURL: "https://github.com/spacewander"
 authorImageURL: "https://avatars.githubusercontent.com/u/4161644?v=4"
 keywords:
 - Go
 - APISIX 
-- APISIX Go 插件
+- Go Plugin
 - APISIX Go plugin
 - apisix-go-plugin-runner
 - Golang
 tags: [Practical Case]
 ---
 
-> 这篇文章将详细讲解如何用 Go 来开发 Apache APISIX 插件。通过拥抱 Go 的生态圈,为 Apache APISIX 开创一片新天地,希望 Go 能让 Apache APISIX 如虎添翼!
+> This article will explain in detail how to use Go to develop Apache APISIX plugins. By embracing the Go ecosystem and breaking new ground for Apache APISIX, we hope that Go will make Apache APISIX even better!
 
-<!--truncate-->
+<! --truncate-->

Review comment:
       ```suggestion
   <!--truncate-->
   ```

##########
File path: website/blog/2021/08/11/interview-TuZhengsong.md
##########
@@ -1,145 +1,145 @@
 ---
-title: "从新手村出来,我在 Apache APISIX 社区发出了第一个 PR"
-author: "Apache APISIX 社区"
+title: I issued my first PR in the Apache APISIX community
+author: Apache APISIX
 authorURL: "https://github.com/Yangxiamao"
 authorImageURL: "https://avatars.githubusercontent.com/u/47442074?v=4"
 keywords:
-- API 网关
+- API Gateway
 - APISIX
 - Apache APISIX
-- 开源社区
-- 开源项目
-description: 这篇采访稿讲述了屠正松从开源社区小白成长为 Apache 顶级开源项目 APISIX committer 的历程。屠正松(GitHub ID:tzssangglass)因深度参与 Apache APISIX 的开发,在社区中贡献很多,2021 年 7 月 22 日被推选为 Apache APISIX committer。
+- Community
+- Open Source
+description: "This interview is about Zhengsong Tu's journey from an open source community nerd to an APISIX committer for Apache's top open source project. Zhengsong Tu (GitHub ID: tzssangglass) was elected as an Apache APISIX committer on July 22, 2021 for his deep involvement in Apache APISIX development and his many contributions to the community."
 tags: [Interview]
 ---
 
-> 这篇采访稿讲述了屠正松从开源社区小白成长为 Apache 顶级开源项目 APISIX committer 的历程。屠正松(GitHub ID:tzssangglass)因深度参与 Apache APISIX 的开发,在社区中贡献很多,2021 年 7 月 22 日被推选为 Apache APISIX committer。
+> This interview is about Zhengsong Tu's journey from an open source community nerd to an APISIX committer for Apache's top open source project. Zhengsong Tu (GitHub ID: tzssangglass) was elected as an Apache APISIX committer on July 22, 2021 for his deep involvement in Apache APISIX development and his many contributions to the community.
 
 <!--truncate-->
 
-> 当我看到那个 issue 后,就有种强烈的想要参与到社区的冲动。看了社区的新手指南后,我像从新手村出来的勇者,准备打怪。
+> When I saw that issue, I had a strong urge to get involved in the community. After reading the community's newbie guide, I was like a brave man coming out of the newbie village, ready to fight.
 >
-> —— Apache APISIX committer 屠正松
+> -- Zhengsong Tu, Apache APISIX committer
 
-历时 282 天,屠正松(GitHub ID:tzssangglass)从开源社区的小白成长为了 Apache APISIX 的 committer。
+In 282 days, Zhengsong Tu (GitHub ID: tzssangglass) has grown from an open source community nerd to an Apache APISIX committer.
 
 ![Apache APISIX committer tzssangglass github](/img/blog_img/2021-08-11-1.webp)
 
-屠正松因深度参与 Apache APISIX 的开发,在社区中贡献很多,2021 年 7 月 22 日被推选为 Apache APISIX committer。
+Zhengsong Tu was elected as Apache APISIX committer on July 22, 2021 for his deep involvement in Apache APISIX development and many contributions in the community.
 
-在一个平淡的下午,我们和正松连线聊了聊。因为疫情关系,居住在南京的他已经多日未外出。在没有和他聊天之前,我没有想到,胡子拉碴的他,竟然走过了这么曲折的路。
+On an uneventful afternoon, we chatted with Zhengsong by phone. Because of the epidemic, he has not been out for many days in Nanjing. Before I talked to him, I didn't expect that the bearded man had traveled such a winding road.
 
-## 大学,我的大学
+## University, my university
 
-> 我大学的时候学的是通信工程,每天最开心的事就是踢球。现在有时候会想,如果能带着现在的记忆回到大学时光就好了。
+> When I was in college, I studied communication engineering, and the happiest thing I did every day was to play soccer. Now sometimes I think that it would be nice to go back to my college days with the memories I have now.
 
-正松在大学期间里面其实没怎么接触过编程,他当年其实有 C 语言的编程课,但是因为忙着踢球,挂科了。可是,他挂科之后的补考也没过,导致重修。最尴尬的是,他重修也没过,后来怎么办呢?毕业之前还有毕业清考。这可不能再挂了,于是正松就去图书馆去借了一本 C 语言的书来看。
+Zhengsong actually didn't have much contact with programming during his college years, he actually had a C programming class, but he failed it because he was too busy playing soccer. However, he failed a make-up exam after failing the class, resulting in a retake. The most embarrassing thing is that he failed the retake as well, so what did he do afterwards? There was a graduation clearing exam before graduation. This can not be failed again, so Zhengsong went to the library to borrow a C language book to read.
 
-“我当时心想,C 语言真的这么难吗?”正松说。
+"I was thinking, "Is C really that hard?" Zhengsong said.
 
-然后他就一直看一直看,看着看着就突然发现编程好像有那么点意思,他看懂了!最后他在毕业前顺利通过了考试。在毕业之后,找到了一份做程序员的工作。
+Then he kept reading and reading and reading, and suddenly he realized that programming seemed to have some meaning, and he understood it! He finally passed the exam before graduating. After graduation, he found a job as a programmer.
 
-“我本来都准备毕业回家找个厂上班了。”,他半开玩笑地说。
+"I was ready to graduate and go home and find a factory to work." , he said half-jokingly.
 
-彼时,他可能不会想到如今的他会成为数个知名开源项目的 developer,参与一些支撑着千万级并发流量的基础设施的开发。
+At that time, he probably wouldn't have thought that today he would be the developer of several well-known open source projects, and involved in the development of some infrastructure that supports millions of concurrent traffic.
 
-## 出象牙塔记
+## Out of the Ivory Tower
 
-> 在工业界,真实的业务场景和学校里学的很不一样的
+> In industry, the real business scenario is very different from what you learn in school.
 
-正松的第一份工作就职于一家做穿戴设备的创业公司,从事智能手环的研发工作。正松和他的前同事们需要通过处理从智能手环上的获取的各种传感器数据,来完成对用户的心率、运动量、血压等的监测。
+Zhengsong's first job was at a wearable device startup, working on the development of smart bracelets. Zhengsong and his former colleagues had to process various sensor data from the smart bracelet to monitor the user's heart rate, exercise, blood pressure and so on.
 
-“工作蛮好玩的,因为在工业界,真实的业务场景和学校里学的很不一样的,很多东西都得从头开始学”,正松说。
+"It was fun because in industry, the real business scenario is very different from what you learn in school, and a lot of things have to be learned from scratch," Masatsu said.
 
-有一天下班之后,这家公司的老板娘突然发了一条信息,说公司的员工暂时休假,什么时候上班等通知。
+One day after work, the owner of this company suddenly sent a message saying that the company's employees were on temporary leave and that they would wait to be notified when to work.
 
-正松当时就觉得不对劲,怎么好好的上着班,突然就休假了?然后他立马打开招聘软件,开始找新的工作。后来才知道,公司的老板跟供应商有合同纠纷,公司短暂停摆了。
+Masatsu felt something was wrong at that time, how to work well, suddenly on vacation? Then he immediately opened the recruitment software and started looking for a new job. Later, he found out that the owner of the company had a contract dispute with the supplier, and the company was briefly shut down.
 
-然后,正松便到另外一家公司从事后端业务开发的工作,学习业界规范、进一步增进技术。过了快一年,因为正松比较喜欢 Nginx、OpenResty、Netty 这类简洁和高性能的技术,他进入一家大公司的开发团队,从事中间件相关开发工作。
+Then, Masatsu went to another company to engage in back-end business development work, to learn the industry norms and further improve technology. After almost a year, he joined the development team of a large company to work on middleware-related development because he liked the simplicity and high performance of technologies like Nginx, OpenResty, and Netty.
 
-“在这家大公司,我做的离业务稍微远那么一点点,更偏向技术一些。“正松说。
+"In this big company, I did a little bit far from the business, more technically oriented. "Masatsu said.
 
-正松接触 Apache APISIX 的时间是 2020 年 9 月份,那时候,他所在的团队使用的是 Kong,但是当时 Kong 无法完全满足他们的需求,于是他们便重新做网关的技术选型,试图寻找更好的方案。正松担任本次技术选型的负责人,于是他关注到了 Apache 基金会的顶级项目 Apache APISIX,进而接触了 Apache APISIX 的社区。
+Zhengsong's contact with Apache APISIX was in September 2020, when his team was using Kong, but Kong was not fully meeting their needs, so they redid the technical selection of the gateway to try to find a better solution. Masatsu was in charge of this technical selection, so he came across the Apache Foundation's top project, Apache APISIX, and was introduced to the Apache APISIX community.
 
-彼时的他,已经毕业三年多了。
+At that time, he had already graduated more than three years ago.
 
-## 出新手村
+## Out of the newbie village
 
-> 我可以给 Apache 基金会的顶级项目提交代码了!作为一个技术工作者,这是一种技术上的自信。
+> I can submit code to the Apache Foundation's top projects! As a technical worker, that's a lot of technical confidence.
 
-正松在开源社区的第一个 PR 是一个 enhancement(功能增强)类型的 PR,这个 PR 让 Apache APISIX 支持了多端口监听。
+Zhengsong's first PR in the open source community was an enhancement type PR, which enabled Apache APISIX to support multi-port listening.
 
-- issue:https://github.com/apache/apisix/issues/1195
-- PR:https://github.com/apache/apisix/pull/2409
+- issue: https://github.com/apache/apisix/issues/1195
+- PR: https://github.com/apache/apisix/pull/2409
 
-这个功能是正松公司需要的,在 issue 区也早有人提到,但是不知为何一直无人认领。之前,正松正好对这方面的知识有所了解,于是他想:”我可以给 Apache APISIX 提个 PR 来 fix 这个问题。“所以他在 issue 里主动要求把这个问题指派给他。
+This feature is needed by Masatsu and has been mentioned in the issue area for a long time, but for some reason it has been unclaimed. Before that, Zhengsong happened to know something about this, so he thought, "I can propose a PR to Apache APISIX to fix this problem. "So he volunteered to have the issue assigned to him in the issue.
 
-他说:“当时我有一种强烈的参与社区的冲动,然后我看了一下 Apache APISIX 社区的新手指南,然后就像拿着武器从新手村出来一样,兴致冲冲的准备参与。”
+He says, "I had a strong urge to get involved in the community, and then I looked at the Apache APISIX community's Beginner's Guide and was as excited to get involved as if I were coming out of the Beginner's Village with a weapon."
 
-选择了这个 issue 之后,正松开始在 GitHub 上面开始跟社区的伙伴讨论细节上的问题,像是配置端口的 style、实现的思路等。在讨论完之后,他开始动手实现。每天晚上下班之后去翻看 Apache APISIX 的代码,测试相关用例。在经历了三四个晚上的奋斗后,测试第一次跑通了!
+After choosing this issue, Masatsu started discussing details with his community partners on GitHub, such as the style of the configuration port, the idea of the implementation, and so on. After the discussion, he started to implement it. Every night after work, he went through the Apache APISIX code and tested the use cases. After three or four nights of struggling, the test ran for the first time!

Review comment:
       ```suggestion
   After choosing this issue, Zhengsong started discussing details with his community partners on GitHub, such as the style of the configuration port, the idea of the implementation, and so on. After the discussion, he started to implement it. Every night after work, he went through the Apache APISIX code and tested the use cases. After three or four nights of struggling, the test ran for the first time!
   ```

##########
File path: website/blog/2021/08/11/interview-TuZhengsong.md
##########
@@ -1,145 +1,145 @@
 ---
-title: "从新手村出来,我在 Apache APISIX 社区发出了第一个 PR"
-author: "Apache APISIX 社区"
+title: I issued my first PR in the Apache APISIX community
+author: Apache APISIX
 authorURL: "https://github.com/Yangxiamao"
 authorImageURL: "https://avatars.githubusercontent.com/u/47442074?v=4"
 keywords:
-- API 网关
+- API Gateway
 - APISIX
 - Apache APISIX
-- 开源社区
-- 开源项目
-description: 这篇采访稿讲述了屠正松从开源社区小白成长为 Apache 顶级开源项目 APISIX committer 的历程。屠正松(GitHub ID:tzssangglass)因深度参与 Apache APISIX 的开发,在社区中贡献很多,2021 年 7 月 22 日被推选为 Apache APISIX committer。
+- Community
+- Open Source
+description: "This interview is about Zhengsong Tu's journey from an open source community nerd to an APISIX committer for Apache's top open source project. Zhengsong Tu (GitHub ID: tzssangglass) was elected as an Apache APISIX committer on July 22, 2021 for his deep involvement in Apache APISIX development and his many contributions to the community."
 tags: [Interview]
 ---
 
-> 这篇采访稿讲述了屠正松从开源社区小白成长为 Apache 顶级开源项目 APISIX committer 的历程。屠正松(GitHub ID:tzssangglass)因深度参与 Apache APISIX 的开发,在社区中贡献很多,2021 年 7 月 22 日被推选为 Apache APISIX committer。
+> This interview is about Zhengsong Tu's journey from an open source community nerd to an APISIX committer for Apache's top open source project. Zhengsong Tu (GitHub ID: tzssangglass) was elected as an Apache APISIX committer on July 22, 2021 for his deep involvement in Apache APISIX development and his many contributions to the community.
 
 <!--truncate-->
 
-> 当我看到那个 issue 后,就有种强烈的想要参与到社区的冲动。看了社区的新手指南后,我像从新手村出来的勇者,准备打怪。
+> When I saw that issue, I had a strong urge to get involved in the community. After reading the community's newbie guide, I was like a brave man coming out of the newbie village, ready to fight.
 >
-> —— Apache APISIX committer 屠正松
+> -- Zhengsong Tu, Apache APISIX committer
 
-历时 282 天,屠正松(GitHub ID:tzssangglass)从开源社区的小白成长为了 Apache APISIX 的 committer。
+In 282 days, Zhengsong Tu (GitHub ID: tzssangglass) has grown from an open source community nerd to an Apache APISIX committer.
 
 ![Apache APISIX committer tzssangglass github](/img/blog_img/2021-08-11-1.webp)
 
-屠正松因深度参与 Apache APISIX 的开发,在社区中贡献很多,2021 年 7 月 22 日被推选为 Apache APISIX committer。
+Zhengsong Tu was elected as Apache APISIX committer on July 22, 2021 for his deep involvement in Apache APISIX development and many contributions in the community.
 
-在一个平淡的下午,我们和正松连线聊了聊。因为疫情关系,居住在南京的他已经多日未外出。在没有和他聊天之前,我没有想到,胡子拉碴的他,竟然走过了这么曲折的路。
+On an uneventful afternoon, we chatted with Zhengsong by phone. Because of the epidemic, he has not been out for many days in Nanjing. Before I talked to him, I didn't expect that the bearded man had traveled such a winding road.
 
-## 大学,我的大学
+## University, my university
 
-> 我大学的时候学的是通信工程,每天最开心的事就是踢球。现在有时候会想,如果能带着现在的记忆回到大学时光就好了。
+> When I was in college, I studied communication engineering, and the happiest thing I did every day was to play soccer. Now sometimes I think that it would be nice to go back to my college days with the memories I have now.
 
-正松在大学期间里面其实没怎么接触过编程,他当年其实有 C 语言的编程课,但是因为忙着踢球,挂科了。可是,他挂科之后的补考也没过,导致重修。最尴尬的是,他重修也没过,后来怎么办呢?毕业之前还有毕业清考。这可不能再挂了,于是正松就去图书馆去借了一本 C 语言的书来看。
+Zhengsong actually didn't have much contact with programming during his college years, he actually had a C programming class, but he failed it because he was too busy playing soccer. However, he failed a make-up exam after failing the class, resulting in a retake. The most embarrassing thing is that he failed the retake as well, so what did he do afterwards? There was a graduation clearing exam before graduation. This can not be failed again, so Zhengsong went to the library to borrow a C language book to read.
 
-“我当时心想,C 语言真的这么难吗?”正松说。
+"I was thinking, "Is C really that hard?" Zhengsong said.
 
-然后他就一直看一直看,看着看着就突然发现编程好像有那么点意思,他看懂了!最后他在毕业前顺利通过了考试。在毕业之后,找到了一份做程序员的工作。
+Then he kept reading and reading and reading, and suddenly he realized that programming seemed to have some meaning, and he understood it! He finally passed the exam before graduating. After graduation, he found a job as a programmer.
 
-“我本来都准备毕业回家找个厂上班了。”,他半开玩笑地说。
+"I was ready to graduate and go home and find a factory to work." , he said half-jokingly.
 
-彼时,他可能不会想到如今的他会成为数个知名开源项目的 developer,参与一些支撑着千万级并发流量的基础设施的开发。
+At that time, he probably wouldn't have thought that today he would be the developer of several well-known open source projects, and involved in the development of some infrastructure that supports millions of concurrent traffic.
 
-## 出象牙塔记
+## Out of the Ivory Tower
 
-> 在工业界,真实的业务场景和学校里学的很不一样的
+> In industry, the real business scenario is very different from what you learn in school.
 
-正松的第一份工作就职于一家做穿戴设备的创业公司,从事智能手环的研发工作。正松和他的前同事们需要通过处理从智能手环上的获取的各种传感器数据,来完成对用户的心率、运动量、血压等的监测。
+Zhengsong's first job was at a wearable device startup, working on the development of smart bracelets. Zhengsong and his former colleagues had to process various sensor data from the smart bracelet to monitor the user's heart rate, exercise, blood pressure and so on.
 
-“工作蛮好玩的,因为在工业界,真实的业务场景和学校里学的很不一样的,很多东西都得从头开始学”,正松说。
+"It was fun because in industry, the real business scenario is very different from what you learn in school, and a lot of things have to be learned from scratch," Masatsu said.
 
-有一天下班之后,这家公司的老板娘突然发了一条信息,说公司的员工暂时休假,什么时候上班等通知。
+One day after work, the owner of this company suddenly sent a message saying that the company's employees were on temporary leave and that they would wait to be notified when to work.
 
-正松当时就觉得不对劲,怎么好好的上着班,突然就休假了?然后他立马打开招聘软件,开始找新的工作。后来才知道,公司的老板跟供应商有合同纠纷,公司短暂停摆了。
+Masatsu felt something was wrong at that time, how to work well, suddenly on vacation? Then he immediately opened the recruitment software and started looking for a new job. Later, he found out that the owner of the company had a contract dispute with the supplier, and the company was briefly shut down.
 
-然后,正松便到另外一家公司从事后端业务开发的工作,学习业界规范、进一步增进技术。过了快一年,因为正松比较喜欢 Nginx、OpenResty、Netty 这类简洁和高性能的技术,他进入一家大公司的开发团队,从事中间件相关开发工作。
+Then, Masatsu went to another company to engage in back-end business development work, to learn the industry norms and further improve technology. After almost a year, he joined the development team of a large company to work on middleware-related development because he liked the simplicity and high performance of technologies like Nginx, OpenResty, and Netty.
 
-“在这家大公司,我做的离业务稍微远那么一点点,更偏向技术一些。“正松说。
+"In this big company, I did a little bit far from the business, more technically oriented. "Masatsu said.
 
-正松接触 Apache APISIX 的时间是 2020 年 9 月份,那时候,他所在的团队使用的是 Kong,但是当时 Kong 无法完全满足他们的需求,于是他们便重新做网关的技术选型,试图寻找更好的方案。正松担任本次技术选型的负责人,于是他关注到了 Apache 基金会的顶级项目 Apache APISIX,进而接触了 Apache APISIX 的社区。
+Zhengsong's contact with Apache APISIX was in September 2020, when his team was using Kong, but Kong was not fully meeting their needs, so they redid the technical selection of the gateway to try to find a better solution. Masatsu was in charge of this technical selection, so he came across the Apache Foundation's top project, Apache APISIX, and was introduced to the Apache APISIX community.
 
-彼时的他,已经毕业三年多了。
+At that time, he had already graduated more than three years ago.
 
-## 出新手村
+## Out of the newbie village
 
-> 我可以给 Apache 基金会的顶级项目提交代码了!作为一个技术工作者,这是一种技术上的自信。
+> I can submit code to the Apache Foundation's top projects! As a technical worker, that's a lot of technical confidence.
 
-正松在开源社区的第一个 PR 是一个 enhancement(功能增强)类型的 PR,这个 PR 让 Apache APISIX 支持了多端口监听。
+Zhengsong's first PR in the open source community was an enhancement type PR, which enabled Apache APISIX to support multi-port listening.
 
-- issue:https://github.com/apache/apisix/issues/1195
-- PR:https://github.com/apache/apisix/pull/2409
+- issue: https://github.com/apache/apisix/issues/1195
+- PR: https://github.com/apache/apisix/pull/2409
 
-这个功能是正松公司需要的,在 issue 区也早有人提到,但是不知为何一直无人认领。之前,正松正好对这方面的知识有所了解,于是他想:”我可以给 Apache APISIX 提个 PR 来 fix 这个问题。“所以他在 issue 里主动要求把这个问题指派给他。
+This feature is needed by Masatsu and has been mentioned in the issue area for a long time, but for some reason it has been unclaimed. Before that, Zhengsong happened to know something about this, so he thought, "I can propose a PR to Apache APISIX to fix this problem. "So he volunteered to have the issue assigned to him in the issue.
 
-他说:“当时我有一种强烈的参与社区的冲动,然后我看了一下 Apache APISIX 社区的新手指南,然后就像拿着武器从新手村出来一样,兴致冲冲的准备参与。”
+He says, "I had a strong urge to get involved in the community, and then I looked at the Apache APISIX community's Beginner's Guide and was as excited to get involved as if I were coming out of the Beginner's Village with a weapon."
 
-选择了这个 issue 之后,正松开始在 GitHub 上面开始跟社区的伙伴讨论细节上的问题,像是配置端口的 style、实现的思路等。在讨论完之后,他开始动手实现。每天晚上下班之后去翻看 Apache APISIX 的代码,测试相关用例。在经历了三四个晚上的奋斗后,测试第一次跑通了!
+After choosing this issue, Masatsu started discussing details with his community partners on GitHub, such as the style of the configuration port, the idea of the implementation, and so on. After the discussion, he started to implement it. Every night after work, he went through the Apache APISIX code and tested the use cases. After three or four nights of struggling, the test ran for the first time!
 
-当时正松内心非常的兴奋,马上按照那个新手指南的引导把 PR 提上去了。然后接受 Code Review 的意见,进一步修改代码。终于,在 10 月 18 号,PR 顺利地 merge 进了仓库。
+Masatsu was very excited and immediately followed the guide to bring up the PR. Then he accepted the comments from Code Review and further modified the code. Finally, on October 18, the PR was successfully merged into the repository.
 
 ![Apache APISIX committer tzssangglass pr](/img/blog_img/2021-08-11-2.webp)
 
-“当时我非常的激动,感觉自己终于实质性地参与到开源社区里面去了。我可以给 Apache 基金会的顶级项目提交代码了!作为一个技术工作者,这是一种技术上的自信。”
+"I was very excited and felt like I was finally substantially involved in the open source community. I could submit code to the Apache Foundation's top projects! As a technical worker, it was a technical confidence."
 
-**这是正松在开源世界的第一个 PR。**
+**This is Zhengsong's first PR in the open source world.**
 
-## 在社区印象深刻的事
+## Things that impressed me in the community
 
-> 因为 etcd 有 MaxCallRecvMsgSize 的限制,就从 etcd 的源头去解决,这是最优雅,也是最适合的。
+> Because etcd has a MaxCallRecvMsgSize limit, it was most elegant and appropriate to go to the source of etcd.
 
-当我们问到,正松在社区印象最深刻的事情是什么的时候,正松想了想说,可能是一个和 bug 有关的问题:etcd 的 MaxCallRecvMsgSize 限制。
+When we asked what was the thing that impressed Masatsu most in the community, Masatsu thought about it and said it was probably a bug-related issue: etcd's MaxCallRecvMsgSize limitation.
 
-正松曾经被 etcd 限制返回体大小的问题折磨过,社区内也多次反映、讨论过这个问题,但在 Apache APISIX 上无论怎么处理都不是很优雅。
+Masatsu had been tormented by etcd's return size limitation problem, and the community had reflected and discussed this problem many times, but it was not very elegant on Apache APISIX no matter how it was handled.
 
-直到今年 4 月份,支流科技的一位小伙伴给 etcd 提交了 PR,最终解决了这个问题。正松听说这个消息时,感到非常的震撼,当时他没有想过这个事情会以这样的方式去解决。但是现在来看的话,这个方法确实是最适合的。
+In April this year, one of our partners submitted a PR to etcd, which finally solved the problem. When Masatsu heard about this, he was very shocked, he didn't think it would be solved in such a way. But in hindsight, this was the way to go.
 
-“因为 etcd 有 MaxCallRecvMsgSize 的限制,就从 etcd 的源头去解决,这是最优雅,也是最适合的。这是很棒的跨社区合作的示例”,正松说。
+"Because etcd has a MaxCallRecvMsgSize limit, it's most elegant and appropriate to go to the source of etcd. This is great example of cross-community collaboration," says Masatsu.
 
 ## Sir, this way
 
-> 大家分工合作不同,但是都是在为开源做贡献。
+> We're all working together differently, but we're all contributing to open source.
 
-正松说,他刚开始参与社区的时候,把当时能看到的 APISIX 文档大部分都过了一遍。所以当时在所在公司工作的时候,同事问他问题,他虽然并不是很清楚,但是他清楚项目的文档分布情况,直接把文档找出来看一下,就大概知道是什么问题了。他认为看文档是熟悉项目的一个合适的方式。
+Zhengsong says that when he first started participating in the community, he went through most of the APISIX documentation he could see at the time. So when he was working in his company, his colleagues asked him questions, and although he was not very clear, he knew the distribution of the project's documentation, so he could look it up directly and know roughly what the problem was. He believes that reading the documentation is an appropriate way to get familiar with the project.
 
-Apache APISIX 的项目官网上,有完善的包括如何提 PR 的新手指南。如果想参与社区的话,可以先把官网和 Github 上的主要的文档都看一下,对项目有基本的了解,也清楚项目的文档分布情况,后面再按需索引文档。
+The Apache APISIX project website has a good guide for newcomers, including how to raise PR. If you want to participate in the community, you can first read the main documentation on the website and Github to get a basic understanding of the project and the distribution of the project's documentation, and then index the documentation as needed.
 
-如果想在代码方面做贡献,或者参与设计的话,一些 Ngnix 或者 OpenResty 方面的知识的储备是必要的。包括看他们官方的文档及和代码,学习他们对于相关 feature 的实现等。
+If you want to contribute to the code, or participate in the design, some knowledge of Ngnix or OpenResty is necessary. This includes looking at their official documentation and code, and learning about their implementation of relevant features.
 
-正松说:“我觉得这一步是无法跳过的。”
+Zhengsong said, "I think this step is impossible to skip."
 
-当然,你可以以使用者的身份,去参与到社区里。比如说你觉得文档有问题,或者说你按照文档去实践的时候,发现并不是那样,你也可以去提一些 issue 指出这些问题。
+Of course, you can get involved in the community as a user. For example, if you think there is something wrong with the documentation, or if you follow the documentation and find that it is not the case, you can also raise some issues to point out these problems.
 
-大家分工合作不同,但是都是在为开源做贡献。
+We are all working together, but we are all contributing to open source.
 
-## 社区欢迎所有人
+## Everyone is welcome in the community
 
-> 但这样做更好
+> But it's better this way
 
-正松说,大家都在开源社区,首先要注意的就是要遵守社区的一些规矩,和社区的小伙伴平等交流。
+Masatsu said, we are all in the open source community, the first thing to pay attention to is to comply with some of the community rules, and the community of partners to communicate on an equal footing.
 
-交流时要注意的点可以分成两种。
+The points to note when communicating can be divided into two kinds.
 
-第一种是,假如你遇到了一些问题,那你应该尽量准确地描述问题,提供可复现的用例。这个其实是最受欢迎的,或者说最能提高沟通效率的一个方式。如果你能把一个问题描述的很清晰,那大家回答问题的效率自然会非常高。
+The first is that if you encounter some problems, then you should try to accurately describe the problem and provide reproducible use cases. This is actually the most popular, or one of the most effective ways to improve communication. If you can describe a problem very clearly, then people will naturally answer the question very high efficiency.
 
-第二种是,如果是提出想法,解决问题等,在动手做之前,对于有歧义的点,需要在公开的场合,比如 issue ,邮件列表等上面讨论,在社区内达成一致,取得共识之后,再开始做。
+The second is that if you are proposing ideas, solving problems, etc., before you do it, for points of ambiguity, you need to discuss them in a public forum, such as issue, mailing lists, etc., to reach agreement in the community, and then start doing it after you have achieved consensus.
 
-## 关于 Apache Way
+## About Apache Way
 
-> 共识也会更新,它是社区推动项目前进的一种力量。
+> Consensus will also be updated, and it is a force for the community to move the project forward.
 
-正松理解的 Apache Way,是社区大于代码。
+The Apache Way, as Masatsu understands it, is about community over code.
 
-他认为,社区本质上是人与人之间的合作,大家分工合作,各司其职。但是在合作和各司其职之前,大家是需要形成一些共识。
+He believes that the community is essentially a collaboration between people, where everyone divides up the work and does their own job. But before we cooperate and do our own work, we need to form some consensus.
 
-共识是一点点积累起来的。社区参与者们抛出一个个问题,社区内会讨论,辩驳,验证,直至最后解决这些问题。在这个过程中,共识在社区内慢慢形成,共识可能是规范,也可能是边界,或者其他的形式。共识也会更新,它是社区推动项目前进的一种力量。这个过程带有一些理想主义色彩。
+Consensus is built up little by little. The community participants throw out a problem, and the community will discuss, argue, verify, and finally solve these problems. In this process, consensus is slowly formed in the community, and it may be a norm, a boundary, or some other form of consensus. Consensus is also updated, and it is a force for the community to move the project forward. This process has some idealistic overtones.
 
-社区的共识其实比你做代码贡献更重要,因为有了共识之后,后面去回溯某一个改动的点的时候,会更加清晰,知道这个改动的起源和当时的视角。
+Community consensus is actually more important than you making code contributions, because with consensus, when you go back to a point of change later, it will be clearer to know the origin of the change and the perspective at that time.
 
-## 最后
+## Finally
 
-最后在关麦之前,我们请正松给我们推荐一些东西。正松想了想,说:“我推荐了一部德国电影,跟社会工程学相关的《我是谁:没有绝对安全的系统》,和一本书,孔飞力老师的《叫魂:1768 年中国妖术大恐慌》。希望大家在忙碌的工作中,也不要忘了充实自己的精神生活。“
+Finally, before we shut down the mike, we asked Masatsu to recommend something to us. After thinking about it, Masatsu said, "I recommend a German film related to social engineering, Who Am I: No Absolutely Safe System, and a book by Fei-Li Kong, Calling the Spirits: The Great Chinese Demon Panic of 1768. I hope you will not forget to enrich your spiritual life even in the midst of your busy work. "

Review comment:
       ```suggestion
   Finally, before we shut down the mike, we asked Zhengsong to recommend something to us. After thinking about it, Zhengsong said, "I recommend a German film related to social engineering, Who Am I: No Absolutely Safe System, and a book by Fei-Li Kong, Calling the Spirits: The Great Chinese Demon Panic of 1768. I hope you will not forget to enrich your spiritual life even in the midst of your busy work. "
   ```

##########
File path: website/blog/2021/08/18/Auth-with-Casbin-in-Apache-APISIX.md
##########
@@ -72,15 +72,15 @@ g, alice, admin
 g, bob,admin
 ```
 
-模型里的 matcher 表明:
+The matcher in the model indicates that.
 
-1. `(g(r.sub, p.sub) || keyMatch(r.sub, p.sub))`:请求里的 subject 和策略里的 subject 有着相同的角色或者请求里的 subject 和策略里的 subject 可以通过内置的方法 `keyMatch` 匹配。`keyMatch` 作为 Lua Casbin 的内置函数,相关的描述以及更多的函数可跳转 [lua-casbin](https://github.com/casbin/lua-casbin/blob/master/src/util/BuiltInFunctions.lua)。
-2. `keyMatch(r.obj, p.obj)`:请求里的 object 和策略里的 object 可相互匹配(代指 URL 链接)。
-3. `keyMatch(r.act, p.act)`:请求里的 action 和策略里的 action 可相互匹配(代指 HTTP 请求方法)。
+1. `(g(r.sub, p.sub) || keyMatch(r.sub, p.sub))`: The subject in the request and the subject in the policy have the same role or the subject in the request and the subject in the policy can be matched by the built-in method `keyMatch`. `keyMatch` is a built-in function of Lua Casbin, a description of which and more can be found at [lua-casbin](https://github.com/casbin/lua-casbin/blob/master/src/util/BuiltInFunctions. lua). 2.
+2. `keyMatch(r.obj, p.obj)`: the object in the request and the object in the policy can match each other (proxy for URL links). 3.
+3. `keyMatch(r.act, p.act)`: the action in the request and the action in the policy match each other (proxy for the HTTP request method).

Review comment:
       ```suggestion
   1. `(g(r.sub, p.sub) || keyMatch(r.sub, p.sub))`: The subject in the request and the subject in the policy have the same role or the subject in the request and the subject in the policy can be matched by the built-in method `keyMatch`. `keyMatch` is a built-in function of Lua Casbin, a description of which and more can be found at [lua-casbin](https://github.com/casbin/lua-casbin/blob/master/src/util/BuiltInFunctions. lua).
   2. `keyMatch(r.obj, p.obj)`: the object in the request and the object in the policy can match each other (proxy for URL links).
   3. `keyMatch(r.act, p.act)`: the action in the request and the action in the policy match each other (proxy for the HTTP request method).
   ```

##########
File path: website/blog/2021/08/19/go-makes-Apache-APISIX-better.md
##########
@@ -178,7 +178,7 @@ curl http://127.0.0.1:9080/apisix/admin/routes/1 -H 'X-API-KEY: edd1c9f034335f13
   "plugins": {
     "ext-plugin-pre-req": {
       "conf": [
-        {"name":"say", "value":"{\"body\":\"hello\"}"}
+        {"name": "say", "value":"{\"body\":\"hello\"}"}

Review comment:
       ```suggestion
           {"name":"say", "value":"{\"body\":\"hello\"}"}
   ```

##########
File path: website/blog/2021/08/19/go-makes-Apache-APISIX-better.md
##########
@@ -97,19 +97,19 @@ func (p *Say) ParseConf(in []byte) (interface{}, error) {
 }
 ```
 
-该插件的上下文是这样的:
+The context of the plugin looks like this.
 
 ```go
 type SayConf struct {
-  Body string `json:"body"`
+  Body string `json: "body"`
 }
 ```
 
-`Filter` 会在每个配置了 say 插件的请求中执行。
+`Filter` is executed on every request with the say plugin configured.
 
 ```go
 func (p *Say) Filter(conf interface{}, w http.ResponseWriter, r pkgHTTP.Request) {
-  body := conf.(SayConf).Body
+  body := conf.(SayConf).

Review comment:
       ```suggestion
     body := conf.(SayConf).Body
   ```

##########
File path: website/blog/2021/08/18/Auth-with-Casbin-in-Apache-APISIX.md
##########
@@ -1,48 +1,48 @@
 ---
-title: "在 Apache APISIX 中使用 Casbin 进行授权"
-author: "Casbin 社区 & Apache APISIX 社区"
+title: Licensing with Casbin in Apache APISIX
+author: Casbin & Apache APISIX
 keywords:
-- API 网关
+- API Gateway
 - APISIX
 - Apache APISIX
 - Casbin
 - RBAC
-description: 当我们在使用 Apache APISIX 时,可能想要在应用里添加复杂的授权逻辑。在此篇文章中,我们将使用 Apache APISIX 的内置 Casbin 插件(authz-casbin)来实现基于角色的访问控制(RBAC)模型。
+description: When we are using Apache APISIX, we may want to add complex authorization logic to our application. In this article, we will use the built-in Casbin plugin (authz-casbin) of Apache APISIX to implement the role-based access control (RBAC) model.
 tags: [Practical Case]
 ---
 
-> 当我们在使用 Apache APISIX 时,可能想要在应用里添加复杂的授权逻辑。在此篇文章中,我们将使用 Apache APISIX 的内置 Casbin 插件(authz-casbin)来实现基于角色的访问控制(RBAC)模型。
+> When we are using Apache APISIX, we may want to add complex authorization logic to our application. In this post, we will use the built-in Casbin plugin (authz-casbin) for Apache APISIX to implement a role-based access control (RBAC) model.
 
-<!--truncate-->
+<! --truncate-->

Review comment:
       ```suggestion
   <!--truncate-->
   ```

##########
File path: website/blog/2021/08/18/Auth-with-Casbin-in-Apache-APISIX.md
##########
@@ -1,48 +1,48 @@
 ---
-title: "在 Apache APISIX 中使用 Casbin 进行授权"
-author: "Casbin 社区 & Apache APISIX 社区"
+title: Licensing with Casbin in Apache APISIX
+author: Casbin & Apache APISIX
 keywords:
-- API 网关
+- API Gateway
 - APISIX
 - Apache APISIX
 - Casbin
 - RBAC
-description: 当我们在使用 Apache APISIX 时,可能想要在应用里添加复杂的授权逻辑。在此篇文章中,我们将使用 Apache APISIX 的内置 Casbin 插件(authz-casbin)来实现基于角色的访问控制(RBAC)模型。
+description: When we are using Apache APISIX, we may want to add complex authorization logic to our application. In this article, we will use the built-in Casbin plugin (authz-casbin) of Apache APISIX to implement the role-based access control (RBAC) model.
 tags: [Practical Case]
 ---
 
-> 当我们在使用 Apache APISIX 时,可能想要在应用里添加复杂的授权逻辑。在此篇文章中,我们将使用 Apache APISIX 的内置 Casbin 插件(authz-casbin)来实现基于角色的访问控制(RBAC)模型。
+> When we are using Apache APISIX, we may want to add complex authorization logic to our application. In this post, we will use the built-in Casbin plugin (authz-casbin) for Apache APISIX to implement a role-based access control (RBAC) model.
 
-<!--truncate-->
+<! --truncate-->
 
-## 介绍
+## Introduction
 
 ### Apache APISIX
 
-[Apache APISIX](https://github.com/apache/apisix) 是一个动态、实时、高性能的 API 网关, 提供负载均衡、动态上游、灰度发布、精细化路由、限流限速、服务降级、服务熔断、身份认证、可观测性等数百项功能。你可以使用 Apache APISIX 来处理传统的南北向流量,以及服务间的东西向流量, 也可以当做 [k8s ingress controller](https://github.com/apache/apisix-ingress-controller) 来使用。
+[Apache APISIX](https://github.com/apache/apisix) is a dynamic, real-time, high-performance API gateway that provides load balancing, dynamic upstream, grayscale publishing, fine-grained routing, flow and speed limiting, service degradation, service meltdown, authentication, observability, and hundreds of other features. You can use Apache APISIX for traditional north-south traffic, as well as east-west traffic between services, or as a [k8s ingress controller](https://github.com/apache/apisix-ingress-controller).
 
 ### Casbin
 
-[Casbin](https://casbin.org/zh-CN/) 是一个强大的、高效的开源访问控制框架,其权限管理机制支持多种访问控制模型。
+[Casbin](https://casbin.org/zh-CN/) is a powerful and efficient open source access control framework with a permission management mechanism that supports multiple access control models.
 
-### authz-casbin 插件介绍
+### authz-casbin plugin introduction
 
-在 Apache APISIX 的使用中,路由匹配和请求授权之间有个隐含的矛盾点:为了更高细粒度的权限控制,需要配置更高细粒度的路由,来精准识别请求并对请求进行授权。在复杂的授权模型场景下,这将导致路由数量成倍增加,加剧了运维复杂度。
-[authz-casbin](https://github.com/apache/apisix/blob/d9b928321fcdd12eef024df8c7c410424c1e0c8b/docs/en/latest/plugins/authz-casbin.md) 是一个基于 lua-casbin 的 Apache APISIX 插件,支持基于各种访问模型的强大授权。Casbin 是一个强大的、高效的开源访问控制框架,支持 ACL、RBAC、ABAC 等访问控制模型,lua-casbin 是 Casbin 访问控制框架的 Lua 版本实现。
-authz-casbin 插件可以把路由匹配和请求授权这两个功能很好地进行解耦,你可以将各种授权访问模型加载到 Apache APISIX 中,借助 lua-casbin 实现高效复杂的授权模式。
+In the use of Apache APISIX, there is an implicit tension between route matching and request authorization: for higher granularity access control, higher granularity routes need to be configured to accurately identify requests and authorize them. In complex authorization model scenarios, this leads to an exponential increase in the number of routes, which increases the complexity of operations and maintenance.
+[authz-casbin](https://github.com/apache/apisix/blob/d9b928321fcdd12eef024df8c7c410424c1e0c8b/docs/en/latest/plugins/authz-casbin. md) is a lua-casbin based Apache APISIX plugin that supports powerful authorization based on various access models. casbin is a powerful and efficient open source access control framework that supports ACL, RBAC, ABAC and other access control models. lua-casbin is a Lua version implementation of the Casbin access control framework.
+The authz-casbin plugin can decouple the two functions of route matching and request authorization very well. You can load various authorization access models into Apache APISIX and implement efficient and complex authorization models with the help of lua-casbin.
 
-**注意**:如果你想要实现身份验证(authentication),你需要使用其他插件或者自己来配置完成验证用户身份,比如 [jwt-auth](https://github.com/apache/apisix/blob/master/docs/zh/latest/plugins/jwt-auth.md) 插件。
+**Note**: If you want to implement authentication, you need to use other plugins or configure yourself to complete the authentication of the user's identity, for example [jwt-auth](https://github.com/apache/apisix/blob/master/docs/zh/ latest/plugins/jwt-auth.md) plugin.

Review comment:
       ```suggestion
   **Note**: If you want to implement authentication, you need to use other plugins or configure yourself to complete the authentication of the user's identity, for example [jwt-auth](https://github.com/apache/apisix/blob/master/docs/zh/latest/plugins/jwt-auth.md) plugin.
   ```

##########
File path: website/blog/2021/08/17/interview-airwallex.md
##########
@@ -1,86 +1,85 @@
 ---
-title: "Apache APISIX 在 Airwallex 的应用 | 专访 Airwallex 技术平台负责人李杨"
-author: "Apache APISIX 社区"
+title: Apache APISIX in Airwallex | Interview with Yang Li, Head of Airwallex Technology Platform
+author: Apache APISIX
 keywords: 
 - APISIX
 - Airwallex
-- 空中云汇
-- 金融
-- 数据主权
-description: 本文采访了 Airwallex 空中云汇 Technical Platform Lead 李杨,李杨负责公司技术平台的演进。采访中详细介绍了 Airwallex 空中云汇在做技术选型时为什么选择 Apache APISIX、Apache APISIX 在 Airwallex 空中云汇的使用场景、Apache APISIX 在生产环境的表现等。
+- Financial
+- Data Sovereignty
+description: In this article, we interviewed Airwallex Technical Platform Lead Yang Li, who is responsible for the evolution of the company's technology platform. In the interview, he introduced in detail why Airwallex chose Apache APISIX when making technology selection, the usage scenarios of Apache APISIX in Airwallex, and the performance of Apache APISIX in production environment. 
 tags: [Interview]
 ---
 
-> 本文采访了 Airwallex 空中云汇 Technical Platform Lead 李杨,李杨负责公司技术平台的演进。采访中详细介绍了 Airwallex 空中云汇在做技术选型时为什么选择 Apache APISIX、Apache APISIX 在 Airwallex 空中云汇的使用场景、Apache APISIX 在生产环境的表现等。
+> This article interviewed Airwallex Technical Platform Lead Yang Li, who is responsible for the evolution of the company's technology platform. The interview details why Airwallex chose Apache APISIX when making the technology selection, the usage scenarios of Apache APISIX in Airwallex, and the performance of Apache APISIX in the production environment.
 
 <!--truncate-->
 
-我们有幸采访到了 Airwallex 的技术平台负责人李杨,在采访中,李杨谈到了为什么在技术选型时选择 Apache APISIX,以及 Apache APISIX 在 Airwallex 的应用。
+We had a chance to interview Yang Li, the technical platform leader of Airwallex. In the interview, Yang Li talked about why he chose Apache APISIX in the technology selection, and the application of Apache APISIX in Airwallex.
 
-**Q:李博士,您好,请简单介绍一下自己和目前从事的工作。**
+**Q: Hello Dr. Li, please briefly introduce yourself and the work you are currently engaged in.**
 
-**李杨:** 你好,我叫李杨(Jan Li),哲学博士,Apache APISIX Committer,Airwallex 空中云汇 Technical Platform Lead,负责公司技术平台的演进。在加入 Airwallex 之前,曾在万向区块链领导运链盟。在万向区块链之前,曾在花旗集团领导 OTC 衍生品风控平台。
+**Jan Li:** Hi, my name is Jan Li, PhD, Apache APISIX Committer, Airwallex Technical Platform Lead, responsible for the evolution of the company's technology platform. Prior to joining Airwallex, I led the Ops Chain Alliance at Wanxiang Blockchain. Prior to Wanxiang Blockchain, he led the OTC derivatives risk control platform at Citigroup.
 
-Airwallex 空中云汇是一家全球金融科技公司,赋能各类规模的企业跨境运营,以此助力全球经济发展。以技术为核心,Airwallex(空中云汇)构建了专有的全球金融基础设施平台,全球支付网络已覆盖 130 多个国家和地区的 50 余种货币,为各类规模的企业提供数字化的金融科技产品,在全球互联的信息化时代,以更高效、安全的方式帮助企业在全世界高速发展。自 2015 年成立以来,Airwallex 空中云汇已获得来自顶级投资机构超 5 亿美元融资,目前在全球共有 12 个办公室及超过 900 名员工。
+Airwallex is a global financial technology company that empowers businesses of all sizes to operate across borders, thereby helping to grow the global economy. With technology at its core, Airwallex has built a proprietary global financial infrastructure platform with a global payment network covering more than 50 currencies in over 130 countries and regions, providing digital fintech products for businesses of all sizes to help them grow at high speed around the world in a more efficient and secure way in the globally connected information age. Since its inception in 2015, Airwallex has received over $500 million in funding from top-tier investors and now has 12 offices and over 900 employees worldwide.
 
-![Airwallex LiYang](https://static.apiseven.com/202108/20210816001.png)
+![Airwallex Li Yang](https://static.apiseven.com/202108/20210816001.png)
 
-**Q:在做技术选型的时候,是什么原因让您/您的技术团队选择使用 Apache APISIX?**
+**Q: What made you/your technical team choose to use Apache APISIX when making the technology selection?**
 
-**李杨**:API 网关是极其重要的基础技术组件,在技术选型时我们主要从 6 个维度比较了主要的网关产品:
+**Yang**: API gateway is an extremely important basic technology component, and we compared the main gateway products in 6 main dimensions during the technology selection.
 
-- **稳定性**:API 网关的稳定性至关重要,在世界排名前 1000 的网站中,有 62.1% 是 Nginx 系的,这说明 Nginx 系 web server 是经过了生产环境复杂多样场景考验的;Apache APISIX 全动态的设计也使得它能够在修改路由时不必 reload,client 的长链接也得以保持;我们也对 Apache APISIX 进行了压力测试,在 CPU 达到 70% 以上时 Apache APISIX 仍能稳定运转。
+- **Stability**: The stability of the API gateway is critical. 62.1% of the top 1000 websites in the world are Nginx-based, which means that the Nginx-based web server has been tested in complex and diverse scenarios in production environments; Apache APISIX's fully dynamic design also allows it to modify routes without having to reload, and the client's long links are maintained. The fully dynamic design of Apache APISIX also allows it to maintain long links to clients without having to reload when modifying routes; we also stress-tested Apache APISIX and found it to be stable when the CPU reached over 70%.
 
-- **性能**:每个 API 请求都会经过 API 网关,减小网关性能损耗能大大降低公司 API 整体响应时间。在 PoC 中我们比较了主要的网关产品,Apache APISIX 的响应延迟比其它网关低 50% 以上;Apache APISIX 数据面的设计也使集群中的每一个实例都相互独立,这也使得它天生支持水平扩展。
+- **Performance**: Every API request passes through the API gateway, and reducing gateway performance loss can greatly reduce the overall response time of the company's API. In our PoC comparison of the major gateway products, Apache APISIX has more than 50% lower response latency than other gateways; the design of the Apache APISIX data plane also makes each instance in the cluster independent of each other, which also makes it inherently support horizontal scaling.
 
-- **可扩展性**: API 网关模式是非常重要的微服务架构模式,符合 API 网关模式的 API 网关必须支持企业复杂的鉴权、权限控制、服务发现、限流、降级、负载均衡、白名单、动态路由等功能,所以支持怎样的定制是选择 API 网关时非常关键的考量。
+- **Scalability**: The API gateway model is a very important microservice architecture model, and API gateways that conform to the API gateway model must support complex enterprise features such as authentication, permission control, service discovery, flow restriction, degradation, load balancing, whitelisting, dynamic routing, etc. So what kind of customization is supported is a very critical consideration when choosing an API gateway.
 
-- **社区活跃度**:新的技术与需求层出不穷,一个活跃的社区是 API 网关跟上技术演进步伐的关键。早在 Apache APISIX 还是 Apache 孵化项目时,其社区就已经非常活跃,从 contributor 数量、issue 响应时间、Pull Request 数量三个指标来看都是非常活跃的社区。
+- **Community Activity**: New technologies and requirements are emerging all the time, and an active community is key for API gateways to keep pace with the evolution of technology. As early as when Apache APISIX was an Apache incubation project, its community was already very active, in terms of contributor count, issue response time, and Pull Request count.
 
-- **私有部署**:API 网关作为企业核心技术架构组件,企业应该把它部署在自己的私有网络边缘。Apache APISIX 具有良好的环境适应性,能够被轻易地部署在包括云计算平台在内的各种环境上。
+- **Private Deployment**: As a core technology architecture component, API gateways should be deployed at the edge of an enterprise's private network. Apache APISIX has good environmental adaptability and can be easily deployed on various environments, including cloud computing platforms.
 
-- **开源协议**:Apache 2.0 赋予了定制 APISIX 的企业相当大的技术自由度。
+- **Open Source Protocol**: Apache 2.0 gives considerable technical freedom to enterprises that customize APISIX.
 
-**Q:Apache APISIX 用在了哪些场景?解决了哪些问题?**
+**Q: What scenarios is Apache APISIX used in? What problems have been solved?**
 
-**李杨**:我们把 Apache APISIX 用作微服务网关模式的核心组件,它被部署在网络边缘,为所有进入 Airwallex 的流量提供通用网关功能,解决的问题包括:
+**Yang**: We use Apache APISIX as a core component of our microservice gateway model, which is deployed at the edge of the network to provide common gateway functionality for all traffic coming into Airwallex, solving problems such as
 
-- 数据主权问题:对于跨国运营的金融基础设施,数据主权是非常关键的监管要求。为此,我们利用 Apache APISIX 动态上游选择的功能开发了符合监管的动态路由插件。动态路由能够根据用户请求的特征智能选择上游来进行请求分发,将复杂的多数据中心协同问题从服务层抽象到网关层。动态路由实质是要回答两个问题:如何对上游进行分组?如何匹配请求与分组。
+- Data sovereignty issues: Data sovereignty is a very critical regulatory requirement for financial infrastructures that operate across borders. To this end, we developed a regulatory compliant dynamic routing plug-in using the Apache APISIX dynamic upstream selection feature. Dynamic routing can intelligently select upstreams for request distribution based on the characteristics of user requests, abstracting the complex multi-data center collaboration problem from the service layer to the gateway layer. Dynamic routing essentially has to answer two questions: How to group upstreams? How to match requests with groupings.
 
-- 微服务隔离:Airwallex 希望各微服务的工程团队能够自主控制自己的服务,有效降低沟通协调的成本,提高工程效能。这一架构理念要求被各团队共享的基础架构组件,比如: API Gateway 都能支持多租户隔离。在保证整个系统的强壮性和成本可控的同时,允许业务团队根据自身的需要对网关功能进行配置和扩展,保持微服务团队与服务的独立性。
+- Microservice Isolation: Airwallex wants the engineering teams of each microservice to have autonomous control over their own services, effectively reducing the cost of communication and coordination and improving engineering effectiveness. This architectural concept requires that infrastructure components shared by teams, such as API Gateway, support multi-tenant isolation. While ensuring the robustness and cost control of the whole system, it allows business teams to configure and extend the gateway functions according to their own needs, maintaining the independence of microservice teams and services.
 
-- 租户级限流:在多租户环境中,每个租户的流量特征是不同的。对不同的租户进行同样的限流无法满足商业上的需求,租户级限流能够根据用户特征做更恰当的限流。
+- Tenant-level flow limit: In a multi-tenant environment, the traffic characteristics of each tenant are different. The same flow restriction for different tenants cannot meet the business needs, and tenant-level flow restriction can do more appropriate flow restriction based on user characteristics.
 
-- 租户级白名单:在多租户环境中,每个租户的访问 IP 是不同的。单一的白名单控制无法满足租户级安全管理的需要,租户级白名单使得每个租户可以控制自己的白名单,也不用担心白名单中的其它用户访问自己的资源。
+- Tenant-level whitelisting: In a multi-tenant environment, each tenant's access IP is different. Single whitelist control cannot meet the needs of tenant-level security management. Tenant-level whitelisting allows each tenant to control its own whitelist and not worry about other users in the whitelist accessing its own resources.
 
-- Authentication:API 网关不仅要支持请求 authentication,还需要支持动态更新密钥,经常更新密钥是保证用户资源安全的关键一环。
+- Authentication: API gateways should not only support request authentication, but also support dynamic key update, which is a key part of ensuring the security of user resources.
 
-- Authorization:企业级应用的权限管理是非常复杂的,不同的应用场景有着截然不同的权限管理模型。API 网关可以根据路由配置验证请求用户是否有足够的权限访问接口,第一时间拦截非法的流量。
+- The API gateway can verify whether the requesting user has sufficient authority to access the interface according to the routing configuration and intercept illegal traffic in the first place.
 
 ![Airwallex arch](https://static.apiseven.com/202108/20210816002.png)
 
-内容比较多简化一下,可以更清楚:
+It's a bit more involved and can be simplified to make it clearer: !
 
 ![Airwallex arch](https://static.apiseven.com/202108/20210816003.png)
 
-**Q:在 Apache APISIX 升级过程中是否顺利?分享一下升级过程中的感受或者故事。**
+**Q:Did you have a smooth upgrade process in Apache APISIX? Share your feelings or stories about the upgrade process.**
 
-为了能够随时升级到新版本的 Apache APISIX,我们把主要的功能都实现为定制化插件。这意味着我们的代码库不可能与 Apache APISIX 主 Repo 核心代码产生冲突,这帮助我们避免了可能遇到的代码冲突。但有时我们也需要修改核心代码,此时我们会尽量在开源社区实现这些功能。在开源社区讨论这些功能的时候,社区的小伙伴们非常热心参与讨论,在大多数情况下都能很快解决我们的问题。
+In order to be able to upgrade to new versions of Apache APISIX at any time, we implemented the main features as custom plugins. This means that our code base is unlikely to conflict with the core Apache APISIX main Repo code, which helps us avoid code conflicts we might encounter. However, there are times when we need to modify the core code, at which point we try to implement these features in the open source community. When we discuss these features in the open source community, the community partners are very eager to participate in the discussion and in most cases solve our problems quickly.
 
-**Q:Apache APISIX 在生产环境运行多久了?在线上表现如何?**
+**Q: How long has Apache APISIX been running in a production environment? How does it perform online?**
 
-**李杨**:生产环境运行了 15 个月了,在开启动态路由、租户级限流、租户级白名单、Authentication、Authorization 等功能的情况下 99% 响应延迟在 23ms 以内,整体表现非常稳定。得益于 Apache APISIX 优秀的插件机制,可以保障我们在几乎不修改它核心代码情况下,增加符合业务需求的私有插件。完备的测试体系也进一步保障了软件质量,可以放心增加插件个性化要求的同时,保证不破坏原有核心逻辑。
+**Yang Li**: The production environment has been running for 15 months, and 99% of the response latency is within 23ms with dynamic routing, tenant-level flow restriction, tenant-level whitelisting, Authentication, Authorization, etc. The overall performance is very stable. Thanks to the excellent plug-in mechanism of Apache APISIX, we can add private plug-ins that meet business requirements with little modification to its core code. The complete testing system also further guarantees the quality of the software and allows us to add plug-ins for personalized requirements without breaking the original core logic.
 
-**Q:Apache APISIX 有哪些不足,希望社区一起建设完善?**
+**Q: What are the shortcomings of Apache APISIX and what do you hope the community will build together to improve?**
 
-**李杨**:Apache APISIX 的数据面设计为它带来了无损的水平扩展和极致的性能,但这也使得路由配置很难做到向前兼容,为新版本的发布带来了一些协调上的困难。
+**LI Yang**: Apache APISIX's data-plane design brings it lossless horizontal scaling and extreme performance, but it also makes the routing configuration difficult to achieve forward compatibility, which brings some coordination difficulties for the release of new versions.

Review comment:
       ```suggestion
   **Yang Li**: Apache APISIX's data-plane design brings it lossless horizontal scaling and extreme performance, but it also makes the routing configuration difficult to achieve forward compatibility, which brings some coordination difficulties for the release of new versions.
   ```

##########
File path: website/blog/2021/08/21/shanghai-meetup.md
##########
@@ -1,99 +1,99 @@
 ---
-title: "8 月 21 日 Apache APISIX Meetup 上海站,欢迎报名参加!"
+title: August 21 Apache APISIX Meetup Shanghai, welcome to register!
 keywords:
-- API 网关
+- API Gateway
 - APISIX
 - Apache APISIX
 - Meetup
-description: 本次 Meetup 由 api7.ai https://www.apiseven.com/ 发起,并邀请爱奇艺、空中云汇等合作伙伴共同为大家呈现。Apache APISIX PMC 成员、贡献者、社区技术专家汇聚一堂,共同探讨 Apache APISIX 社区发展、行业实践等话题。
+description: This Meetup was initiated by api7.ai https://www.apiseven.com/, and invited partners such as iQiYi and Airwallex to present it. Apache APISIX PMC members, contributors, and community technical experts gathered to discuss Apache APISIX community development, industry practices, and other topics. 
 tags: [Events]
 ---
 
-> 本次 Meetup 由 [api7.ai](https://www.apiseven.com/) 发起,并邀请爱奇艺、空中云汇等合作伙伴共同为大家呈现。Apache APISIX PMC 成员、贡献者、社区技术专家汇聚一堂,共同探讨 Apache APISIX 社区发展、行业实践等话题。
+> This Meetup is initiated by [api7.ai](https://www.apiseven.com/), and invited partners such as iQiYi and Airwallex to present it. Apache APISIX PMC members, contributors, and community technical experts gathered to discuss Apache APISIX community development, industry practices, and other topics.
 
-<!--truncate-->
+<! --truncate-->
 
-#### 时间:2021 年 8 月 21 日 13:30
+#### Time: August 21, 2021, 13:30
 
-#### 地点:上海市黄浦区中区广场 6 楼静和岛二期
+#### Location: Jinghe Island II, 6th Floor, Central Plaza, Huangpu District, Shanghai
 
-#### 参加本次 Meetup,你可以
+#### By attending this Meetup, you can
 
-- 共同探讨 Apache APISIX 社区的前世今生
-- 听爱奇艺科学家讲述,爱奇艺是如何使用 Apache APISIX 支撑起千万级调用量的服务
-- 空中云汇是如何在使用 Apache APISIX 时兼顾用户体验、整洁架构与数据主权
-- 了解集中式身份认证的优点以及如何在 APISIX 上进行集中式身份认证
+- Discuss the past and present of the Apache APISIX community
+- Hear from Akiyo scientists about how Akiyo uses Apache APISIX to support a service with 10 million calls
+- How Airwallex uses Apache APISIX to balance user experience, clean architecture and data sovereignty
+- Learn about the benefits of centralized authentication and how to do it on APISIX
 
-如果你感兴趣的话,千万不要错过,**扫描活动海报二维码报名吧!**
+If you're interested, don't miss it, **scan the event poster for QR code to register!**
 
-tips:疫情防控不放松,我们将会控制现场活动规模,名额有限,报名从速!
+Tips: We will control the size of the event as the epidemic is not relaxed, so registration is limited.
 
-## 活动安排
+## Event Schedule
 
-![Apache APISIX Meetup](/img/blog_img/2021-08-21-1.jpg)
+The event schedule![Apache APISIX Meetup](/img/blog_img/2021-08-21-1.jpg)

Review comment:
       ```suggestion
   ![Apache APISIX Meetup](/img/blog_img/2021-08-21-1.jpg)
   ```

##########
File path: website/blog/2021/08/19/go-makes-Apache-APISIX-better.md
##########
@@ -1,60 +1,60 @@
 ---
-title: "Go 让 Apache APISIX 如虎添翼"
-author: "罗泽轩"
+title: Go gives Apache APISIX a run for its money
+author: Zexuan Luo
 authorURL: "https://github.com/spacewander"
 authorImageURL: "https://avatars.githubusercontent.com/u/4161644?v=4"
 keywords:
 - Go
 - APISIX 
-- APISIX Go 插件
+- Go Plugin
 - APISIX Go plugin
 - apisix-go-plugin-runner
 - Golang
 tags: [Practical Case]
 ---
 
-> 这篇文章将详细讲解如何用 Go 来开发 Apache APISIX 插件。通过拥抱 Go 的生态圈,为 Apache APISIX 开创一片新天地,希望 Go 能让 Apache APISIX 如虎添翼!
+> This article will explain in detail how to use Go to develop Apache APISIX plugins. By embracing the Go ecosystem and breaking new ground for Apache APISIX, we hope that Go will make Apache APISIX even better!
 
-<!--truncate-->
+<! --truncate-->
 
-## 为什么是 Go
+## Why Go
 
-[Apache APISIX](https://github.com/apache/apisix) 允许用户通过插件的方式来拓展功能,如鉴权、限流、请求改写等核心功能都是通过插件的方式实现的。虽然 Apache APISIX 核心代码是使用 Lua 编写的,但是 Apache APISIX 支持多语言开发插件,比如 Go 、Java。
+[Apache APISIX](https://github.com/apache/apisix) allows users to extend functionality by way of plugins. Core features such as forensics, flow restriction, request rewriting, etc. are implemented by way of plugins. Although the core code of Apache APISIX is written in Lua, Apache APISIX supports multi-language development of plugins, such as Go, Java.
 
-这篇文章将详细讲解如何用 Go 来开发 Apache APISIX 插件。通过拥抱 Go 的生态圈,为 Apache APISIX 开创一片新天地,希望 Go 能让 Apache APISIX 如虎添翼!
+This article will explain in detail how to develop Apache APISIX plugins in Go. By embracing the Go ecosystem, we are breaking new ground for Apache APISIX, and we hope that Go will make Apache APISIX even better!
 
-## 安装
+## Installation
 
-采用库的方式来使用 Go Runner,[apisix-go-plugin-runner](https://github.com/apache/apisix-go-plugin-runner) 中的 `cmd/go-runner` 官方给出的例子,展示该如何使用 Go Runner SDK。未来也会支持通过 Go Plugin 的机制加载预先编译好的插件。
+To use Go Runner as a library, the official `cmd/go-runner` example in [apisix-go-plugin-runner](https://github.com/apache/apisix-go-plugin-runner) shows how to use the Go Runner SDK. The Go Runner SDK will also support loading pre-compiled plugins via the Go Plugin mechanism in the future.
 
-## 开发
+## Development
 
-### 使用 Go Runner SDK 进行开发
+### Developing with the Go Runner SDK
 
 ```bash
 $ tree cmd/go-runner
 cmd/go-runner
 ├── main.go
 ├── main_test.go
 ├── plugins
-│   ├── say.go
-│   └── say_test.go
+│ ├── say.go
+│ └── say_test.go

Review comment:
       ```suggestion
   │   ├── say.go
   │   └── say_test.go
   ```

##########
File path: website/blog/2021/08/16/Using-the-Apache-APISIX-OpenID-Connect-Plugin-for-Centralized-Authentication.md
##########
@@ -4,16 +4,16 @@ author: "Peter Zhu"
 authorURL: "https://github.com/starsz"
 authorImageURL: "https://avatars.githubusercontent.com/u/25628854?v=4"
 keywords:
-- API gateway
-- APISIX
-- Apache APISIX
-- Okta
-- Centralized Authentication
+  - API gateway
+  - APISIX
+  - Apache APISIX
+  - Okta
+  - Centralized Authentication

Review comment:
       ```suggestion
   - API gateway
   - APISIX
   - Apache APISIX
   - Okta
   - Centralized Authentication
   ```

##########
File path: website/blog/2021/08/11/interview-TuZhengsong.md
##########
@@ -1,145 +1,145 @@
 ---
-title: "从新手村出来,我在 Apache APISIX 社区发出了第一个 PR"
-author: "Apache APISIX 社区"
+title: I issued my first PR in the Apache APISIX community
+author: Apache APISIX
 authorURL: "https://github.com/Yangxiamao"
 authorImageURL: "https://avatars.githubusercontent.com/u/47442074?v=4"
 keywords:
-- API 网关
+- API Gateway
 - APISIX
 - Apache APISIX
-- 开源社区
-- 开源项目
-description: 这篇采访稿讲述了屠正松从开源社区小白成长为 Apache 顶级开源项目 APISIX committer 的历程。屠正松(GitHub ID:tzssangglass)因深度参与 Apache APISIX 的开发,在社区中贡献很多,2021 年 7 月 22 日被推选为 Apache APISIX committer。
+- Community
+- Open Source
+description: "This interview is about Zhengsong Tu's journey from an open source community nerd to an APISIX committer for Apache's top open source project. Zhengsong Tu (GitHub ID: tzssangglass) was elected as an Apache APISIX committer on July 22, 2021 for his deep involvement in Apache APISIX development and his many contributions to the community."
 tags: [Interview]
 ---
 
-> 这篇采访稿讲述了屠正松从开源社区小白成长为 Apache 顶级开源项目 APISIX committer 的历程。屠正松(GitHub ID:tzssangglass)因深度参与 Apache APISIX 的开发,在社区中贡献很多,2021 年 7 月 22 日被推选为 Apache APISIX committer。
+> This interview is about Zhengsong Tu's journey from an open source community nerd to an APISIX committer for Apache's top open source project. Zhengsong Tu (GitHub ID: tzssangglass) was elected as an Apache APISIX committer on July 22, 2021 for his deep involvement in Apache APISIX development and his many contributions to the community.
 
 <!--truncate-->
 
-> 当我看到那个 issue 后,就有种强烈的想要参与到社区的冲动。看了社区的新手指南后,我像从新手村出来的勇者,准备打怪。
+> When I saw that issue, I had a strong urge to get involved in the community. After reading the community's newbie guide, I was like a brave man coming out of the newbie village, ready to fight.
 >
-> —— Apache APISIX committer 屠正松
+> -- Zhengsong Tu, Apache APISIX committer
 
-历时 282 天,屠正松(GitHub ID:tzssangglass)从开源社区的小白成长为了 Apache APISIX 的 committer。
+In 282 days, Zhengsong Tu (GitHub ID: tzssangglass) has grown from an open source community nerd to an Apache APISIX committer.
 
 ![Apache APISIX committer tzssangglass github](/img/blog_img/2021-08-11-1.webp)
 
-屠正松因深度参与 Apache APISIX 的开发,在社区中贡献很多,2021 年 7 月 22 日被推选为 Apache APISIX committer。
+Zhengsong Tu was elected as Apache APISIX committer on July 22, 2021 for his deep involvement in Apache APISIX development and many contributions in the community.
 
-在一个平淡的下午,我们和正松连线聊了聊。因为疫情关系,居住在南京的他已经多日未外出。在没有和他聊天之前,我没有想到,胡子拉碴的他,竟然走过了这么曲折的路。
+On an uneventful afternoon, we chatted with Zhengsong by phone. Because of the epidemic, he has not been out for many days in Nanjing. Before I talked to him, I didn't expect that the bearded man had traveled such a winding road.
 
-## 大学,我的大学
+## University, my university
 
-> 我大学的时候学的是通信工程,每天最开心的事就是踢球。现在有时候会想,如果能带着现在的记忆回到大学时光就好了。
+> When I was in college, I studied communication engineering, and the happiest thing I did every day was to play soccer. Now sometimes I think that it would be nice to go back to my college days with the memories I have now.
 
-正松在大学期间里面其实没怎么接触过编程,他当年其实有 C 语言的编程课,但是因为忙着踢球,挂科了。可是,他挂科之后的补考也没过,导致重修。最尴尬的是,他重修也没过,后来怎么办呢?毕业之前还有毕业清考。这可不能再挂了,于是正松就去图书馆去借了一本 C 语言的书来看。
+Zhengsong actually didn't have much contact with programming during his college years, he actually had a C programming class, but he failed it because he was too busy playing soccer. However, he failed a make-up exam after failing the class, resulting in a retake. The most embarrassing thing is that he failed the retake as well, so what did he do afterwards? There was a graduation clearing exam before graduation. This can not be failed again, so Zhengsong went to the library to borrow a C language book to read.
 
-“我当时心想,C 语言真的这么难吗?”正松说。
+"I was thinking, "Is C really that hard?" Zhengsong said.
 
-然后他就一直看一直看,看着看着就突然发现编程好像有那么点意思,他看懂了!最后他在毕业前顺利通过了考试。在毕业之后,找到了一份做程序员的工作。
+Then he kept reading and reading and reading, and suddenly he realized that programming seemed to have some meaning, and he understood it! He finally passed the exam before graduating. After graduation, he found a job as a programmer.
 
-“我本来都准备毕业回家找个厂上班了。”,他半开玩笑地说。
+"I was ready to graduate and go home and find a factory to work." , he said half-jokingly.
 
-彼时,他可能不会想到如今的他会成为数个知名开源项目的 developer,参与一些支撑着千万级并发流量的基础设施的开发。
+At that time, he probably wouldn't have thought that today he would be the developer of several well-known open source projects, and involved in the development of some infrastructure that supports millions of concurrent traffic.
 
-## 出象牙塔记
+## Out of the Ivory Tower
 
-> 在工业界,真实的业务场景和学校里学的很不一样的
+> In industry, the real business scenario is very different from what you learn in school.
 
-正松的第一份工作就职于一家做穿戴设备的创业公司,从事智能手环的研发工作。正松和他的前同事们需要通过处理从智能手环上的获取的各种传感器数据,来完成对用户的心率、运动量、血压等的监测。
+Zhengsong's first job was at a wearable device startup, working on the development of smart bracelets. Zhengsong and his former colleagues had to process various sensor data from the smart bracelet to monitor the user's heart rate, exercise, blood pressure and so on.
 
-“工作蛮好玩的,因为在工业界,真实的业务场景和学校里学的很不一样的,很多东西都得从头开始学”,正松说。
+"It was fun because in industry, the real business scenario is very different from what you learn in school, and a lot of things have to be learned from scratch," Masatsu said.
 
-有一天下班之后,这家公司的老板娘突然发了一条信息,说公司的员工暂时休假,什么时候上班等通知。
+One day after work, the owner of this company suddenly sent a message saying that the company's employees were on temporary leave and that they would wait to be notified when to work.
 
-正松当时就觉得不对劲,怎么好好的上着班,突然就休假了?然后他立马打开招聘软件,开始找新的工作。后来才知道,公司的老板跟供应商有合同纠纷,公司短暂停摆了。
+Masatsu felt something was wrong at that time, how to work well, suddenly on vacation? Then he immediately opened the recruitment software and started looking for a new job. Later, he found out that the owner of the company had a contract dispute with the supplier, and the company was briefly shut down.
 
-然后,正松便到另外一家公司从事后端业务开发的工作,学习业界规范、进一步增进技术。过了快一年,因为正松比较喜欢 Nginx、OpenResty、Netty 这类简洁和高性能的技术,他进入一家大公司的开发团队,从事中间件相关开发工作。
+Then, Masatsu went to another company to engage in back-end business development work, to learn the industry norms and further improve technology. After almost a year, he joined the development team of a large company to work on middleware-related development because he liked the simplicity and high performance of technologies like Nginx, OpenResty, and Netty.
 
-“在这家大公司,我做的离业务稍微远那么一点点,更偏向技术一些。“正松说。
+"In this big company, I did a little bit far from the business, more technically oriented. "Masatsu said.
 
-正松接触 Apache APISIX 的时间是 2020 年 9 月份,那时候,他所在的团队使用的是 Kong,但是当时 Kong 无法完全满足他们的需求,于是他们便重新做网关的技术选型,试图寻找更好的方案。正松担任本次技术选型的负责人,于是他关注到了 Apache 基金会的顶级项目 Apache APISIX,进而接触了 Apache APISIX 的社区。
+Zhengsong's contact with Apache APISIX was in September 2020, when his team was using Kong, but Kong was not fully meeting their needs, so they redid the technical selection of the gateway to try to find a better solution. Masatsu was in charge of this technical selection, so he came across the Apache Foundation's top project, Apache APISIX, and was introduced to the Apache APISIX community.
 
-彼时的他,已经毕业三年多了。
+At that time, he had already graduated more than three years ago.
 
-## 出新手村
+## Out of the newbie village
 
-> 我可以给 Apache 基金会的顶级项目提交代码了!作为一个技术工作者,这是一种技术上的自信。
+> I can submit code to the Apache Foundation's top projects! As a technical worker, that's a lot of technical confidence.
 
-正松在开源社区的第一个 PR 是一个 enhancement(功能增强)类型的 PR,这个 PR 让 Apache APISIX 支持了多端口监听。
+Zhengsong's first PR in the open source community was an enhancement type PR, which enabled Apache APISIX to support multi-port listening.
 
-- issue:https://github.com/apache/apisix/issues/1195
-- PR:https://github.com/apache/apisix/pull/2409
+- issue: https://github.com/apache/apisix/issues/1195
+- PR: https://github.com/apache/apisix/pull/2409
 
-这个功能是正松公司需要的,在 issue 区也早有人提到,但是不知为何一直无人认领。之前,正松正好对这方面的知识有所了解,于是他想:”我可以给 Apache APISIX 提个 PR 来 fix 这个问题。“所以他在 issue 里主动要求把这个问题指派给他。
+This feature is needed by Masatsu and has been mentioned in the issue area for a long time, but for some reason it has been unclaimed. Before that, Zhengsong happened to know something about this, so he thought, "I can propose a PR to Apache APISIX to fix this problem. "So he volunteered to have the issue assigned to him in the issue.
 
-他说:“当时我有一种强烈的参与社区的冲动,然后我看了一下 Apache APISIX 社区的新手指南,然后就像拿着武器从新手村出来一样,兴致冲冲的准备参与。”
+He says, "I had a strong urge to get involved in the community, and then I looked at the Apache APISIX community's Beginner's Guide and was as excited to get involved as if I were coming out of the Beginner's Village with a weapon."
 
-选择了这个 issue 之后,正松开始在 GitHub 上面开始跟社区的伙伴讨论细节上的问题,像是配置端口的 style、实现的思路等。在讨论完之后,他开始动手实现。每天晚上下班之后去翻看 Apache APISIX 的代码,测试相关用例。在经历了三四个晚上的奋斗后,测试第一次跑通了!
+After choosing this issue, Masatsu started discussing details with his community partners on GitHub, such as the style of the configuration port, the idea of the implementation, and so on. After the discussion, he started to implement it. Every night after work, he went through the Apache APISIX code and tested the use cases. After three or four nights of struggling, the test ran for the first time!
 
-当时正松内心非常的兴奋,马上按照那个新手指南的引导把 PR 提上去了。然后接受 Code Review 的意见,进一步修改代码。终于,在 10 月 18 号,PR 顺利地 merge 进了仓库。
+Masatsu was very excited and immediately followed the guide to bring up the PR. Then he accepted the comments from Code Review and further modified the code. Finally, on October 18, the PR was successfully merged into the repository.
 
 ![Apache APISIX committer tzssangglass pr](/img/blog_img/2021-08-11-2.webp)
 
-“当时我非常的激动,感觉自己终于实质性地参与到开源社区里面去了。我可以给 Apache 基金会的顶级项目提交代码了!作为一个技术工作者,这是一种技术上的自信。”
+"I was very excited and felt like I was finally substantially involved in the open source community. I could submit code to the Apache Foundation's top projects! As a technical worker, it was a technical confidence."
 
-**这是正松在开源世界的第一个 PR。**
+**This is Zhengsong's first PR in the open source world.**
 
-## 在社区印象深刻的事
+## Things that impressed me in the community
 
-> 因为 etcd 有 MaxCallRecvMsgSize 的限制,就从 etcd 的源头去解决,这是最优雅,也是最适合的。
+> Because etcd has a MaxCallRecvMsgSize limit, it was most elegant and appropriate to go to the source of etcd.
 
-当我们问到,正松在社区印象最深刻的事情是什么的时候,正松想了想说,可能是一个和 bug 有关的问题:etcd 的 MaxCallRecvMsgSize 限制。
+When we asked what was the thing that impressed Masatsu most in the community, Masatsu thought about it and said it was probably a bug-related issue: etcd's MaxCallRecvMsgSize limitation.
 
-正松曾经被 etcd 限制返回体大小的问题折磨过,社区内也多次反映、讨论过这个问题,但在 Apache APISIX 上无论怎么处理都不是很优雅。
+Masatsu had been tormented by etcd's return size limitation problem, and the community had reflected and discussed this problem many times, but it was not very elegant on Apache APISIX no matter how it was handled.
 
-直到今年 4 月份,支流科技的一位小伙伴给 etcd 提交了 PR,最终解决了这个问题。正松听说这个消息时,感到非常的震撼,当时他没有想过这个事情会以这样的方式去解决。但是现在来看的话,这个方法确实是最适合的。
+In April this year, one of our partners submitted a PR to etcd, which finally solved the problem. When Masatsu heard about this, he was very shocked, he didn't think it would be solved in such a way. But in hindsight, this was the way to go.
 
-“因为 etcd 有 MaxCallRecvMsgSize 的限制,就从 etcd 的源头去解决,这是最优雅,也是最适合的。这是很棒的跨社区合作的示例”,正松说。
+"Because etcd has a MaxCallRecvMsgSize limit, it's most elegant and appropriate to go to the source of etcd. This is great example of cross-community collaboration," says Masatsu.

Review comment:
       ```suggestion
   "Because etcd has a MaxCallRecvMsgSize limit, it's most elegant and appropriate to go to the source of etcd. This is great example of cross-community collaboration," says Zhengsong.
   ```

##########
File path: website/blog/2021/08/11/interview-TuZhengsong.md
##########
@@ -1,145 +1,145 @@
 ---
-title: "从新手村出来,我在 Apache APISIX 社区发出了第一个 PR"
-author: "Apache APISIX 社区"
+title: I issued my first PR in the Apache APISIX community
+author: Apache APISIX
 authorURL: "https://github.com/Yangxiamao"
 authorImageURL: "https://avatars.githubusercontent.com/u/47442074?v=4"
 keywords:
-- API 网关
+- API Gateway
 - APISIX
 - Apache APISIX
-- 开源社区
-- 开源项目
-description: 这篇采访稿讲述了屠正松从开源社区小白成长为 Apache 顶级开源项目 APISIX committer 的历程。屠正松(GitHub ID:tzssangglass)因深度参与 Apache APISIX 的开发,在社区中贡献很多,2021 年 7 月 22 日被推选为 Apache APISIX committer。
+- Community
+- Open Source
+description: "This interview is about Zhengsong Tu's journey from an open source community nerd to an APISIX committer for Apache's top open source project. Zhengsong Tu (GitHub ID: tzssangglass) was elected as an Apache APISIX committer on July 22, 2021 for his deep involvement in Apache APISIX development and his many contributions to the community."
 tags: [Interview]
 ---
 
-> 这篇采访稿讲述了屠正松从开源社区小白成长为 Apache 顶级开源项目 APISIX committer 的历程。屠正松(GitHub ID:tzssangglass)因深度参与 Apache APISIX 的开发,在社区中贡献很多,2021 年 7 月 22 日被推选为 Apache APISIX committer。
+> This interview is about Zhengsong Tu's journey from an open source community nerd to an APISIX committer for Apache's top open source project. Zhengsong Tu (GitHub ID: tzssangglass) was elected as an Apache APISIX committer on July 22, 2021 for his deep involvement in Apache APISIX development and his many contributions to the community.
 
 <!--truncate-->
 
-> 当我看到那个 issue 后,就有种强烈的想要参与到社区的冲动。看了社区的新手指南后,我像从新手村出来的勇者,准备打怪。
+> When I saw that issue, I had a strong urge to get involved in the community. After reading the community's newbie guide, I was like a brave man coming out of the newbie village, ready to fight.
 >
-> —— Apache APISIX committer 屠正松
+> -- Zhengsong Tu, Apache APISIX committer
 
-历时 282 天,屠正松(GitHub ID:tzssangglass)从开源社区的小白成长为了 Apache APISIX 的 committer。
+In 282 days, Zhengsong Tu (GitHub ID: tzssangglass) has grown from an open source community nerd to an Apache APISIX committer.
 
 ![Apache APISIX committer tzssangglass github](/img/blog_img/2021-08-11-1.webp)
 
-屠正松因深度参与 Apache APISIX 的开发,在社区中贡献很多,2021 年 7 月 22 日被推选为 Apache APISIX committer。
+Zhengsong Tu was elected as Apache APISIX committer on July 22, 2021 for his deep involvement in Apache APISIX development and many contributions in the community.
 
-在一个平淡的下午,我们和正松连线聊了聊。因为疫情关系,居住在南京的他已经多日未外出。在没有和他聊天之前,我没有想到,胡子拉碴的他,竟然走过了这么曲折的路。
+On an uneventful afternoon, we chatted with Zhengsong by phone. Because of the epidemic, he has not been out for many days in Nanjing. Before I talked to him, I didn't expect that the bearded man had traveled such a winding road.
 
-## 大学,我的大学
+## University, my university
 
-> 我大学的时候学的是通信工程,每天最开心的事就是踢球。现在有时候会想,如果能带着现在的记忆回到大学时光就好了。
+> When I was in college, I studied communication engineering, and the happiest thing I did every day was to play soccer. Now sometimes I think that it would be nice to go back to my college days with the memories I have now.
 
-正松在大学期间里面其实没怎么接触过编程,他当年其实有 C 语言的编程课,但是因为忙着踢球,挂科了。可是,他挂科之后的补考也没过,导致重修。最尴尬的是,他重修也没过,后来怎么办呢?毕业之前还有毕业清考。这可不能再挂了,于是正松就去图书馆去借了一本 C 语言的书来看。
+Zhengsong actually didn't have much contact with programming during his college years, he actually had a C programming class, but he failed it because he was too busy playing soccer. However, he failed a make-up exam after failing the class, resulting in a retake. The most embarrassing thing is that he failed the retake as well, so what did he do afterwards? There was a graduation clearing exam before graduation. This can not be failed again, so Zhengsong went to the library to borrow a C language book to read.
 
-“我当时心想,C 语言真的这么难吗?”正松说。
+"I was thinking, "Is C really that hard?" Zhengsong said.
 
-然后他就一直看一直看,看着看着就突然发现编程好像有那么点意思,他看懂了!最后他在毕业前顺利通过了考试。在毕业之后,找到了一份做程序员的工作。
+Then he kept reading and reading and reading, and suddenly he realized that programming seemed to have some meaning, and he understood it! He finally passed the exam before graduating. After graduation, he found a job as a programmer.
 
-“我本来都准备毕业回家找个厂上班了。”,他半开玩笑地说。
+"I was ready to graduate and go home and find a factory to work." , he said half-jokingly.
 
-彼时,他可能不会想到如今的他会成为数个知名开源项目的 developer,参与一些支撑着千万级并发流量的基础设施的开发。
+At that time, he probably wouldn't have thought that today he would be the developer of several well-known open source projects, and involved in the development of some infrastructure that supports millions of concurrent traffic.
 
-## 出象牙塔记
+## Out of the Ivory Tower
 
-> 在工业界,真实的业务场景和学校里学的很不一样的
+> In industry, the real business scenario is very different from what you learn in school.
 
-正松的第一份工作就职于一家做穿戴设备的创业公司,从事智能手环的研发工作。正松和他的前同事们需要通过处理从智能手环上的获取的各种传感器数据,来完成对用户的心率、运动量、血压等的监测。
+Zhengsong's first job was at a wearable device startup, working on the development of smart bracelets. Zhengsong and his former colleagues had to process various sensor data from the smart bracelet to monitor the user's heart rate, exercise, blood pressure and so on.
 
-“工作蛮好玩的,因为在工业界,真实的业务场景和学校里学的很不一样的,很多东西都得从头开始学”,正松说。
+"It was fun because in industry, the real business scenario is very different from what you learn in school, and a lot of things have to be learned from scratch," Masatsu said.
 
-有一天下班之后,这家公司的老板娘突然发了一条信息,说公司的员工暂时休假,什么时候上班等通知。
+One day after work, the owner of this company suddenly sent a message saying that the company's employees were on temporary leave and that they would wait to be notified when to work.
 
-正松当时就觉得不对劲,怎么好好的上着班,突然就休假了?然后他立马打开招聘软件,开始找新的工作。后来才知道,公司的老板跟供应商有合同纠纷,公司短暂停摆了。
+Masatsu felt something was wrong at that time, how to work well, suddenly on vacation? Then he immediately opened the recruitment software and started looking for a new job. Later, he found out that the owner of the company had a contract dispute with the supplier, and the company was briefly shut down.
 
-然后,正松便到另外一家公司从事后端业务开发的工作,学习业界规范、进一步增进技术。过了快一年,因为正松比较喜欢 Nginx、OpenResty、Netty 这类简洁和高性能的技术,他进入一家大公司的开发团队,从事中间件相关开发工作。
+Then, Masatsu went to another company to engage in back-end business development work, to learn the industry norms and further improve technology. After almost a year, he joined the development team of a large company to work on middleware-related development because he liked the simplicity and high performance of technologies like Nginx, OpenResty, and Netty.
 
-“在这家大公司,我做的离业务稍微远那么一点点,更偏向技术一些。“正松说。
+"In this big company, I did a little bit far from the business, more technically oriented. "Masatsu said.
 
-正松接触 Apache APISIX 的时间是 2020 年 9 月份,那时候,他所在的团队使用的是 Kong,但是当时 Kong 无法完全满足他们的需求,于是他们便重新做网关的技术选型,试图寻找更好的方案。正松担任本次技术选型的负责人,于是他关注到了 Apache 基金会的顶级项目 Apache APISIX,进而接触了 Apache APISIX 的社区。
+Zhengsong's contact with Apache APISIX was in September 2020, when his team was using Kong, but Kong was not fully meeting their needs, so they redid the technical selection of the gateway to try to find a better solution. Masatsu was in charge of this technical selection, so he came across the Apache Foundation's top project, Apache APISIX, and was introduced to the Apache APISIX community.
 
-彼时的他,已经毕业三年多了。
+At that time, he had already graduated more than three years ago.
 
-## 出新手村
+## Out of the newbie village
 
-> 我可以给 Apache 基金会的顶级项目提交代码了!作为一个技术工作者,这是一种技术上的自信。
+> I can submit code to the Apache Foundation's top projects! As a technical worker, that's a lot of technical confidence.
 
-正松在开源社区的第一个 PR 是一个 enhancement(功能增强)类型的 PR,这个 PR 让 Apache APISIX 支持了多端口监听。
+Zhengsong's first PR in the open source community was an enhancement type PR, which enabled Apache APISIX to support multi-port listening.
 
-- issue:https://github.com/apache/apisix/issues/1195
-- PR:https://github.com/apache/apisix/pull/2409
+- issue: https://github.com/apache/apisix/issues/1195
+- PR: https://github.com/apache/apisix/pull/2409
 
-这个功能是正松公司需要的,在 issue 区也早有人提到,但是不知为何一直无人认领。之前,正松正好对这方面的知识有所了解,于是他想:”我可以给 Apache APISIX 提个 PR 来 fix 这个问题。“所以他在 issue 里主动要求把这个问题指派给他。
+This feature is needed by Masatsu and has been mentioned in the issue area for a long time, but for some reason it has been unclaimed. Before that, Zhengsong happened to know something about this, so he thought, "I can propose a PR to Apache APISIX to fix this problem. "So he volunteered to have the issue assigned to him in the issue.
 
-他说:“当时我有一种强烈的参与社区的冲动,然后我看了一下 Apache APISIX 社区的新手指南,然后就像拿着武器从新手村出来一样,兴致冲冲的准备参与。”
+He says, "I had a strong urge to get involved in the community, and then I looked at the Apache APISIX community's Beginner's Guide and was as excited to get involved as if I were coming out of the Beginner's Village with a weapon."
 
-选择了这个 issue 之后,正松开始在 GitHub 上面开始跟社区的伙伴讨论细节上的问题,像是配置端口的 style、实现的思路等。在讨论完之后,他开始动手实现。每天晚上下班之后去翻看 Apache APISIX 的代码,测试相关用例。在经历了三四个晚上的奋斗后,测试第一次跑通了!
+After choosing this issue, Masatsu started discussing details with his community partners on GitHub, such as the style of the configuration port, the idea of the implementation, and so on. After the discussion, he started to implement it. Every night after work, he went through the Apache APISIX code and tested the use cases. After three or four nights of struggling, the test ran for the first time!
 
-当时正松内心非常的兴奋,马上按照那个新手指南的引导把 PR 提上去了。然后接受 Code Review 的意见,进一步修改代码。终于,在 10 月 18 号,PR 顺利地 merge 进了仓库。
+Masatsu was very excited and immediately followed the guide to bring up the PR. Then he accepted the comments from Code Review and further modified the code. Finally, on October 18, the PR was successfully merged into the repository.
 
 ![Apache APISIX committer tzssangglass pr](/img/blog_img/2021-08-11-2.webp)
 
-“当时我非常的激动,感觉自己终于实质性地参与到开源社区里面去了。我可以给 Apache 基金会的顶级项目提交代码了!作为一个技术工作者,这是一种技术上的自信。”
+"I was very excited and felt like I was finally substantially involved in the open source community. I could submit code to the Apache Foundation's top projects! As a technical worker, it was a technical confidence."
 
-**这是正松在开源世界的第一个 PR。**
+**This is Zhengsong's first PR in the open source world.**
 
-## 在社区印象深刻的事
+## Things that impressed me in the community
 
-> 因为 etcd 有 MaxCallRecvMsgSize 的限制,就从 etcd 的源头去解决,这是最优雅,也是最适合的。
+> Because etcd has a MaxCallRecvMsgSize limit, it was most elegant and appropriate to go to the source of etcd.
 
-当我们问到,正松在社区印象最深刻的事情是什么的时候,正松想了想说,可能是一个和 bug 有关的问题:etcd 的 MaxCallRecvMsgSize 限制。
+When we asked what was the thing that impressed Masatsu most in the community, Masatsu thought about it and said it was probably a bug-related issue: etcd's MaxCallRecvMsgSize limitation.
 
-正松曾经被 etcd 限制返回体大小的问题折磨过,社区内也多次反映、讨论过这个问题,但在 Apache APISIX 上无论怎么处理都不是很优雅。
+Masatsu had been tormented by etcd's return size limitation problem, and the community had reflected and discussed this problem many times, but it was not very elegant on Apache APISIX no matter how it was handled.
 
-直到今年 4 月份,支流科技的一位小伙伴给 etcd 提交了 PR,最终解决了这个问题。正松听说这个消息时,感到非常的震撼,当时他没有想过这个事情会以这样的方式去解决。但是现在来看的话,这个方法确实是最适合的。
+In April this year, one of our partners submitted a PR to etcd, which finally solved the problem. When Masatsu heard about this, he was very shocked, he didn't think it would be solved in such a way. But in hindsight, this was the way to go.
 
-“因为 etcd 有 MaxCallRecvMsgSize 的限制,就从 etcd 的源头去解决,这是最优雅,也是最适合的。这是很棒的跨社区合作的示例”,正松说。
+"Because etcd has a MaxCallRecvMsgSize limit, it's most elegant and appropriate to go to the source of etcd. This is great example of cross-community collaboration," says Masatsu.
 
 ## Sir, this way
 
-> 大家分工合作不同,但是都是在为开源做贡献。
+> We're all working together differently, but we're all contributing to open source.
 
-正松说,他刚开始参与社区的时候,把当时能看到的 APISIX 文档大部分都过了一遍。所以当时在所在公司工作的时候,同事问他问题,他虽然并不是很清楚,但是他清楚项目的文档分布情况,直接把文档找出来看一下,就大概知道是什么问题了。他认为看文档是熟悉项目的一个合适的方式。
+Zhengsong says that when he first started participating in the community, he went through most of the APISIX documentation he could see at the time. So when he was working in his company, his colleagues asked him questions, and although he was not very clear, he knew the distribution of the project's documentation, so he could look it up directly and know roughly what the problem was. He believes that reading the documentation is an appropriate way to get familiar with the project.
 
-Apache APISIX 的项目官网上,有完善的包括如何提 PR 的新手指南。如果想参与社区的话,可以先把官网和 Github 上的主要的文档都看一下,对项目有基本的了解,也清楚项目的文档分布情况,后面再按需索引文档。
+The Apache APISIX project website has a good guide for newcomers, including how to raise PR. If you want to participate in the community, you can first read the main documentation on the website and Github to get a basic understanding of the project and the distribution of the project's documentation, and then index the documentation as needed.
 
-如果想在代码方面做贡献,或者参与设计的话,一些 Ngnix 或者 OpenResty 方面的知识的储备是必要的。包括看他们官方的文档及和代码,学习他们对于相关 feature 的实现等。
+If you want to contribute to the code, or participate in the design, some knowledge of Ngnix or OpenResty is necessary. This includes looking at their official documentation and code, and learning about their implementation of relevant features.
 
-正松说:“我觉得这一步是无法跳过的。”
+Zhengsong said, "I think this step is impossible to skip."
 
-当然,你可以以使用者的身份,去参与到社区里。比如说你觉得文档有问题,或者说你按照文档去实践的时候,发现并不是那样,你也可以去提一些 issue 指出这些问题。
+Of course, you can get involved in the community as a user. For example, if you think there is something wrong with the documentation, or if you follow the documentation and find that it is not the case, you can also raise some issues to point out these problems.
 
-大家分工合作不同,但是都是在为开源做贡献。
+We are all working together, but we are all contributing to open source.
 
-## 社区欢迎所有人
+## Everyone is welcome in the community
 
-> 但这样做更好
+> But it's better this way
 
-正松说,大家都在开源社区,首先要注意的就是要遵守社区的一些规矩,和社区的小伙伴平等交流。
+Masatsu said, we are all in the open source community, the first thing to pay attention to is to comply with some of the community rules, and the community of partners to communicate on an equal footing.

Review comment:
       ```suggestion
   Zhengsong said, we are all in the open source community, the first thing to pay attention to is to comply with some of the community rules, and the community of partners to communicate on an equal footing.
   ```

##########
File path: website/blog/2021/08/21/shanghai-meetup.md
##########
@@ -1,99 +1,99 @@
 ---
-title: "8 月 21 日 Apache APISIX Meetup 上海站,欢迎报名参加!"
+title: August 21 Apache APISIX Meetup Shanghai, welcome to register!
 keywords:
-- API 网关
+- API Gateway
 - APISIX
 - Apache APISIX
 - Meetup
-description: 本次 Meetup 由 api7.ai https://www.apiseven.com/ 发起,并邀请爱奇艺、空中云汇等合作伙伴共同为大家呈现。Apache APISIX PMC 成员、贡献者、社区技术专家汇聚一堂,共同探讨 Apache APISIX 社区发展、行业实践等话题。
+description: This Meetup was initiated by api7.ai https://www.apiseven.com/, and invited partners such as iQiYi and Airwallex to present it. Apache APISIX PMC members, contributors, and community technical experts gathered to discuss Apache APISIX community development, industry practices, and other topics. 
 tags: [Events]
 ---
 
-> 本次 Meetup 由 [api7.ai](https://www.apiseven.com/) 发起,并邀请爱奇艺、空中云汇等合作伙伴共同为大家呈现。Apache APISIX PMC 成员、贡献者、社区技术专家汇聚一堂,共同探讨 Apache APISIX 社区发展、行业实践等话题。
+> This Meetup is initiated by [api7.ai](https://www.apiseven.com/), and invited partners such as iQiYi and Airwallex to present it. Apache APISIX PMC members, contributors, and community technical experts gathered to discuss Apache APISIX community development, industry practices, and other topics.
 
-<!--truncate-->
+<! --truncate-->

Review comment:
       ```suggestion
   <!--truncate-->
   ```

##########
File path: website/blog/2021/08/24/shanghai-meetup-recap.md
##########
@@ -1,62 +1,60 @@
 ---
-title: "Apache APISIX Meetup 上海站全程回顾"
-author: "Apache APISIX 社区"
+title: Apache APISIX Meetup in Shanghai
+author: Apache APISIX
 keywords:
-- API 网关
+- API Gateway
 - APISIX
 - Meetup
-- 上海站
-- 回顾
-description: 活动回顾:Apache APISIX Meetup 上海站议题分享及视频回顾。
+description: "Event Review: Apache APISIX Meetup Shanghai Topic Sharing and Video Review."
 tags: [Events]
 ---
 
-> 活动回顾:Apache APISIX Meetup 上海站议题分享及视频回顾。
+> Event review: Apache APISIX Meetup Shanghai topic sharing and video review.
 
-<!--truncate-->
+<! --truncate-->
 
-Apache APISIX Meetup 上海站已于上周六(8 月 21 日)顺利举办🎉🎉🎉
+Apache APISIX Meetup Shanghai was successfully held last Saturday (August 21st) 🎉🎉🎉🎉
 
-本次 Meetup 由 [API7.AI](https://www.apiseven.com/zh) 发起,邀请了爱奇艺、AirWallex 空中云汇等合作伙伴,与 Apache APISIX 技术大咖、Apache APISIX PMC 成员、社区技术专家汇聚一堂,共同探讨了关于 Apache APISIX 社区发展、行业实践等话题。
+The Meetup was initiated by [API7.AI](https://www.apiseven.com/zh), and invited partners such as iQiyi, AirWallex, and other partners to come together with Apache APISIX technical experts, Apache APISIX PMC members, and community technical experts to discuss about The conference was a great opportunity to discuss Apache APISIX community development, industry practices and other topics.
 
-一起来回顾下大会中令人难忘的精彩演讲吧!
+Let's take a look back at some of the most memorable talks from the conference!
 
-## 基于 Apache APISIX,爱奇艺 API 网关的落地实践
+## Apache APISIX-based Aiki API Gateway Implementation Practice
 
-**讲师**:何聪
+**Instructor**: Cong He
 
-**个人介绍**:高级研发工程师,IIG 基础架构部-计算云,主要负责爱奇艺网关开发和运维工作。
+**Personal Introduction**: Senior R&D Engineer, IIG Infrastructure Department - Compute Cloud, mainly responsible for iQiyi Gateway development and operation and maintenance.

Review comment:
       ```suggestion
   **Personal Introduction**: Senior R&D Engineer, IIG Infrastructure Department - Compute Cloud, mainly responsible for iQiYi Gateway development and operation and maintenance.
   ```

##########
File path: website/blog/2021/08/21/shanghai-meetup.md
##########
@@ -1,99 +1,99 @@
 ---
-title: "8 月 21 日 Apache APISIX Meetup 上海站,欢迎报名参加!"
+title: August 21 Apache APISIX Meetup Shanghai, welcome to register!
 keywords:
-- API 网关
+- API Gateway
 - APISIX
 - Apache APISIX
 - Meetup
-description: 本次 Meetup 由 api7.ai https://www.apiseven.com/ 发起,并邀请爱奇艺、空中云汇等合作伙伴共同为大家呈现。Apache APISIX PMC 成员、贡献者、社区技术专家汇聚一堂,共同探讨 Apache APISIX 社区发展、行业实践等话题。
+description: This Meetup was initiated by api7.ai https://www.apiseven.com/, and invited partners such as iQiYi and Airwallex to present it. Apache APISIX PMC members, contributors, and community technical experts gathered to discuss Apache APISIX community development, industry practices, and other topics. 
 tags: [Events]
 ---
 
-> 本次 Meetup 由 [api7.ai](https://www.apiseven.com/) 发起,并邀请爱奇艺、空中云汇等合作伙伴共同为大家呈现。Apache APISIX PMC 成员、贡献者、社区技术专家汇聚一堂,共同探讨 Apache APISIX 社区发展、行业实践等话题。
+> This Meetup is initiated by [api7.ai](https://www.apiseven.com/), and invited partners such as iQiYi and Airwallex to present it. Apache APISIX PMC members, contributors, and community technical experts gathered to discuss Apache APISIX community development, industry practices, and other topics.
 
-<!--truncate-->
+<! --truncate-->
 
-#### 时间:2021 年 8 月 21 日 13:30
+#### Time: August 21, 2021, 13:30
 
-#### 地点:上海市黄浦区中区广场 6 楼静和岛二期
+#### Location: Jinghe Island II, 6th Floor, Central Plaza, Huangpu District, Shanghai
 
-#### 参加本次 Meetup,你可以
+#### By attending this Meetup, you can
 
-- 共同探讨 Apache APISIX 社区的前世今生
-- 听爱奇艺科学家讲述,爱奇艺是如何使用 Apache APISIX 支撑起千万级调用量的服务
-- 空中云汇是如何在使用 Apache APISIX 时兼顾用户体验、整洁架构与数据主权
-- 了解集中式身份认证的优点以及如何在 APISIX 上进行集中式身份认证
+- Discuss the past and present of the Apache APISIX community
+- Hear from Akiyo scientists about how Akiyo uses Apache APISIX to support a service with 10 million calls
+- How Airwallex uses Apache APISIX to balance user experience, clean architecture and data sovereignty
+- Learn about the benefits of centralized authentication and how to do it on APISIX
 
-如果你感兴趣的话,千万不要错过,**扫描活动海报二维码报名吧!**
+If you're interested, don't miss it, **scan the event poster for QR code to register!**
 
-tips:疫情防控不放松,我们将会控制现场活动规模,名额有限,报名从速!
+Tips: We will control the size of the event as the epidemic is not relaxed, so registration is limited.
 
-## 活动安排
+## Event Schedule
 
-![Apache APISIX Meetup](/img/blog_img/2021-08-21-1.jpg)
+The event schedule![Apache APISIX Meetup](/img/blog_img/2021-08-21-1.jpg)
 
-## 议题介绍
+## Introduction to the topic
 
-### 基于 Apache APISIX,爱奇艺 API 网关的落地实践
+### Apache APISIX based, iQiYi API gateway implementation practice
 
-#### 分享嘉宾
+#### Sharing Guests
 
-蒋文杰 / 爱奇艺科学家
+Wenjie Jiang / Scientist, iQiYi
 
-#### 议题详情
+#### Topic Details
 
-API 网关已经成为微服务架构中不可或缺的一环。它既承担着服务对外的唯一门户,又需要满足许多应用的共性功能。爱奇艺作为一家在线视频公司,每天需要承载千万级的调用量,并且对数据的安全、用户请求响应时效、系统的稳定都有着极其严格的要求,因此公司需要打造一个高性能、高可用的 API 网关。本文简单介绍爱奇艺 API 网关的架构以及实现的功能,包括请求分发、条件路由、API 管理、限流熔断、安全三防、监控报警以及全链路追踪等。
+API gateway has become an indispensable part of microservice architecture. It is the only portal for services to the outside world, but also needs to meet the common functions of many applications. As an online video company, Aqiyi needs to carry tens of millions of calls every day and has extremely strict requirements for data security, user request response time, and system stability, so the company needs to build a high-performance and highly available API gateway. This article briefly introduces the architecture of Aiki API gateway and the functions implemented, including request distribution, conditional routing, API management, flow-limiting fusion, security triple prevention, monitoring and alarming, and full-link tracking.
 
-### 如何使用 Apache APISIX 进行集中式身份认证
+### How to use Apache APISIX for centralized authentication
 
-#### 分享嘉宾
+#### Sharing Guests
 
-朱欣欣 / api7.ai 工程师,Apache APISIX Committer
+Xinxin Zhu / api7.ai Engineer, Apache APISIX Committer
 
-#### 议题详情
+#### Topic Details
 
-身份认证是零信任架构中非常重要的一环。通过身份认证可以有效保护服务,避免未经授权的恶意访问,数据泄漏以及黑客攻击。APISIX 作为一个动态、实时、高性能的 API 网关,支持丰富的身份认证插件,本次分享将介绍集中式身份认证的优点和如何在 APISIX 上进行集中式身份认证。
+Authentication is a very important part of zero-trust architecture. APISIX is a dynamic, real-time, high-performance API gateway that supports a rich set of authentication plugins.
 
-### 数据主权与 Apache APISIX 网关落地实践
+### Data Sovereignty and Apache APISIX Gateway Landing Practice
 
-#### 分享嘉宾
+#### Sharing Guests
 
-李杨 / 空中云汇技术平台负责人
+Yang Li / Head of Airwallex Technology Platform
 
-#### 议题详情
+#### Topic Details
 
-数据无处不在,每时每刻都有海量数据在世界各地被处理、传输、存储。然而数据世界不是法外之地,数据的收集与处理必须遵照各国法律执行。这为企业的技术架构提出了巨大的挑战,如何兼顾用户体验、整洁架构与数据主权?API 网关在企业架构中具有特殊地位,也因此能在数据主权场景下起到特殊重要的作用。
+Data is everywhere, and massive amounts of data are being processed, transmitted, and stored all over the world every moment. However, the world of data is not a place outside the law, and the collection and processing of data must comply with the laws of each country. The API gateway has a special position in the enterprise architecture and therefore plays a special role in the data sovereignty scenario.
 
-### 独行者速,众行者远,Apache APISIX 感恩有你
+### The One Who Walks Alone Goes Fast, The Many Who Walk Far, Apache APISIX Thanks to You
 
-#### 分享嘉宾
+#### Sharing Guests
 
-王院生 / api7.ai 联合创始人 & CTO
+Yansheng Wang / Co-founder & CTO of api7.ai
 
-#### 议题详情
+#### Topic Details
 
-Apache APISIX 从开源第一天就以社区方式成长,短短两年时间产品多项技术指标包揽第一,迅速成为全世界最活跃 API 网关项目,并确定了专属于 Apache APISIX 的道路:统一 7 层流量处理。一个人可能走的很快,一群人才能走的更远,Apache APISIX 成长之路感恩有你。
+Apache APISIX has been growing as a community since the first day of open source. In just two years, the product has won the first place in many technical indicators and quickly become the most active API gateway project in the world, and has defined the path that belongs to Apache APISIX: unified 7-layer traffic processing. One person can go fast, but a group of people can go farther, and we are grateful to you for the growth of Apache APISIX.
 
-## 周边福利
+## Peripheral Benefits
 
-参加 Meetup,与讲师互动,有机会获得 Apache APISIX 最新周边:超大鼠标垫、精致马克杯、Apache APISIX 徽章、定制雨伞。
+Join the Meetup, interact with the instructors, and get a chance to win the latest Apache APISIX gifts: mouse pads, coffee mugs, Apache APISIX badges, and umbrellas.
 
 ![Apache APISIX Gift](/img/blog_img/2021-08-21-4.jpg)
 
-## 参与方式
+## How to participate
 
-### 现场报名
+### On-site registration
 
-扫描上方活动海报二维码即可报名!
+Scan the event poster QR code above to sign up!
 
-### 线上直播
+### Online Live Streaming
 
-如果不能到现场参加 Meetup,关注 Apache APISIX 视频号观看直播。
+If you can't make it to the Meetup, follow the Apache APISIX video to watch the live stream.
 
-![Apache APISIX Live](/img/blog_img/2021-08-21-2.png)
+Live![Apache APISIX Live](/img/blog_img/2021-08-21-2.png)

Review comment:
       ```suggestion
   ![Apache APISIX Live](/img/blog_img/2021-08-21-2.png)
   ```

##########
File path: website/blog/2021/08/30/weekly-report.md
##########
@@ -1,89 +1,89 @@
 ---
-title: "Apache APISIX 社区周报 | 2021 8.23-8.29"
+title: Apache APISIX Community Weekly Report | 2021 8.23-8.29
 keywords:
 - APISIX
-- 社区周报
-- 贡献者
+- Community Weekly
+- Contributor
 - Good first issue
-description: “独行者速,众行者远”。Apache APISIX 社区周报希望可以帮助社区小伙伴们更好地掌握 Apache APISIX 社区的每周进展,方便大家参与到 Apache APISIX 社区中来。
+description: The Apache APISIX Community Weekly Newsletter hopes to help community members better understand the weekly progress of the Apache APISIX community and facilitate your participation in the Apache APISIX community.
 tags: [Events]
 ---
 
 <!--truncate-->
 
-## 导语
+## Introduction
 
-Apache APISIX 从开源第一天就以社区方式成长,迅速成为全世界最活跃的开源 API 网关项目。这些成就,离不开社区小伙伴们的共同奋斗。
+Apache APISIX has grown as a community from the first day of open source and has quickly become the most active open source API gateway project in the world. These achievements cannot be achieved without the joint efforts of our community partners.
 
-“独行者速,众行者远”。Apache APISIX 社区周报希望可以帮助社区小伙伴们更好地掌握 Apache APISIX 社区的每周进展,方便大家参与到 Apache APISIX 社区中来。
+"The Apache APISIX Community Weekly Newsletter hopes to help community members better grasp the weekly progress of the Apache APISIX community and facilitate your participation in the Apache APISIX community.
 
-我们还整理了一些适合新来社区的小伙伴们参加的 issue !感兴趣的同学们,走过路过不要错过!
+We've also put together some issues for those new to the community! If you are interested, don't miss them!
 
-## 贡献者统计
+## Contributor statistics
 
-![新增贡献者数量](https://static.apiseven.com/202108/1630393952402-4965d35c-6b05-4f71-9966-2fea7f7939d3.JPG)
+![Number of new contributors](https://static.apiseven.com/202108/1630393952402-4965d35c-6b05-4f71-9966-2fea7f7939d3.JPG)
 
-![本周新晋贡献者](https://static.apiseven.com/202108/1630393952406-9f61c39b-ea9e-4451-bd26-ab845a32a222.JPG)
+![New contributors this week](https://static.apiseven.com/202108/1630393952406-9f61c39b-ea9e-4451-bd26-ab845a32a222.JPG)
 
 ## Good first issue
 
 ### Issue #4241
 
-**链接**:https://github.com/apache/apisix/issues/4241
+**Link**: https://github.com/apache/apisix/issues/4241
 
-**问题描述**:现在在将 jwt-auth 插件添加到一个 service/route 时,jwt 令牌未包含“key”声明。
+**Problem Description**: Now when adding the jwt-auth plugin to a service/route, the jwt token does not contain a "key" declaration.
 
 ```shell
 {
-  "iss":"http://127.0.0.1",
-  "client_id":"application1",
+  "iss": "http://127.0.0.1",

Review comment:
       ```suggestion
     "iss":"http://127.0.0.1",
   ```

##########
File path: website/blog/2021/08/30/Ingress-Meeting.md
##########
@@ -1,46 +1,46 @@
 ---
-title: "社区会议| 周三下午 2 点,Apache APISIX Ingress 社区会议与你不见不散"
+title: Webinar| See you at the Apache APISIX Ingress Community Meeting on Wednesday at 2pm!
 author: "Apache APISIX 社区"
 keywords:
 - API 网关
 - APISIX
 - Ingress
-description: Apache APISIX Ingress 社区会议,建立与社区用户和开发者们的沟通渠道,帮助大家了解 Apache APISIX Ingress 的发展方向和开发计划。 
+description: Apache APISIX Ingress community meetings to establish a channel of communication with community users and developers and to help everyone understand the direction and development plans for Apache APISIX Ingress.
 tags: [Events]
 ---
 
-> 随着 [Apache APISIX Ingress Controller 1.0 版本](https://apisix.apache.org/blog/2021/06/18/first-GA-version-v1.0-of-Apache-APISIX-Ingress-Controller-released) 发布,越来越多的开发者开始关注 Apache APISIX Ingress 方案,Apache APISIX 社区希望能够建立与社区用户和开发者们更直接的沟通渠道,帮助大家了解 Apache APISIX Ingress 的发展方向和开发计划,希望每一位用户、每一位开发者的声音都可以被听见。 因此,Apache APISIX 社区开始组织每两周线上社区会议。
+> With the release of [Apache APISIX Ingress Controller version 1.0](https://apisix.apache.org/blog/2021/06/18/first-GA-version-v1.0-of-Apache-APISIX-Ingress- Controller-released), more and more developers have started to pay attention to the Apache APISIX Ingress solution. The Apache APISIX community hopes to establish a more direct communication channel with users and developers in the community to help them understand the development direction and development plans of Apache APISIX Ingress. We hope that every user and developer's voice will be heard. Therefore, the Apache APISIX community has started to organize bi-weekly online community meetings.

Review comment:
       ```suggestion
   > With the release of [Apache APISIX Ingress Controller version 1.0](https://apisix.apache.org/blog/2021/06/18/first-GA-version-v1.0-of-Apache-APISIX-Ingress-Controller-released), more and more developers have started to pay attention to the Apache APISIX Ingress solution. The Apache APISIX community hopes to establish a more direct communication channel with users and developers in the community to help them understand the development direction and development plans of Apache APISIX Ingress. We hope that every user and developer's voice will be heard. Therefore, the Apache APISIX community has started to organize bi-weekly online community meetings.
   ```

##########
File path: website/blog/2021/08/30/Ingress-Meeting.md
##########
@@ -1,46 +1,46 @@
 ---
-title: "社区会议| 周三下午 2 点,Apache APISIX Ingress 社区会议与你不见不散"
+title: Webinar| See you at the Apache APISIX Ingress Community Meeting on Wednesday at 2pm!
 author: "Apache APISIX 社区"
 keywords:
 - API 网关
 - APISIX
 - Ingress
-description: Apache APISIX Ingress 社区会议,建立与社区用户和开发者们的沟通渠道,帮助大家了解 Apache APISIX Ingress 的发展方向和开发计划。 
+description: Apache APISIX Ingress community meetings to establish a channel of communication with community users and developers and to help everyone understand the direction and development plans for Apache APISIX Ingress.
 tags: [Events]
 ---
 
-> 随着 [Apache APISIX Ingress Controller 1.0 版本](https://apisix.apache.org/blog/2021/06/18/first-GA-version-v1.0-of-Apache-APISIX-Ingress-Controller-released) 发布,越来越多的开发者开始关注 Apache APISIX Ingress 方案,Apache APISIX 社区希望能够建立与社区用户和开发者们更直接的沟通渠道,帮助大家了解 Apache APISIX Ingress 的发展方向和开发计划,希望每一位用户、每一位开发者的声音都可以被听见。 因此,Apache APISIX 社区开始组织每两周线上社区会议。
+> With the release of [Apache APISIX Ingress Controller version 1.0](https://apisix.apache.org/blog/2021/06/18/first-GA-version-v1.0-of-Apache-APISIX-Ingress- Controller-released), more and more developers have started to pay attention to the Apache APISIX Ingress solution. The Apache APISIX community hopes to establish a more direct communication channel with users and developers in the community to help them understand the development direction and development plans of Apache APISIX Ingress. We hope that every user and developer's voice will be heard. Therefore, the Apache APISIX community has started to organize bi-weekly online community meetings.
 
-<!--truncate-->
+<! --truncate-->

Review comment:
       ```suggestion
   <!--truncate-->
   ```

##########
File path: website/blog/2021/08/31/Apache APISIX × KubeSphere-a-better-gateway-and-K8S-Ingress-Controller.md
##########
@@ -1,102 +1,102 @@
 ---
-title: "Apache APISIX × KubeSphere:提供更好用的网关及 K8S Ingress Controller"
-author: "张晋涛"
+title: "Apache APISIX × KubeSphere: Providing a better gateway and K8S Ingress Controller"
+author: Jintao Zhang
 authorURL: "https://github.com/tao12345666333"
 authorImageURL: "https://avatars.githubusercontent.com/u/3264292?v=4"
 keywords:
-- API 网关
+- API Gateway
 - APISIX
 - KubeSphere
 - Ingress
-description: 本文介绍了在 KubeSphere 中使用 Apache APISIX 的官方 Helm 仓库直接部署 Apache APISIX 和 APISIX Ingress Controller 。并且 Apache APISIX 可通过作为网关,或者 APISIX Ingress Controller 的数据面来承载业务流量。
+description: This article describes the direct deployment of Apache APISIX and APISIX Ingress Controller in KubeSphere using the official Apache APISIX Helm repository. And Apache APISIX can be used as a gateway or as a data plane for APISIX Ingress Controller to carry business traffic.
 tags: [Practical Case]
 ---
 
-> 本文介绍了在 KubeSphere 中使用 Apache APISIX 的官方 Helm 仓库直接部署 Apache APISIX 和 APISIX Ingress Controller 。并且 Apache APISIX 可通过作为网关,或者 APISIX Ingress Controller 的数据面来承载业务流量。
+> This article describes the direct deployment of Apache APISIX and APISIX Ingress Controller in KubeSphere using the official Apache APISIX Helm repository. And Apache APISIX can be used as a gateway or a data plane for APISIX Ingress Controller to carry business traffic.
 
 <!--truncate-->
 
-## KubeSphere 介绍
+## Introduction to KubeSphere
 
-[KubeSphere](https://kubesphere.io/) 是在 Kubernetes 之上构建的面向云原生应用的系统,完全开源,支持多云与多集群管理,提供全栈的 IT 自动化运维能力,简化企业的 DevOps 工作流。它的架构可以非常方便地使第三方应用与云原生生态组件进行即插即用 (plug-and-play) 的集成。
+[KubeSphere](https://kubesphere.io/) is a cloud-native application-oriented system built on top of Kubernetes, fully open source, supporting multi-cloud and multi-cluster management, providing full-stack IT automation capabilities, and simplifying enterprise DevOps workflows. Its architecture makes it easy to integrate third-party applications with cloud-native eco-components in a plug-and-play fashion.
 
-作为全栈的多租户容器平台,KubeSphere 提供了运维友好的向导式操作界面,帮助企业快速构建一个强大和功能丰富的容器云平台。KubeSphere 为用户提供构建企业级 Kubernetes 环境所需的多项功能,例如多云与多集群管理、Kubernetes 资源管理、DevOps、应用生命周期管理、微服务治理(服务网格)、日志查询与收集、服务与网络、多租户管理、监控告警、事件与审计查询、存储管理、访问权限控制、GPU 支持、网络策略、镜像仓库管理以及安全管理等。
+As a full-stack, multi-tenant container platform, KubeSphere provides an operations-friendly, wizard-based interface to help organizations quickly build a powerful and feature-rich container cloud platform. DevOps, application lifecycle management, microservice governance (service grid), log query and collection, service and networking, multi-tenant management, monitoring and alerting, event and audit queries, storage management, access control, GPU support, network policies, image repository management, and security management.
 
-## Apache APISIX 介绍
+## Introduction to Apache APISIX
 
-[Apache APISIX](https://github.com/apache/apisix) 是一款开源的高性能、动态云原生网关,由深圳支流科技有限公司于 2019 年捐赠给 Apache 基金会,当前已经成为 Apache 基金会的顶级开源项目,也是 GitHub 上最活跃的网关项目。Apache APISIX 当前已经覆盖了 API 网关,LB,Kubernetes Ingress,Service Mesh 等多种场景。
+[Apache APISIX](https://github.com/apache/apisix) is an open source, high-performance, dynamic cloud-native gateway donated to the Apache Foundation by Shenzhen Tributary Technology Co. Apache APISIX currently covers API gateways, LB, Kubernetes Ingress, Service Mesh, and many other scenarios.
 
-## 前置条件
+## Prerequisites
 
-将现有 Kubernetes 集群已纳入 KubeSphere 管理。
+Existing Kubernetes clusters already managed in KubeSphere.
 
-## 部署 Apache APISIX 和 Apache APISIX Ingress Controller
+## Deploy Apache APISIX and Apache APISIX Ingress Controller
 
-我们可以参考 KubeSphere 的文档启用 KubeSphere 的 [AppStore](https://kubesphere.io/docs/pluggable-components/app-store/),或者使用使用 Apache APISIX 的 [Helm 仓库](https://charts.apiseven.com)来进行部署。这里,我们直接使用 Apache APISIX 的 Helm 仓库进行部署。
+We can either enable KubeSphere's [AppStore](https://kubesphere.io/docs/pluggable-components/app-store/) by referring to KubeSphere's documentation, or use the [Helm repository](https://kubesphere.io/docs/pluggable-components/app-store/) using Apache APISIX (https://charts.apiseven.com) for deployment. Here, we directly use the Helm repository of Apache APISIX for deployment.
 
-执行以下命令即可添加 Apache APISIX 的 Helm repo,并完成部署。
+Execute the following command to add the Helm repo for Apache APISIX and complete the deployment.
 
 ```shell
-➜  ~ helm repo add apisix https://charts.apiseven.com
+➜ ~ helm repo add apisix https://charts.apiseven.com
 "apisix" has been added to your repositories
-➜  ~ helm repo add bitnami https://charts.bitnami.com/bitnami
+➜ ~ helm repo add bitnami https://charts.bitnami.com/bitnami
 "bitnami" has been added to your repositories
-➜  ~ helm repo update
-➜  ~ kubectl create ns apisix
+➜ ~ helm repo update
+➜ ~ kubectl create ns apisix
 namespace/apisix created
-➜  ~ helm install apisix apisix/apisix --set gateway.type=NodePort --set ingress-controller.enabled=true --namespace apisix
-W0827 18:19:58.504653  294386 warnings.go:70] apiextensions.k8s.io/v1beta1 CustomResourceDefinition is deprecated in v1.16+, unavailable in v1.22+; use apiextensions.k8s.io/v1 CustomResourceDefinition
+➜ ~ helm install apisix apisix/apisix --set gateway.type=NodePort --set ingress-controller.enabled=true --namespace apisix
+W0827 18:19:58.504653 294386 warnings.go:70] apiextensions.k8s.io/v1beta1 CustomResourceDefinition is deprecated in v1.16+, unavailable in v1.22+; use apiextensions.k8s.io/v1 CustomResourceDefinition
 NAME: apisix
 LAST DEPLOYED: Fri Aug 27 18:20:00 2021
 NAMESPACE: apisix
 STATUS: deployed
 REVISION: 1
 TEST SUITE: None
-NOTES:
-1. Get the application URL by running these commands:
+NOTES.

Review comment:
       ```suggestion
   NOTES:
   ```

##########
File path: website/blog/2021/08/11/interview-TuZhengsong.md
##########
@@ -1,145 +1,145 @@
 ---
-title: "从新手村出来,我在 Apache APISIX 社区发出了第一个 PR"
-author: "Apache APISIX 社区"
+title: I issued my first PR in the Apache APISIX community
+author: Apache APISIX
 authorURL: "https://github.com/Yangxiamao"
 authorImageURL: "https://avatars.githubusercontent.com/u/47442074?v=4"
 keywords:
-- API 网关
+- API Gateway
 - APISIX
 - Apache APISIX
-- 开源社区
-- 开源项目
-description: 这篇采访稿讲述了屠正松从开源社区小白成长为 Apache 顶级开源项目 APISIX committer 的历程。屠正松(GitHub ID:tzssangglass)因深度参与 Apache APISIX 的开发,在社区中贡献很多,2021 年 7 月 22 日被推选为 Apache APISIX committer。
+- Community
+- Open Source
+description: "This interview is about Zhengsong Tu's journey from an open source community nerd to an APISIX committer for Apache's top open source project. Zhengsong Tu (GitHub ID: tzssangglass) was elected as an Apache APISIX committer on July 22, 2021 for his deep involvement in Apache APISIX development and his many contributions to the community."
 tags: [Interview]
 ---
 
-> 这篇采访稿讲述了屠正松从开源社区小白成长为 Apache 顶级开源项目 APISIX committer 的历程。屠正松(GitHub ID:tzssangglass)因深度参与 Apache APISIX 的开发,在社区中贡献很多,2021 年 7 月 22 日被推选为 Apache APISIX committer。
+> This interview is about Zhengsong Tu's journey from an open source community nerd to an APISIX committer for Apache's top open source project. Zhengsong Tu (GitHub ID: tzssangglass) was elected as an Apache APISIX committer on July 22, 2021 for his deep involvement in Apache APISIX development and his many contributions to the community.
 
 <!--truncate-->
 
-> 当我看到那个 issue 后,就有种强烈的想要参与到社区的冲动。看了社区的新手指南后,我像从新手村出来的勇者,准备打怪。
+> When I saw that issue, I had a strong urge to get involved in the community. After reading the community's newbie guide, I was like a brave man coming out of the newbie village, ready to fight.
 >
-> —— Apache APISIX committer 屠正松
+> -- Zhengsong Tu, Apache APISIX committer
 
-历时 282 天,屠正松(GitHub ID:tzssangglass)从开源社区的小白成长为了 Apache APISIX 的 committer。
+In 282 days, Zhengsong Tu (GitHub ID: tzssangglass) has grown from an open source community nerd to an Apache APISIX committer.
 
 ![Apache APISIX committer tzssangglass github](/img/blog_img/2021-08-11-1.webp)
 
-屠正松因深度参与 Apache APISIX 的开发,在社区中贡献很多,2021 年 7 月 22 日被推选为 Apache APISIX committer。
+Zhengsong Tu was elected as Apache APISIX committer on July 22, 2021 for his deep involvement in Apache APISIX development and many contributions in the community.
 
-在一个平淡的下午,我们和正松连线聊了聊。因为疫情关系,居住在南京的他已经多日未外出。在没有和他聊天之前,我没有想到,胡子拉碴的他,竟然走过了这么曲折的路。
+On an uneventful afternoon, we chatted with Zhengsong by phone. Because of the epidemic, he has not been out for many days in Nanjing. Before I talked to him, I didn't expect that the bearded man had traveled such a winding road.
 
-## 大学,我的大学
+## University, my university
 
-> 我大学的时候学的是通信工程,每天最开心的事就是踢球。现在有时候会想,如果能带着现在的记忆回到大学时光就好了。
+> When I was in college, I studied communication engineering, and the happiest thing I did every day was to play soccer. Now sometimes I think that it would be nice to go back to my college days with the memories I have now.
 
-正松在大学期间里面其实没怎么接触过编程,他当年其实有 C 语言的编程课,但是因为忙着踢球,挂科了。可是,他挂科之后的补考也没过,导致重修。最尴尬的是,他重修也没过,后来怎么办呢?毕业之前还有毕业清考。这可不能再挂了,于是正松就去图书馆去借了一本 C 语言的书来看。
+Zhengsong actually didn't have much contact with programming during his college years, he actually had a C programming class, but he failed it because he was too busy playing soccer. However, he failed a make-up exam after failing the class, resulting in a retake. The most embarrassing thing is that he failed the retake as well, so what did he do afterwards? There was a graduation clearing exam before graduation. This can not be failed again, so Zhengsong went to the library to borrow a C language book to read.
 
-“我当时心想,C 语言真的这么难吗?”正松说。
+"I was thinking, "Is C really that hard?" Zhengsong said.
 
-然后他就一直看一直看,看着看着就突然发现编程好像有那么点意思,他看懂了!最后他在毕业前顺利通过了考试。在毕业之后,找到了一份做程序员的工作。
+Then he kept reading and reading and reading, and suddenly he realized that programming seemed to have some meaning, and he understood it! He finally passed the exam before graduating. After graduation, he found a job as a programmer.
 
-“我本来都准备毕业回家找个厂上班了。”,他半开玩笑地说。
+"I was ready to graduate and go home and find a factory to work." , he said half-jokingly.
 
-彼时,他可能不会想到如今的他会成为数个知名开源项目的 developer,参与一些支撑着千万级并发流量的基础设施的开发。
+At that time, he probably wouldn't have thought that today he would be the developer of several well-known open source projects, and involved in the development of some infrastructure that supports millions of concurrent traffic.
 
-## 出象牙塔记
+## Out of the Ivory Tower
 
-> 在工业界,真实的业务场景和学校里学的很不一样的
+> In industry, the real business scenario is very different from what you learn in school.
 
-正松的第一份工作就职于一家做穿戴设备的创业公司,从事智能手环的研发工作。正松和他的前同事们需要通过处理从智能手环上的获取的各种传感器数据,来完成对用户的心率、运动量、血压等的监测。
+Zhengsong's first job was at a wearable device startup, working on the development of smart bracelets. Zhengsong and his former colleagues had to process various sensor data from the smart bracelet to monitor the user's heart rate, exercise, blood pressure and so on.
 
-“工作蛮好玩的,因为在工业界,真实的业务场景和学校里学的很不一样的,很多东西都得从头开始学”,正松说。
+"It was fun because in industry, the real business scenario is very different from what you learn in school, and a lot of things have to be learned from scratch," Masatsu said.
 
-有一天下班之后,这家公司的老板娘突然发了一条信息,说公司的员工暂时休假,什么时候上班等通知。
+One day after work, the owner of this company suddenly sent a message saying that the company's employees were on temporary leave and that they would wait to be notified when to work.
 
-正松当时就觉得不对劲,怎么好好的上着班,突然就休假了?然后他立马打开招聘软件,开始找新的工作。后来才知道,公司的老板跟供应商有合同纠纷,公司短暂停摆了。
+Masatsu felt something was wrong at that time, how to work well, suddenly on vacation? Then he immediately opened the recruitment software and started looking for a new job. Later, he found out that the owner of the company had a contract dispute with the supplier, and the company was briefly shut down.

Review comment:
       ```suggestion
   Zhengsong felt something was wrong at that time, how to work well, suddenly on vacation? Then he immediately opened the recruitment software and started looking for a new job. Later, he found out that the owner of the company had a contract dispute with the supplier, and the company was briefly shut down.
   ```

##########
File path: website/blog/2021/08/31/Apache APISIX × KubeSphere-a-better-gateway-and-K8S-Ingress-Controller.md
##########
@@ -1,102 +1,102 @@
 ---
-title: "Apache APISIX × KubeSphere:提供更好用的网关及 K8S Ingress Controller"
-author: "张晋涛"
+title: "Apache APISIX × KubeSphere: Providing a better gateway and K8S Ingress Controller"
+author: Jintao Zhang
 authorURL: "https://github.com/tao12345666333"
 authorImageURL: "https://avatars.githubusercontent.com/u/3264292?v=4"
 keywords:
-- API 网关
+- API Gateway
 - APISIX
 - KubeSphere
 - Ingress
-description: 本文介绍了在 KubeSphere 中使用 Apache APISIX 的官方 Helm 仓库直接部署 Apache APISIX 和 APISIX Ingress Controller 。并且 Apache APISIX 可通过作为网关,或者 APISIX Ingress Controller 的数据面来承载业务流量。
+description: This article describes the direct deployment of Apache APISIX and APISIX Ingress Controller in KubeSphere using the official Apache APISIX Helm repository. And Apache APISIX can be used as a gateway or as a data plane for APISIX Ingress Controller to carry business traffic.
 tags: [Practical Case]
 ---
 
-> 本文介绍了在 KubeSphere 中使用 Apache APISIX 的官方 Helm 仓库直接部署 Apache APISIX 和 APISIX Ingress Controller 。并且 Apache APISIX 可通过作为网关,或者 APISIX Ingress Controller 的数据面来承载业务流量。
+> This article describes the direct deployment of Apache APISIX and APISIX Ingress Controller in KubeSphere using the official Apache APISIX Helm repository. And Apache APISIX can be used as a gateway or a data plane for APISIX Ingress Controller to carry business traffic.
 
 <!--truncate-->
 
-## KubeSphere 介绍
+## Introduction to KubeSphere
 
-[KubeSphere](https://kubesphere.io/) 是在 Kubernetes 之上构建的面向云原生应用的系统,完全开源,支持多云与多集群管理,提供全栈的 IT 自动化运维能力,简化企业的 DevOps 工作流。它的架构可以非常方便地使第三方应用与云原生生态组件进行即插即用 (plug-and-play) 的集成。
+[KubeSphere](https://kubesphere.io/) is a cloud-native application-oriented system built on top of Kubernetes, fully open source, supporting multi-cloud and multi-cluster management, providing full-stack IT automation capabilities, and simplifying enterprise DevOps workflows. Its architecture makes it easy to integrate third-party applications with cloud-native eco-components in a plug-and-play fashion.
 
-作为全栈的多租户容器平台,KubeSphere 提供了运维友好的向导式操作界面,帮助企业快速构建一个强大和功能丰富的容器云平台。KubeSphere 为用户提供构建企业级 Kubernetes 环境所需的多项功能,例如多云与多集群管理、Kubernetes 资源管理、DevOps、应用生命周期管理、微服务治理(服务网格)、日志查询与收集、服务与网络、多租户管理、监控告警、事件与审计查询、存储管理、访问权限控制、GPU 支持、网络策略、镜像仓库管理以及安全管理等。
+As a full-stack, multi-tenant container platform, KubeSphere provides an operations-friendly, wizard-based interface to help organizations quickly build a powerful and feature-rich container cloud platform. DevOps, application lifecycle management, microservice governance (service grid), log query and collection, service and networking, multi-tenant management, monitoring and alerting, event and audit queries, storage management, access control, GPU support, network policies, image repository management, and security management.
 
-## Apache APISIX 介绍
+## Introduction to Apache APISIX
 
-[Apache APISIX](https://github.com/apache/apisix) 是一款开源的高性能、动态云原生网关,由深圳支流科技有限公司于 2019 年捐赠给 Apache 基金会,当前已经成为 Apache 基金会的顶级开源项目,也是 GitHub 上最活跃的网关项目。Apache APISIX 当前已经覆盖了 API 网关,LB,Kubernetes Ingress,Service Mesh 等多种场景。
+[Apache APISIX](https://github.com/apache/apisix) is an open source, high-performance, dynamic cloud-native gateway donated to the Apache Foundation by Shenzhen Tributary Technology Co. Apache APISIX currently covers API gateways, LB, Kubernetes Ingress, Service Mesh, and many other scenarios.
 
-## 前置条件
+## Prerequisites
 
-将现有 Kubernetes 集群已纳入 KubeSphere 管理。
+Existing Kubernetes clusters already managed in KubeSphere.
 
-## 部署 Apache APISIX 和 Apache APISIX Ingress Controller
+## Deploy Apache APISIX and Apache APISIX Ingress Controller
 
-我们可以参考 KubeSphere 的文档启用 KubeSphere 的 [AppStore](https://kubesphere.io/docs/pluggable-components/app-store/),或者使用使用 Apache APISIX 的 [Helm 仓库](https://charts.apiseven.com)来进行部署。这里,我们直接使用 Apache APISIX 的 Helm 仓库进行部署。
+We can either enable KubeSphere's [AppStore](https://kubesphere.io/docs/pluggable-components/app-store/) by referring to KubeSphere's documentation, or use the [Helm repository](https://kubesphere.io/docs/pluggable-components/app-store/) using Apache APISIX (https://charts.apiseven.com) for deployment. Here, we directly use the Helm repository of Apache APISIX for deployment.
 
-执行以下命令即可添加 Apache APISIX 的 Helm repo,并完成部署。
+Execute the following command to add the Helm repo for Apache APISIX and complete the deployment.
 
 ```shell
-➜  ~ helm repo add apisix https://charts.apiseven.com
+➜ ~ helm repo add apisix https://charts.apiseven.com
 "apisix" has been added to your repositories
-➜  ~ helm repo add bitnami https://charts.bitnami.com/bitnami
+➜ ~ helm repo add bitnami https://charts.bitnami.com/bitnami
 "bitnami" has been added to your repositories
-➜  ~ helm repo update
-➜  ~ kubectl create ns apisix
+➜ ~ helm repo update
+➜ ~ kubectl create ns apisix
 namespace/apisix created
-➜  ~ helm install apisix apisix/apisix --set gateway.type=NodePort --set ingress-controller.enabled=true --namespace apisix
-W0827 18:19:58.504653  294386 warnings.go:70] apiextensions.k8s.io/v1beta1 CustomResourceDefinition is deprecated in v1.16+, unavailable in v1.22+; use apiextensions.k8s.io/v1 CustomResourceDefinition
+➜ ~ helm install apisix apisix/apisix --set gateway.type=NodePort --set ingress-controller.enabled=true --namespace apisix
+W0827 18:19:58.504653 294386 warnings.go:70] apiextensions.k8s.io/v1beta1 CustomResourceDefinition is deprecated in v1.16+, unavailable in v1.22+; use apiextensions.k8s.io/v1 CustomResourceDefinition
 NAME: apisix
 LAST DEPLOYED: Fri Aug 27 18:20:00 2021
 NAMESPACE: apisix
 STATUS: deployed
 REVISION: 1
 TEST SUITE: None
-NOTES:
-1. Get the application URL by running these commands:
+NOTES.
+1: Get the application URL by running these commands:
   export NODE_PORT=$(kubectl get --namespace apisix -o jsonpath="{.spec.ports[0].nodePort}" services apisix-gateway)
   export NODE_IP=$(kubectl get nodes --namespace apisix -o jsonpath="{.items[0].status.addresses[0].address}")
   echo http://$NODE_IP:$NODE_PORT
 ```
 
-验证是否已经成功部署且运行:
+Verify that it has been successfully deployed and is running.
 
 ```shell
-➜  ~ kubectl -n apisix get pods
-NAME                                         READY   STATUS    RESTARTS   AGE
-apisix-77d7545d4d-cvdhs                      1/1     Running   0          4m7s
-apisix-etcd-0                                1/1     Running   0          4m7s
-apisix-etcd-1                                1/1     Running   0          4m7s
-apisix-etcd-2                                1/1     Running   0          4m7s
-apisix-ingress-controller-74c6b5fbdd-94ngk   1/1     Running   0          4m7s
+➜ ~ kubectl -n apisix get pods
+NAME READY STATUS RESTARTS AGE
+apisix-77d7545d4d-cvdhs 1/1 Running 0 4m7s
+apisix-etcd-0 1/1 Running 0 4m7s
+apisix-etcd-1 1/1 Running 0 4m7s
+apisix-etcd-2 1/1 Running 0 4m7s
+apisix-ingress-controller-74c6b5fbdd-94ngk 1/1 Running 0 4m7s

Review comment:
       ```suggestion
   NAME                                         READY   STATUS    RESTARTS   AGE
   apisix-77d7545d4d-cvdhs                      1/1     Running   0          4m7s
   apisix-etcd-0                                1/1     Running   0          4m7s
   apisix-etcd-1                                1/1     Running   0          4m7s
   apisix-etcd-2                                1/1     Running   0          4m7s
   apisix-ingress-controller-74c6b5fbdd-94ngk   1/1     Running   0          4m7s
   ```

##########
File path: website/blog/2021/08/18/Auth-with-Casbin-in-Apache-APISIX.md
##########
@@ -1,48 +1,48 @@
 ---
-title: "在 Apache APISIX 中使用 Casbin 进行授权"
-author: "Casbin 社区 & Apache APISIX 社区"
+title: Licensing with Casbin in Apache APISIX
+author: Casbin & Apache APISIX
 keywords:
-- API 网关
+- API Gateway
 - APISIX
 - Apache APISIX
 - Casbin
 - RBAC
-description: 当我们在使用 Apache APISIX 时,可能想要在应用里添加复杂的授权逻辑。在此篇文章中,我们将使用 Apache APISIX 的内置 Casbin 插件(authz-casbin)来实现基于角色的访问控制(RBAC)模型。
+description: When we are using Apache APISIX, we may want to add complex authorization logic to our application. In this article, we will use the built-in Casbin plugin (authz-casbin) of Apache APISIX to implement the role-based access control (RBAC) model.
 tags: [Practical Case]
 ---
 
-> 当我们在使用 Apache APISIX 时,可能想要在应用里添加复杂的授权逻辑。在此篇文章中,我们将使用 Apache APISIX 的内置 Casbin 插件(authz-casbin)来实现基于角色的访问控制(RBAC)模型。
+> When we are using Apache APISIX, we may want to add complex authorization logic to our application. In this post, we will use the built-in Casbin plugin (authz-casbin) for Apache APISIX to implement a role-based access control (RBAC) model.
 
-<!--truncate-->
+<! --truncate-->
 
-## 介绍
+## Introduction
 
 ### Apache APISIX
 
-[Apache APISIX](https://github.com/apache/apisix) 是一个动态、实时、高性能的 API 网关, 提供负载均衡、动态上游、灰度发布、精细化路由、限流限速、服务降级、服务熔断、身份认证、可观测性等数百项功能。你可以使用 Apache APISIX 来处理传统的南北向流量,以及服务间的东西向流量, 也可以当做 [k8s ingress controller](https://github.com/apache/apisix-ingress-controller) 来使用。
+[Apache APISIX](https://github.com/apache/apisix) is a dynamic, real-time, high-performance API gateway that provides load balancing, dynamic upstream, grayscale publishing, fine-grained routing, flow and speed limiting, service degradation, service meltdown, authentication, observability, and hundreds of other features. You can use Apache APISIX for traditional north-south traffic, as well as east-west traffic between services, or as a [k8s ingress controller](https://github.com/apache/apisix-ingress-controller).
 
 ### Casbin
 
-[Casbin](https://casbin.org/zh-CN/) 是一个强大的、高效的开源访问控制框架,其权限管理机制支持多种访问控制模型。
+[Casbin](https://casbin.org/zh-CN/) is a powerful and efficient open source access control framework with a permission management mechanism that supports multiple access control models.
 
-### authz-casbin 插件介绍
+### authz-casbin plugin introduction
 
-在 Apache APISIX 的使用中,路由匹配和请求授权之间有个隐含的矛盾点:为了更高细粒度的权限控制,需要配置更高细粒度的路由,来精准识别请求并对请求进行授权。在复杂的授权模型场景下,这将导致路由数量成倍增加,加剧了运维复杂度。
-[authz-casbin](https://github.com/apache/apisix/blob/d9b928321fcdd12eef024df8c7c410424c1e0c8b/docs/en/latest/plugins/authz-casbin.md) 是一个基于 lua-casbin 的 Apache APISIX 插件,支持基于各种访问模型的强大授权。Casbin 是一个强大的、高效的开源访问控制框架,支持 ACL、RBAC、ABAC 等访问控制模型,lua-casbin 是 Casbin 访问控制框架的 Lua 版本实现。
-authz-casbin 插件可以把路由匹配和请求授权这两个功能很好地进行解耦,你可以将各种授权访问模型加载到 Apache APISIX 中,借助 lua-casbin 实现高效复杂的授权模式。
+In the use of Apache APISIX, there is an implicit tension between route matching and request authorization: for higher granularity access control, higher granularity routes need to be configured to accurately identify requests and authorize them. In complex authorization model scenarios, this leads to an exponential increase in the number of routes, which increases the complexity of operations and maintenance.
+[authz-casbin](https://github.com/apache/apisix/blob/d9b928321fcdd12eef024df8c7c410424c1e0c8b/docs/en/latest/plugins/authz-casbin. md) is a lua-casbin based Apache APISIX plugin that supports powerful authorization based on various access models. casbin is a powerful and efficient open source access control framework that supports ACL, RBAC, ABAC and other access control models. lua-casbin is a Lua version implementation of the Casbin access control framework.

Review comment:
       ```suggestion
   [authz-casbin](https://github.com/apache/apisix/blob/d9b928321fcdd12eef024df8c7c410424c1e0c8b/docs/en/latest/plugins/authz-casbin.md) is a lua-casbin based Apache APISIX plugin that supports powerful authorization based on various access models. casbin is a powerful and efficient open source access control framework that supports ACL, RBAC, ABAC and other access control models. lua-casbin is a Lua version implementation of the Casbin access control framework.
   ```

##########
File path: website/blog/2021/08/30/weekly-report.md
##########
@@ -1,89 +1,89 @@
 ---
-title: "Apache APISIX 社区周报 | 2021 8.23-8.29"
+title: Apache APISIX Community Weekly Report | 2021 8.23-8.29
 keywords:
 - APISIX
-- 社区周报
-- 贡献者
+- Community Weekly
+- Contributor
 - Good first issue
-description: “独行者速,众行者远”。Apache APISIX 社区周报希望可以帮助社区小伙伴们更好地掌握 Apache APISIX 社区的每周进展,方便大家参与到 Apache APISIX 社区中来。
+description: The Apache APISIX Community Weekly Newsletter hopes to help community members better understand the weekly progress of the Apache APISIX community and facilitate your participation in the Apache APISIX community.
 tags: [Events]
 ---
 
 <!--truncate-->
 
-## 导语
+## Introduction
 
-Apache APISIX 从开源第一天就以社区方式成长,迅速成为全世界最活跃的开源 API 网关项目。这些成就,离不开社区小伙伴们的共同奋斗。
+Apache APISIX has grown as a community from the first day of open source and has quickly become the most active open source API gateway project in the world. These achievements cannot be achieved without the joint efforts of our community partners.
 
-“独行者速,众行者远”。Apache APISIX 社区周报希望可以帮助社区小伙伴们更好地掌握 Apache APISIX 社区的每周进展,方便大家参与到 Apache APISIX 社区中来。
+"The Apache APISIX Community Weekly Newsletter hopes to help community members better grasp the weekly progress of the Apache APISIX community and facilitate your participation in the Apache APISIX community.
 
-我们还整理了一些适合新来社区的小伙伴们参加的 issue !感兴趣的同学们,走过路过不要错过!
+We've also put together some issues for those new to the community! If you are interested, don't miss them!
 
-## 贡献者统计
+## Contributor statistics
 
-![新增贡献者数量](https://static.apiseven.com/202108/1630393952402-4965d35c-6b05-4f71-9966-2fea7f7939d3.JPG)
+![Number of new contributors](https://static.apiseven.com/202108/1630393952402-4965d35c-6b05-4f71-9966-2fea7f7939d3.JPG)
 
-![本周新晋贡献者](https://static.apiseven.com/202108/1630393952406-9f61c39b-ea9e-4451-bd26-ab845a32a222.JPG)
+![New contributors this week](https://static.apiseven.com/202108/1630393952406-9f61c39b-ea9e-4451-bd26-ab845a32a222.JPG)
 
 ## Good first issue
 
 ### Issue #4241
 
-**链接**:https://github.com/apache/apisix/issues/4241
+**Link**: https://github.com/apache/apisix/issues/4241
 
-**问题描述**:现在在将 jwt-auth 插件添加到一个 service/route 时,jwt 令牌未包含“key”声明。
+**Problem Description**: Now when adding the jwt-auth plugin to a service/route, the jwt token does not contain a "key" declaration.
 
 ```shell
 {
-  "iss":"http://127.0.0.1",
-  "client_id":"application1",
+  "iss": "http://127.0.0.1",
+  "client_id": "application1",

Review comment:
       ```suggestion
     "client_id":"application1",
   ```




-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org