chore: rename EMQX Broker to just EMQX

README-CN.md

@@ -1,4 +1,4 @@
-# EMQX Broker
+# EMQX
 
 [![GitHub Release](https://img.shields.io/github/release/emqx/emqx?color=brightgreen&label=Release)](https://github.com/emqx/emqx/releases)
 [![Build Status](https://img.shields.io/travis/emqx/emqx?label=Build)](https://travis-ci.org/emqx/emqx)

README-JP.md

@@ -1,4 +1,4 @@
-# EMQX Broker
+# EMQX
 
 [![GitHub Release](https://img.shields.io/github/release/emqx/emqx?color=brightgreen&label=Release)](https://github.com/emqx/emqx/releases)
 [![Build Status](https://img.shields.io/travis/emqx/emqx?label=Build)](https://travis-ci.org/emqx/emqx)

README.md

@@ -1,4 +1,4 @@
-# EMQX Broker
+# EMQX
 
 [![GitHub Release](https://img.shields.io/github/release/emqx/emqx?color=brightgreen&label=Release)](https://github.com/emqx/emqx/releases)
 [![Build Status](https://img.shields.io/travis/emqx/emqx?label=Build)](https://travis-ci.org/emqx/emqx)

apps/emqx_dashboard/README.md

@@ -2,7 +2,7 @@
 emqx-dashboard
 ==============
 
-Dashboard for the EMQX Broker.
+EMQX Dashboard
 
 REST API
 --------

apps/emqx_exhook/docs/design-cn.md

@@ -2,7 +2,7 @@
 
 ## 动机
 
-在 EMQX Broker v4.1-v4.2 中，我们发布了 2 个插件来扩展 emqx 的编程能力：
+在 EMQX v4.1-v4.2 中，我们发布了 2 个插件来扩展 emqx 的编程能力：
 
 1. `emqx-extension-hook` 提供了使用 Java, Python 向 Broker 挂载钩子的功能
 2. `emqx-exproto` 提供了使用 Java，Python 编写用户自定义协议接入插件的功能

apps/emqx_gateway/README.md

@@ -1,6 +1,6 @@
 # emqx_gateway
 
-***This is a very early prototype application*** for Gateway in EMQX Broker 5.0
+EMQX Gateway
 
 ## Concept
 

apps/emqx_gateway/src/coap/README.md

@@ -17,7 +17,7 @@
 
 # EMQX 5.0 CoAP Gateway
 
-emqx-coap is a CoAP Gateway for EMQX Broker. It translates CoAP messages into MQTT messages and make it possible to communiate between CoAP clients and MQTT clients.
+emqx-coap is a CoAP Gateway for EMQX. It translates CoAP messages into MQTT messages and make it possible to communiate between CoAP clients and MQTT clients.
 
 
 <a id="orgeddbc94"></a>

apps/emqx_gateway/src/emqx_gateway_api_clients.erl

@@ -739,7 +739,7 @@ common_client_props() ->
                        "packet">>})}
     , {recv_oct,
        mk(integer(),
-          #{ desc => <<"Number of bytes received by EMQX Broker">>})}
+          #{ desc => <<"Number of bytes received">>})}
     , {recv_cnt,
        mk(integer(),
           #{ desc => <<"Number of socket packets received">>})}

apps/emqx_gateway/src/exproto/README.md

@@ -1,6 +1,6 @@
 # emqx-exproto
 
-The `emqx_exproto` extremely enhance the extensibility for EMQX. It allow using an others programming language to **replace the protocol handling layer in EMQX Broker**.
+The `emqx_exproto` extremely enhance the extensibility for EMQX. It allow using an others programming language to **replace the protocol handling layer in EMQX**.
 
 ## Feature
 

apps/emqx_gateway/src/lwm2m/README.md

@@ -1,5 +1,5 @@
 
-# LwM2M Gateway for the EMQX Broker.
+# LwM2M Gateway
 
 [The LwM2M Specifications](http://www.openmobilealliance.org/release/LightweightM2M) is a Lightweight Machine to Machine protocol.
 

apps/emqx_management/src/emqx_mgmt_api_clients.erl

@@ -323,8 +323,7 @@ fields(client) ->
             <<"Number of PUBLISH QoS1 packets received">>})},
         {'recv_msg.qos2', hoconsc:mk(integer(), #{desc =>
             <<"Number of PUBLISH QoS2 packets received">>})},
-        {recv_oct, hoconsc:mk(integer(), #{desc =>
+        {recv_oct, hoconsc:mk(integer(), #{desc => <<"Number of bytes received">>})},
-            <<"Number of bytes received by EMQX Broker (the same below)">>})},
         {recv_pkt, hoconsc:mk(integer(), #{desc => <<"Number of MQTT packets received">>})},
         {reductions, hoconsc:mk(integer(), #{desc => <<"Erlang reduction">>})},
         {send_cnt, hoconsc:mk(integer(), #{desc => <<"Number of TCP packets sent">>})},

apps/emqx_management/src/emqx_mgmt_api_metrics.erl

@@ -48,8 +48,8 @@ properties() ->
     [
         {'actions.failure',                 integer, <<"Number of failure executions of the rule engine action">>},
         {'actions.success',                 integer, <<"Number of successful executions of the rule engine action">>},
-        {'bytes.received',                  integer, <<"Number of bytes received by EMQX Broker">>},
+        {'bytes.received',                  integer, <<"Number of bytes received ">>},
-        {'bytes.sent',                      integer, <<"Number of bytes sent by EMQX Broker on this connection">>},
+        {'bytes.sent',                      integer, <<"Number of bytes sent on this connection">>},
         {'client.auth.anonymous',           integer, <<"Number of clients who log in anonymously">>},
         {'client.authenticate',             integer, <<"Number of client authentications">>},
         {'client.check_authz',              integer, <<"Number of Authorization rule checks">>},
@@ -66,9 +66,9 @@ properties() ->
         {'delivery.dropped.queue_full',     integer, <<"Number of messages with a non-zero QoS that were dropped because the message queue was full when sending">>},
         {'delivery.dropped.too_large',      integer, <<"The number of messages that were dropped because the length exceeded the limit when sending">>},
         {'messages.acked',                  integer, <<"Number of received PUBACK and PUBREC packet">>},
-        {'messages.delayed',                integer, <<"Number of delay- published messages stored by EMQX Broker">>},
+        {'messages.delayed',                integer, <<"Number of delay-published messages">>},
-        {'messages.delivered',              integer, <<"Number of messages forwarded to the subscription process internally by EMQX Broker">>},
+        {'messages.delivered',              integer, <<"Number of messages forwarded to the subscription process internally">>},
-        {'messages.dropped',                integer, <<"Total number of messages dropped by EMQX Broker before forwarding to the subscription process">>},
+        {'messages.dropped',                integer, <<"Total number of messages dropped before forwarding to the subscription process">>},
         {'messages.dropped.await_pubrel_timeout', integer, <<"Number of messages dropped due to waiting PUBREL timeout">>},
         {'messages.dropped.no_subscribers', integer, <<"Number of messages dropped due to no subscribers">>},
         {'messages.forward',                integer, <<"Number of messages forwarded to other nodes">>},
@@ -80,7 +80,7 @@ properties() ->
         {'messages.qos2.received',          integer, <<"Number of QoS 2 messages received from clients">>},
         {'messages.qos2.sent',              integer, <<"Number of QoS 2 messages sent to clients">>},
         {'messages.received',               integer, <<"Number of messages received from the client, equal to the sum of messages.qos0.received\fmessages.qos1.received and messages.qos2.received">>},
-        {'messages.retained',               integer, <<"Number of retained messages stored by EMQX Broker">>},
+        {'messages.retained',               integer, <<"Number of retained messages">>},
         {'messages.sent',                   integer, <<"Number of messages sent to the client, equal to the sum of messages.qos0.sent\fmessages.qos1.sent and messages.qos2.sent">>},
         {'packets.auth.received',           integer, <<"Number of received AUTH packet">>},
         {'packets.auth.sent',               integer, <<"Number of sent AUTH packet">>},

apps/emqx_rule_engine/README.md

@@ -1,7 +1,7 @@
 
 # emqx-rule-engine
 
-IoT Rule Engine for EMQX Broker.
+IoT Rule Engine
 
 ## Concept