You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@apisix.apache.org by yi...@apache.org on 2022/03/31 08:00:46 UTC

[apisix-website] branch master updated: docs: fix typos in OpenTelemetry blog (#994)

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

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


The following commit(s) were added to refs/heads/master by this push:
     new 974b652  docs: fix typos in OpenTelemetry blog (#994)
974b652 is described below

commit 974b652a27148c35920ebf2a112d66ea7c2ebe1f
Author: yilinzeng <36...@users.noreply.github.com>
AuthorDate: Thu Mar 31 16:00:40 2022 +0800

    docs: fix typos in OpenTelemetry blog (#994)
---
 website/blog/2022/02/28/apisix-integration-opentelemetry-plugin.md  | 6 +++---
 .../2022/02/28/apisix-integration-opentelemetry-plugin.md           | 6 +++---
 2 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/website/blog/2022/02/28/apisix-integration-opentelemetry-plugin.md b/website/blog/2022/02/28/apisix-integration-opentelemetry-plugin.md
index d3f0911..b4d052d 100644
--- a/website/blog/2022/02/28/apisix-integration-opentelemetry-plugin.md
+++ b/website/blog/2022/02/28/apisix-integration-opentelemetry-plugin.md
@@ -186,7 +186,7 @@ The Apache APISIX service is introduced, and the topology of the final applicati
 
 ![error/Architecture diagram.png](https://static.apiseven.com/202108/1646040225319-819f10ab-9643-4bd7-8f99-07f9a6c84bf8.png)
 
-The Trace data reporting process is as follows. Among them, since Apache APISIX is deployed separately and not in the network of docker-compose, Apache APISIX accesses the OTLP HTTP Receiver of OpenTelemetery Collector through the locally mapped port (`127.0.0.1:4138`).
+The Trace data reporting process is as follows. Among them, since Apache APISIX is deployed separately and not in the network of docker-compose, Apache APISIX accesses the OTLP HTTP Receiver of OpenTelemetry Collector through the locally mapped port (`127.0.0.1:4138`).
 
 ![error/Trace data reporting process.png](https://static.apiseven.com/202108/1646040470172-4d44c6ca-b890-4245-9c87-3a42d8b59f47.png)
 
@@ -300,7 +300,7 @@ services:
 
 It should be noted that demo-client.environment.DEMO_SERVER_ENDPOINT needs to be changed to your Apache APISIX address, and ensure that it can be accessed normally in the container.
 
-Of course, you can also deploy Apache APISIX through docekr-compose.yaml. For details, please refer to the [Apache APISIX official documentation](https://github.com/apache/apisix-docker/blob/master/docs/en/latest/example.md).
+Of course, you can also deploy Apache APISIX through `docker-compose.yaml`. For details, please refer to the [Apache APISIX official documentation](https://github.com/apache/apisix-docker/blob/master/docs/en/latest/example.md).
 
 #### Step 3: Test
 
@@ -318,7 +318,7 @@ You can only remove the configuration of the `opentelemetry` global plugin if yo
 
 ## Summary
 
-After Apache APISIX integrates OpenTelemetery, it can easily connect with most mainstream Trace systems on the market with the help of OpenTelemetry's rich plug-ins. In addition, Apache APISIX has also implemented SkyWalking and Zipkin native standard protocol plug-ins, and is also actively cooperating with major communities to create a more powerful ecosystem.
+After Apache APISIX integrates OpenTelemetry, it can easily connect with most mainstream Trace systems on the market with the help of OpenTelemetry's rich plug-ins. In addition, Apache APISIX has also implemented SkyWalking and Zipkin native standard protocol plug-ins, and is also actively cooperating with major communities to create a more powerful ecosystem.
 
 Apache APISIX is also currently working on additional plugins to support integration with more services, so if you're interested, feel free to start a discussion thread in our GitHub Discussion or communicate via the mailing list.
 
diff --git a/website/i18n/zh/docusaurus-plugin-content-blog/2022/02/28/apisix-integration-opentelemetry-plugin.md b/website/i18n/zh/docusaurus-plugin-content-blog/2022/02/28/apisix-integration-opentelemetry-plugin.md
index 80b3f80..36ea269 100644
--- a/website/i18n/zh/docusaurus-plugin-content-blog/2022/02/28/apisix-integration-opentelemetry-plugin.md
+++ b/website/i18n/zh/docusaurus-plugin-content-blog/2022/02/28/apisix-integration-opentelemetry-plugin.md
@@ -186,7 +186,7 @@ docker-compose up -d
 
 ![error/Architecture diagram.png](https://static.apiseven.com/202108/1646040225319-819f10ab-9643-4bd7-8f99-07f9a6c84bf8.png)
 
-Trace 数据上报流程如下。其中由于 Apache APISIX 是单独部署的,并不在 `docker-compose` 的网络内,所以 Apache APISIX 是通过本地映射的端口(即 `127.0.0.1:4138`)访问到 OpenTelemetery Collector 的 OTLP HTTP Receiver 的。
+Trace 数据上报流程如下。其中由于 Apache APISIX 是单独部署的,并不在 `docker-compose` 的网络内,所以 Apache APISIX 是通过本地映射的端口(即 `127.0.0.1:4138`)访问到 OpenTelemetry Collector 的 OTLP HTTP Receiver 的。
 
 ![error/Trace data reporting process.png](https://static.apiseven.com/202108/1646040470172-4d44c6ca-b890-4245-9c87-3a42d8b59f47.png)
 
@@ -300,7 +300,7 @@ services:
 
 需要注意,`demo-client.environment.DEMO_SERVER_ENDPOINT` 处需要改为您的 Apache APISIX 地址,且保证在容器内可以正常访问。
 
-当然,您也可以通过 `docekr-compose.yaml` 部署 Apache APISIX ,具体可以参考 [Apache APISIX 官方文档](https://github.com/apache/apisix-docker/blob/master/docs/en/latest/example.md)。
+当然,您也可以通过 `docker-compose.yaml` 部署 Apache APISIX ,具体可以参考 [Apache APISIX 官方文档](https://github.com/apache/apisix-docker/blob/master/docs/en/latest/example.md)。
 
 #### 步骤三:测试
 
@@ -318,7 +318,7 @@ services:
 
 ## 总结
 
-Apache APISIX 在集成 OpenTelemetery 之后,借助 OpenTelemetry 丰富的插件能够与市场上大部分主流的 Trace 系统轻松实现对接。此外,Apache APISIX 也实现了 SkyWalking 和 Zipkin 原生标准协议插件,也在积极与各大社区合作打造更加强大的生态。
+Apache APISIX 在集成 OpenTelemetry 之后,借助 OpenTelemetry 丰富的插件能够与市场上大部分主流的 Trace 系统轻松实现对接。此外,Apache APISIX 也实现了 SkyWalking 和 Zipkin 原生标准协议插件,也在积极与各大社区合作打造更加强大的生态。
 
 Apache APISIX 项目目前正在开发其他插件以支持集成更多服务,如果您对此有兴趣,您可以通过 [GitHub Discussions](https://github.com/apache/apisix/discussions) 发起讨论,或通过[邮件列表](https://apisix.apache.org/docs/general/join)进行交流.