[servicecomb-docs] 02/02: Update interface-constraints.md

[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/servicecomb-docs.git

commit 2080fc0ebd3a8e7e876370e40982d85dc26b4e1a
Author: 自然 <na...@qq.com>
AuthorDate: Fri Sep 6 19:58:19 2019 +0800

    Update interface-constraints.md
---
 java-chassis-reference/zh_CN/build-provider/interface-constraints.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/java-chassis-reference/zh_CN/build-provider/interface-constraints.md b/java-chassis-reference/zh_CN/build-provider/interface-constraints.md
index a8e768a..7e6c119 100644
--- a/java-chassis-reference/zh_CN/build-provider/interface-constraints.md
+++ b/java-chassis-reference/zh_CN/build-provider/interface-constraints.md
@@ -9,7 +9,7 @@ ServiceComb-Java-Chassis建议接口定义遵循一个简单的原则：接口
 ```java
 public Person query(String id);
 public Object query(String id);
-public class Person {String name;}
+public Person query(String name);
 ```
 
 显然调用接口一，我们知道要传递一个String类型的id参数，返回值是一个Person类型，Person里面存在String类型的name参数。调用接口二，我们不知道怎么处理返回值，必须参考服务提供者的文档说明。这个视角是熟练的RPC开发者的视角。