This is an automated email from the ASF dual-hosted git repository.
xiaoyu pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/shenyu-website.git
The following commit(s) were added to refs/heads/main by this push:
new 79fca31ed24 Optimized syntax (#851)
79fca31ed24 is described below
commit 79fca31ed243e25c33ddde50d5bb48ae3353c2cd
Author: balloon72 <[email protected]>
AuthorDate: Wed Jan 18 15:34:13 2023 +0800
Optimized syntax (#851)
* Optimized syntax
* Syntax optimization
---
blog/SPI-SourceCode-Analysis-MatchStrategy-SPI.md | 2 +-
versioned_docs/version-2.5.0/user-guide/spring-cloud-proxy.md | 6 +++---
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/blog/SPI-SourceCode-Analysis-MatchStrategy-SPI.md
b/blog/SPI-SourceCode-Analysis-MatchStrategy-SPI.md
index 63229c9f48c..99e48cd59b2 100644
--- a/blog/SPI-SourceCode-Analysis-MatchStrategy-SPI.md
+++ b/blog/SPI-SourceCode-Analysis-MatchStrategy-SPI.md
@@ -11,7 +11,7 @@ In most of the `plugins` ( such as `Dubbo`,
`gRPC`,`Spring-cloud`, etc) of `Apac
- `PredictJudge`-predicate
- `MatchStrategy`-matching strategy
-Relatively speaking, the `MatchStrategy` is the part that needs the least
extension points. For the combination judgement of multiple conditions, the
common select rules are: All conditions are matched, at least one is match, at
least the first is met, or most of conditions satisfied. As well need to
handle various type of parameters, for example: `IP`, `header`, `uri`, etc.
How to make the `MatchStrategy` to be simple to use and extensible?
+Relatively speaking, the `MatchStrategy` is the part that needs the least
extension points. For the combined judgement of multiple conditions, the common
selection rules are: All conditions are matched, at least one is matched, at
least the first is met, or most of conditions satisfied. As well need to
handle various types of parameters, for example: `IP`, `header`, `uri`, etc.
How to make the `MatchStrategy` to be simple to use and extensible?
## MatchStrategy
diff --git a/versioned_docs/version-2.5.0/user-guide/spring-cloud-proxy.md
b/versioned_docs/version-2.5.0/user-guide/spring-cloud-proxy.md
index 36c990dd80d..076fafeae4b 100644
--- a/versioned_docs/version-2.5.0/user-guide/spring-cloud-proxy.md
+++ b/versioned_docs/version-2.5.0/user-guide/spring-cloud-proxy.md
@@ -120,7 +120,7 @@ public class ShenyuBootstrapApplication {
Please refer to
[shenyu-examples-springcloud](https://github.com/apache/incubator-shenyu/tree/v2.5.0/shenyu-examples/shenyu-examples-springcloud)
-* Add the following dependencies to your `Spring Cloud` microservice :
+* Add the following dependencies to your `Spring Cloud` micro service :
```xml
<dependency>
@@ -278,7 +278,7 @@ Special note: currently only supports `@RequestMapping,
@GetMapping, @PostMappin
```
-* After successfully registering your service, go to the backend management
system PluginList -> rpc proxy -> springCloud ', you will see the automatic
registration of selectors and rules information.
+* After successfully registering your service, go to the Back-end management
system PluginList -> rpc proxy -> springCloud ', you will see the automatic
registration of selectors and rules information.
@@ -288,7 +288,7 @@ Special note: currently only supports `@RequestMapping,
@GetMapping, @PostMappin
* firstly,the domain name that requested before in your service, now need to
replace with gateway's domain name.
-* secondly, Apache ShenYu gateway needs a route prefix which comes from
`contextPath`, it configured during the integration with gateway, you can
change it freely in divide plugin of `shenyu-admin`, if your familiar with it.
+* secondly, Apache ShenYu gateway needs a route prefix which comes from
`contextPath`, it configured during the integration with gateway, you can
change it freely in divide plugin of `shenyu-admin`, if you're familiar with it.
> For example, your have an `order` service and it has a interface, the
> request url: `http://localhost:8080/test/save` .
>
