[GitHub] WillemJiang closed pull request #60: Catalog tanslation issue fix

[GitBox <gi...@apache.org>]

WillemJiang closed pull request #60: Catalog tanslation issue fix
URL: https://github.com/apache/incubator-servicecomb-docs/pull/60
 
 
   

This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:

As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):

diff --git a/java-chassis-reference/en_US/build-provider/configuration/parameter-validator.md b/java-chassis-reference/en_US/build-provider/configuration/parameter-validator.md
index 3862c99..148ee16 100644
--- a/java-chassis-reference/en_US/build-provider/configuration/parameter-validator.md
+++ b/java-chassis-reference/en_US/build-provider/configuration/parameter-validator.md
@@ -1,5 +1,5 @@
-## Scene Description
-
+# Parameter Validation
+## Scenario
 The user uses the parameter validation on the provider client, and can set the corresponding parameter input requirements in advance, and perform the effect processing before the interface is actually called to achieve the effect of the control parameter input standard.
 
 ## Configuration instructions
diff --git a/java-chassis-reference/en_US/build-provider/service-configuration.md b/java-chassis-reference/en_US/build-provider/service-configuration.md
index bf7f433..10e5815 100644
--- a/java-chassis-reference/en_US/build-provider/service-configuration.md
+++ b/java-chassis-reference/en_US/build-provider/service-configuration.md
@@ -1,14 +1,12 @@
-## [负载均衡策略](/build-provider/configuration/lb-strategy.html)
-• ServiceComb提供了基于Ribbon的负载均衡方案，用户可以通过配置文件配置负载均衡策略，当前支持随机、顺序、基于响应时间的权值等多种负载均衡路由策略## [Service Center](https://github.com/apache/incubator-servicecomb-saga){:target="_blank"}  
+## [Load Balancing Policy](/build-provider/configuration/lb-strategy.html)
+• ServiceComb provides a Ribbon-based load balancing solution. You can configure a load balancing policy in the configuration file. Currently, a load balancing routing policy can be random, sequential, or based on response time weight. [Service Center](https://github.com/apache/incubator-servicecomb-saga)
 
-## [限流策略](/build-provider/configuration/ratelimite-strategy.html) 
-• 用户在provider端使用限流策略，可以限制指定微服务向其发送请求的频率，达到限制每秒钟最大请求数量的效果。  
+## [Rate Limiting Policy](/build-provider/configuration/ratelimite-strategy.html) 
+• Users at the provider end can use the rate limiting policy to limit the maximum number of requests sent from a specified microservice per second.
 
+## [Fallback Policy](/build-provider/configuration/parameter-validator.html)  
+• A fallback policy is used when a service request is abnormal.
 
-## [降级策略](/build-provider/configuration/parameter-validator.html)  
-• 降级策略是当服务请求异常时，微服务所采用的异常处理策略。
-
-
-## [参数效验](/build-provider/configuration/parameter-validator.html)
-• 用户在provider端使用参数效验，可以对相应的参数输入要求预先进行设置，在接口实际调用前进行效验处理，达到控制参数输入标准的效果。
+## [Parameter Validation](/build-provider/configuration/parameter-validator.html)
+• The user uses the parameter validation on the provider client, and can set the corresponding parameter input requirements in advance, and perform the effect processing before the interface is actually called to achieve the effect of the control parameter input standard.
 
diff --git a/java-chassis-reference/en_US/catalog/build-provider.md b/java-chassis-reference/en_US/catalog/build-provider.md
index 8ecabf9..8a73f1c 100644
--- a/java-chassis-reference/en_US/catalog/build-provider.md
+++ b/java-chassis-reference/en_US/catalog/build-provider.md
@@ -1,38 +1,38 @@
-## [Service Definition] (/build-provider/definition/service-definition.html)
+## [Service Definition](/build-provider/definition/service-definition.html)
 • Service definition information is the identity of the microservice, which defines which application the service belongs to, as well as the name and version. The service definition information may also have extension information for defining attribute metadata of the service.
  
 
-## [Defining Service Contracts] (/build-provider/define-contract.html)
+## [Defining Service Contracts](/build-provider/define-contract.html)
 • Service contract, which refers to the micro-service interface contract based on the OpenAPI specification, which is the definition of the interface between the server and the consumer. The java chassis provides two ways to define contracts: code first and contract first.
 
 
-## [Use implicit contract] (/build-provider/code-first.html)
+## [Use implicit contract](/build-provider/code-first.html)
 • The downgrade strategy is the exception handling strategy used by the microservice when the service request is abnormal.
 
 
-## [Using Swagger Annotations] (/build-provider/swagger-annotation.html)
+## [Using Swagger Annotations](/build-provider/swagger-annotation.html)
 • Swagger provides a set of annotations to describe the interface contract. Users can use annotations to add descriptions of contracts to the code. ServiceComb supports some of these annotations.
 
 
-## [Developing microservices with SpringMVC] (/build-provider/springmvc.html)
+## [Developing microservices with SpringMVC](/build-provider/springmvc.html)
 • ServiceComb supports SpringMVC annotations, allowing the development of microservices using SpringMVC style. It is recommended to read the project in detail with reference to the project SpringMVC.
 
-## [Developing microservices with JAX-RS] (/build-provider/jaxrs.html)
+## [Developing microservices with JAX-RS](/build-provider/jaxrs.html)
 • ServiceComb supports developers using JAX-RS annotations to develop services using JAX-RS patterns.
 
-## [Using Swagger Annotations] (/build-provider/swagger-annotation.html)
+## [Using Swagger Annotations](/build-provider/swagger-annotation.html)
 • Swagger provides a set of annotations to describe the interface contract. Users can use annotations to add descriptions of contracts to the code. ServiceComb supports some of these annotations.
 
-## [Using Swagger Annotations] (/build-provider/swagger-annotation.html)
+## [Using Swagger Annotations](/build-provider/swagger-annotation.html)
 • Swagger provides a set of annotations to describe the interface contract. Users can use annotations to add descriptions of contracts to the code. ServiceComb supports some of these annotations.
 
-## [Developing microservices with transparent RPC] (/build-provider/transparent-rpc.html)
+## [Developing microservices with transparent RPC](/build-provider/transparent-rpc.html)
 • The transparent RPC development model is a development model based on interfaces and interfaces. Service developers do not need to use Spring MVC and JAX-RS annotations.
 
-## [interface definition and data type] (/build-provider/swagger-annotation.html)
+## [interface definition and data type](/build-provider/swagger-annotation.html)
 • ServiceComb-Java-Chassis suggests that the interface definition follows a simple principle: the interface definition is the interface usage specification, and you can identify how to call this interface without looking at the code implementation. It can be seen that this principle stands on the user side and is easier to use as a reference. ServiceComb will generate interface contracts based on interface definitions, interfaces that conform to this principle, and the generated contracts are also easy for users to read.
 
-## [Service Listening Address and Publishing Address] (/build-provider/listen-address-and-publish-address.html)
+## [Service Listening Address and Publishing Address](/build-provider/listen-address-and-publish-address.html)
 • In JavaChassis, the listening and publishing addresses of the service are two separate concepts that can be configured independently:
 
 Listening address: refers to the address that the microservice instance listens to when it starts. This configuration item determines which IPs can be accessed by this IP.
@@ -40,7 +40,7 @@ Publish address: refers to the address where the microservice instance is regist
 
 ## [Service Configuration](/build-provider/service-configuration.html)
 
-• [Load Balancing Policy] (/build-provider/configuration/lb-strategy.html)
-• [Limiting Policy] (/build-provider/configuration/ratelimite-strategy.html)
-• [Downgrade Strategy] (/build-provider/configuration/downgrade-strategy.html)
-• [Parameters and Research] (/build-provider/configuration/parameter-validator.html)
\ No newline at end of file
+• [Load Balancing Policy](/build-provider/configuration/lb-strategy.html)
+• [Limiting Policy](/build-provider/configuration/ratelimite-strategy.html)
+• [Downgrade Strategy](/build-provider/configuration/downgrade-strategy.html)
+• [Parameters and Research](/build-provider/configuration/parameter-validator.html)
\ No newline at end of file


 

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services