This is an automated email from the ASF dual-hosted git repository.
hyunkun pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/dubbo-website.git
The following commit(s) were added to refs/heads/master by this push:
new c7cbfe5 Fix a typo in architecture page(#428)
c7cbfe5 is described below
commit c7cbfe57c2361f27d53a74f133232fedc3e594b7
Author: Zhao Junwang <zhjw...@gmail.com>
AuthorDate: Wed Jul 10 13:15:56 2019 +0800
Fix a typo in architecture page(#428)
---
docs/en-us/user/preface/architecture.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/docs/en-us/user/preface/architecture.md
b/docs/en-us/user/preface/architecture.md
index 184c941..90fdef7 100644
--- a/docs/en-us/user/preface/architecture.md
+++ b/docs/en-us/user/preface/architecture.md
@@ -30,7 +30,7 @@ Dubbo has the following features: Connectivity, Robustness,
Scalability and Upgr
* 'Provider' registers services to 'Register' and report time-consuming
statistic(not include network overhead) to 'Monitor'
* 'Consumer' gets a list of service provider addresses from `Registry`, call
the provider directly according to the LB algorithm, report the time-consuming
statistic to `Monitor`, which includes network overhead
* The connections between `Register`, `Provider` and `Consumer` are long
connections, `Moniter` is an exception
-* `Register` is aware of the existence of `Provider` through the long
connection, when `Provider` gets down, `Provider` will push the event to
`Consumer`
+* `Register` is aware of the existence of `Provider` through the long
connection, when `Provider` gets down, `Register` will push the event to
`Consumer`
* It doesn't affect the already running instances of `Provider` and `Consumer`
even all of the `Register` and `Monitor` get down, since `Consumer` got a cache
of `Provider`s list
* `Register` and `Monitor` are optional, `Consumer` can connect `Provider`
directly
