SylviaBABY commented on code in PR #1169: URL: https://github.com/apache/apisix-website/pull/1169#discussion_r909271624
########## website/blog/2021/06/28/why-we-need-Apache-APISIX.md: ########## @@ -155,24 +156,24 @@ The diagram on the right shows the internal architecture of APISIX Mesh. After talking so much about the present of APISIX, let's also talk about the future of APISIX. -Because APISIX is currently an Apache Foundation project, it is no longer the property of individuals or companies, but of all humanity. This gives every one of you in the community the right to decide which direction it will go. +Because APISIX is an Apache Foundation project, it is no longer the property of individuals or companies but all humanity. This gives everyone in the community the right to decide which direction it will go. -The default configuration center for the open source version of APISIX is etcd, and while it is still the best choice, we still often hear about support for other configuration centers when we talk to users, more often than not because etcd is so new that it is not on the list of supported products in the company's existing operations and maintenance products. So we plan to make APISIX work with other configuration centers. +The default configuration center for the open-source version of APISIX is etcd. While it is still the best choice, we often hear about support for other configuration centers when talking to users because etcd is so new that it is not on the list of supported products in the company's existing operations and maintenance products. So we plan to make APISIX work with other configuration centers.  -APISIX is already on the road to full traffic data plane, and I believe we all ask questions such as: Why do we need to unify traffic forwarding? Does unification bring value to the enterprise? What are the benefits to the technical staff? With these questions in mind, let's look at the following diagram. +APISIX is already on the road to the full traffic data plane, and I believe we all ask questions such as: Why do we need to unify traffic forwarding? Does unification bring value to the enterprise? What are the benefits to the technical staff? With these questions in mind, let's look at the following diagram.  -Unification itself is not the goal, but the benefits after unification is the logic behind our pursuit, and several different perspectives are given below to elaborate separately. +Unification itself is not the goal, but the benefits after unification are the logic behind our pursuit, and several different perspectives are given below to elaborate separately. - Operation and maintenance role: use the same operation and maintenance tools to collect logs, metrics, etc., and reuse existing accumulations. -- Development role: based on standardized APISIX plug-in development, the capabilities can be easily reused, and the accumulated experience can be applied to different product lines such as LB, API Gateway, K8s Ingress, etc. +- Development role: based on standardized APISIX plugin development, the capabilities can be easily reused, and the accumulated experience can be applied to different product lines such as LB, API Gateway, K8s Ingress, etc. - Company value: Unify technology stack, reduce company operation cost, reduce the difficulty of transitioning to microservices and cloud-native, and accelerate enterprise digital transformation. -Last but not least is the APISIX [Slack channel](https://apisix.apache.org/docs/general/join#join-the-slack-channel), any questions can be left here or on [Github issue](https://github.com/apache/apisix/issues), there will be someone to respond quickly, thanks again. +Last but not least is the APISIX [Slack channel](https://apisix.apache.org/docs/general/join#join-the-slack-channel), any questions can be left here, or on [Github issue](https://github.com/apache/apisix/issues), there will be someone to respond quickly, thanks again. -Click to watch the [video](https://www.bilibili.com/video/BV1w54y1V73Z?p=1&share_medium=android&share_plat=android&share_source=COPY&share_tag=s_i×tamp=1621812452&unique_k=PEusrt) +Click [here](https://www.bilibili.com/video/BV1w54y1V73Z) to watch the [recordig video](https://www.bilibili.com/video/BV1w54y1V73Z). Review Comment: ```suggestion Click [here](https://www.bilibili.com/video/BV1w54y1V73Z) to watch the recording video. ``` -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
