docs: Content SEO updates (#2990)

* update yaml frontmatter format

* update abstract document

* update abstract factory

* use the new pattern template

* acyclic visitor seo

* adapter seo

* ambassador seo

* acl seo

* aaa seo

* async method invocation seo

* balking seo

* bridge seo

* builder seo

* business delegate and bytecode seo

* caching seo

* callback seo

* chain seo

* update headings

* circuit breaker seo

* client session + collecting parameter seo

* collection pipeline seo

* combinator SEO

* command seo

* cqrs seo

* commander seo

* component seo

* composite seo

* composite entity seo

* composite view seo

* context object seo

* converter seo

* crtp seo

* currying seo

* dao seo

* data bus seo

* data locality seo

* data mapper seo

* dto seo

* decorator seo

* delegation seo

* di seo

* dirty flag seo

* domain model seo

* double buffer seo

* double checked locking seo

* double dispatch seo

* dynamic proxy seo

* event aggregator seo

* event-based asynchronous seo

* eda seo

* event queue seo

* event sourcing seo

* execute around seo

* extension objects seo

* facade seo

* factory seo

* factory kit seo

* factory method seo

* fanout/fanin seo

* feature toggle seo

* filterer seo

* fluent interface seo

* flux seo

* flyweight seo

* front controller seo

* function composition seo

* game loop seo

* gateway seo

* guarded suspension seo

* half-sync/half-async seo

* health check seo

* hexagonal seo

* identity map seo

* intercepting filter seo

* interpreter seo

* iterator seo

* layers seo

* lazy loading seo

* leader election seo

* leader/followers seo

* lockable object seo

* rename and add seo for marker interface

* master-worker seo

* mediator seo

* memento seo

* metadata mapping seo

* microservice aggregator seo

* api gw seo

* microservices log aggregration seo

* mvc seo

* mvi seo

* mvp seo

* mvvm seo

* monad seo

* monitor seo

* monostate seo

* multiton seo

* mute idiom seo

* naked objects & notification seo

* null object seo

* object mother seo

* object pool seo

* observer seo

* optimistic locking seo

* page controller seo

* page object seo

* parameter object seo

* partial response seo

* pipeline seo

* poison pill seo

* presentation model seo

* private class data seo

* producer-consumer seo

* promise seo

* property seo

* prototype seo

* proxy seo

* queue-based load leveling seo

* reactor seo

* registry seo

* repository seo

* RAII seo

* retry seo

* role object seo

* saga seo

* separated interface seo

* serialized entity seo

* serialized lob seo

* servant seo

* server session seo

* service layer seo

* service locator seo

* service to worker seo

* sharding seo

* single table inheritance seo

* singleton seo

* spatial partition seo

* special case seo

* specification seo

* state seo

* step builder seo

* strangler seo

* strategy seo

* subclass sandbox seo

* table module seo

* template method seo

* throttling seo

* tolerant reader seo

* trampoline seo

* transaction script seo

* twin seo

* type object seo

* unit of work seo

* update method seo

* value object seo

* version number seo

* virtual proxy seo

* visitor seo

* seo enhancements

* seo improvements

* SEO enhancements

* SEO improvements

* SEO additions

* SEO improvements

* more SEO improvements

* rename hexagonal + SEO improvements

* SEO improvements

* more SEO stuff

* SEO improvements

* SEO optimizations

* SEO enhancements

* enchance SEO

* improve SEO

* SEO improvements

* update headers

memento/README.md

@@ -1,14 +1,16 @@
 ---
-title: Memento
+title: "Memento Pattern in Java: Preserving Object State for Undo Operations"
+shortTitle: Memento
+description: "Learn how to implement the Memento design pattern in Java to capture and restore object state without violating encapsulation. Ideal for undo functionality in applications."
 category: Behavioral
 language: en
 tag:
-    - Encapsulation
-    - Gang of Four
-    - Memory management
-    - Object composition
-    - State tracking
-    - Undo
+  - Encapsulation
+  - Gang of Four
+  - Memory management
+  - Object composition
+  - State tracking
+  - Undo
 ---
 
 ## Also known as
@@ -16,15 +18,15 @@ tag:
 * Snapshot
 * Token
 
-## Intent
+## Intent of Memento Design Pattern
 
-Without violating encapsulation, capture and externalize an object's internal state so that the object can be restored to this state later.
+The Memento design pattern in Java allows developers to capture and restore an object's internal state without violating encapsulation.
 
-## Explanation
+## Detailed Explanation of Memento Pattern with Real-World Examples
 
 Real-world example
 
-> Imagine a text editor application that allows users to write and edit documents. The text editor uses the Memento design pattern to implement its undo and redo functionality. Each time a user makes a change to the document, the editor creates a snapshot (memento) of the current state of the document. These snapshots are stored in a history list. When the user clicks the undo button, the editor restores the document to the state saved in the most recent memento. This process allows users to revert to previous versions of their document without exposing or altering the internal data structures of the editor.
+> A text editor application can utilize the Memento design pattern in Java to enable undo and redo functionalities. By capturing the current state of a document as a memento each time a change is made, the application can easily restore the document to any previous state. The snapshots are stored in a history list. When the user clicks the undo button, the editor restores the document to the state saved in the most recent memento. This process allows users to revert to previous versions of their document without exposing or altering the internal data structures of the editor.
 
 In plain words
 
@@ -34,9 +36,9 @@ Wikipedia says
 
 > The memento pattern is a software design pattern that provides the ability to restore an object to its previous state (undo via rollback).
 
-**Programmatic Example**
+## Programmatic Example of Memento Pattern in Java
 
-We are working on an astrology application where we need to analyze star properties over time. We are creating snapshots of star states using the Memento pattern.
+In our astrology application, we use the Memento pattern to capture and restore the state of star objects. Each state is saved as a memento, allowing us to revert to previous states as needed.
 
 Let's first define the types of stars we are capable to handle.
 
@@ -159,19 +161,18 @@ Program output:
 14:09:15.881 [main] INFO com.iluwatar.memento.App -- sun age: 10000000 years mass: 500000 tons
 ```
 
-## Applicability
+## When to Use the Memento Pattern in Java
 
 Use the Memento pattern when
 
-* A snapshot of an object's state must be saved so that it can be restored to that state later, and
-* A direct interface to obtaining the state would expose implementation details and break the object's encapsulation
+* You need to capture an object's state in Java and restore it later without exposing its internal structure. This is crucial for maintaining encapsulation and simplifying the management of object states.
+* A direct interface to obtaining the state would expose implementation details and break the object's encapsulation.
 
-## Known uses
+## Real-World Applications of Memento Pattern in Java
 
-* Java Util Package: Various classes in the Java Util Package, such as java.util.Date and java.util.Calendar, can be reverted to previous states using similar principles, though not implemented directly as the Memento Pattern.
-* Undo mechanisms in software: Text editors and graphic editors often use this pattern to implement undo actions.
+The Memento pattern is used in various Java applications, including the java.util.Date and java.util.Calendar classes, which can revert to previous states. It's also common in text editors and graphic editors for undo mechanisms.
 
-## Consequences
+## Benefits and Trade-offs of Memento Pattern
 
 Benefits:
 
@@ -183,12 +184,12 @@ Trade-offs:
 * Can be expensive in terms of memory if a large number of states are saved.
 * Care must be taken to manage the lifecycle of mementos to avoid memory leaks.
 
-## Related Patterns
+## Related Java Design Patterns
 
 * [Command](https://java-design-patterns.com/patterns/command/): Often used together; commands store state for undoing operations in mementos.
 * [Prototype](https://java-design-patterns.com/patterns/prototype/): Mementos may use prototyping to store the state.
 
-## Credits
+## References and Credits
 
 * [Design Patterns: Elements of Reusable Object-Oriented Software](https://amzn.to/3w0pvKI)
 * [Head First Design Patterns: Building Extensible and Maintainable Object-Oriented Software](https://amzn.to/49NGldq)