fix(doc): edgex source doc fix (#1383)

Signed-off-by: Jiyong Huang <huangjy@emqx.io>

Signed-off-by: Jiyong Huang <huangjy@emqx.io>

docs/en_US/edgex/edgex_source_tutorial.md

@@ -91,12 +91,12 @@ device_conf: # Filter only Random-Integer-Device
   messageType: request
 another_app_service_conf:
   topic: new-rules-events
-int8_conf: # Filter only Random-Integer-Device int8 reading
-  topic: edgex/events/#/Random-Integer-Device/int8
+int8_conf: # Filter only Random-Integer-Device Int8 reading
+  topic: edgex/events/#/Random-Integer-Device/Int8
   messageType: request
 ```
 
-With this configuration, users have 3 confkey that would connect to different edgeX data flows. For example, if a user have two rules: rule1 need to process all events while rule2 only process the int8 reading of Random-Integer-Device. Then the user can create two streams: edgexAll and edgexInt8.
+With this configuration, users have 3 confkey that would connect to different edgeX data flows. For example, if a user have two rules: rule1 need to process all events while rule2 only process the Int8 reading of Random-Integer-Device. Then the user can create two streams: edgexAll and edgexInt8.
 
 ```sql
 CREATE STREAM edgexAll() WITH (FORMAT="JSON", TYPE="edgex")
@@ -108,7 +108,7 @@ With this definition, the default confkey will be used and the rules using this
 CREATE STREAM edgexInt8(int8 bigint) WITH (FORMAT="JSON", TYPE="edgex", CONF_KEY="int8_conf")
 ```
 
-Differently, the edgexInt8 specify the confkey explicitly to use `int8_conf` which configures to filtered topic for Random-Integer-Device device int8 reading. Thus, it will only receive int8 reading for every event and the event structure is fixed. So, the stream definition also define the schema instead of schemaless.
+Differently, the edgexInt8 specify the confkey explicitly to use `int8_conf` which configures to filtered topic for Random-Integer-Device device Int8 reading. Thus, it will only receive Int8 reading for every event and the event structure is fixed. So, the stream definition also define the schema instead of schemaless.
 
 Similarly, users can create streams for each confkey. And each rule can pick the streams depending on its interests.
 

docs/zh_CN/edgex/edgex_source_tutorial.md

@@ -91,12 +91,12 @@ device_conf: # 只过滤 Random-Integer-Device
   messageType: request
 another_app_service_conf:
   topic: new-rules-events
-int8_conf: # 只过滤 Random-Integer-Device int8 reading
-  topic: edgex/events/#/Random-Integer-Device/int8
+int8_conf: # 只过滤 Random-Integer-Device Int8 reading
+  topic: edgex/events/#/Random-Integer-Device/Int8
   messageType: request
 ```
 
-通过这种配置，用户有 3 个 confkey 可以连接到不同的 edgeX 数据流。 例如，如果用户有两个规则：rule1 需要处理所有事件，而 rule2 只处理 Random-Integer-Device 的 int8 读取。 然后用户可以创建两个流：edgexAll 和 edgexInt8。
+通过这种配置，用户有 3 个 confkey 可以连接到不同的 edgeX 数据流。 例如，如果用户有两个规则：rule1 需要处理所有事件，而 rule2 只处理 Random-Integer-Device 的 Int8 读取。 然后用户可以创建两个流：edgexAll 和 edgexInt8。
 
 ```sql
 CREATE STREAM edgexAll() WITH (FORMAT="JSON", TYPE="edgex")
@@ -108,7 +108,7 @@ CREATE STREAM edgexAll() WITH (FORMAT="JSON", TYPE="edgex")
 CREATE STREAM edgexInt8(int8 bigint) WITH (FORMAT="JSON", TYPE="edgex", CONF_KEY="int8_conf")
 ```
 
-不同之处在于，edgexInt8 明确指定 confkey 使用 `int8_conf`，它配置为 Random-Integer-Device 设备 int8读取的筛选主题。 因此，它只会接收每个事件的 int8 读取，并且事件结构是固定的。 因此，流定义也定义了模式，而不是无模式。
+不同之处在于，edgexInt8 明确指定 confkey 使用 `int8_conf`，它配置为 Random-Integer-Device 设备 Int8读取的筛选主题。 因此，它只会接收每个事件的 Int8 读取，并且事件结构是固定的。 因此，流定义也定义了模式，而不是无模式。
 
 同样，用户可以为每个 confkey 创建流。 每个规则都可以根据其关注点选择流。