commit 0423219d7fe6689905f3a8733a80ab944a60e0df
author chinx <c54948054@126.com> Wed Oct 16 10:50:46 2019 +0800
committer chinx <c54948054@126.com> Wed Oct 16 10:52:39 2019 +0800
tree 8048e72ab39e435dd44e1943e10a2995ba988b24
parent 625a1edd0061b2c52739688c9552f093a42f60f4

Update the Eureka spelling in the image

syncer/README-ZH.md

diff --git a/syncer/README-ZH.md b/syncer/README-ZH.md
index 65bfc0f..dc99363 100644
--- a/syncer/README-ZH.md
+++ b/syncer/README-ZH.md
@@ -15,7 +15,7 @@
 
 ### 2. ServiceCenter Syncer架构
 Syncer的运行时架构图如下：  
-![image](./images/SyncerArchitecture.png?raw=true&v=1)  
+![image](./images/SyncerArchitecture.png?raw=true&v=2)  
 如图所示，  
 
 - 在每个服务中心内，均部署了一套服务注册中心（ServiceCenter、Eurake或者其他）集群，该集群管理其所属服务中心的所有微服务实例，并且是彼此隔离的。同时在每个服務中心里各自部署了一个Syncer集群，它负责从注册中心发现实例，并向服务中心注册来自其他服务中心的实例信息。  

syncer/README.md

diff --git a/syncer/README.md b/syncer/README.md
index eb46e06..ff34a5b 100644
--- a/syncer/README.md
+++ b/syncer/README.md
@@ -15,7 +15,7 @@
 
 ### 2. ServiceCenter Syncer Architecture
 Syncer's runtime architecture diagram is as follows,
-![image](./images/SyncerArchitecture.png?raw=true&v=1)  
+![image](./images/SyncerArchitecture.png?raw=true&v=2)  
 There are three service-centers, 
 
 - Within each service center, a service registry (ServiceCenter, Eurake, or other) cluster is deployed that manages all microservice instances of the service center to which it belongs, and the service centers are isolated from each other. At the same time, a Syner cluster is deployed in each service center, which is responsible for discovering instances from the registry and registering instance information from other service centers to its own service centers.

syncer/images/SyncerArchitecture.png

diff --git a/syncer/images/SyncerArchitecture.png b/syncer/images/SyncerArchitecture.png
index 5742d54..95b8f27 100644
--- a/syncer/images/SyncerArchitecture.png
+++ b/syncer/images/SyncerArchitecture.png
Binary files differ