fix: restore correct Chinese encoding and fix markdownlint errors

- Restore UTF-8 encoding for Chinese text in all affected README files
- Fix garbled Chinese in company logos (拼多多, 爱奇艺, 二维火, etc.)
- Fix table column style in Sentinel_Dashboard_Feature.md (MD060)
- Fix bare URLs in sentinel-demo-dubbo README (MD034)
- Remove BOM markers from dashboard documentation files

Fixes encoding issues introduced in commit 7b9f7c7

Author: Layau-code

README.md

@@ -1,4 +1,4 @@
-# Sentinel: The Sentinel of Your Microservices
+# Sentinel: The Sentinel of Your Microservices
 
 <img src="https://user-images.githubusercontent.com/9434884/43697219-3cb4ef3a-9975-11e8-9a9c-73f4f537442d.png" alt="Sentinel Logo" width="50%">
 
@@ -18,7 +18,7 @@ to guarantee reliability and resilience for microservices.
 
 Sentinel has the following features:
 
-- **Rich applicable scenarios**: Sentinel has been wildly used in Alibaba, and has covered almost all the core-scenarios in Double-11 (11.11) Shopping Festivals in the past 10 years, such as 鈥淪econd Kill鈥?which needs to limit burst flow traffic to meet the system capacity, message peak clipping and valley fills, circuit breaking for unreliable downstream services, cluster flow control, etc.
+- **Rich applicable scenarios**: Sentinel has been wildly used in Alibaba, and has covered almost all the core-scenarios in Double-11 (11.11) Shopping Festivals in the past 10 years, such as “Second Kill” which needs to limit burst flow traffic to meet the system capacity, message peak clipping and valley fills, circuit breaking for unreliable downstream services, cluster flow control, etc.
 - **Real-time monitoring**: Sentinel also provides real-time monitoring ability. You can see the runtime information of a single machine in real-time, and the aggregated runtime info of a cluster with less than 500 nodes.
 - **Widespread open-source ecosystem**: Sentinel provides out-of-box integrations with commonly-used frameworks and libraries such as Spring Cloud, gRPC, Apache Dubbo and Quarkus. You can easily use Sentinel by simply add the adapter dependency to your services.
 - **Polyglot support**: Sentinel has provided native support for Java, [Go](https://github.com/alibaba/sentinel-golang), [C++](https://github.com/alibaba/sentinel-cpp) and [Rust](https://github.com/sentinel-group/sentinel-rust).
@@ -35,7 +35,7 @@ Please refer to [OpenSergo](https://opensergo.io/) for details.
 
 See the [Sentinel Website](https://sentinelguard.io/) for the official website of Sentinel.
 
-See the [涓枃鏂囨。](https://sentinelguard.io/zh-cn/docs/introduction.html) for document in Chinese.
+See the [中文文档](https://sentinelguard.io/zh-cn/docs/introduction.html) for document in Chinese.
 
 See the [Wiki](https://github.com/alibaba/Sentinel/wiki) for full documentation, examples, blog posts, operational details and other information.
 
@@ -112,13 +112,13 @@ For more information, please refer to [How To Use](https://sentinelguard.io/en-u
 After running the demo for a while, you can see the following records in `~/logs/csp/${appName}-metrics.log.{date}` (When using the default `DateFileLogHandler`).
 
 ```plaintext
-|--timestamp-|------date time----|-resource-|p|block|s|e|rt|occupied
-1529998904000|2018-06-26 15:41:44|HelloWorld|20|0|20|0|0|0
-1529998905000|2018-06-26 15:41:45|HelloWorld|20|5579|20|0|728|0
-1529998906000|2018-06-26 15:41:46|HelloWorld|20|15698|20|0|0|0
-1529998907000|2018-06-26 15:41:47|HelloWorld|20|19262|20|0|0|0
-1529998908000|2018-06-26 15:41:48|HelloWorld|20|19502|20|0|0|0
-1529998909000|2018-06-26 15:41:49|HelloWorld|20|18386|20|0|0|0
+|--timestamp-|------date time----|-resource-|p |block|s |e|rt  |occupied
+1529998904000|2018-06-26 15:41:44|HelloWorld|20|0    |20|0|0   |0
+1529998905000|2018-06-26 15:41:45|HelloWorld|20|5579 |20|0|728 |0
+1529998906000|2018-06-26 15:41:46|HelloWorld|20|15698|20|0|0   |0
+1529998907000|2018-06-26 15:41:47|HelloWorld|20|19262|20|0|0   |0
+1529998908000|2018-06-26 15:41:48|HelloWorld|20|19502|20|0|0   |0
+1529998909000|2018-06-26 15:41:49|HelloWorld|20|18386|20|0|0   |0
 
 p stands for incoming request, block for blocked by rules, s for success handled by Sentinel, e for exception count, rt for average response time (ms), occupied stands for occupiedPassQps since 1.5.0 which enable us booking more than 1 shot when entering.
 ```
@@ -160,9 +160,9 @@ You can start with the issues labeled with [`good first issue`](https://github.c
 
 ## Enterprise Service
 
-If you need Sentinel enterprise service support (Sentinel 浼佷笟鐗?, or purchase cloud product services,
+If you need Sentinel enterprise service support (Sentinel 企业版), or purchase cloud product services,
 you can join the discussion by the DingTalk group (34754806). It can also be directly activated
-and used through the [microservice engine (MSE 寰湇鍔″紩鎿? provided by Alibaba Cloud](https://cn.aliyun.com/product/aliware/mse?spm=sentinel-github.index.0.0.0).
+and used through the [microservice engine (MSE 微服务引擎) provided by Alibaba Cloud](https://cn.aliyun.com/product/aliware/mse?spm=sentinel-github.index.0.0.0).
 
 ## Credits
 
@@ -178,13 +178,13 @@ If you are using Sentinel, please [add your company here](https://github.com/ali
 ![Alibaba Group](https://docs.alibabagroup.com/assets2/images/en/global/logo_header.png)
 ![AntFin](https://user-images.githubusercontent.com/9434884/90598732-30961c00-e226-11ea-8c86-0b1d7f7875c7.png)
 ![Taiping Renshou](http://www.cntaiping.com/tplresource/cms/www/taiping/img/home_new/tp_logo_img.png)
-![鎷煎澶歖(http://cdn.pinduoduo.com/assets/img/pdd_logo_v3.png)
-![鐖卞鑹篯(https://user-images.githubusercontent.com/9434884/90598445-a51c8b00-e225-11ea-9327-3543525f3f2a.png)
+![拼多多](http://cdn.pinduoduo.com/assets/img/pdd_logo_v3.png)
+![爱奇艺](https://user-images.githubusercontent.com/9434884/90598445-a51c8b00-e225-11ea-9327-3543525f3f2a.png)
 ![Shunfeng Technology](https://user-images.githubusercontent.com/9434884/48463502-2f48eb80-e817-11e8-984f-2f9b1b789e2d.png)
-![浜岀淮鐏玗(https://user-images.githubusercontent.com/9434884/49358468-bc43de00-f70d-11e8-97fe-0bf05865f29f.png)
+![二维火](https://user-images.githubusercontent.com/9434884/49358468-bc43de00-f70d-11e8-97fe-0bf05865f29f.png)
 ![Mandao](https://user-images.githubusercontent.com/9434884/48463559-6cad7900-e817-11e8-87e4-42952b074837.png)
-![鏂囪僵鍦ㄧ嚎](http://static.winxuancdn.com/css/v2/images/logo.png)
-![瀹㈠浜慮(https://www.keruyun.com/static/krynew/images/logo.png)
-![浜插疂瀹漖(https://stlib.qbb6.com/wclt/img/home_hd/version1/title_logo.png)
-![閲戞眹閲戣瀺](https://res.jinhui365.com/r/images/logo2.png?v=1.527)
-![闂數璐璢(http://cdn.52shangou.com/shandianbang/official-source/3.1.1/build/images/logo.png)
+![文轩在线](http://static.winxuancdn.com/css/v2/images/logo.png)
+![客如云](https://www.keruyun.com/static/krynew/images/logo.png)
+![亲宝宝](https://stlib.qbb6.com/wclt/img/home_hd/version1/title_logo.png)
+![金汇金融](https://res.jinhui365.com/r/images/logo2.png?v=1.527)
+![闪电购](http://cdn.52shangou.com/shandianbang/official-source/3.1.1/build/images/logo.png)

sentinel-adapter/sentinel-spring-webmvc-adapter/README.md

@@ -1,4 +1,4 @@
-# Sentinel Spring MVC Adapter
+# Sentinel Spring MVC Adapter
 
 ## Introduction
 
@@ -91,23 +91,23 @@ config.setBlockExceptionHandler((request, response, e) -> {
 
 - Common configuration in `SentinelWebMvcConfig` and `SentinelWebMvcTotalConfig`:
 
-| name | description | type | default value |
-| ------ | ------------ | ------ | ------- |
-| `blockExceptionHandler` | The handler that handles the block request | `BlockExceptionHandler` | null (throw out the BlockException) |
-| `originParser` | Extracting request origin (e.g. IP or appName from HTTP Header) from HTTP request | `RequestOriginParser` | - |
+ | name | description | type | default value | 
+ | ------ | ------------ | ------ | ------- | 
+ | `blockExceptionHandler` | The handler that handles the block request | `BlockExceptionHandler` | null (throw out the BlockException) | 
+ | `originParser` | Extracting request origin (e.g. IP or appName from HTTP Header) from HTTP request | `RequestOriginParser` | - | 
 
 - `SentinelWebMvcConfig` configuration:
 
-| name | description | type | default value |
-| ------ | ------------ | ------ | ------- |
-| urlCleaner | The `UrlCleaner` interface is designed for clean and unify the URL resource. | `UrlCleaner` | - |
-| requestAttributeName | Attribute key in request used by Sentinel (internal) | `String` | `$$sentinel_spring_web_entry_attr` |
-| httpMethodSpecify | Specify whether the URL resource name should contain the HTTP method prefix (e.g. `POST:`). | `boolean` | `false` |
-| webContextUnify | Specify whether unify web context(i.e. use the default context name). | `boolean` | `true` |
+ | name | description | type | default value | 
+ | ------ | ------------ | ------ | ------- | 
+ | urlCleaner | The `UrlCleaner` interface is designed for clean and unify the URL resource. | `UrlCleaner` | - | 
+ | requestAttributeName | Attribute key in request used by Sentinel (internal) | `String` | `$$sentinel_spring_web_entry_attr` | 
+ | httpMethodSpecify | Specify whether the URL resource name should contain the HTTP method prefix (e.g. `POST:`). | `boolean` | `false` | 
+ | webContextUnify | Specify whether unify web context(i.e. use the default context name). | `boolean` | `true` | 
 
 - `SentinelWebMvcTotalConfig` configuration:
 
-| name | description | type | default value |
-| ------ | ------------ | ------ | ------- |
-| totalResourceName | The resource name in `SentinelTotalInterceptor` | `String` | `spring-mvc-total-url-request` |
-| requestAttributeName | Attribute key in request used by Sentinel (internal) | `String` | `$$sentinel_spring_web_total_entry_attr` |
+ | name | description | type | default value | 
+ | ------ | ------------ | ------ | ------- | 
+ | totalResourceName | The resource name in `SentinelTotalInterceptor` | `String` | `spring-mvc-total-url-request` | 
+ | requestAttributeName | Attribute key in request used by Sentinel (internal) | `String` | `$$sentinel_spring_web_total_entry_attr` | 

sentinel-cluster/sentinel-cluster-server-envoy-rls/README.md

@@ -1,4 +1,4 @@
-# Sentinel Token Server (Envoy RLS implementation)
+# Sentinel Token Server (Envoy RLS implementation)
 
 This module provides the [Envoy rate limiting gRPC service](https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/other_features/global_rate_limiting#arch-overview-rate-limit) implementation
 with Sentinel token server.
@@ -50,7 +50,11 @@ We may also retrieve the converted `FlowRule` via the command API `localhost:871
 
 The configuration list:
 
- |Item (env)|Item (JVM property)|Description|Default Value|Required||--------|--------|--------|--------|--------||`SENTINEL_RLS_GRPC_PORT`|`csp.sentinel.grpc.server.port`|The RLS gRPC server port|**10240**|false||`SENTINEL_RLS_RULE_FILE_PATH`|`csp.sentinel.rls.rule.file`|The path of the RLS rule yaml file|-|**true**||`SENTINEL_RLS_ACCESS_LOG`|-|Whether to enable the access log (`on` for enable)|off|false|
+ | Item (env) | Item (JVM property) | Description | Default Value | Required | 
+ | -------- | -------- | -------- | -------- | -------- | 
+ | `SENTINEL_RLS_GRPC_PORT` | `csp.sentinel.grpc.server.port` | The RLS gRPC server port | **10240** | false | 
+ | `SENTINEL_RLS_RULE_FILE_PATH` | `csp.sentinel.rls.rule.file` | The path of the RLS rule yaml file | - | **true** | 
+ | `SENTINEL_RLS_ACCESS_LOG` | - | Whether to enable the access log (`on` for enable) | off | false | 
 
 ## Samples
 

sentinel-dashboard/README.md

@@ -1,22 +1,22 @@
-# Sentinel 鎺у埗鍙?
+# Sentinel 控制台
 
-## 0. 姒傝堪
+## 0. 概述
 
-Sentinel 鎺у埗鍙版槸娴侀噺鎺у埗銆佺啍鏂檷绾ц鍒欑粺涓€閰嶇疆鍜岀鐞嗙殑鍏ュ彛锛屽畠涓虹敤鎴锋彁渚涗簡鏈哄櫒鑷彂鐜般€佺皣鐐归摼璺嚜鍙戠幇銆佺洃鎺с€佽鍒欓厤缃瓑鍔熻兘銆傚湪 Sentinel 鎺у埗鍙颁笂锛屾垜浠彲浠ラ厤缃鍒欏苟瀹炴椂鏌ョ湅娴侀噺鎺у埗鏁堟灉銆?
+Sentinel 控制台是流量控制、熔断降级规则统一配置和管理的入口，它为用户提供了机器自发现、簇点链路自发现、监控、规则配置等功能。在 Sentinel 控制台上，我们可以配置规则并实时查看流量控制效果。
 
-## 1. 缂栬瘧鍜屽惎鍔?
+## 1. 编译和启动
 
-### 1.1 濡備綍缂栬瘧
+### 1.1 如何编译
 
-浣跨敤濡備笅鍛戒护灏嗕唬鐮佹墦鍖呮垚涓€涓?fat jar:
+使用如下命令将代码打包成一个 fat jar:
 
 ```bash
 mvn clean package
 ```
 
-### 1.2 濡備綍鍚姩
+### 1.2 如何启动
 
-浣跨敤濡備笅鍛戒护鍚姩缂栬瘧鍚庣殑鎺у埗鍙帮細
+使用如下命令启动编译后的控制台：
 
 ```bash
 java -Dserver.port=8080 \
@@ -25,42 +25,45 @@ java -Dserver.port=8080 \
 -jar target/sentinel-dashboard.jar
 ```
 
-涓婅堪鍛戒护涓垜浠寚瀹氬嚑涓?JVM 鍙傛暟锛屽叾涓?`-Dserver.port=8080` 鏄?Spring Boot 鐨勫弬鏁帮紝
-鐢ㄤ簬鎸囧畾 Spring Boot 鏈嶅姟绔惎鍔ㄧ鍙ｄ负 `8080`銆傚叾浣欏嚑涓槸 Sentinel 瀹㈡埛绔殑鍙傛暟銆?
+上述命令中我们指定几个 JVM 参数，其中 `-Dserver.port=8080` 是 Spring Boot 的参数，
+用于指定 Spring Boot 服务端启动端口为 `8080`。其余几个是 Sentinel 客户端的参数。
 
-涓轰究浜庢紨绀猴紝鎴戜滑瀵规帶鍒跺彴鏈韩鍔犲叆浜嗘祦閲忔帶鍒跺姛鑳斤紝鍏蜂綋鍋氭硶鏄紩鍏?Sentinel 鎻愪緵鐨?`CommonFilter` 杩欎釜 Servlet Filter銆?
-涓婅堪 JVM 鍙傛暟鐨勫惈涔夋槸锛?
+为便于演示，我们对控制台本身加入了流量控制功能，具体做法是引入 Sentinel 提供的 `CommonFilter` 这个 Servlet Filter。
+上述 JVM 参数的含义是：
 
- |鍙傛暟|浣滅敤||--------|--------||`-Dcsp.sentinel.dashboard.server=localhost:8080`|鍚?Sentinel 鎺ュ叆绔寚瀹氭帶鍒跺彴鐨勫湴鍧€||`-Dproject.name=sentinel-dashboard`|鍚?Sentinel 鎸囧畾搴旂敤鍚嶇О锛屾瘮濡備笂闈㈠搴旂殑搴旂敤鍚嶇О灏变负 `sentinel-dashboard`|
+ | 参数 | 作用 | 
+ | -------- | -------- | 
+ | `-Dcsp.sentinel.dashboard.server=localhost:8080` | 向 Sentinel 接入端指定控制台的地址 | 
+ | `-Dproject.name=sentinel-dashboard` | 向 Sentinel 指定应用名称，比如上面对应的应用名称就为 `sentinel-dashboard` | 
 
-鍏ㄩ儴鐨勯厤缃」鍙互鍙傝€?[鍚姩閰嶇疆椤规枃妗(https://github.com/alibaba/Sentinel/wiki/%E5%90%AF%E5%8A%A8%E9%85%8D%E7%BD%AE%E9%A1%B9)銆?
+全部的配置项可以参考 [启动配置项文档](https://github.com/alibaba/Sentinel/wiki/%E5%90%AF%E5%8A%A8%E9%85%8D%E7%BD%AE%E9%A1%B9)。
 
-缁忚繃涓婅堪閰嶇疆锛屾帶鍒跺彴鍚姩鍚庝細鑷姩鍚戣嚜宸卞彂閫佸績璺炽€傜▼搴忓惎鍔ㄥ悗娴忚鍣ㄨ闂?`localhost:8080` 鍗冲彲璁块棶 Sentinel 鎺у埗鍙般€?
+经过上述配置，控制台启动后会自动向自己发送心跳。程序启动后浏览器访问 `localhost:8080` 即可访问 Sentinel 控制台。
 
-浠?Sentinel 1.6.0 寮€濮嬶紝Sentinel 鎺у埗鍙版敮鎸佺畝鍗曠殑**鐧诲綍**鍔熻兘锛岄粯璁ょ敤鎴峰悕鍜屽瘑鐮侀兘鏄?`sentinel`銆傜敤鎴峰彲浠ラ€氳繃濡備笅鍙傛暟杩涜閰嶇疆锛?
+从 Sentinel 1.6.0 开始，Sentinel 控制台支持简单的**登录**功能，默认用户名和密码都是 `sentinel`。用户可以通过如下参数进行配置：
 
-- `-Dsentinel.dashboard.auth.username=sentinel` 鐢ㄤ簬鎸囧畾鎺у埗鍙扮殑鐧诲綍鐢ㄦ埛鍚嶄负 `sentinel`锛?
-- `-Dsentinel.dashboard.auth.password=123456` 鐢ㄤ簬鎸囧畾鎺у埗鍙扮殑鐧诲綍瀵嗙爜涓?`123456`锛涘鏋滅渷鐣ヨ繖涓や釜鍙傛暟锛岄粯璁ょ敤鎴峰拰瀵嗙爜鍧囦负 `sentinel`锛?
-- `-Dserver.servlet.session.timeout=7200` 鐢ㄤ簬鎸囧畾 Spring Boot 鏈嶅姟绔?session 鐨勮繃鏈熸椂闂达紝濡?`7200` 琛ㄧず 7200 绉掞紱`60m` 琛ㄧず 60 鍒嗛挓锛岄粯璁や负 30 鍒嗛挓锛?
+- `-Dsentinel.dashboard.auth.username=sentinel` 用于指定控制台的登录用户名为 `sentinel`；
+- `-Dsentinel.dashboard.auth.password=123456` 用于指定控制台的登录密码为 `123456`；如果省略这两个参数，默认用户和密码均为 `sentinel`；
+- `-Dserver.servlet.session.timeout=7200` 用于指定 Spring Boot 服务端 session 的过期时间，如 `7200` 表示 7200 秒；`60m` 表示 60 分钟，默认为 30 分钟；
 
-## 2. 瀹㈡埛绔帴鍏?
+## 2. 客户端接入
 
-閫夋嫨鍚堥€傜殑鏂瑰紡鎺ュ叆 Sentinel锛岀劧鍚庡湪搴旂敤鍚姩鏃跺姞鍏?JVM 鍙傛暟 `-Dcsp.sentinel.dashboard.server=consoleIp:port` 鎸囧畾鎺у埗鍙板湴鍧€鍜岀鍙ｃ€?
-纭繚瀹㈡埛绔湁璁块棶閲忥紝**Sentinel 浼氬湪瀹㈡埛绔娆¤皟鐢ㄧ殑鏃跺€欒繘琛屽垵濮嬪寲锛屽紑濮嬪悜鎺у埗鍙板彂閫佸績璺冲寘**锛屽皢瀹㈡埛绔撼鍏ュ埌鎺у埗鍙扮殑绠¤緰涔嬩笅銆?
+选择合适的方式接入 Sentinel，然后在应用启动时加入 JVM 参数 `-Dcsp.sentinel.dashboard.server=consoleIp:port` 指定控制台地址和端口。
+确保客户端有访问量，**Sentinel 会在客户端首次调用的时候进行初始化，开始向控制台发送心跳包**，将客户端纳入到控制台的管辖之下。
 
-瀹㈡埛绔帴鍏ョ殑璇︾粏姝ラ璇峰弬鑰?[Wiki 鏂囨。](https://github.com/alibaba/Sentinel/wiki/%E6%8E%A7%E5%88%B6%E5%8F%B0#3-%E5%AE%A2%E6%88%B7%E7%AB%AF%E6%8E%A5%E5%85%A5%E6%8E%A7%E5%88%B6%E5%8F%B0)銆?
+客户端接入的详细步骤请参考 [Wiki 文档](https://github.com/alibaba/Sentinel/wiki/%E6%8E%A7%E5%88%B6%E5%8F%B0#3-%E5%AE%A2%E6%88%B7%E7%AB%AF%E6%8E%A5%E5%85%A5%E6%8E%A7%E5%88%B6%E5%8F%B0)。
 
-## 3. 楠岃瘉鏄惁鎺ュ叆鎴愬姛
+## 3. 验证是否接入成功
 
-瀹㈡埛绔纭厤缃苟鍚姩鍚庯紝浼?*鍦ㄥ垵娆¤皟鐢ㄥ悗**涓诲姩鍚戞帶鍒跺彴鍙戦€佸績璺冲寘锛屾眹鎶ヨ嚜宸辩殑瀛樺湪锛?
-鎺у埗鍙版敹鍒板鎴风蹇冭烦鍖呬箣鍚庯紝浼氬湪宸︿晶瀵艰埅鏍忎腑鏄剧ず璇ュ鎴风淇℃伅銆傚鏋滄帶鍒跺彴鑳藉鐪嬪埌瀹㈡埛绔殑鏈哄櫒淇℃伅锛屽垯琛ㄦ槑瀹㈡埛绔帴鍏ユ垚鍔熶簡銆?
+客户端正确配置并启动后，会**在初次调用后**主动向控制台发送心跳包，汇报自己的存在；
+控制台收到客户端心跳包之后，会在左侧导航栏中显示该客户端信息。如果控制台能够看到客户端的机器信息，则表明客户端接入成功了。
 
-## 6. 鏋勫缓Docker闀滃儚
+## 6. 构建Docker镜像
 
 ```bash
 docker build --build-arg SENTINEL_VERSION=1.8.9 -t ${REGISTRY}/sentinel-dashboard:v1.8.9 .
 ```
 
-*娉ㄦ剰锛歋entinel 鎺у埗鍙扮洰鍓嶄粎鏀寔鍗曟満閮ㄧ讲銆係entinel 鎺у埗鍙伴」鐩彁渚?Sentinel 鍔熻兘鍏ㄩ泦绀轰緥锛屼笉浣滀负寮€绠卞嵆鐢ㄧ殑鐢熶骇鐜鎺у埗鍙帮紝涓嶆彁渚涘畨鍏ㄥ彲闈犱繚闅溿€傝嫢甯屾湜鍦ㄧ敓浜х幆澧冧娇鐢ㄨ鏍规嵁[鏂囨。](https://github.com/alibaba/Sentinel/wiki/%E5%9C%A8%E7%94%9F%E4%BA%A7%E7%8E%AF%E5%A2%83%E4%B8%AD%E4%BD%BF%E7%94%A8-Sentinel)鑷杩涜瀹氬埗鍜屾敼閫犮€?
+*注意：Sentinel 控制台目前仅支持单机部署。Sentinel 控制台项目提供 Sentinel 功能全集示例，不作为开箱即用的生产环境控制台，不提供安全可靠保障。若希望在生产环境使用请根据[文档](https://github.com/alibaba/Sentinel/wiki/%E5%9C%A8%E7%94%9F%E4%BA%A7%E7%8E%AF%E5%A2%83%E4%B8%AD%E4%BD%BF%E7%94%A8-Sentinel)自行进行定制和改造。*
 
-鏇村锛歔鎺у埗鍙板姛鑳戒粙缁峕(./Sentinel_Dashboard_Feature.md)銆?
+更多：[控制台功能介绍](./Sentinel_Dashboard_Feature.md)。