chore(en): modify emqx.io links

Signed-off-by: Swilder-M <[email protected]>

en/201911/introduction-to-the-commonly-used-mqtt-client-library.md

@@ -2,7 +2,7 @@
 
 MQTT is a lightweight [publish-subscribe](https://www.emqx.com/en/blog/mqtt-5-introduction-to-publish-subscribe-model) mode messaging protocol designed for IoT applications in low-bandwidth and unstable network environments. MQTT is based on the publish/subscribe paradigm and works on the TCP/IP protocol family. [MQTT protocol](https://www.emqx.com/en/mqtt-guide) is lightweight, simple, open and easy to implement， which makes it suitable for a wide range of applications.
 
-MQTT is based on the client-server communication mode. MQTT server is called as MQTT Broker. Currently, there are many MQTT Brokers in the industry, whose advantages and disadvantages and functional differences will not be discussed in this article. Taking the [most popular MQTT broker - EMQX](https://www.emqx.io/) in the open source community as an example, this article uses the public Broker `broker.emqx.io` provided by  [EMQ](https://www.emqx.com/en) , and uses a simple example of connecting Broker, publishing and processing messages by client to summarizes the usage and examples of [MQTT client libraries](https://www.emqx.com/en/mqtt-client-sdk) under different programming languages and platforms.
+MQTT is based on the client-server communication mode. MQTT server is called as MQTT Broker. Currently, there are many MQTT Brokers in the industry, whose advantages and disadvantages and functional differences will not be discussed in this article. Taking the [most popular MQTT broker - EMQX](https://github.com/emqx/emqx) in the open source community as an example, this article uses the public Broker `broker.emqx.io` provided by  [EMQ](https://www.emqx.com/en) , and uses a simple example of connecting Broker, publishing and processing messages by client to summarizes the usage and examples of [MQTT client libraries](https://www.emqx.com/en/mqtt-client-sdk) under different programming languages and platforms.
 
 The selected MQTT client libraries are as follows:
 

en/202107/application-of-mqtt-protocol-in-oil-and-gas-industry.md

@@ -71,7 +71,7 @@ MQTT protocol has the characteristics of lightweight and high reliable QoS. It c
 
 ### Reduce the cost of hardware and software
 
-The lightweight design of MQTT greatly reduces the hardware requirements from the client to the server. In the EMQ cloud-side data collection solution, the highly available [MQTT broker - EMQX](https://www.emqx.io) in the central computer room of the plant and the lightweight edge industrial gateway Neuron used in production and business replace the expensive SCADA system and data collection and storage server on the field-station side, which reduces the overall hardware and software costs by more than 50%.
+The lightweight design of MQTT greatly reduces the hardware requirements from the client to the server. In the EMQ cloud-side data collection solution, the highly available [MQTT broker - EMQX](https://github.com/emqx/emqx) in the central computer room of the plant and the lightweight edge industrial gateway Neuron used in production and business replace the expensive SCADA system and data collection and storage server on the field-station side, which reduces the overall hardware and software costs by more than 50%.
 
 ### Save labor cost
 

en/202107/introducing-emqx-cloud-on-microsoft-azure.md

@@ -1,6 +1,6 @@
 EMQ, the leader of open-source and cloud-native distributed MQTT broker for IoT, is pleased to announce that EMQX Cloud is now available on Microsoft Azure.
 
-[EMQX Cloud](https://www.emqx.com/en/cloud) is a fully managed MQTT service built on the worldwide used [open-source MQTT broker - EMQX](https://www.emqx.io), which has more than 10 million downloads and hundreds of thousands of deployments around the globe.
+[EMQX Cloud](https://www.emqx.com/en/cloud) is a fully managed MQTT service built on the worldwide used [open-source MQTT broker - EMQX](https://github.com/emqx/emqx), which has more than 10 million downloads and hundreds of thousands of deployments around the globe.
 
 EMQX Cloud helps our users carry out their IoT projects with [MQTT](https://www.emqx.com/en/mqtt-guide) in a simple way, without the burden of deploying and managing the self-managed MQTT service in multiple regions of the cloud.
 

en/202108/how-to-use-mqtt-in-php.md

@@ -1,6 +1,6 @@
 [PHP](https://www.php.net) is a widely-used open source multi-purpose scripting language, which can be embedded in HTML and is especially suitable for Web development.
 
-This article mainly introduces how to use the `php-mqtt/client` client library in PHP projects to implement the functions of connection, subscription, unsubscribing, message receiving and sending between [MQTT client](https://www.emqx.com/en/blog/mqtt-client-tools) and [MQTT broker](https://www.emqx.io).
+This article mainly introduces how to use the `php-mqtt/client` client library in PHP projects to implement the functions of connection, subscription, unsubscribing, message receiving and sending between [MQTT client](https://www.emqx.com/en/blog/mqtt-client-tools) and [MQTT broker](https://github.com/emqx/emqx).
 
 
 

en/202108/mqtt-broker-clustering-part-1-load-balancing.md

@@ -11,7 +11,7 @@ Here is the quote from [https://mqtt.org/](https://mqtt.org/)
 
 [MQTT clients](https://www.emqx.com/en/blog/introduction-to-the-commonly-used-mqtt-client-library) are also similar to HTTP clients: they establish TCP connections to a server and send and receive data. The difference is that HTTP uses a request/response model, while MQTT uses a publish/subscribe model.
 
-A real life example: a temperature sensor in the living room periodically publishes its readings to an [MQTT broker](https://www.emqx.io), a smart-home application may subscribe to the temperature readings and make smart-home decisions for you. For example: turn on the AC when it’s above 32 celsius degrees.
+A real life example: a temperature sensor in the living room periodically publishes its readings to an MQTT broker, a smart-home application may subscribe to the temperature readings and make smart-home decisions for you. For example: turn on the AC when it’s above 32 celsius degrees.
 
 
 

en/202110/mqtt-broker-clustering-part-3-challenges-and-solutions-of-emqx-horizontal-scalability.md

@@ -1,6 +1,6 @@
 In this blog post, we will introduce some of the improvements of the MQTT broker cluster scalability. We will mostly focus on the database engine that EMQX uses internally and how we improved it in EMQX 5.0.  
 
-Before we start, you should know how data is replicated in the EMQX cluster: [EMQX Broker](https://www.emqx.io) stores the runtime information about the topics and clients in [Mnesia](http://erlang.org/doc/man/mnesia.html) database, which helps replicate this data across the cluster.
+Before we start, you should know how data is replicated in the EMQX cluster: [EMQX Broker](https://github.com/emqx/emqx) stores the runtime information about the topics and clients in [Mnesia](http://erlang.org/doc/man/mnesia.html) database, which helps replicate this data across the cluster.
 
 
 ## What is Mnesia?

en/202111/emqx-newsletter-202110.md

@@ -1,4 +1,4 @@
-Besides making EMQX stronger and faster as an [MQTT messaging broker](https://www.emqx.io), we also try hard to make it ops-friendly. From configuration to management API, dashboard UI to live code upgrade, single node docker run to massive scale clustering.
+Besides making EMQX stronger and faster as an [MQTT messaging broker](https://www.emqx.com/en/products/emqx), we also try hard to make it ops-friendly. From configuration to management API, dashboard UI to live code upgrade, single node docker run to massive scale clustering.
 
 In October, EMQX development teams have been mostly focusing on HTTP management API, the readiness of which will be checkpoint for the beta.2 release.
 

en/202111/ios-mqtt5-client.md

@@ -175,7 +175,7 @@ If you use the APIs related to `beginBackgroundTaskWithName` and `endBackgroundT
 
 ## Summary
 
-So far, we have connected the CocoaMQTT client to the public MQTT Broker and realized the connection, message publishing, and subscription between the client and the [MQTT Broker](https://www.emqx.io).
+So far, we have connected the CocoaMQTT client to the public MQTT Broker and realized the connection, message publishing, and subscription between the client and the MQTT broker.
 
 > Get the code from [https://github.com/emqx/CocoaMQTT/tree/master/Example](https://github.com/emqx/CocoaMQTT/tree/master/Example). 
 

en/202111/popular-online-public-mqtt-brokers.md

@@ -19,7 +19,7 @@ This article selects the following commonly used public MQTT brokers:
 
 ### EMQX
 
-It is a free online [MQTT 5 broker](https://www.emqx.io/) provided by [EMQX Cloud](https://www.emqx.com/en/cloud). There are two access points provided, Global and CN, of which EMQX (Global) is deployed in AWS, Oregon, USA, and EMQX (CN) is deployed in Tencent Cloud, Shanghai.
+It is a free online [MQTT 5 broker](https://www.emqx.com/en/products/emqx) provided by [EMQX Cloud](https://www.emqx.com/en/cloud). There are two access points provided, Global and CN, of which EMQX (Global) is deployed in AWS, Oregon, USA, and EMQX (CN) is deployed in Tencent Cloud, Shanghai.
 
 Both access points are EMQX clusters composed of 2 nodes. Later, more nodes can be automatically added according to the actual access volume and load. According to the background display, the server is based on [EMQX Enterprise](https://www.emqx.com/en/products/emqx) 4.2.6, and the current running time is 128 days.
 

en/202112/emqx-newsletter-202111.md

@@ -88,7 +88,7 @@ The condition of a large number of offline devices may be caused by some externa
 
 Forwarding data to non-relational databases is supported by EMQX Cloud. At present, the resource configuration of the rule engine has added support for Alibaba Cloud MongoDB. The rule engine can be used to persist data to MongoDB of Alibaba Cloud. It provides more choices for business developers to achieve data persistence, which makes business landing more easily.
 
-EMQX team is always committed to bringing a better [MQTT broker](https://www.emqx.io) for the IoT era. Please stay tuned on EMQX.
+EMQX team is always committed to bringing a better MQTT broker for the IoT era. Please stay tuned on EMQX.
 
 
 <section class="promotion">

en/202201/introduction-to-the-open-source-testing-tool-jmeter.md

@@ -4,7 +4,7 @@ The IoT industry is developing explosively. As the scale of endpoints continues
 
 On the one hand, performance test provides a basis for evaluating IoT systems, which can be verified from multiple dimensions of design indicators, scalability and reliability. On the other hand, performance test also helps to optimize IoT systems and find system performance bottlenecks as soon as possible, so as to provide optimization suggestions. In addition, performance test can also assist the formulation of capacity plans and provide a reference for future capacity expansion plan.
 
-The IoT system has the features of large amount of access devices, diverse protocols, complex integration architecture, and frequent cross-departmental development collaboration, which also makes the IoT performance test face many challenges. **This series of articles will take the IoT platform based on [EMQX](https://www.emqx.io) as an example to introduce how to use performance test tools to verify and test platform-related quality indicators.**
+The IoT system has the features of large amount of access devices, diverse protocols, complex integration architecture, and frequent cross-departmental development collaboration, which also makes the IoT performance test face many challenges. **This series of articles will take the IoT platform based on [EMQX](https://www.emqx.com/en/products/emqx) as an example to introduce how to use performance test tools to verify and test platform-related quality indicators.**
 
 ## Selection of the test tool -- Introduction to JMeter
 

en/202201/mqtt-for-elixir.md

@@ -22,7 +22,7 @@ We will demonstrate some of MQTT's advantages in our setup.
 
 An essential thing about MQTT is that it simplifies the client's logic, which is critical for embedded devices. This is achieved with the pubsub model: in MQTT, there is no concept of a "server". Instead, all participating entities are clients connecting to a so-called *broker*. Clients *subscribe* to *topics*, *publish* messages to them, and the broker does the routing (and many other things).
 
-A good production-ready broker, like [EMQX](https://www.emqx.io) generally provides not only MQTT routing capabilities but many other interesting features, like
+A good production-ready broker, like [EMQX](https://www.emqx.com/en/products/emqx) generally provides not only MQTT routing capabilities but many other interesting features, like
 
 - other kinds of connection methods, like WebSockets;
 - different models of authentication and authorization;

en/202201/mqttx-v-1-7-0-release-notes.md

@@ -19,7 +19,7 @@ In 1.7.0, MQTTX adds a lot of support for the property configuration of MQTT 5.0
 
 To use and test the features of MQTT 5.0, MQTTX v1.7.0 needs to be used with MQTT Broker that supports MQTT 5.0.
 
-Cloud-native distributed [MQTT broker - EMQX](https://www.emqx.io) supports the MQTT 5.0 protocol since version 3.0. It is the first broker in the open-source community to support this protocol specification and is fully compatible with MQTT 3.1 and 3.1.1 protocols. Connecting to EMQX by Using MQTTX, you can quickly use and test the features of MQTT 5.0.
+Cloud-native distributed [MQTT broker - EMQX](https://github.com/emqx/emqx) supports the MQTT 5.0 protocol since version 3.0. It is the first broker in the open-source community to support this protocol specification and is fully compatible with MQTT 3.1 and 3.1.1 protocols. Connecting to EMQX by Using MQTTX, you can quickly use and test the features of MQTT 5.0.
 
 ### Support MQTT 5.0 User Properties
 

en/202201/mqttx-v-1-7-2-release-notes.md

@@ -53,6 +53,6 @@ Next, we will focus on the following aspects:
 
 ## Conclusion
 
-MQTTX is designed to connect to test MQTT Brokers such as [EMQX](https://www.emqx.io). The one-click connection and a clean graphical interface make it easy to explore and debug MQTT features. MQTTX provides comprehensive testing capabilities for MQTT features. Fully open-source and community-driven makes it integrated with more rich, powerful, user-friendly features. With MQTTX and EMQX - the cloud-native distributed messaging broker, we believe that the test and development of IoT platforms will become easier.
+MQTTX is designed to connect to test MQTT Brokers such as [EMQX](https://github.com/emqx/emqx). The one-click connection and a clean graphical interface make it easy to explore and debug MQTT features. MQTTX provides comprehensive testing capabilities for MQTT features. Fully open-source and community-driven makes it integrated with more rich, powerful, user-friendly features. With MQTTX and EMQX - the cloud-native distributed messaging broker, we believe that the test and development of IoT platforms will become easier.
 
 The MQTTX project is completely open-source. You can go to [Github](https://github.com/emqx/MQTTX/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc) to submit the problems encountered during use, or fork the MQTTX project to submit a revised PR to us. We will review and deal with it in time. We would also like to thank all users in the community for their contributions and feedback. The use and affirmation of each community user is the driving force for the advancement of our products.

en/202202/advanced-testing-of-erlang-and-elixir-applications.md

@@ -1,4 +1,4 @@
-One of the defining features of [EMQX](https://www.emqx.io) is its support of clustering: messages in the [MQTT topics](https://www.emqx.com/en/blog/advanced-features-of-mqtt-topics) are forwarded between the broker nodes transparently for the clients. We are developing a system that is fault-tolerant, has high throughput and low latency. Individual nodes can be shut down, restarted or even paused for a long period of time, but the cluster as a whole continues to serve traffic. 
+One of the defining features of [EMQX](https://www.emqx.com/en/products/emqx) is its support of clustering: messages in the [MQTT topics](https://www.emqx.com/en/blog/advanced-features-of-mqtt-topics) are forwarded between the broker nodes transparently for the clients. We are developing a system that is fault-tolerant, has high throughput and low latency. Individual nodes can be shut down, restarted or even paused for a long period of time, but the cluster as a whole continues to serve traffic. 
 
 In order to sync and replicate metadata throughout the cluster more efficiently, we've developed Mria: a lightweight eventually-consistent database management system. These features help us create a low-latency, horizontally scalable system, but they also significantly raise the requirements for testing. Development of distributed systems is a notoriously hard problem: some of the most basic assumptions about how the code is executed are not applicable when any part of the system can suddenly die or stutter, when network connections between the nodes may disappear, and the clocks on the different nodes may not be in sync. 
 

en/202202/building-emqx-releases-with-elixirs-mix.md

@@ -1,6 +1,6 @@
 We are happy to announce that now [EMQX](https://github.com/emqx/emqx/) can be built using Elixir!
 
-What does that mean?  EMQX is the most popular open source [MQTT broker](https://www.emqx.io), written in Erlang, which makes it highly scalable and with high-performance real-time message processing.  The Erlang EMQX releases will remain as always, and added to that there will be some packages that are built using Elixir's Mix build tool.  These work just as the Erlang ones, with the difference that the shell you have available when using EMQX's console is [IEx](https://hexdocs.pm/iex/1.13/IEx.html).
+What does that mean?  EMQX is the most popular open source MQTT broker, written in Erlang, which makes it highly scalable and with high-performance real-time message processing.  The Erlang EMQX releases will remain as always, and added to that there will be some packages that are built using Elixir's Mix build tool.  These work just as the Erlang ones, with the difference that the shell you have available when using EMQX's console is [IEx](https://hexdocs.pm/iex/1.13/IEx.html).
 
 Here are a few benefits of building with Elixir:
 

en/202202/emq-is-now-the-foundational-member-of-oasis.md

@@ -6,7 +6,7 @@ OASIS Open is one of the most respected, nonprofit international open source and
 
 ## Pioneering Participant in MQTT and the IoT Messaging
 
-EMQ has been working on [EMQX](https://www.emqx.io/), the open source distributed MQTT broker which is fully compatible with MQTT 3.1 and 3.1.1 specifications since 2013. Then when MQTT became an OASIS open standard in 2016, we actively engaged in the development and discussion of the MQTT 5.0 specification. It’s EMQX that innovatively introduced the [shared subscription](https://www.emqx.com/en/blog/introduction-to-mqtt5-protocol-shared-subscription) features back when the specification was still in draft form.
+EMQ has been working on [EMQX](https://github.com/emqx/emqx), the open source distributed MQTT broker which is fully compatible with MQTT 3.1 and 3.1.1 specifications since 2013. Then when MQTT became an OASIS open standard in 2016, we actively engaged in the development and discussion of the MQTT 5.0 specification. It’s EMQX that innovatively introduced the [shared subscription](https://www.emqx.com/en/blog/introduction-to-mqtt5-protocol-shared-subscription) features back when the specification was still in draft form.
 
 One of the most game-changing releases so far came in 2020 when EMQ introduced EMQX 4.0, the world's first cloud-native MQTT 5.0 Server with the full latest specification support. Now EMQX has become the world's most popular cloud-native distributed MQTT broker with a high-performance real-time message processing engine, connecting more than 100 million IoT devices worldwide for IoT data movement, processing and analytics.
 

en/202203/emqx-v-4-4-new-feature-a-top-view-of-slowest-subscribers.md

@@ -1,6 +1,6 @@
 ## Background
 
-As a [MQTT broker](https://www.emqx.io) admin, you may often want to know which clients are the slowest. We have a nice ‘top’ view for you. One option is perhaps to instrument the subscriber code with latency measurements. However given in MQTT world, the subscribers might be devices out in the wild which are hard to upgrade or collect metrics from.
+As a MQTT broker admin, you may often want to know which clients are the slowest. We have a nice ‘top’ view for you. One option is perhaps to instrument the subscriber code with latency measurements. However given in MQTT world, the subscribers might be devices out in the wild which are hard to upgrade or collect metrics from.
 
 EMQX v4.4 has a nice feature to overcome this challenge.