docs: updates to several patterns

aggregator-microservices/README.md

@@ -18,7 +18,7 @@ To aggregate responses from multiple microservices and return a consolidated res
 
 ## Explanation
 
-Real world example
+Real-world example
 
 > Imagine an online travel booking platform. When a user searches for a vacation package, the platform needs to gather information from several different services: flights, hotels, car rentals, and local attractions. Instead of the user making separate requests to each service, the platform employs an Aggregator Microservice. This microservice calls each of these services, collects their responses, and then consolidates the information into a single, unified response that is sent back to the user. This simplifies the user experience by providing all necessary travel details in one place and reduces the number of direct interactions the user needs to have with the underlying services.
 
@@ -98,10 +98,6 @@ curl http://localhost:50004/product
 {"title":"The Product Title.","productInventories":5}
 ```
 
-## Class diagram
-
-![Class diagram of the Aggregator Microservices Pattern](./aggregator-service/etc/aggregator-service.png "Aggregator Microservice")
-
 ## Applicability
 
 The Aggregator Microservices Design Pattern is particularly useful in scenarios where a client requires a composite response that is assembled from data provided by multiple microservices. Common use cases include e-commerce applications where product details, inventory, and reviews might be provided by separate services, or in dashboard applications where aggregated data from various services is displayed in a unified view.