diff --git a/rfc/rfc-55/classDesign.png b/rfc/rfc-55/hudi-sync-class-diagram.png
similarity index 100%
rename from rfc/rfc-55/classDesign.png
rename to rfc/rfc-55/hudi-sync-class-diagram.png
diff --git a/rfc/rfc-55/ArchitectureMetaSync.png b/rfc/rfc-55/hudi-sync-flows.png
similarity index 100%
rename from rfc/rfc-55/ArchitectureMetaSync.png
rename to rfc/rfc-55/hudi-sync-flows.png
diff --git a/rfc/rfc-55/rfc-55.md b/rfc/rfc-55/rfc-55.md
index 096b40a27c39c..4d5fb3790f2f9 100644
--- a/rfc/rfc-55/rfc-55.md
+++ b/rfc/rfc-55/rfc-55.md
@@ -32,7 +32,7 @@ JIRA: [HUDI-3730](https://issues.apache.org/jira/browse/HUDI-3730)
 
 ## Abstract
 
-![ArchitectureMetaSync.png](ArchitectureMetaSync.png)
+![hudi-sync-flows.png](hudi-sync-flows.png)
 
 Hudi support sync to various metastores via different processing framework like Spark, Flink, and Kafka connect. 
 
@@ -45,7 +45,7 @@ We need a standard way to run hudi sync. We also need a unified abstraction of X
 
 ## Classes design
 
-![classDesign.png](classDesign.png)
+![hudi-sync-class-diagram.png](hudi-sync-class-diagram.png)
 
 Below are the proposed key classes to handle the main sync logic. They are extensible for different metastores.