tiny improve
diff --git a/java-chassis-reference/en_US/general-development/cross-app-invocation.md b/java-chassis-reference/en_US/general-development/cross-app-invocation.md
index cf3e576..2ff70e5 100644
--- a/java-chassis-reference/en_US/general-development/cross-app-invocation.md
+++ b/java-chassis-reference/en_US/general-development/cross-app-invocation.md
@@ -1,15 +1,21 @@
# Cross App Invocation
-### Concept Description
+## Concept Description
An application is a layer in the microservice instance isolation hierarchy, and an application contains multiple microservices. By default, only microservice instances of the same application are allowed to call each other.
-### Scenario
+## Scenario
When a user needs micro-services between different applications to call each other, it is necessary to enable the cross-application calling function.
-### Configuration instructions
+## Configuration instructions
-To enable cross-application calls, you first need to enable cross-application call configuration in the microservice.yaml file on the provider side. The configuration items are as follows:
+To enable cross-application calls, you first need to enable cross-application call configuration in the microservice.yaml file on the provider side.
+
+_Note_:
+* Need to upgrade the micro service version number to re-register micro service information in the service center
+* Even in the development development environment, you need to upgrade the microservice version number, because in the development environment, only the contract changes, will re-register the contract
+
+The configuration items are as follows:
```yaml
service_description:
# other configuration omitted
@@ -19,7 +25,7 @@
When the consumer client specifies the microservice name to call the provider, it needs to add the application ID to which the provider belongs, and the format becomes `[appID]:[microserviceName]`.
-### Sample Code
+## Sample Code
The example assumes that the application to which the provider belongs is helloApp, the name of the microservice is helloProvider, the application to which the consumer belongs is helloApp2, and the name of the microservice is helloConsumer.
diff --git a/java-chassis-reference/en_US/start/first-sample.md b/java-chassis-reference/en_US/start/first-sample.md
index 275a7f8..90e36b8 100644
--- a/java-chassis-reference/en_US/start/first-sample.md
+++ b/java-chassis-reference/en_US/start/first-sample.md
@@ -7,11 +7,14 @@
Before you start, developers need to choose a familiar development method. There are currently 3 ways to choose:
* Spring MVC
-* JAX RS
+* JaxRS
* RPC
+Because transparent RPC acts as a Producer without any RESTful semantics, the automatically generated contracts are all POST methods, and only the BODY parameters are not in line with the usual rules of RESTful.
+Therefore, it is recommended to choose JaxRS or Spring MVC as the Producer development mode, and transparent RPC as the developer development mode.
+
Their corresponding samples project are:
-* [Spring MVC] (https://github.com/apache/incubator-servicecomb-java-chassis/tree/master/samples/springmvc-sample)
-* [JAX RS] (https://github.com/apache/incubator-servicecomb-java-chassis/tree/master/samples/jaxrs-sample)
+* [Spring MVC](https://github.com/apache/incubator-servicecomb-java-chassis/tree/master/samples/springmvc-sample)
+* [JaxRS](https://github.com/apache/incubator-servicecomb-java-chassis/tree/master/samples/jaxrs-sample)
* [RPC](https://github.com/apache/incubator-servicecomb-java-chassis/tree/master/samples/pojo-sample)
-* Or use [archetypes] (https://github.com/apache/incubator-servicecomb-java-chassis/tree/master/archetypes)
\ No newline at end of file
+* Or use [archetypes](https://github.com/apache/incubator-servicecomb-java-chassis/tree/master/archetypes)
\ No newline at end of file
diff --git a/java-chassis-reference/zh_CN/general-development/cross-app-invocation.md b/java-chassis-reference/zh_CN/general-development/cross-app-invocation.md
index 1fcae26..9714aad 100644
--- a/java-chassis-reference/zh_CN/general-development/cross-app-invocation.md
+++ b/java-chassis-reference/zh_CN/general-development/cross-app-invocation.md
@@ -1,14 +1,20 @@
-### 概念阐述
+# 跨应用调用
+
+## 概念阐述
应用是微服务实例隔离层次中的一层，一个应用包含多个微服务。默认情况下，只允许同应用的微服务实例相互调用。
-### 场景描述
+## 场景描述
当用户需要不同应用间的微服务相互调用时，就需要开启跨应用调用功能。
-### 配置说明
+## 配置说明
-若要开启跨应用调用，首先需在provider端的microservice.yaml文件开启跨应用调用配置。配置项如下：
+若要开启跨应用调用，首先需在provider端的microservice.yaml文件开启跨应用调用配置。
+注意：
+* 需要升级微服务版本号，以便在服务中心重新注册微服务信息
+* 即使是development开发环境，也需要升级微服务版本号，因为development环境下，也只有契约发生变化，才会重新注册契约
+配置项如下：
```yaml
service_description:
# other configuration omitted
@@ -18,7 +24,7 @@
consumer端指定微服务名称调用provider的时候，需要加上provider所属的应用ID，格式变为`[appID]:[microserviceName]`。
-### 示例代码
+## 示例代码
示例假设provider所属应用为helloApp，微服务名称为helloProvider；consumer所属应用为helloApp2，微服务名称为helloConsumer。
diff --git a/java-chassis-reference/zh_CN/start/first-sample.md b/java-chassis-reference/zh_CN/start/first-sample.md
index 3ec45f4..253e2b0 100644
--- a/java-chassis-reference/zh_CN/start/first-sample.md
+++ b/java-chassis-reference/zh_CN/start/first-sample.md
@@ -8,11 +8,14 @@
开始之前，开发者需要先选择熟悉的开发方式，目前有3种方式可供选择：
* Spring MVC
-* JAX RS
+* JaxRS
* RPC
+因为透明RPC作为Producer时，不带任何RESTful语义，此时自动生成的契约全是POST方法，且只有BODY参数，不太符合RESTful的通常规则
+所以建议选择JaxRS或Spring MVC作为Producer开发模式，透明RPC作为Consumer的开发模式。
+
他们对应的samples项目分别是：
* [Spring MVC](https://github.com/apache/incubator-servicecomb-java-chassis/tree/master/samples/springmvc-sample)
-* [JAX RS](https://github.com/apache/incubator-servicecomb-java-chassis/tree/master/samples/jaxrs-sample)
+* [JaxRS](https://github.com/apache/incubator-servicecomb-java-chassis/tree/master/samples/jaxrs-sample)
* [RPC](https://github.com/apache/incubator-servicecomb-java-chassis/tree/master/samples/pojo-sample)
* 或者使用[archetypes](https://github.com/apache/incubator-servicecomb-java-chassis/tree/master/archetypes)
