[incubator-servicecomb-website] 02/06: fix table style

[ni...@apache.org]

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

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

commit 3cee0d15f4d51b8a348cf9c700efda38a669d876
Author: zhengyangyong <ya...@huawei.com>
AuthorDate: Wed Feb 28 10:12:01 2018 +0800

    fix table style
    
    Signed-off-by: zhengyangyong <ya...@huawei.com>
---
 _users/cn/metrics-in-1.0.0-m1.md |  3 ++-
 _users/metrics-in-1.0.0-m1.md    | 12 ++++++++----
 2 files changed, 10 insertions(+), 5 deletions(-)

diff --git a/_users/cn/metrics-in-1.0.0-m1.md b/_users/cn/metrics-in-1.0.0-m1.md
index fdf633e..98137d6 100644
--- a/_users/cn/metrics-in-1.0.0-m1.md
+++ b/_users/cn/metrics-in-1.0.0-m1.md
@@ -199,7 +199,8 @@ Metrics数据将以Map<String, Double>的形式输出，为了能够方便用户
 *demo/perf/PerfMetricsFilePublisher.java提供了MetricsLoader更详细的使用示例*
 
 ## 如何扩展
-Java Chassis Metrics支持自定义Metrics扩展，MonitorManager包含一组获取各类Monitor的方法：
+Java Chassis Metrics支持自定义Metrics扩展，MonitorManager包含一组获取各类Monitor的方法：  
+
 | 方法名       | 描述         |
 | :---------- | :---------- |
 | getCounter | 获取一个计数器类的Monitor |
diff --git a/_users/metrics-in-1.0.0-m1.md b/_users/metrics-in-1.0.0-m1.md
index 7703e1e..a15a076 100644
--- a/_users/metrics-in-1.0.0-m1.md
+++ b/_users/metrics-in-1.0.0-m1.md
@@ -39,7 +39,8 @@ So,upgrading from 0.5.0 to 1.0.0-m1,we had done a fully reconstruction,now it's
 | metrics-core        | Metrics core module,work immediately after imported |
 | metrics-integration | Include metrics Integration with other monitor system |
 
-The dependency of this modules is:
+The dependency of this modules is:  
+
 ![MetricsDependency.png](/assets/images/MetricsDependency.png)
 
 ### Use event collect invocation data,not from Hystrix(handler-bizkeeper)any more
@@ -84,7 +85,8 @@ Metrics had many classifications,we can divided them into two major types by how
 From 1.0.0-m1,build-in two type Metric output:   
 ### JVM Information
 ID format is : *jvm(statistic=gauge,name={name})*
-name include:
+name include:  
+
 | Name     | Description                               |
 | :----------- | :------------------------------- |
 | cpuLoad | CPU load rate                    |
@@ -94,7 +96,8 @@ name include:
 
 ### Invocation Information
 ID format is : *servicecomb.invocation(operation={operationName},role={role},stage={stage},statistic={statistic},status={status},unit={unit})*
-Tag name and value below:
+Tag name and value below:  
+
 | Tag Name       | Description                  | Options or Values |
 | :---------- | :---------- | :--------------------- |
 | operationName | Operation full name | MicroserviceQualifiedName |
@@ -196,7 +199,8 @@ Metrics data will output as Map<String,Double>,in order to let user easier fetch
 *More detail can be found in demo/perf/PerfMetricsFilePublisher.java*
 
 ## How to Extend Custom Metrics
-Java Chassis Metrics support user extend custom metrics,MonitorManager had a set of method get different type of Monitor:
+Java Chassis Metrics support user extend custom metrics,MonitorManager had a set of method get different type of Monitor:  
+
 | Method Name       | Description         |
 | :---------- | :---------- |
 | getCounter | Get a counter monitor |

-- 
To stop receiving notification emails like this one, please contact
ningjiang@apache.org.