diff --git a/data-access-object/README.md b/data-access-object/README.md
index bd020252d..7e84299e2 100644
--- a/data-access-object/README.md
+++ b/data-access-object/README.md
@@ -199,10 +199,6 @@ The program output:
 10:02:09.898 [main] INFO com.iluwatar.dao.App -- customerDao.getAllCustomers(): java.util.stream.ReferencePipeline$Head@f2f2cc1
 ```
 
-## Detailed Explanation of Data Access Object Pattern with Real-World Examples
-
-![Data Access Object](./etc/dao.png "Data Access Object")
-
 ## When to Use the Data Access Object Pattern in Java
 
 Use the Data Access Object in any of the following situations:
diff --git a/data-locality/README.md b/data-locality/README.md
index e9f556b8a..a59103b3f 100644
--- a/data-locality/README.md
+++ b/data-locality/README.md
@@ -128,10 +128,6 @@ The console output:
 
 In this way, the data-locality module demonstrates the Data Locality pattern. By updating all components of the same type together, it increases the likelihood that the data needed for the update is already in the cache, thereby improving performance.
 
-## Detailed Explanation of Data Locality Pattern with Real-World Examples
-
-![Data Locality](./etc/data-locality.urm.png "Data Locality pattern class diagram")
-
 ## When to Use the Data Locality Pattern in Java
 
 This pattern is applicable in scenarios where large datasets are processed and performance is critical. It's particularly useful in: